You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Model and thinking routes remain separate from Role capability. They resolve through `@henryqw/pi-task-models`; fallback is attempted only before launch, and a started child is never retried.
15
15
- Each `delegate_task` runs one bounded task in an ephemeral `pi --mode json -p --no-session` child with abort propagation, configurable idle/hard deadlines, and bounded concurrency. Main owns decomposition, integration, and cross-cutting decisions.
16
16
- Main-visible streaming updates, results, and errors are capped at 50 KiB. Unused JSON event payloads are discarded before buffering.
17
+
- The bundled delegated-development Skill is Main-side policy only: it fails before delegation without a committed Git `HEAD`, reviews only an exact verified base-to-tip committed patch with referenced files, and merges only the reviewed commit. It does not change the generic non-Git/unborn-`HEAD` fallback.
17
18
- Generic managed Herdr hosting is a separate library surface for workers that must survive orchestrator pauses or restarts. Callers retain domain prompts, state, and lifecycle decisions.
18
19
- The TUI widget projects active ephemeral children and briefly shows terminal status; it owns no lifecycle state.
Copy file name to clipboardExpand all lines: packages/pi-auto-dag/CONTEXT.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,8 +37,8 @@ System-owned identity binding reviewer verdict to run, review kind, Local Issue,
37
37
_Avoid_: Reviewer correlation field, model token
38
38
39
39
**Review Packet**:
40
-
Canonical fresh reviewer handoff containing delivery context, Local Issue, worktree, base, and Required Gate. Existing reviewers receive only changed gate, findings, or resolution data.
41
-
_Avoid_: Reviewer prompt variant, echoed orchestration state
40
+
Canonical fresh reviewer handoff containing delivery context, Local Issue, worktree, base, Required Gate, and a read-only exact binary patch artifact. The artifact is atomically persisted privately under the run directory after base/commit verification and identifies its path, base, commit, byte count, SHA-256, and deterministic child-branch or explicit integration-head context; its patch body is never in the prompt. Existing reviewers receive only changed gate, findings, or resolution data.
41
+
_Avoid_: Reviewer prompt variant, inline diff, echoed orchestration state
42
42
43
43
**Local Issue**:
44
44
Immutable work definition identified by a stable string within a Delivery Graph.
Copy file name to clipboardExpand all lines: packages/pi-auto-dag/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ Pass the exact graph object to `auto_dag_execute`. It is immutable for the durat
102
102
103
103
1. The caller normalizes an approved plan into the exact graph and calls `auto_dag_execute`. Planning is externally owned (for example by `/ship`).
104
104
2. Auto DAG validates structure, then shows one TUI confirmation bound to the SHA-256 of the exact graph. It display-escapes every exact `testing` command that will later run through `sh -c`, alongside both fixed Roles. Execution never starts without this confirmation.
105
-
3. Ready tasks share one Git base at the frozen HEAD. Each gets a child worktree, the fixed implementer Role, one required commit, and the exact `testing` command through `sh -c`. The fixed reviewer Role sees the commit and gate evidence; approval requires system-owned exit code `0`.
105
+
3. Ready tasks share one Git base at the frozen HEAD. Each gets a child worktree, the fixed implementer Role, one required commit, and the exact `testing` command through `sh -c`. A fresh fixed reviewer Role receives the commit, gate evidence, and a read-only run-private exact binary patch reference (path, base, commit, size, SHA-256); the patch body is never in its prompt. Approval requires system-owned exit code `0`.
106
106
4. After each wave passes, commits are cherry-picked by Local Issue ID and the next wave starts. A cherry-pick conflict returns that task to its workers.
107
107
5. After every implementation task, Final Check runs on clean integration `HEAD`; product failure repairs through the owning Local Issue.
108
108
6. When all gates pass, Auto DAG pushes one branch and opens exactly one PR. Ownership ends there; post-PR sweep and CI status are caller-owned (for example `/ship`).
0 commit comments