mcp: thread project arg through run_script and eval_expression

[borisbat]

Summary

• Thread project arg through run_script and eval_expression MCP tools — the last two compile-family outliers that shell out to daslang.exe but never piped -project <file> through. Any script/expression that needed .das_project-bound module resolution silently failed.
• Document the previously-shipped-but-undocumented project arg on live_launch, and add the missing live_commands row to the Live-Reload Control tables in both utils/mcp/README.md and doc/source/reference/utils/mcp.rst.

What changed

File	Change
utils/mcp/tools/run_script.das	Trailing project : string = "" param, validate_project_arg early-return, -project <file> argv injection.
utils/mcp/tools/eval_expression.das	Same shape, plus thread project through the daslib-require rewrite retry path.
utils/mcp/protocol.das	PROJECT_PROP added to both tool schemas; dispatch_tool passes the already-extracted project string.
utils/mcp/test_tools.das	Two new [test] functions mirroring test_compile_check_invalid_project — exercise both validate_project_arg error branches (nonexistent path, wrong extension) for both tools.
utils/mcp/README.md + doc/source/reference/utils/mcp.rst	Tool tables updated; live_commands row inserted.

Out of scope

Removing the daslang-live single-instance OS-level lock and adding a -port CLI flag to unblock concurrent live instances. The MCP-side port arg already exists on every live_* tool — once the executable cooperates, the MCP surface needs minimal further work. Tracking separately.

Test plan

• format_file clean on every changed .das file (all already_formatted).
• utils/lint/main.das clean on all 4 changed .das files (0 issues, 0 errors).
• compile_check on utils/mcp/main.das — entry point compiles, every require still resolves.
• test_tools.das — 287/287 pass, including the two new tests:
  • test_run_script_invalid_project ✓
  • test_eval_expression_invalid_project ✓
• Sphinx build with -W clean (handwritten-RST surface — list-table edits, no toctree changes).
• CI: full matrix (lint, tests, AOT, extended_checks, sphinx).

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR completes MCP “compile-family” parity by threading the optional .das_project-backed project argument through the remaining subprocess-based tools (run_script, eval_expression), ensuring module resolution works consistently when invoking daslang.exe. It also updates MCP documentation tables and adds targeted tests to lock in focused validation errors for invalid project paths.

Changes:

• Add optional project parameter validation and -project <file> argv forwarding to run_script and eval_expression (including eval retry path).
• Extend MCP tool schemas (protocol.das) to expose the project property for both tools and pass it through dispatch.
• Add tests covering both invalid-project error branches for run_script and eval_expression, plus documentation updates (including live_commands row).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
utils/mcp/tools/run_script.das	Validates project and forwards it to daslang.exe via -project.
utils/mcp/tools/eval_expression.das	Adds project validation/forwarding and threads it through the retry/rewrite execution path.
utils/mcp/protocol.das	Adds project to tool schemas for run_script/eval_expression and passes it through dispatch.
utils/mcp/test_tools.das	Adds new unit tests ensuring focused errors for invalid project args in both tools.
utils/mcp/README.md	Documents project for run_script/eval_expression and adds live_commands to the live tools table.
doc/source/reference/utils/mcp.rst	Updates reference tables: documents project for execution tools and live_launch, and adds live_commands.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.