Hold loop reports to the app's criteria at post time and keep phase prompts out of New Session

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-03 04:08:36 -08:00
1 parent 33f1783979
commit 61f27f81ab
7 files changed
+497 -35

No files matched your search

+9
View File
@@ -177,6 +177,15 @@ At the end of the run, post once a top-level `loopOutcome`:
- `subject` is one imperative line under 100 characters saying what changed (it
becomes the commit subject). `summary` is one line under 200 characters.
The app stamps `loopExpect` into the session as the phase starts: the criteria
it will judge the report by (`review`, `fix` as `"smart"` or the level list,
`guess`). It is the app's field, never yours to post. The console holds every
`loopOutcome` to it, so a report missing a required piece (`review.ran: false`
on a review run, no `review.triage.ran` under Smart pick, a skipped Critical in
the triage, no re-check with fixes chosen, assumed tasks without `--guess`) is
refused at post time with the field named, while the run can still do that
step and repost.
Then post `{"agent":{"status":"waiting"}}` and keep waiting with the usual
bounded `wait` slices until the app ends the session. Never end the turn on text.
If the post is refused (exit 3), fix the field it names and post again.