Repository navigation
Description
Refs: #7303
Summary
DX-5 from #7303: reading the wake payload takes a multi-step parsing recipe. No slice of #7303 carried it: #8013 named DX-4, DX-6, DX-8, DX-10 and DX-14, and #8015 named DX-13. The closing comment and #12365 do not name it either. The recipe is still on main at plugins/planning/skills/interview/context/surface.md:50: check the exit status, Read the background task's output file, take the last line that starts with {, drop the line number and tab Read adds, and on a PARTIAL view run grep '^{' '<output-file>' | tail -n 1 instead. The output file mixes stderr with stdout and ends with an [exited with code N] footer (verification record at context/surface.md:317-323).
Under the 2026-10-12 decision on #7303, re-verify DX-5 on main first. If it is confirmed, fix it. If it is not confirmed, close this issue and give the reason in the PR body or a comment.
One possible fix: watch.sh also writes its JSON line to a fixed file in the data dir, so the wake reads that one file. watch.sh is generated from lib/session-bridge/, so the fix goes there and the shared copies are regenerated.
Acceptance criteria
- The wake JSON is read in one documented step after the exit-status check, with no line-number stripping or last-
{-line search. -
context/surface.md"The wake" and the surface README describe that one step, and the old recipe is gone. - A watcher test asserts the payload is readable that way on an exit-0 wake.
- Shared copies of
lib/session-bridge/files are regenerated withsync-shared-copieswhen the fix touches them.
Metadata
Metadata
Assignees
Labels
Type
Fields
Work status
Activity
github-actions commentedon Nov 2, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: the interview wake payload (DX-5 from #7303) still needs a multi-step read recipe. The proposed fix is for the watcher to also write its JSON line to a fixed file, so the wake reads one file. Acceptance criteria cover the docs, a watcher test, and regenerating the shared copies. The issue asks for a re-verify on main first, and that step is part of the work. I found no likely duplicates.
Automated triage, applied by the lanes App.
github-actions commentedon Nov 2, 2026
github-actions commentedon Nov 2, 2026