fix(j5): route Squadrons and inbox across environments

[Jacksondr5]

Closes #105

What Changed

Squadrons and the human inbox now read from each connected environment. Creation, thread homes, launch choices, inbox navigation, and replies keep the owning environment throughout the web/desktop flow. Disconnected sources retain their loaded results and show incomplete coverage.

Why

These J5 features previously sent reads and actions through the primary environment even when remote environments were connected. The change reuses the existing connection registry and the shared authenticated HTTP transport, including bearer and relay DPoP credentials with one refresh-and-retry. Data stays on its owning server; no database migration is needed.

Takeover changes (aaa3719f5b)

• J5 reads go through executeAuthenticatedEnvironmentHttpRequest, so a relay token the server rejects is refreshed and retried once; focused test added.
• The index landing keeps upstream's bootstrap wait before judging a Squadron's folder missing.
• Environment labels render only once results span more than one environment; a single-environment client keeps the name-only picker row from FORK case 20 (the multi-environment label line is recorded there as pending Jackson's sign-off).
• The docs/user/remote-access.md edit moved under docs/j5/product/cross-device.md; FORK.md case 34 records the upstream-owned paths and amends cases 9 and 20.
• CodeRabbit findings dispositioned in the PR comment; two fixed.

Validation

• Touched tests pass: 154 web, 25 client-runtime J5, 12 server; scoped typechecks clean for contracts, client runtime, web, and server; lint reports only pre-existing React compiler warnings in the touched scope.
• Headless Chromium with two isolated, populated servers (original head): merged Squadrons/inbox, remote creation (HTTP 201), a remote reply (HTTP 200), navigation to the remote sender thread; database reads confirmed only the remote question closed.
• Headless Chromium against a seeded single-environment worktree (takeover head): thread homes, scope dropdown and filtering, ambient-scope auto-launch, New thread picker, draft chip, inbox page and bell; offline state renders the per-environment notice.
• Web and desktop share the updated entry points: sidebar, command palette, new-thread shortcuts, draft chip, and inbox. Native mobile screens are a separate increment; provider adapters are unchanged.
• Direct HTTP was exercised end to end. Relay token refresh is covered by a focused test; a live relay/tunnel session remains unverified.

UI Changes

Two-environment captures use the same fixture data on both servers (same Linux host, so the displayed hostname is shared). Before: j5/main at the time. After: original head 19b20b1ad9; the multi-environment presentation is unchanged at aaa3719f5b.

View	Before	After
Inbox
Squadron picker

Remote reply recording (10 seconds) · Inbox after the remote reply

Single-environment presentation at aaa3719f5b (no environment labels, matching case 20):

Picker	Scope dropdown

Evidence lives on j5/evidence, pinned to 414156c02 (two-environment) and 0b4237987 (single-environment, with SHA256SUMS).

Checklist

• One concern: environment routing for Squadrons and the human inbox
• Explained what changed and why
• Included before/after images
• Included a short interaction recording
• FORK.md case recorded for the upstream-owned paths

Implemented with GPT-6 using the Codex harness; takeover fixes by Claude Fable 5.1 using Claude Code.

🤖 Generated with Claude Code

[Jacksondr5]

Posted by an AI agent on Jackson's behalf

CodeRabbit CLI record — coderabbit review --committed --base j5/main --agent at reviewer-clean head 19b20b1ad9; 6 findings, dispositioned here and fixed where noted in aaa3719f5b.

#	Severity	File	Disposition
1	major	apps/web/src/j5/squadron/ThreadHomesClient.ts (scope effect reads requestedRef)	Dismissed. New refs are requested by the non-forced effect as they arrive; the forced reread is deliberately keyed to scope selection and its generation only, so a thread-list change never forces a whole-scope reread.
2	minor	apps/web/src/j5/state.ts (force bypasses unsupported)	Fixed. An unsupported source is never refreshed; force only bypasses the in-flight guard.
3	minor	apps/web/src/j5/a2a/HumanInboxBell.tsx (? when count is 0 and incomplete)	Dismissed. Documented behavior: a question mark means no positive count is available while some environment cannot be refreshed; 0* would claim a known zero.
4	minor	apps/web/src/j5/a2a/HumanInboxPage.tsx (previous key set dropped when data is null)	Dismissed. data is null only for an unsupported source or one that has never loaded; AsyncResult keeps the last value across failures, so a transient failure keeps its key set.
5	minor	packages/client-runtime/src/j5/inbox.ts (notice copy separator)	Fixed. Error notices use the same em-dash separator as the offline notice.
6	minor	packages/client-runtime/src/j5/squadrons.ts (all-unsupported directory reports error)	Dismissed. When every environment lacks the J5 routes the first-run gate must show unavailable-with-retry, not an empty ready directory that invites creation.

Additional changes in aaa3719f5b from the takeover review: J5 reads now go through the shared executeAuthenticatedEnvironmentHttpRequest (relay token refresh-and-retry, with a focused test); the index landing keeps upstream's bootstrap wait; environment labels render only once results span more than one environment (case 20 kept for a single environment); the docs/user/remote-access.md edit moved under docs/j5; FORK.md case 34 records the upstream-owned paths.