feat: complete M2 content workspace and inspector

This commit is contained in:
Rbanh committed 2026-07-17 23:40:49 -04:00
1 parent 931f561e7f
commit cf6eaba534
438 files changed
+59749 -19043

No files matched your search

@@ -0,0 +1,20 @@
---
name: blacksite-gitea-sync
description: Read and synchronize exact Blacksite Gitea issues, epics, and milestones with current scope, implementation state, verification evidence, canonical documentation, and release-candidate status while avoiding duplicate issues and noisy updates.
---
# Blacksite Gitea synchronization
Read `.codex/workflow.toml` and [the state model](references/gitea-state-model.md). Use the configured Gitea connector; do not scrape or invent tracker state.
Supported modes are `read`, `plan`, `status`, `scope-delta`, `candidate`, and `close`.
1. Read exact known issue, parent epic, milestone, and recent relevant comments first. Search broadly only to locate an unknown item or prevent a duplicate.
2. Summarize acceptance locally and create a dry-run mutation plan before every write.
3. Follow configured permissions. Creation and scope/milestone changes require explicit authority; closure is candidate-only; delete/reopen is explicit.
4. Add at most one meaningful status comment per completed slice.
5. Distinguish working-tree implementation from engineering-complete, acceptance-in-progress, candidate-ready, and closure evidence.
6. Mark acceptance only when code, focused tests, and required native/package evidence exist and remain valid.
7. On failure, re-read the exact item, detect partial success, and retry only the missing operation.
Never push or close as a side effect. Record remote mutations and their readback in session state.
@@ -0,0 +1,14 @@
# Gitea state model
Gitea owns accepted scope, criteria, priority, dependencies, work state, candidate/evidence links, blockers, and milestone composition. It does not replace code, tests, ADRs, canonical docs, or native evidence.
States:
- `Implementing`: active local work.
- `Engineering-complete`: relevant engineering gates pass; native/product acceptance may remain.
- `Acceptance-in-progress`: native or stakeholder validation is active or exposed a gap.
- `Candidate-ready`: stable scope and a nominated tree are ready for remaining release gates.
- `Blocked`: an external condition prevents progress.
- `Closed`: candidate evidence and every criterion are accepted.
User-discovered UX gaps return an item to acceptance-in-progress and become scope deltas, not automatic new issues. Close children, final signoff, epic, then milestone. Never close a milestone with open assigned issues unless the user explicitly changes its definition.