fix: bound follower debug json output

2026-07-03 18:14:37 +00:00
parent 530e02a243
commit c0062455fd
2 changed files with 54 additions and 3 deletions
@@ -34,6 +34,8 @@ When a repeated runtime pitfall or visibility defect is found during branch-foll

 `debug-step` wrappers must be failure-visible and non-crashing. If the target-side Job fails, returns an older schema, or omits optional summary fields, the operator-facing CLI must render `-`/null plus the target error and Job identity; it must not throw a local TypeError before showing the target evidence.

+`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.
+
 ## Source Authority

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