[MashellHan]

Summary

Refresh the two visible Activities surfaces from their existing local snapshot routes every five seconds, measured from the start of each read. Returning to a visible document triggers an immediate read through the existing visibility hook. The Mini App retains its app ID and revision checks, and both surfaces retain abort, access, stale-data and unmount handling. No provider request or scheduler changes are included.

Validation

• The affected Local Usage component tests passed 29/29 and the Mini App dashboard tests passed 5/5, including new contributions becoming visible while Token data stays older, hidden polling stopping, and immediate visibility return.
• pnpm typecheck --project ui passed. The normal push hook passed for all four changed files.
• check:edit failed 82/84: one isolated server did not become ready in 20 seconds with an empty startup log; that same contract passed in the later ready run. The existing dashboard browser E2E reached its 120-second test timeout.
• The sole check:ready failed 1387/1388 on that browser E2E. Two separately bound focused reruns with an existing Chrome 157 cache and the exact source-pinned Chrome 153 cache both reached a Chrome DevTools connection but failed waiting 15 seconds for a tab, before Vite fixture creation or UI assertions. The original failures and both corrected-prerequisite results are retained in the private handoff. Runtime browser acceptance remains pending.
• After PR Focus Activities refresh on unpaid Beijing days #748 merged, a conflict-free normal merge of actual main f2b361c8498b8bd364629903683d81be08c02039 kept all four accepted Front blobs and all eleven accepted Backend blobs unchanged. pnpm check:plan --base f2b361c8498b8bd364629903683d81be08c02039 selected only the four Front files. pnpm check:fixtures and the normal unskipped push hook passed. The original focused and sole-ready evidence carries on unchanged Front source; packaged native acceptance remains pending the accepted combined merged cut.
• After PR Review daily QA backlog and follow unresolved work #749 merged, a second conflict-free normal merge of actual main d604853292157e6c334fcb8dc93fc37c11e82d5e kept all four accepted Front blobs and all fifteen incoming main blobs unchanged. pnpm check:plan --base d604853292157e6c334fcb8dc93fc37c11e82d5e again selected only the four Front files, and the normal unskipped push hook passed. No source logic or fixture changed in this composition.

No App build, install or live data test is part of this source PR. Backend provider and publication work is in a separate PR.

QA-Handoff: 986655a

[MashellHan]

The original independent Reviewer accepted source head 32e1249, tree 96ae51ae9e1bdc87d1664bf7c0627672d42fab2f. The four-file review found no actionable changed-hunk issue. Canonical source receipt SHA256: 8dd776fde82237a11131efa89ac4b36a5813e01fe8f74d1c7fbbf17ec2180162.

CI 43361861040 passed for that head. The same Front owner is composing accepted Backend main f2b361c into this branch; unchanged reviewed blobs carry their review, while the composed head must receive its own required CI.

Original edit FAILED 82/84 and ready FAILED 1387/1388 remain recorded. Changed unit checks passed 29/29 and 5/5. Both explicit Chrome 157 and source-pinned 153 reached DevTools but failed before fixture navigation or UI assertions because no page appeared within 15000 ms. Their causes remain unproved; these setup failures are not runtime acceptance.

The sole Front installer will reuse the existing signed native App CDP fixture on the eventual accepted combined-main package. It will replace only the owned synthetic contribution snapshot A with B, witness visible PR/commit updates and elapsed time on the real local polling path, and retain older Token values. Required fixture, package, preservation and cleanup checks remain. No further external-browser retry, broad ready, new framework, duplicate build or reviewer is requested. Actual helper installation and natural fresh publication/display timing remain pending.

[MashellHan]

Required current-head CI 43363816772:1 passed for 986655a. Normal protected merge produced abd7a6d, tree 4fe28354b2e9873cf2316f7c7ef536f77ff17aae. The four accepted frontend blobs and all incoming main blobs remained unchanged.

The sole installer completed one signed package build, isolated native contribution polling with an unchanged older Token snapshot, package startup and private-file acceptance. The guarded App switch and serial helper/cache apply are installed. Routines, Mini App inventory, configuration, retained history and rollback were preserved; installed reader/API reconciliation passed and the original 300-second writer was restored. The completed installation cut is released.

Natural freshness acceptance remains FAILED / PENDING REPAIR: the first scheduled focused collection published retained stale observations. Faster publication alone does not satisfy the fresh-data target. The original Backend now owns one isolated fresh-main correction for the focused Profile/ADO paths, transport continuation and bounded source progress. Exact runtime evidence stays private. No credential-expiry conclusion, login or fallback is supported by this finding.

The same original reviewer owns the coherent correction, followed by required current-head CI, normal merge, sole-owner delivery and natural verification. Existing local and external-browser failures remain retained; the accepted frontend source and successful isolated native polling evidence carry without a duplicate source review or build.