feat(engine): task-gate surfaces — proposed-task, tasks-overview, author-task-gate, phase-tree#492
Merged
Merged
Conversation
This was referenced Jul 21, 2026
Merged
leeovery
force-pushed
the
feat/render-findings-gates
branch
from
July 22, 2026 14:24
7169d34 to
d367029
Compare
leeovery
force-pushed
the
feat/render-task-gates
branch
from
July 22, 2026 14:24
37b4f7b to
1931c53
Compare
…hor-task-gate, phase-tree The task-gate family codifies: the byte-identical proposed-task displays and approval menus in the implementation analysis loop and the review actions loop become one proposed-task surface (gate mode rides as a flag — one consumer carries it in the cycle response, the other in staging frontmatter); their cycle overviews become tasks-overview; the planning task-authoring menu becomes author-task-gate; and the D5 phase tree lands — numbered phase nodes with wrapped tree detail, --approve appending the structure gate for define-phases. plan-construction's twin task-list gate reuses the stage-1 surface via --variant existing (no auto opt-in; "confirmed" phrasing) and loses its gate-mode read. Five consumer references swapped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
leeovery
force-pushed
the
feat/render-task-gates
branch
from
July 22, 2026 14:25
1931c53 to
aff44a6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stage 3 of the render-surfaces programme (design log: #489; base: #491). The task-gate family plus the D5 phase tree.
Surfaces
proposed-task— the analysis loop (implementation) and review actions loop carried byte-identical 15-line task displays, approval menus, and auto lines; now one payload surface. Gate mode is a--gateflag rather than an address read — deliberately: one consumer carries the mode in the cycle response, the other in staging-file frontmatter, so the flow owns the mode and the surface owns the form. Per-consumer comment hint (--comment-hint).tasks-overview— the proposed-tasks cycle overview both loops shared.author-task-gate— planning's per-task authoring menu (scalars as flags; the task detail itself remains a verbatim file emission the flow owns).phase-tree— D5 lands:Phase structure — N phases.with numbered phase nodes and wrapped[label, value]tree detail rows throughtreeList;--approveappends the structure gate.define-phasesgets shaped output for the first time (its previous instruction was "present as rendered markdown", freeform).task-list --variant existing— plan-construction's twin gate reuses the stage-1 surface: same display, "confirmed" auto phrasing, gated menu without the auto opt-in (matching its existing-tables semantics); itstask_list_gate_moderead left the prose.Five consumer swaps: analysis-loop, review-actions-loop, author-tasks, plan-construction, define-phases.
Test plan
npm test— 1496/1496. Typecheck + conventions lint clean.🤖 Generated with Claude Code
Stack