fix: expose follower closeout gates

2026-07-03 18:20:51 +00:00
parent c0062455fd
commit dc488302b8
2 changed files with 46 additions and 0 deletions
@@ -36,6 +36,8 @@ When a repeated runtime pitfall or visibility defect is found during branch-foll

 `debug-step` output must stay bounded in both text and JSON modes. The default machine payload should include step result, compact state/status/decision/write summaries, target Job identity and short error/timing fields only. Full target Job logs, full target JSON and long stdout/stderr tails belong behind explicit drill-down, not in the default `--json` payload.

+`status-read`, `events`, `logs` and debug summaries must expose compact closeout gate details when a follower is not aligned: git-mirror readiness, Tekton PipelineRun condition, Argo sync/health, runtime target sha/readiness and short errors. Repeating only phase/observed/target/message is a visibility defect and must be fixed before further rollout tuning.
+
 ## Source Authority

 - Follower decisions must not read host source worktrees, target dev directories, `.worktree/*`, local git state, or direct GitHub branch refs.