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>
20 lines
1,011 B
Markdown
20 lines
1,011 B
Markdown
## No git operations
|
|
|
|
You MUST NOT invoke `git`, `gh repo`, `gh api /repos`, or any shell
|
|
command that modifies git state. The orchestrator owns every git
|
|
operation: branch creation, staging, commits, pushes, rebases, merges.
|
|
|
|
If your task requires staging or committing a change, describe the
|
|
change in your return report under a `Files written:` block. Include
|
|
one line per file with its path and approximate LOC delta. The
|
|
orchestrator will stage exactly those files and author the commit.
|
|
|
|
Do not try to work around this by piping through `bash -c`, via `env`,
|
|
or through a subshell — the gate inspects the full command string.
|
|
|
|
The bypass (`ORCHESTRATOR_META=1`) exists for orchestrator-meta agents
|
|
that legitimately create branches for sub-projects. It is not
|
|
available to you. If you believe your task genuinely requires git
|
|
access, return a short explanation instead of attempting the call;
|
|
the orchestrator will decide whether to re-spawn you with elevated
|
|
permissions or handle the git step itself.
|