build-snapshot

Overview ¶

build-snapshot — populate build/snapshot/ from the current repo state for the M-AGENT-MCP MCP server.

Layout produced:

build/snapshot/
  versioned/<ver>/
    effects.json
    limitations.json
    stdlib_summary.json
    stdlib/<module>.json
    prompts/full.json
    prompts/agent.json    (if a versioned agent prompt exists)
    prompts/devtools.json (if a versioned devtools prompt exists)
    examples_index.json   (if examples_report.json exists)
  versioned/latest -> versioned/<ver>
  unscoped/
    versions_index.json
    benchmarks_index.json
    benchmarks/by_model/<model>.json
    changelog/<ver>.json
    design_docs_index.json
    roadmap.json

All outputs are stable JSON (sorted keys, deterministic iteration order) so the snapshot is byte-identical between runs (modulo built_at).

SCOPE NOTE: design doc M2 specifies SQLite (benchmarks.sqlite + docs.sqlite FTS5). We chose JSON for v1 because the AILANG-side mcp_tools/ modules read from `std/fs` and have no `std/sqlite` builtin yet. SQLite is a clean v2 optimization — either via a new builtin or by registering query-shaped tools as Go-side MCP handlers alongside the AILANG ones.