archipelagoandClaude Fable 5
e1a3f31a0a
Demo images / Build & push demo images (push) Successful in 3m32s
User-reported checkpoint regression: on a genuinely first visit to Cloud this session, no folder opened on click (subsequent visits fine). Root-caused on archi-dev-box, not guessed: - The click DID register (confirmed via a direct DOM listener) and DID call router.push (confirmed by patching the live router instance) — but the push's promise never settled, because Vue Router awaits the target route's async component, and that dynamic import() itself never resolved. - Confirmed via a manual import() from the page console: importing ANY lazy route chunk (Fleet, CloudFolder, AppDetails — unrelated views) hangs identically after visiting Cloud once, but works instantly before ever visiting Cloud. Not chunk-specific, not router-specific. - Traced to exactly one permanently-pending network request: a File Browser `GET /app/filebrowser/api/resources/Photos` call from Cloud's own onMounted burst, confirmed hung via request-lifecycle tracking (never finishes or fails, still pending after 10s). The identical request, issued manually with a fresh token outside of Cloud.vue, returns in 29ms — ruling out the backend/File Browser itself. - Mechanism: Cloud.vue's syncOnEntry() (loadCounts/loadPeers/ loadPeerFiles) fires from BOTH onMounted and onActivated with no fresh-mount guard (02-04 exempted it, reasoning each resource is individually staleness/inflight-deduped — true per-resource, but the two back-to-back passes still double the concurrent request volume at the single riskiest instant in a session: first KeepAlive activation, stacked on whatever other cached view's own onMounted burst is firing at the same moment). On real hardware that volume was enough to leave one File Browser request stuck, which then starves Chromium's per-origin connection pool — breaking every subsequent same-origin fetch, including the lazy chunk any later navigation needs. Not a router or click-handler bug; the click and push both worked correctly the whole time. Fix: give Cloud.vue the same fresh-mount guard already used in Home.vue/Web5.vue/Mesh.vue/Server.vue (skip onActivated's redundant first-activation re-fire since onMounted just ran it). Removes the duplicate-burst mechanism without changing steady-state reactivation — onActivated still re-syncs normally on every later KeepAlive round-trip. No visual/behavioral change (D-01 rule). Full test suite green (95 files / 774 tests), type-check and build clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>