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
Copy file name to clipboardExpand all lines: docs/TASK-PASSPORT.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,6 +200,18 @@ historical so they are not mistaken for active instructions.
200
200
201
201
The normal human-facing sequence is: start the task, keep status/scope/next actions current, record verification with evidence, print a handoff when another agent or chat may continue, then finalize only after verification is final.
202
202
203
+
The verification order matters: iterate checks while verification is `pending`
204
+
and fix freely; when no edits remain, commit the in-scope changes and confirm
205
+
the commit changed nothing (clean tree, hooks silent) before recording the
206
+
final verdict. From there the task has two endings. With no external wait, end
207
+
with one `task finalize --status passed` call carrying evidence and the commit
208
+
hash, so no `verifying` window opens. With an external wait (review, PR merge,
209
+
re-score), record `passed`, then `task park`; after the external result,
210
+
finalize — or return verification to `pending` if changes are needed. A
211
+
recorded final verdict moves the task to `verifying` and freezes code changes;
212
+
to commit already-verified changes from there, set verification back to
213
+
`pending`, commit, then re-record the verdict.
214
+
203
215
Temporary work switching uses `task park`, not `task finalize`. Parking keeps a
204
216
passport open and switchable while unrelated work becomes current. Finalization
205
217
means the task is complete, failed, or explicitly accepted as-is.
return"Current task is verifying. Finish or record verification before editing code, or park it for unrelated work.";
195
+
return"Current task is verifying: a final verdict is recorded and code changes are frozen. Finalize the task; to commit already-verified changes, set verification to pending, commit, then re-record the verdict. Park the task for unrelated work.";
196
196
}
197
197
if(status==="parked"){
198
198
return"Current task is parked. Switch to it, or start the task this work belongs to.";
Copy file name to clipboardExpand all lines: src/integrations/install.ts
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,10 @@ Task lifecycle gate:
85
85
- treat review mode as a scope check, not an automatic new Task Passport: keep reviews that verify the current active/verifying task inside that task as evidence/checkpoint; park, switch, or start a separate review task only for unrelated reviews
86
86
- park deferred work with \`task_park\`/\`task park\`, or switch/close only when appropriate, before starting unrelated work
87
87
- do not finalize a task just to free the current slot; finalization means verification is passed, failed, or explicitly accepted as complete
88
-
- finalize after the task's changes are committed; park a verified task that is still waiting for review or commit instead of closing it
88
+
- verification order: iterate checks with verification pending and fix freely; when no edits remain, commit the in-scope changes and confirm the commit changed nothing (clean tree, hooks silent) before recording the final verdict
89
+
- no external wait: end with one \`task_finalize\` call carrying the final status, evidence, and commit hash, so no verifying window opens
90
+
- external wait (review, PR merge, re-score): record \`passed\` via \`task_update_verification\`, then \`task_park\`; after the external result finalize, or return verification to pending if changes are needed
91
+
- a recorded final verdict moves the task to verifying and freezes code changes; to commit already-verified changes from there, set verification back to pending, commit, then re-record the verdict
89
92
- keep next actions current: clear or replace a stale plan (\`task update --clear-next-actions\`) before finalizing, so closed passports read as history, not as open work
90
93
- if a task still has next actions and must pause for unrelated work, park it instead of using \`task_finalize\`/\`task finalize --status accepted\`; force accepted finalization only when the remaining next actions are intentionally historical
91
94
- do not mutate a review task into implementation work
0 commit comments