Skip to content

v0.4.2 — Dogfooded baseline + MCP detection fix

Choose a tag to compare

View all tags
@JRS1986 JRS1986 released this 18 May 20:42
· 103 commits to main since this release
v0.4.2
7ba3835
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release. Two changes since v0.4.1, plus a doc clarification.

Added

Dogfooded baseline on the scaffold's own repo (narrow scope)

The scaffold now runs itself on its own repository, adopting only the bits the project actually uses:

  • `AGENTS.md` at the repo root documents the real maintainer workflow: verification commands (`uv run ruff check`, `uv run pytest -q`), the no-runtime-dependency / no-LLM-calls / no-network / no-telemetry posture, the plain commit-message convention, and when to use session traces (3+ modules touched, or architectural changes).
  • `.github/PULL_REQUEST_TEMPLATE/agentic-change.md` generated by `coding-scaffold pr-template init` — same artifact users get.
  • `.coding-scaffold/eval-config.json` runs the readiness benchmark as a smoke check with `policy_exists` and `denied_files_configured` disabled. This repo IS the policy generator; it does not generate policy for its own development. The MCP check auto-skips because no MCP servers are declared.
  • `.coding-scaffold/sessions/.gitkeep` keeps the session-trace location available for larger PRs.

Result: `coding-scaffold eval run --target .` reports 9/9 checks passed on the scaffold's own repo.

Fixed

`eval mcp_policy_exists_if_mcp_detected` no longer false-flags on file presence alone

The check previously treated any of `opencode.json`, `.claude/settings.json`, `.claude/settings.local.json`, or `.codex/config.toml` existing as "MCP in use". But `.claude/settings.local.json` is commonly present in Claude Code installs without any MCP entries — file existence alone, not declared servers.

The check now uses `scan_mcp` and only fires when at least one server is actually parsed from a config. One new regression test.

Documentation

The 10-minute team pilot path is now clearer in README.md, docs/wiki/Getting-Started.md, and docs/wiki/Team-Rollout.md.

Verification

  • `uv run ruff check` clean.
  • `uv run pytest -q` → 311 passed.
  • `coding-scaffold eval run --target .` → 9/9 passed on the scaffold's own repo.
  • `coding-scaffold context lint --target .` → 0 findings on the scaffold's own repo.

Backwards compatibility

Fully backwards compatible with v0.4.1. Users running `coding-scaffold eval` against a project that has a `.claude/settings.local.json` without MCP entries will now correctly see the check skip rather than incorrectly fail.

Full notes: CHANGELOG.md.

Assets 2
Loading