Files
pipdock/ui
poli0981andClaude Opus 5 01426b97a8 feat(app): health_run, and a progress forwarder that knows its own channel
NOT_YET is down to three, and only health_fix is still Phase 3's.

forward_progress hardcoded "plan-progress". It now takes the channel as a `&'static str`
rather than a String, because the names are the closed set in EVENTS — a literal typo
becomes a compile error instead of an event nobody is listening for, which is the failure
that leaves a progress bar at zero while the work runs to completion behind it.

The health slot is its own, not Sessions<Session>. A run mutates nothing, so refusing it
while an install streams would be a lock with no invariant behind it — and S5 bug 1 is the
standing warning about claims that wedge. But two Run clicks would put six subprocesses
over one folder, so it needs *a* slot. Sessions<T> was already generic and already tested
with a u32.

It is typed Sessions<HealthSession> rather than Sessions<()> deliberately: P5's health_fix
has to check the user's consent against a report the *server* holds — a count arriving from
the frontend proves nothing about what the frontend displayed — which is the same shape
ack_ok checks a GuardAck against the guard that produced it. Typing it now means P5 does
not redo the slot.

The implicit tools-venv sync runs on the same channel, so a first run on a fresh install
shows the ~15 s bootstrap rather than an unexplained pause, and the total is decided before
the first event because whether a sync is owed is exactly what changes it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-12 23:31:37 +07:00
..