[Task] Complete contribution routing and source issue/PR handoff for repository cutover #8670

Accepted on main — 2026-10-08

PR #8675 is merged at 8802a883d6069d689d110008c904787b3b691042. The lead verified a clean checkout of actual main, both expected parents (658a9da… and reviewed 59257dc…), and exact tree equality with the reviewed/tested candidate (412add1e4bf3c853b6a31e6773e7eb4f88aea012). Only the four reviewed documentation/data files differ from the accepted structural baseline. The three product roots remain present.

The durable register contains all 205 issues and 31 PRs from the two verified dated snapshots, with 236 unique source URLs/node identities. Its SHA-256 is 73eb0dcdc21c2178ffba06663c831f30d7d039e08c4eb49089b7d4f392dcf3f1, unchanged from independent review. The 17:54 refresh confirmed no source deltas before commit; it is not a freeze of future source activity. Refresh again before archival or individual source mutations.

Exact-head merge acceptance records independent APPROVE + HIGH, Greptile 5/5, resolved advisory review, passing CI and original-log verification. Packages passed 5,050 unit/integration and 227 component tests; the overlapping full PR suite passed 7,865 tests. Both retain 144 explicit skips. Package publishing was skipped.

All six criteria of this bounded record/instructions slice are satisfied. No source-side notices, transfers/closures, publisher activation or archival occurred. These operational actions and the pending maintenance/npm ownership decisions remain under #8216/#8220. The program remains open; Slack stays deferred and React discovery follows cutover.

Program: #8194
Parent: #8216 (under #8197)
Dependency: #8667 accepted on main
Related: #8219, #8220, #8636

Outcome

Make contribution ownership and the disposition of existing Studio/Extensions issues and PRs durable in Core before source-repository archival. Build on the accepted source/history/release catch-up and the completed source-only triage; do not turn unaccepted proposals into required feature delivery.

Scope

Refresh the current open issue/PR inventories and compare them with the 2026-10-08 snapshot of 31 PRs and 205 issues. Preserve original URLs, authors and exact PR heads. Adopt existing Core destinations where matching work exists. Record a linked destination or an explicit, justified archival disposition for each source item, including represented/superseded work, proposals retained for future scheduling and unresolved technical follow-ups. Do not claim an entire PR is implemented from a partial source match or a larger dependency version. Reconcile the existing migration ledger and contributor/release-owner instructions with the final product directory layout.

Use an isolated worktree and one focused PR. Reuse current accepted technical triage reports, with their source and runtime limits intact. Reconcile any source delta before publishing final records. Source issue transfer/closure or contributor notices must be concrete, authorized and separately verified; never silently discard original work. Release support policy, npm ownership and publisher activation remain explicit operational decisions in their existing issues.

Bounded delivery slice

Usable deliverable: one reviewed Core PR containing the complete attributed source issue/PR register and contributor routing instructions. Keep source URLs readable and state represented, partial and deferred work accurately. The prepared snapshot contains 205 issues and 31 PRs; refresh changes before committing.

Estimate: approximately 1–2 hours from activation, including review and the existing CI cycle, assuming the refreshed inventory is unchanged and checks pass. Reassess if a new source delta or requirement materially changes that estimate.

Boundary: this slice records the handoff and current Core contribution route. It does not implement the retained proposals, bulk-transfer or close source items, activate publishers, end maintenance support or archive repositories. Exact source-side operational changes remain in the subsequent verified cutover packet. Completion is the merged register/instructions plus the existing acceptance criteria below, not completion of the wider program.

Acceptance criteria

• Refresh paginated source issue/PR inventories and record snapshot identities, counts and deltas.
• Publish a durable Core register covering every inventoried item with original URL/author, exact PR head where applicable, justified disposition, and concrete continuation destination or documented retained-source reference.
• Verify candidate duplicates against their actual Core scope; preserve partial/unrepresented proposals and original attribution without asserting unexecuted runtime/security acceptance.
• Update contribution paths, issue/PR routing and ownership instructions for core/, extensions/ and studio/; preserve the decided maintenance/release boundaries without inventing owner decisions.
• Validate register completeness, links, uniqueness and destination state; independently review and pass the appropriate repository gates, merge and verify the final records on main.
• Record which source-side mutations have actually happened and what remains in the publisher/archival runbook. This task does not itself publish packages, deploy software or archive repositories.

Exclusions

No production Slack work, React Studio discovery, implementation of every open feature proposal, full compatibility matrix expansion or publisher activation. Those remain in their existing scopes. Keep exactly one active delivery Task; activate this only after #8667 acceptance and after checking for an existing matching task/PR.