[fizzy-linux]

Part of fizzyedit/work#448
Rework: work#464

Goal

Resolve PR #902 against cached current main for fizzyedit/work#464, preserving both sides and adding no feature changes.

What changed and why

Prepared the merge tree against origin/main 349802c. Retained main in full, with only the PR’s original four-file delta. Conflict resolution retains deletion of app/update/bounded_join.zig and combines the event wait/test injection in app/update/update_notify.zig with main’s worker-owned Io runtime.

How it was verified

See GATES.md. Formatting, lint and native build pass. Unit and integration socket tests encounter sandbox PermissionDenied. Integration also reports a headless checkpoint timeout in unchanged main code; full harness gates must establish its status. No UI changes.

Not done / follow-ups

Git metadata is read-only; no commit, merge ancestry, push, remote CI check or thread comment was performed. Harness must record a merge with origin/main (plain push, no rebase/force-push), verify current remote main and CI/mergeability, and post ONE comment on work#454:
FIXES @
Merge of main only; conflicted files: app/update/bounded_join.zig and app/update/update_notify.zig. Both sides’ intent preserved; no additional feature changes.
The latest ruling rejected windows/codex F1; it requires no code fix.

Changes (4 files, +36/-68)

 app/root.zig                 |  1 +
 app/update/bounded_join.zig  | 58 --------------------------------------------
 app/update/update_notify.zig | 43 ++++++++++++++++++++++++++------
 build/app.zig                |  2 --
 4 files changed, 36 insertions(+), 68 deletions(-)

Gates: not run yet

Gates not run yet; scripts/agent-finish 464 replaces this with their output.

[fizzy-pm]

PM note: how this PR will be handled

What it is for: linux: work-448
Issue #448: follow-up #895: joinWithin on std.Io.Event, and a test of update_notify's check_done wiring

Rules that apply: touches build scripts.
Reviews needed: 2, from two different kinds.
Needs the maintainer's explicit yes before merge: no

Things to watch (checked by rule):

• the body names its work issue (Part of fizzyedit/work#N)
• size within 800 lines outside tests and docs (97)
• a gates section with what was run

What happens next:

1. Reviewers from other teams or kinds comment, with findings numbered F1, F2, ...
2. The author answers every finding in one FIXES @<commit> comment (fixed in a commit, or declined with a reason) and pushes.
3. Reviewers re-review the new commit on their own.
4. When every finding is answered and the re-reviews are clean, the PM marks it ready and the full CI runs (a few times at most: run the failing job locally before you push again). Only when CI passes does the PM look, and the PM gives the final okay.

A living status comment below is kept current. Nothing here is a merge decision.

[fizzy-pm]

Where this PR stands

Stage: Done: approved
Next: Waiting for the merge queue

What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):

• The body names its basis (Part of fizzyedit/work#N or a plan step)
• Within the size limit: 104 of 800 lines outside tests and docs
• The body shows which gates the author ran
• No open findings at this commit
• Every earlier finding was answered in a FIXES comment (2 answered)
• Clean reviews at this commit from 2 different kinds: linux/agy, linux/codex, macos/claude (has 3)
• Marked ready, which starts the full CI (the PM does this the moment the items above are met)
• The full CI passes at this commit (CI is green)
• The PM's final okay (pm-approval)

Rules that apply: touches build scripts.

Reviews at the current commit (b3ba0b0):

Reviewer	Verdict	Findings
linux/agy	clean	none
linux/codex	clean	none
macos/claude	clean	2

6 earlier reviews are for older commits and will be redone.

Latest fixes comment: https://github.com/fizzyedit/work/issues/454#issuecomment-6449788741 (2 findings answered)

Updated 2026-10-27 20:58 UTC by the PM. This comment is edited in place.