[Task] Route source repository contributors to consolidated Core #8676

Program: #8194
Parent: #8216
Dependency: #8670 (accepted on main)

Outcome

Route new consolidated development from the Studio and Extensions source repositories to Core, preserving existing source history and the accepted 3.8/3.9 maintenance procedure.

Bounded scope

Prepare one small documentation PR per source repository: a prominent README contribution notice, plus an existing contribution entrypoint only where necessary. Link Core's product directory, contribution guide and attributed handoff register. Keep original contributor URLs and all runtime/build/publisher files unchanged. Adopt a matching existing PR if one appears.

Preparation estimate: about 30–60 minutes plus ordinary source-repository review/CI. Stop and reassess if this requires workflow changes or further policy choices. This task remains open until the exact approved source changes are merged and verified; preparation alone is not cutover completion.

Operational constraint

The current source main workflows automatically publish to Feedz even for documentation-only merges. The verified nonpublishing method used by source catch-up PRs Studio1125 and Extensions287 applies here: pass every required exact-head PR check and independent review, then perform a normal SHA-pinned merge with [skip ci] only in the final merge subject. Keep PR head commits free of skip markers. Reconfirm unchanged source bases/workflow inventory before merging, then verify actual parents/tree/subject and zero Packages runs for the new merge SHA after a bounded observation. Dynamic analysis may still run. This suppresses only the two new push-triggered publishers; it changes no standing publisher authority, maintenance policy, release/dispatch behavior or archival settings. Independent execution-plan review is APPROVE + HIGH. Do not expand this task into publisher implementation, end maintenance, or infer npm ownership.

Acceptance criteria

• Verify current source tips, contribution entrypoints, existing matching PRs and workflow effects.
• Prepare minimal source notices that accurately route consolidated work to Core while retaining existing maintenance and source contribution identities.
• Independently review the exact changes and pass the applicable repository PR checks, recording any unavailable gate honestly.
• Using the verified nonpublishing merge method after the authorized review/CI gates pass, merge and verify the notices in both source repositories; record exact commits and remaining archival actions.

No issue transfers/closures, feature implementation, package publication, repository settings changes, archival, Slack or React work is authorized by this task. Work exclusively in isolated worktrees. Lead owns integration, operational approval boundaries and final verification.

Accepted delivery

Both source contribution notices are accepted and merged after exact-head independent APPROVE + HIGH review and successful repository PR checks:

• Studio #1128: reviewed head 36a48d80453b9530eba17ffdf96e8ab086673df5, actual main merge dab6831ac11aa0d2caef93f39c8e705d9459bbaa. Hosted PR run 37827375367 recorded 1,911 .NET passes, zero failures/skips across 18 assembly/framework summaries.
• Extensions #288: reviewed head 12ab3e017d28e4854d9e8144fdf9f9498c21d0aa, actual main merge 2611ee6d9b6fb5e50f4c0b3fbc9cc15b355b4751. Hosted PR run 37827398894 recorded 539 .NET passes, zero failures/skips across 15 assembly/framework summaries.

Lead readback verified each actual merge's two expected parents, reviewed/tested tree equality, literal [skip ci] final subject, current remote main, and exactly README.md/CONTRIBUTING.md in the delta. No skip marker was added to either tested PR head. Fresh exact-merge queries and separate Packages-workflow queries observed zero Packages runs; platform-managed dynamic analysis runs did occur. This is bounded observation of these merge events, not universal publisher quiescence or feed-level proof. Existing release/manual-dispatch and future-push authority remains unchanged.

Studio's issue-route advisory was resolved using current Core issue creation policy ALL and interaction limit NO_LIMIT, with an evidence reply and independent confirmation. Extensions Copilot was requested once but produced no delivered review during the bounded watch; it is not claimed as passing. Its required independent exact-head review and CI passed under the source repository policy. Original hosted test logs were downloaded and parsed; no additional browser/runtime or package-publication acceptance is implied.

The notices route new development to Core and preserve the source contribution identities and existing 3.8/3.9 maintenance procedure. Task #8676 is complete. Parent #8216 and Program #8194 remain open for the selected maintenance/npm publishing replacement, source publisher retirement and verified archival. No settings, publication, issue transfer or repository archival was performed.