feat: full compile-and-run flow for .rizz files in VS Code

[Copilot]

The extension only provided LSP features; running a .rizz file required manually chaining three shell commands. This adds a one-click end-to-end pipeline: .rizz → rizzoc → output.c → gcc → binary → run.

VS Code extension (vscode-rizz-lsp)

• rizzLsp.runFile command — registered as a $(play) button in editor/title/run, visible only for .rizz files. Saves the file, compiles, and runs in a dedicated integrated terminal.
• getRizzocCommand() — resolves the compiler in priority order: rizzLsp.compiler.command setting → _build/default/src/bin/main.exe (local dune build) → opam exec -- dune exec rizzoc --.
• getRuntimePath() — resolves C headers: bundled runtime/ dir (VSIX install) → ../../src/runtime (dev/repo mode).
• Shell injection guard — rizzLsp.compiler.cc is validated against an allowlist before use in the terminal command.
• Two new settings: rizzLsp.compiler.command (rizzoc path, auto-detected if empty) and rizzLsp.compiler.cc (C compiler, default gcc).

Runtime bundling

• scripts/copy-runtime.js — copies src/runtime/*.h into vscode-rizz-lsp/runtime/ and removes stale headers from previous builds.
• vscode:prepublish now runs copy:runtime first, so the VSIX is self-contained and works without the full repo structure.
• vscode-rizz-lsp/out/ and vscode-rizz-lsp/runtime/ added to .gitignore (generated artefacts).

Other

• Root npm run transpile / npm run rizz fixed to use -o output / ./output (was relying on a.out).
• .vscode/tasks.json gets a rizz: run file task.
• README documents the full flow, the run button, and the new settings.

Original prompt

yes, please start the implimentation of the full flow

[Chronological Review: The conversation began with the user inquiring about bundling the runtime inside an extension or installing it from GitHub as an artifact. The user then requested to start the implementation of the full flow, indicating a desire to move forward with development.]

[Intent Mapping:

1. "would it be possible to somehow bundle the runtime inside the extension or have it install it from github if we published it as an artifact on a release?" - User is exploring options for runtime distribution.
2. "yes, please start the implementation of the full flow" - User is requesting the initiation of the implementation process.]

[Technical Inventory:

• Repository: RizzoMemory
• Current branch: main
• User's current file: d:\school\RizzoMemory\examples\match.rizz
• Focus on bundling runtime or installation from GitHub.]

[Code Archaeology: No specific code changes or files were discussed in detail, but the user's focus on the match.rizz file suggests it may be relevant to the implementation.]

[Progress Assessment: The user has expressed a clear intent to implement a feature related to runtime distribution but has not yet begun the actual coding process.]

[Context Validation: The user is looking to implement a full flow for runtime distribution, either by bundling it or installing it from GitHub, and has indicated readiness to start this implementation.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested to start the implementation of the full flow.
• Tool Results Summary: No specific tool results were generated as the conversation focused on user requests rather than tool execution.
• Pre-Summary State: The agent was preparing to begin the implementation process as requested by the user.
• Operation Context: The commands executed were directly related to the user's goal of implementing a runtime distribution method.]

1. Conversation Overview: - Primary Objectives: - "would it be possible to somehow bundle the runtime inside the extension or have it install it from github if we published it as an artifact on a release?" - Exploring runtime distribution options. - "yes, please start the implementation of the full flow" - Requesting to initiate the implementation process. - Session Context: The conversation has focused on the user's desire to implement a feature related to runtime distribution, with a clear transition from inquiry to action. - User Intent Evolution: The user moved from exploring options to actively requesting the start of the implementation.

2. Technical Foundation:

• Repository: RizzoMemory
• Current branch: main
• User's current file: d:\school\RizzoMemory\examples\match.rizz

3. Codebase Status:

• File Name: match.rizz
• Purpose: Likely related to the implementation of the runtime distribution feature.
• Current State: No specific modifications discussed yet.
• Key Code Segments: Not specified in the conversation.
• Dependencies: Not detailed, but likely related to the overall project structure.

4. Problem Resolution:

• Issues Encountered: None explicitly mentioned.
• Solutions Implemented: None yet, as the implementation has not started.
• Debugging Context: No ongoing troubleshooting efforts noted.
• Lessons Learned: No insights or patterns have been discussed yet.

5. Progress Tracking:

• Completed Tasks: None completed yet.
• Partially Complete Work: The user has requested to start the implementation, indicating readiness to proceed.
• Validated Outcomes: None confirmed through testing.

6. Active Work State:

• Current Focus: The user is focused on implementing the full flow for runtime distribution.
• Recent Context: The user has expressed a desire to bundle the runtime or install it from GitHub.
• Working Code: No specific code snippets have been discussed recently.
• Immediate Context: The user is ready to begin the implementation process.

7. Recent Operations:

• Last Agent Commands: User requested to start the implementation of the full flow.
• Tool Results Summary: No specific tool results were generated as the conversation focused on user requests.
• Pre-Summary State: The agent was preparing to begin the implementation process.
• Operation Context: The commands executed were directly related to the user's goal of implementing a runtime distribution method.

8. Continuation Plan:

• Pending Task: Start the implementation of the full flow for runtime distribution.
• Next Action: Immediate next step is to begin coding the requested implementation as per the user's directive.

Created from VS Code.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.