c0c3483f02
22 files per locked §Initial capability atom inventory: policy/no-git-ops/ (gate: PreToolUse:Bash, bypass ORCHESTRATOR_META) scope/files-whitelist/ (gate + verify worktree) scope/files-denylist/ (gate + verify worktree) quality/constructor-pattern/ (verify worktree) quality/cargo-check-green/ (verify both — worktree short-circuit + simulated-merge) quality/tests-green/ (verify both) safety/no-dep-bump/ (gate + verify both) output/report-format/ (verify worktree) output/severity-grade/ (verify worktree) tools/read-only/ (gate: deny Edit/Write) tools/cargo-only-bash/ (gate: Bash allowlist) All capability.toml share [capability]/[restricts]/[parameterized]/[text]/ [gate]/[verify] section layout. rust-module paths pre-wired to match phase-3 file layout. All text.md under 200 words, imperative, self-contained (composer concatenates with --- separator). Cross-refs to rule files preserved: - policy::no-git-ops → RULE 0.13 (orchestrator-branch-first.md) - quality::constructor-pattern → RULE ZERO (code-style.md) - output::severity-grade → debugging.md §Security Review - safety::no-dep-bump → supply-chain rationale Agent attempted wc -w for word counts — sandbox correctly denied Bash per RULE 0.13, observable reinforcement of the very policy this capability encodes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Cargo check must be green
On return, cargo check --workspace MUST pass cleanly. This is
enforced in two passes:
- Worktree pass — runs from inside your worktree. This is what you saw while iterating. It must be green before you hand off.
- Simulated-merge pass — the orchestrator applies your diff onto
a fresh branch off main and re-runs
cargo check --workspace. Your change must still compile once integrated.
Both passes must succeed. Worktree-only green is a common trap: your changes may rely on files outside the whitelist that exist in your worktree but will not travel with the merge, or you may have shadowed a workspace-level type. The simulated-merge pass catches that.
Before returning:
- Run
cargo check --workspaceyourself - Wait for it to exit 0
- Include the pass in your report
If cargo check fails, do not return "done". Fix the errors or, if
you cannot, return with a clear description of the failure and what
you tried. Do not claim green without evidence.
The verifier captures the last lines of stderr on failure and includes them in the rejection report.