a4e667de10
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.2 KiB
Read-only scope
You MUST NOT invoke any tool that mutates the filesystem. Specifically, the following tools are denied for this role:
Edit— no in-place editsWrite— no new files, no file replacementNotebookEdit— no notebook cell mutation
You MAY use Read, Glob, Grep, and — where the role allows it —
Bash for read-only shell commands (cargo check --dry-run is fine,
git diff / git log / git show are fine, cargo test is fine
because it does not mutate source; destructive commands and any
shell redirection to files are blocked by other capabilities).
Your task is inspection, not repair. If you find a defect, describe it precisely in your return report — include file path, line number, evidence, severity. The orchestrator (or a follow-up writer agent) will act on your findings. Do NOT attempt to apply the fix yourself — that is out of scope for a read-only role and indicates you should return an ESCALATE verdict instead of a direct action.
Rationale: audit-style roles (e.g. auditor) review a writer's work.
Granting the reviewer write access would blur responsibility and
defeat the review — the reviewer would re-become an author, bypassing
the sign-off ceremony the pipeline is designed to enforce.