Bootstrap repo-tracked wiki pages (10 required pages), the operator- confirmed sync script, PR template publication gate, and safety tests so Gitea-Tools can publish to the live Gitea Wiki per issue #224. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
19 lines
1.5 KiB
Markdown
19 lines
1.5 KiB
Markdown
# Safety and Gates
|
|
|
|
## Navigation
|
|
|
|
- [Home](Home.md) | [Operator Guide](Operator-Guide.md) | [Repositories Map](Repositories.md) | [Identity and Profiles](Identity-and-Profiles.md) | [Workflow Model](Workflow.md) | [Safety and Gates](Safety-and-Gates.md) | [MCP Tools Reference](MCP-Tools.md) | [Operator Runbooks](Runbooks.md) | [Open Decisions](Open-Decisions.md) | [Project History](History.md)
|
|
|
|
*Prompts express intent; MCP tools enforce safety.*
|
|
|
|
## Primary gates
|
|
|
|
1. **Fail closed** — Unknown tasks, missing capability resolution, or profile mismatches block mutations.
|
|
2. **Task capability map** — `gitea_resolve_task_capability` must precede gated issue/PR mutations.
|
|
3. **Issue lock** — `gitea_lock_issue` required before author implementation on a tracked issue.
|
|
4. **Head SHA pinning** — Reviews and merges refuse when the PR head moved.
|
|
5. **Explicit merge confirmation** — `gitea_merge_pr` requires `confirmation="MERGE PR <n>"`.
|
|
6. **No self-review / self-merge** — Authenticated user must differ from PR author for approve/merge.
|
|
7. **Review decision lock** — Live review mutations require validation-phase dry-run and `gitea_mark_final_review_decision`.
|
|
8. **Redaction** — Tokens, passwords, and keychain material never appear in tool output.
|
|
9. **Wiki publication (#224)** — `docs/wiki/` and the sync helper are prerequisites only. Closing a wiki issue requires live Gitea Wiki proof on the repo Wiki tab. See [Runbooks](Runbooks.md#wiki-publication-readiness-gate-224). |