fix: check agent-work delivery readiness at launch and handoff

[ahmad-ajmal]

Apps that queue agent work can remain healthy after a one-shot test while later tasks stay unclaimed. This change reports delivery readiness separately from server health and requires a live delivery check at creator/modify handoff.

Changes

• Share bounded, read-only delivery inspection across fresh/idempotent serve, list, and bridge. Report absent/stale/running local bridges, observed waiting work, and unknown queue reads without implicitly starting agent runs.
• Record the endpoint selected by a background bridge and flag bridges still watching dev, or legacy records with an unknown endpoint. Verify app identity before sending credentials during live queue inspection.
• Explain the independent bridge lifecycle on app stop, and avoid equating process liveness with successful delivery or absence of a local bridge with absence of an external subscriber.
• Require creator/modify to verify live delivery and leave a detached bridge for authorized handoffs. Document static detection limits and add CLI lifecycle regressions.

Validation

• pnpm -r build, pnpm -r typecheck, and pnpm -r test passed; conformance: 86/86. The full CLI suite was rerun successfully after the final wording correction. Three existing symlink checks were skipped because symlinks were unavailable on Windows.
• Fresh React/Node blueprint E2E on Windows with a real SQLite database: scaffold → install → dev → validate (no unchecked steps) → promote → live serve.
• Real Pi completed five tasks, including work queued after the detached launch command exited, work submitted after app stop/serve, and a retry after an actual harness failure.
• Browser checks covered validation, status/filter/empty states, waiting/no-listener, progress/input-required, completion/failure/cancellation, retry, offline recovery, and 390px layout. CLI CRUD, duplicate refusal, wrong dev target, stale bridge records, idempotent start, and unknown queue state also passed.
• git diff --check passed. Test processes were stopped. Fresh browser E2E coverage is limited to the React/Node blueprint and Pi headless route.

Dependencies and scope

Registered in GitHub stack #26 above #27, #25 and #21, targeting main. The PR's direct base is ahmad/fix-triage-requeue, keeping its diff focused on this change.

Bridge opt-in remains unchanged. OS reboot startup, crash supervision, and external subscriber discovery are outside this change.

Closes #12.