1.4 KiB
1.4 KiB
| name | description |
|---|---|
| blacksite-gitea-sync | 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. Use the configured Gitea connector; do not scrape or invent tracker state.
Supported modes are read, plan, status, scope-delta, candidate, and close.
- Read exact known issue, parent epic, milestone, and recent relevant comments first. Search broadly only to locate an unknown item or prevent a duplicate.
- Summarize acceptance locally and create a dry-run mutation plan before every write.
- Follow configured permissions. Creation and scope/milestone changes require explicit authority; closure is candidate-only; delete/reopen is explicit.
- Add at most one meaningful status comment per completed slice.
- Distinguish working-tree implementation from engineering-complete, acceptance-in-progress, candidate-ready, and closure evidence.
- Mark acceptance only when code, focused tests, and required native/package evidence exist and remain valid.
- 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.