atomadic-forge 0.5.1__tar.gz → 0.5.3__tar.gz

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/CHANGELOG.md

@@ -1,5 +1,66 @@
 # Changelog
 
+## 0.5.3 - Documentation metadata sync
+
+Small follow-up to `0.5.2` so the published package description and
+current-facing docs no longer advertise stale `0.3.x` version strings,
+old test counts, or the pre-`0.5.2` MCP tool count.
+
+### Fixed
+
+- README install and contributor snippets now show the current Forge
+  version family and `937 passed, 2 skipped`.
+- Current ecosystem positioning now reflects the `0.5.3` PyPI line and
+  23-tool MCP surface.
+- First-run and VS Code extension docs now reference the current MCP
+  surface/version expectations.
+
+---
+
+## 0.5.2 - Agent ergonomics and language-aware guidance
+
+Implements the first round of quality-of-life improvements from the
+Forge agent review. This release makes Forge friendlier when an agent
+uses it on JavaScript repos, documentation/research patches, or live
+MCP connections.
+
+### Added
+
+- `forge mcp doctor` smoke-tests MCP stdio with framed `initialize`,
+  `tools/list`, and `shutdown` requests. It reports version, project
+  root, tool count, framed-stdio status, server exit code, and a
+  recovery hint.
+- `tools/list` entries now include a `cli_command` fallback so agents
+  can switch from MCP to shell without guessing command names.
+- Shared validation heuristics now detect `package.json` scripts,
+  JS/TS tests, tier roots, and release-gate commands.
+
+### Improved
+
+- `context-pack` prefers `npm run verify` / `npm test` for JavaScript
+  projects and derives `forge wire` gates from real tier roots.
+- `preflight` recognizes non-code artifacts such as `docs/`,
+  `research/`, `.github/`, and `cognition/guides/` as valid project
+  memory instead of misplaced source.
+- `select-tests` discovers JS/TS test files and avoids mirror pytest
+  requirements for documentation-only changes.
+- `score-patch` no longer treats docs/research-only diffs as code
+  changes without tests, and emits language-aware validation commands
+  when a project root is provided.
+- `compose-tools verify_patch` now maps to
+  `score_patch -> select_tests -> wire -> certify`.
+- Hidden worktrees, experiment directories, build output, and
+  `node_modules` are skipped when deriving release-gate wire roots.
+
+### Tests
+
+- Added regression tests for JavaScript validation selection,
+  non-code artifact preflight, docs-only patch scoring, exact
+  `verify_patch` recipe matching, MCP CLI fallback metadata, and
+  `forge mcp doctor`.
+
+---
+
 ## 0.5.1 — MCP stdio framing compatibility
 
 Fixes `forge mcp serve` for MCP hosts that use LSP-style

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: atomadic-forge
-Version: 0.5.1
+Version: 0.5.3
 Summary: Atomadic Forge — absorb, enforce, emerge. Polyglot (Python + JavaScript/TypeScript) architecture guardian for AI-generated code.
 Author: Atomadic
 License-Expression: BUSL-1.1
@@ -185,7 +185,7 @@ Each tier is a layer of **verified building blocks**. Higher tiers never invent
 
 ```bash
 pip install atomadic-forge
-forge --version   # atomadic-forge 0.3.2
+forge --version   # atomadic-forge 0.5.3
 forge doctor      # environment check
 ```
 
@@ -198,7 +198,7 @@ generate).
 ```bash
 git clone https://github.com/atomadictech/atomadic-forge && cd atomadic-forge
 pip install -e ".[dev]"
-python -m pytest               # 841 passing, 2 skipped
+python -m pytest               # 937 passed, 2 skipped
 ```
 
 ## AI Agent integration (MCP)
@@ -216,14 +216,21 @@ Forge ships a **Model Context Protocol server** — add it to Cursor, Claude Cod
 }
 ```
 
-**21 tools exposed:** `recon` · `wire` · `certify` · `enforce` · `audit_list` · `auto_plan` · `auto_step` · `auto_apply` · `context_pack` · `preflight_change` · `score_patch` · `select_tests` · `rollback_plan` · `explain_repo` · `adapt_plan` · `compose_tools` · `load_policy` · `why_did_this_change` · `what_failed_last_time` · `list_recipes` · `get_recipe`
+**23 tools exposed:** `recon` · `wire` · `certify` · `enforce` · `audit_list` · `auto_plan` · `auto_step` · `auto_apply` · `context_pack` · `preflight_change` · `score_patch` · `select_tests` · `rollback_plan` · `explain_repo` · `adapt_plan` · `compose_tools` · `load_policy` · `why_did_this_change` · `what_failed_last_time` · `list_recipes` · `get_recipe` · `trust_gate_response` · `exported_api_check`
 
 **5 resources:** Receipt schema · formalization docs · lineage chain · blocker summary · verdicts
 
 ```bash
 forge mcp serve --help   # full tool + resource listing with examples
+forge mcp doctor --project . --json
 ```
 
+As of `0.5.2`, `tools/list` includes a `cli_command` fallback for
+each MCP tool. `context-pack`, `preflight`, `select-tests`, and
+`score-patch` also use language-aware validation commands so
+JavaScript projects get `npm run verify` / `npm test` guidance and
+documentation/research paths are treated as non-code project memory.
+
 ### Subscription required for `forge mcp serve`
 
 Every `tools/call` against the MCP server is gated behind a paid Forge
@@ -370,7 +377,7 @@ Forge waits before returning a clear provider error.
 
 | Command | Purpose |
 |---------|---------|
-| `forge mcp serve` | Stdio JSON-RPC MCP server — 21 tools for Cursor / Claude Code / Aider / Devin. |
+| `forge mcp serve` | Stdio JSON-RPC MCP server — 23 tools for Cursor / Claude Code / Aider / Devin. |
 | `forge plan / plan-list / plan-show / plan-step / plan-apply` | Agent plan persistence and step-by-step apply. |
 | `forge iterate` | LLM loop: intent → code → absorb → wire → score → iterate. Single shot. |
 | `forge evolve` | Recursive improvement: N rounds, catalog grows each round. |
@@ -442,7 +449,7 @@ Forge ships with named limits. No overpromise.
 | Product | What it is | Status |
 |---------|------------|--------|
 | **AAAA-Nexus** | Trust/safety/payments substrate for autonomous agents | Live at [atomadic.tech](https://atomadic.tech) |
-| **Atomadic Forge** | Absorb-and-emerge engine for developers (this repo) | **0.3.2** — on PyPI, 841 tests, 100/100, MCP server, desktop GUI |
+| **Atomadic Forge** | Absorb-and-emerge engine for developers (this repo) | **0.5.3** — on PyPI, 937 tests, 100/100, 23-tool MCP server, desktop GUI |
 | **Atomadic Assistant** | Sovereign AI assistant with cognitive loop on Cloudflare | In development |
 
 ## License
@@ -470,7 +477,7 @@ Apache 2.0.
 **Forge itself is monadic.** Every source file belongs to one tier. The repo is a worked example:
 
 ```bash
-python -m pytest                     # 841 passing, 2 skipped
+python -m pytest                     # 937 passed, 2 skipped
 forge doctor                         # Environment check
 forge wire src/atomadic_forge        # Scan for violations (PASS)
 forge certify . --fail-under 100     # Score and gate the repo (100/100)
@@ -492,7 +499,7 @@ forge commandsmith smoke             # Smoke-test all 36+ registered verbs
 - ✓ **100/100 certify** — forge scores itself on every CI run
 - ✓ **0 wire violations** — forge passes its own import-law scan
 - ✓ **On PyPI** — `pip install atomadic-forge`
-- ✓ **MCP server** — 21 tools, 5 resources; works with Cursor, Claude Code, Aider, Devin
+- ✓ **MCP server** — 23 tools, 5 resources; works with Cursor, Claude Code, Aider, Devin
 - ✓ **Desktop GUI** — Forge Studio (Tauri 2 + React)
 - ✓ **Ed25519 signing** — `forge certify --local-sign`
 - ✓ **CycloneDX SBOM** — `forge sbom`

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/README.md

@@ -153,7 +153,7 @@ Each tier is a layer of **verified building blocks**. Higher tiers never invent
 
 ```bash
 pip install atomadic-forge
-forge --version   # atomadic-forge 0.3.2
+forge --version   # atomadic-forge 0.5.3
 forge doctor      # environment check
 ```
 
@@ -166,7 +166,7 @@ generate).
 ```bash
 git clone https://github.com/atomadictech/atomadic-forge && cd atomadic-forge
 pip install -e ".[dev]"
-python -m pytest               # 841 passing, 2 skipped
+python -m pytest               # 937 passed, 2 skipped
 ```
 
 ## AI Agent integration (MCP)
@@ -184,14 +184,21 @@ Forge ships a **Model Context Protocol server** — add it to Cursor, Claude Cod
 }
 ```
 
-**21 tools exposed:** `recon` · `wire` · `certify` · `enforce` · `audit_list` · `auto_plan` · `auto_step` · `auto_apply` · `context_pack` · `preflight_change` · `score_patch` · `select_tests` · `rollback_plan` · `explain_repo` · `adapt_plan` · `compose_tools` · `load_policy` · `why_did_this_change` · `what_failed_last_time` · `list_recipes` · `get_recipe`
+**23 tools exposed:** `recon` · `wire` · `certify` · `enforce` · `audit_list` · `auto_plan` · `auto_step` · `auto_apply` · `context_pack` · `preflight_change` · `score_patch` · `select_tests` · `rollback_plan` · `explain_repo` · `adapt_plan` · `compose_tools` · `load_policy` · `why_did_this_change` · `what_failed_last_time` · `list_recipes` · `get_recipe` · `trust_gate_response` · `exported_api_check`
 
 **5 resources:** Receipt schema · formalization docs · lineage chain · blocker summary · verdicts
 
 ```bash
 forge mcp serve --help   # full tool + resource listing with examples
+forge mcp doctor --project . --json
 ```
 
+As of `0.5.2`, `tools/list` includes a `cli_command` fallback for
+each MCP tool. `context-pack`, `preflight`, `select-tests`, and
+`score-patch` also use language-aware validation commands so
+JavaScript projects get `npm run verify` / `npm test` guidance and
+documentation/research paths are treated as non-code project memory.
+
 ### Subscription required for `forge mcp serve`
 
 Every `tools/call` against the MCP server is gated behind a paid Forge
@@ -338,7 +345,7 @@ Forge waits before returning a clear provider error.
 
 | Command | Purpose |
 |---------|---------|
-| `forge mcp serve` | Stdio JSON-RPC MCP server — 21 tools for Cursor / Claude Code / Aider / Devin. |
+| `forge mcp serve` | Stdio JSON-RPC MCP server — 23 tools for Cursor / Claude Code / Aider / Devin. |
 | `forge plan / plan-list / plan-show / plan-step / plan-apply` | Agent plan persistence and step-by-step apply. |
 | `forge iterate` | LLM loop: intent → code → absorb → wire → score → iterate. Single shot. |
 | `forge evolve` | Recursive improvement: N rounds, catalog grows each round. |
@@ -410,7 +417,7 @@ Forge ships with named limits. No overpromise.
 | Product | What it is | Status |
 |---------|------------|--------|
 | **AAAA-Nexus** | Trust/safety/payments substrate for autonomous agents | Live at [atomadic.tech](https://atomadic.tech) |
-| **Atomadic Forge** | Absorb-and-emerge engine for developers (this repo) | **0.3.2** — on PyPI, 841 tests, 100/100, MCP server, desktop GUI |
+| **Atomadic Forge** | Absorb-and-emerge engine for developers (this repo) | **0.5.3** — on PyPI, 937 tests, 100/100, 23-tool MCP server, desktop GUI |
 | **Atomadic Assistant** | Sovereign AI assistant with cognitive loop on Cloudflare | In development |
 
 ## License
@@ -438,7 +445,7 @@ Apache 2.0.
 **Forge itself is monadic.** Every source file belongs to one tier. The repo is a worked example:
 
 ```bash
-python -m pytest                     # 841 passing, 2 skipped
+python -m pytest                     # 937 passed, 2 skipped
 forge doctor                         # Environment check
 forge wire src/atomadic_forge        # Scan for violations (PASS)
 forge certify . --fail-under 100     # Score and gate the repo (100/100)
@@ -460,7 +467,7 @@ forge commandsmith smoke             # Smoke-test all 36+ registered verbs
 - ✓ **100/100 certify** — forge scores itself on every CI run
 - ✓ **0 wire violations** — forge passes its own import-law scan
 - ✓ **On PyPI** — `pip install atomadic-forge`
-- ✓ **MCP server** — 21 tools, 5 resources; works with Cursor, Claude Code, Aider, Devin
+- ✓ **MCP server** — 23 tools, 5 resources; works with Cursor, Claude Code, Aider, Devin
 - ✓ **Desktop GUI** — Forge Studio (Tauri 2 + React)
 - ✓ **Ed25519 signing** — `forge certify --local-sign`
 - ✓ **CycloneDX SBOM** — `forge sbom`

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/docs/05-faq.md

@@ -429,27 +429,31 @@ config:
 }
 ```
 
-Once registered, the agent gets **21 tools** + **5 resources** (the
-full Codex-1..5 surface as of `v0.3.0`). The 21 tools group into
+Once registered, the agent gets **23 tools** + **5 resources** (the
+full Codex-1..5 surface plus response/API trust gates). The 23 tools group into
 *inventory* (`recon` / `wire` / `certify` / `enforce` / `audit_list` /
 `agent_summary`), *action loop* (`auto_plan` / `auto_step` /
 `auto_apply`), and *Copilot's Copilot* (`context_pack` /
 `preflight_change` / `score_patch` / `select_tests` / `rollback_plan` /
 `explain_repo` / `adapt_plan` / `compose_tools` / `load_policy` /
 `why_did_this_change` / `what_failed_last_time` / `list_recipes` /
-`get_recipe`). See the full **[Agents Guide](AGENTS_GUIDE.md)** for
+`get_recipe` / `trust_gate_response` / `exported_api_check`). See the full **[Agents Guide](AGENTS_GUIDE.md)** for
 integration patterns, the agent-friendly `agent_summary` /
 `context_pack` tools, the Forge Receipt schema agents should
 consume, F-code routing for mechanical fixes, the proposal-engine
 flow, and best practices.
 
+For MCP troubleshooting, run `forge mcp doctor --project . --json`.
+As of `0.5.2`, `tools/list` also includes a `cli_command` fallback for
+each MCP tool, and validation hints are language-aware.
+
 ### What's the difference between AGENTS.md and the Agents Guide?
 
 - **`AGENTS.md`** at the repo root is for agents *building* Forge —
   the dev contract: tier discipline, F-code namespace, schema
   versioning, branch hygiene, the verification lane.
 - **`docs/AGENTS_GUIDE.md`** is for agents *using* Forge — Cursor /
-  Claude Code / Aider / etc. integrating via MCP, calling the 21
+  Claude Code / Aider / etc. integrating via MCP, calling the 23
   tools, consuming Receipts, running `preflight_change` /
   `score_patch` guardrails, applying mechanical fixes via `enforce`.
 

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/docs/AGENTS_GUIDE.md

@@ -42,26 +42,23 @@ Claude Code / Aider / your own):
 }
 ```
 
-Once registered, the agent gets **21 tools** + **5 resources** in its
-tool list (the full Codex-1..5 surface, shipped at v0.3.0). No
+Once registered, the agent gets **23 tools** + **5 resources** in its
+tool list. No
 additional setup.
 
 Smoke test that the server is reachable:
 
 ```bash
-printf '%s\n%s\n%s\n' \
-  '{"jsonrpc":"2.0","id":1,"method":"initialize"}' \
-  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \
-  '{"jsonrpc":"2.0","id":3,"method":"shutdown"}' \
-  | forge mcp serve --project .
+forge mcp doctor --project . --json
 ```
 
-→ returns `serverInfo`, the 21 tool schemas, and `{}` for shutdown.
+Returns Forge version, tool count, framed-stdio status, and the next
+recovery command if the MCP host needs a restart.
 Or against the installed CLI:
 
 ```bash
 $ forge --version
-atomadic-forge 0.3.0
+atomadic-forge 0.5.3
 ```
 
 The `--version` flag (and `-V`) is the canonical "Forge is wired in
@@ -69,7 +66,7 @@ correctly" smoke check — pin it in your setup scripts.
 
 ---
 
-## The 21 MCP tools — by phase of an agent's lifecycle
+## The 23 MCP tools — by phase of an agent's lifecycle
 
 | Inventory (read-only) | Action loop | Copilot's Copilot |
 |---|---|---|
@@ -86,6 +83,8 @@ correctly" smoke check — pin it in your setup scripts.
 |  |  | `what_failed_last_time` |
 |  |  | `list_recipes` |
 |  |  | `get_recipe` |
+|  |  | `trust_gate_response` |
+|  |  | `exported_api_check` |
 
 **Inventory tools — read-only state queries.** Cheap; safe to call
 in a loop:
@@ -126,6 +125,12 @@ always-on senior engineer beside the coding agent:
 | **`what_failed_last_time`** ← *Codex-5* | `what_failed/v1` — historical failures scoped to an area | "What went wrong here before — so I don't repeat it?" |
 | **`list_recipes`** ← *Codex-5* | catalogue of golden-path recipes | First-orientation. Pre-baked: `release_hardening`, `add_cli_command`, `fix_wire_violation`, `add_feature`, `publish_mcp`. |
 | **`get_recipe`** ← *Codex-5* | `recipe/v1` — step-by-step plan | "Walk me through `release_hardening` step by step." |
+| **`trust_gate_response`** | `trust_gate/v1` — response hallucination checks | Before sending generated implementation notes or code snippets back to a human. |
+| **`exported_api_check`** | `exported_api_check/v1` — docstring/API promise verification | Before publishing generated modules that claim public functions in docs. |
+
+Every `tools/list` entry includes a `cli_command` fallback. If the MCP
+transport drops, use that command shape directly in the shell while
+you restart the editor or MCP host.
 
 (Plus four `plan_list` / `plan_show` / `plan_step` / `plan_apply`
 verbs from Codex-3 — same 1:1 mapping to the CLI verbs of the same
@@ -139,13 +144,20 @@ name.)
    orientation; `preflight_change` *before* every write;
    `score_patch` *after* drafting the diff. Forge is the always-on
    senior engineer reviewing each step.
-3. **Proposal-engine (full 21 tools)**: `auto_plan` for direction,
+3. **Proposal-engine (full 23 tools)**: `auto_plan` for direction,
    `adapt_plan` for capability-aware filtering, `auto_apply` to
    execute, `enforce` for mechanical fixes, `rollback_plan` if
    anything regresses, `why_did_this_change` /
    `what_failed_last_time` for historical context. Forge drives;
    the agent supplies LLM context where Forge can't mechanize.
 
+`context_pack`, `preflight_change`, `select_tests`, and `score_patch`
+are language-aware as of `0.5.2`: JavaScript projects with
+`package.json` scripts get `npm run verify` / `npm test`, tier wire
+commands are derived from real tier roots, and documentation paths
+such as `docs/`, `research/`, `.github/`, and `cognition/guides/` are
+treated as non-code artifacts rather than misplaced source.
+
 ---
 
 ## The 5 MCP resources
@@ -356,7 +368,7 @@ Forge's normative answer; only the *attestation chain* is missing.
 | Symptom | Likely cause | Fix |
 |---|---|---|
 | Tools list returns 0 tools | MCP client didn't pass `--project .` | Check args in MCP config |
-| Tools list returns < 21 (e.g. 6 or 10) | Old `forge` install (pre-v0.3.0) | `pip install -U atomadic-forge` (or `pip install -e .` from the repo). Pin `forge --version >= 0.3.0`. |
+| Tools list returns < 23 (e.g. 21 or 10) | Old `forge` install | `pip install -U atomadic-forge` (or `pip install -e .` from the repo). Pin `forge --version >= 0.5.3`. |
 | `wire` says PASS but agent still hits import errors | Agent is running tests in a different working directory | `--project` should match the test cwd |
 | `certify` returns score 90 instead of 100 | Project has no `.github/workflows/` and no `CHANGELOG.md` (operational axis is 0) | Add either; both are 5pts |
 | Receipt's `signatures` is null | `AAAA_NEXUS_API_KEY` not set, or AAAA-Nexus endpoint not yet shipped | Soft-fail behavior — Receipt is still valid for local use |
@@ -423,7 +435,7 @@ control plane around any coding agent**:
   true` when the agent's intent fans out across more than 8 files
   (configurable). CLI exits 1 in that case so a pre-commit hook can
   block.
-- **`score_patch`** (MCP-only: `score_patch`) — diff-level risk
+- **`score_patch`** (CLI: `forge score-patch`, MCP: `score_patch`) — diff-level risk
   preview. Given a unified-diff string, surfaces architectural_risk
   (new upward imports), public_api_risk (`__init__.py` touched),
   release_risk (pyproject / version / CHANGELOG / LICENSE), test_risk

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/docs/COMMANDS.md

@@ -1,6 +1,6 @@
 # Atomadic Forge — Command Reference
 
-All verbs available in the `forge` CLI as of 0.2.2.
+All verbs available in the `forge` CLI as of 0.5.3.
 
 ## Pipeline / absorption
 
@@ -206,7 +206,7 @@ clean shutdown. The soft-fail contract from `receipt_signer.py`
 applies — every tool gracefully degrades when an upstream (e.g.,
 AAAA-Nexus signing) is unreachable.
 
-**The 21 MCP tools, grouped by phase of an agent's lifecycle:**
+**The 23 MCP tools, grouped by phase of an agent's lifecycle:**
 
 | Inventory (read-only) | Action loop | Copilot's Copilot |
 |---|---|---|
@@ -223,11 +223,28 @@ AAAA-Nexus signing) is unreachable.
 |  |  | `what_failed_last_time` |
 |  |  | `list_recipes` |
 |  |  | `get_recipe` |
+|  |  | `trust_gate_response` |
+|  |  | `exported_api_check` |
 
 **5 MCP resources:** `forge://docs/receipt`, `forge://docs/formalization`,
 `forge://lineage/chain`, `forge://schema/receipt`,
 `forge://summary/blockers`.
 
+### `forge mcp doctor`
+
+Agent-facing MCP health check. It starts the local stdio server in
+memory, sends framed `initialize`, `tools/list`, and `shutdown`
+requests, and reports whether the transport path is healthy.
+
+```bash
+forge mcp doctor --project . --json
+```
+
+Returns `atomadic-forge.mcp_doctor/v1` with Forge version, project
+root, tool count, framed-stdio status, server exit code, and a
+`next_command`. If this passes but your editor's live MCP tools fail,
+restart the MCP host/editor so it respawns the server.
+
 What this unlocks per Golden Path Lane C: the Forge Receipt JSON
 becomes consumable by every major coding-agent platform via the same
 schema as `forge certify --emit-receipt` — *one Receipt across
@@ -317,10 +334,11 @@ a repo. Wraps scout + wire + certify and adds:
 - `architecture_law` — pinned 5-tier law text (so the agent doesn't
   have to look it up).
 - `tier_map`, `blockers_summary`, `best_next_action`.
-- `test_commands` — detected from pyproject / tox.ini / package.json /
-  Cargo.toml / Makefile.
-- `release_gate` — the canonical `ruff && pytest && wire && certify
-  ≥ 75` recipe.
+- `test_commands` — language-aware detection from `package.json`
+  scripts, pyproject / tox.ini, Cargo.toml, or Makefile.
+- `release_gate` — language-aware validation: JS repos prefer
+  `npm run verify` / `npm test`, Python repos get pytest/ruff, and
+  `forge wire` targets real tier roots instead of hard-coded `src`.
 - `risky_files`, `recent_lineage`, `pinned_resources`.
 
 ```bash
@@ -339,10 +357,13 @@ write, emits `atomadic-forge.preflight/v1` with:
 - `forbidden_imports` — tiers above this file's tier (read-only, but
   the agent should treat as hard rules before drafting).
 - `likely_tests` — mirror-style: `tests/test_<stem>.py`,
-  `<stem>_test.py`, etc.
+  `<stem>_test.py`, JS/TS `*.test.*` / `*.spec.*`, etc.
 - `siblings_to_read` — first 5 `.py` siblings in the same dir.
 - Overall `write_scope_too_broad` flag (default threshold = 8 files;
   override with `--scope-threshold N`).
+- Non-code artifacts under `docs/`, `research/`, `.github/`,
+  `cognition/guides/`, and similar paths are accepted as project
+  memory with no tier warning.
 
 ```bash
 forge preflight 'Add a parser helper' \
@@ -353,17 +374,22 @@ Exits **1** when `write_scope_too_broad` is true — designed to be
 called from a pre-commit hook or an agent's tool-use loop. Add
 `--json` for machine-readable output.
 
-(`score_patch` — diff-scoring of a candidate unified-diff — is
-intentionally MCP-only. Diff strings are awkward as positional CLI
-args; agents pipe the diff through the `score_patch` MCP tool
-instead.)
+`score_patch` also has a CLI front door:
+
+```bash
+git diff | forge score-patch --project-root .
+forge score-patch --file patch.diff --project-root .
+```
+
+When a project root is supplied, its suggested validation commands use
+the same language-aware gate as `context-pack`.
 
-### Copilot's Copilot — the rest of Codex-5 (MCP-only)
+### Copilot's Copilot — the rest of Codex-5
 
 The 8 modules added in `276a092` (Codex's items #5–#12) ship as MCP
-tools rather than CLI verbs. Agents consume them through the running
-`forge mcp serve` over stdio JSON-RPC. Each returns a versioned JSON
-schema agents should treat as a contract:
+tools and CLI verbs. Agents can consume them through `forge mcp serve`
+or use the `cli_command` fallback exposed by `tools/list`. Each returns
+a versioned JSON schema agents should treat as a contract:
 
 | MCP tool | Schema | What it answers |
 |---|---|---|
@@ -376,6 +402,8 @@ schema agents should treat as a contract:
 | `adapt_plan` | `atomadic-forge.agent_plan_adapted/v1` | Filter an `agent_plan/v1` for a specific agent's capability set (`edit_files`, `run_commands`, `network`, `review`, `delegate`). Each card gets `recommended_handling`: `apply` / `delegate` / `ask_human` / `report_only`. |
 | `compose_tools` | n/a (returns ordered tool list) | Goal-keyword → ordered tool sequence. Pre-baked recipes: `orient`, `release_check`, `fix_violation`, `before_edit`, `verify_patch`. |
 | `list_recipes` / `get_recipe` | `atomadic-forge.recipe/v1` | Golden-path playbooks: `release_hardening`, `add_cli_command`, `fix_wire_violation`, `add_feature`, `publish_mcp`. Each recipe is a step-by-step plan agents can `get_recipe` and execute. |
+| `trust_gate_response` | `trust_gate/v1` | Check generated responses for unresolved imports, syntax errors, stub-pattern code, false capability claims, and placeholder URLs. |
+| `exported_api_check` | `exported_api_check/v1` | Verify that docstring-promised public APIs resolve to actual top-level definitions. |
 
 These complete Codex's 12-item Copilot's Copilot enumeration — items
 #5–#12. Items #1–#3 are the Codex-4 hero primitives
@@ -391,7 +419,7 @@ Prints the installed Forge version and exits 0. Hardened in v0.3.0
 
 ```bash
 $ forge --version
-atomadic-forge 0.3.0
+atomadic-forge 0.5.3
 ```
 
 ### `.forge` sidecars — Lane D W8

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/docs/FIRST_10_MINUTES.md

@@ -185,7 +185,7 @@ You now know enough to use Forge productively. For specific topics:
 - [tutorials/](tutorials/) — quickstart tutorials and the JS / TS path.
 - **[AGENTS_GUIDE.md](AGENTS_GUIDE.md)** — using Forge from a coding
   agent (Cursor / Claude Code / Aider / Devin / Copilot / Codex) via
-  the built-in MCP server. One config snippet, **21 tools**, 5
+  the built-in MCP server. One config snippet, **23 tools**, 5
   resources. The fastest way to put Forge in front of every PR your
   team's agents touch.
 - [MULTI_REPO.md](MULTI_REPO.md) — absorbing more than one repo at once.

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "atomadic-forge"
-version = "0.5.1"
+version = "0.5.3"
 description = "Atomadic Forge — absorb, enforce, emerge. Polyglot (Python + JavaScript/TypeScript) architecture guardian for AI-generated code."
 readme = "README.md"
 requires-python = ">=3.10"

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/src/atomadic_forge/__init__.py

@@ -9,4 +9,4 @@ Public version surface only — every symbol lives in its tier package and
 is re-exported lazily by the CLI.
 """
 
-__version__ = "0.5.1"
+__version__ = "0.5.3"

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/src/atomadic_forge/a1_at_functions/agent_context_pack.py

@@ -20,6 +20,7 @@ from typing import TypedDict
 
 from .agent_summary import summarize_blockers
 from .lineage_reader import read_lineage
+from .validation_commands import detect_test_commands, release_gate_commands
 
 SCHEMA_VERSION_CONTEXT_PACK_V1 = "atomadic-forge.context_pack/v1"
 
@@ -86,40 +87,12 @@ def _read_repo_purpose(project_root: Path) -> str:
 
 
 def _detect_test_commands(project_root: Path) -> list[str]:
-    cmds: list[str] = []
-    if (project_root / "pyproject.toml").exists():
-        cmds.append("python -m pytest")
-    if (project_root / "tox.ini").exists():
-        cmds.append("tox")
-    if (project_root / "package.json").exists():
-        cmds.append("npm test")
-    if (project_root / "Cargo.toml").exists():
-        cmds.append("cargo test")
-    if (project_root / "Makefile").exists():
-        # Look for a 'test' target.
-        try:
-            mk = (project_root / "Makefile").read_text(
-                encoding="utf-8", errors="replace")
-            if re.search(r"^test:", mk, re.MULTILINE):
-                cmds.append("make test")
-        except OSError:
-            pass
-    if not cmds:
-        cmds.append("# no test runner detected — add tests/ + pytest")
-    return cmds
+    return detect_test_commands(project_root)
 
 
 def _release_gate(project_root: Path) -> list[str]:
     """Heuristic release gate: lint + tests + wire + certify ≥ 75."""
-    gate: list[str] = []
-    if (project_root / "pyproject.toml").exists():
-        gate.append("python -m ruff check .")
-    gate.extend([
-        "python -m pytest",
-        "forge wire src --fail-on-violations",
-        "forge certify . --fail-under 75",
-    ])
-    return gate
+    return release_gate_commands(project_root)
 
 
 def _risky_files(lineage: list[dict], top_n: int = 10) -> list[dict]:

{atomadic_forge-0.5.1 → atomadic_forge-0.5.3}/src/atomadic_forge/a1_at_functions/mcp_protocol.py

@@ -884,6 +884,32 @@ TOOLS: dict[str, dict[str, Any]] = {
     },
 }
 
+_CLI_FALLBACKS: dict[str, str] = {
+    "recon": "forge recon <repo> --json",
+    "wire": "forge wire <tier-root> --json",
+    "certify": "forge certify <project-root> --json",
+    "enforce": "forge enforce <tier-root>",
+    "audit_list": "forge audit list --json",
+    "auto_plan": "forge plan <repo> --json",
+    "auto_step": "forge plan-step <plan-id> <card-id> --project <repo>",
+    "auto_apply": "forge plan-apply <plan-id> --project <repo>",
+    "context_pack": "forge context-pack <project-root> --json",
+    "preflight_change": "forge preflight <intent> <file...> --project <repo> --json",
+    "score_patch": "git diff | forge score-patch --project-root <repo>",
+    "select_tests": "forge select-tests --file <path> --project-root <repo> <intent>",
+    "rollback_plan": "forge rollback-plan --file <path> --project-root <repo>",
+    "explain_repo": "forge explain-repo <project-root>",
+    "adapt_plan": "forge adapt-plan --file <plan.json>",
+    "compose_tools": "forge compose-tools <goal>",
+    "load_policy": "forge load-policy <project-root>",
+    "why_did_this_change": "forge why-did-this-change <file> --project-root <repo>",
+    "what_failed_last_time": "forge what-failed-last-time <area> --project-root <repo>",
+    "list_recipes": "forge recipes --json",
+    "get_recipe": "forge recipes <name> --json",
+    "trust_gate_response": "MCP-only: trust_gate_response",
+    "exported_api_check": "MCP-only: exported_api_check",
+}
+
 
 # --- Resource registry ---------------------------------------------------
 
@@ -1093,7 +1119,8 @@ def _list_tools() -> dict[str, Any]:
         "tools": [
             {"name": t["name"],
              "description": t["description"],
-             "inputSchema": t["inputSchema"]}
+             "inputSchema": t["inputSchema"],
+             "cli_command": _CLI_FALLBACKS.get(t["name"], "")}
             for t in TOOLS.values()
         ],
     }