Verify that Codex app-server can fork threads
This commit is contained in:
@@ -6,7 +6,6 @@
|
|||||||
|
|
||||||
# M3 — Second vendor and review
|
# M3 — Second vendor and review
|
||||||
|
|
||||||
- Verify that Codex app-server can fork threads
|
|
||||||
- Review profiles and triggers
|
- Review profiles and triggers
|
||||||
Reviews are done by a separate agent session, never the implementer, by default from a different vendor. Each review targets a snapshot and is cached by tree sha; when the task's tree moves on, existing reviews are marked stale. A review profile (security, performance, privacy, visual UX, plan conformance, ...) has a prompt, vendor, model, output schema and capture config; workflow stages reference profiles by name. Triggers: on `ask_human` (the inbox item appears at once and the review attaches when done, even if the item was resolved first), before merge, on demand, and periodically on elapsed time or diff size, debounced to turn boundaries or a quiet period. A `request_review(scope, concerns[], profile?)` MCP tool lets agents ask for one.
|
Reviews are done by a separate agent session, never the implementer, by default from a different vendor. Each review targets a snapshot and is cached by tree sha; when the task's tree moves on, existing reviews are marked stale. A review profile (security, performance, privacy, visual UX, plan conformance, ...) has a prompt, vendor, model, output schema and capture config; workflow stages reference profiles by name. Triggers: on `ask_human` (the inbox item appears at once and the review attaches when done, even if the item was resolved first), before merge, on demand, and periodically on elapsed time or diff size, debounced to turn boundaries or a quiet period. A `request_review(scope, concerns[], profile?)` MCP tool lets agents ask for one.
|
||||||
- Decide the periodic review thresholds
|
- Decide the periodic review thresholds
|
||||||
|
|||||||
Reference in New Issue
Block a user