0be354a920
Single-commit clean baseline after security scrub of niche-tells, project codenames, internal jargon, and contributor-email leaks. Contents: - 100 Rust crates (_primitives/_rust/) - 37 agent manifests (_manifests/) + generated specs (_generated/) - 67 user-invocable skills (skills/) - 33 hooks (hooks/) - Composition blocks (_blocks/) - Documentation (docs/, README.md) - TS adapter packages (_ts_packages/) - Assembler (_assembler/) - Roles (_roles/) - Templates (_templates/) - Forgejo CI (.forgejo/) Author: Denis Parfionovich <info@greendragon.info> License: see LICENSE.
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.