[MashellHan]

Problem and result

The first installed focused Activities cycle published stale GitHub and ADO observations. A protected, read-only GitHub query reproduced invalid_profile_pr: GitHub echoed the exact requested partial-day window but also returned PR rows from before from on the same calendar day. The collector now validates all raw rows, pagination, totals, duplicates and account/repository identities, then credits only PRs whose createdAt is inside the exact requested window. Prior scoped days remain retained, while a completed focus can authoritatively correct today's count to zero.

A synthetic ADO detail timeout after a verified pinned prefix exposed a separate continuation loss. Retriable transport and HTTP 408/429/5xx interruptions now retain that prefix through restart; invalid proof and other HTTP statuses still fail closed. Fixed stage/status reasons and a bounded share of the existing 25-second provider budget make later sources progress without increasing the writer deadline. The protected adapters are exercised with synthetic HTTP, including exact focused query bounds.

Validation

• GitHub Profile Python 40/40; ADO Python 45/45; protected memory adapter 20/20.
• Final check:edit: 2/2 with stable inputs.
• Final check:ready: 37 files, 1377/1377 with stable inputs. It took 126.908 seconds, above the 120-second advisory target. The earlier ready 1377/1377 applies to the pre-inheritance source.
• git diff --check passed. Normal pre-push hook and current-head CI are tracked separately.

Limits

The initial natural ADO generic read failure remains unclassified. A later unchanged-helper cycle completed source 1 and reported head-changed-during-scan for source 0, which is a distinct event. No Backend live collector/cache test, extra remote probe, App build or credential fallback was used. Fresh end-to-end publication within 30 seconds requires natural current-head evidence after integration.

Follow-up to #748. QA-Handoff: 82f0e17

[MashellHan]

The original independent source review accepted head 82f0e17. Required current-head CI 43370087126 passed, and the normal protected merge produced 41ed54d.

That signed installation passed preservation and installed-reader reconciliation, but its first natural focused publication retained a stale GitHub source. The failed freshness evidence remains preserved. The initial generic ADO failure remains unresolved as to its historical cause.

The remaining Profile boundary failure was corrected by #752, normally merged as 6e8cd25 after the same original independent review and required CI. Its signed delivery is now accepted: the first natural primary publication took 10.3 seconds with all four source cutoffs current and no stale source. Installed API reconciliation and retained history passed; legacy subsequently completed and the original job exited successfully. The same 300-second schedule is restored and the reserved cut is released.

Known GitHub visibility limits remain explicit. This is one observed primary-publication sample, not a latency guarantee or a new live-screen timing claim. All earlier failed checks and stale publications retain their original provenance.