Repository navigation
[Feature] F2.4: Migration of contribution/release documentation and source ownership #8216
Description
Current program ownership — 2026-10-11
Delivery program: #8741; native parent is now #8198. Portfolio/history: #8194.
This mixed Feature retains all seven accepted children and their evidence, including source/contributor register #8670 and routing #8676; source Program #8740 links those accepted outcomes. Remaining maintenance/publisher/source-authority/contributor-final-inventory/cutover and archival requirements stay open here. Nothing is accepted or dropped by reparenting.
#8734 is accepted/closed via normally merged #8737 at actual main c46850de361cb84f267845ba66394c87262e2aab, exact reviewed tree64e. #8746 is now the sole active Task; #8736 stays queued Agent Ready/Pending. The owner-approved smaller-program split prioritizes the new Apps/Templates source milestones after finishing the already-active Task; it does not cancel operational obligations or authorize activation/publication/archival.
Current checkpoint — 2026-10-11T20:15:27.525758+00:00: #8734 accepted; #8746 is the sole active Task (In Progress / Assigned / Pending), with Sol6.1High in an isolated worktree performing the first source-mapping checkpoint before edits. #8736 is queued Todo / Agent Ready / Pending; no second implementation is assigned.
Earlier scope and dated evidence (retained)
Publisher preparation checkpoint — 2026-10-11 17:20 UTC
Publisher preparation correction in review: PR #8735 now targets the shared branch at 50e8beb03f04b249969bdf9d783653ad32a20a4a. Greptile's valid WASM-disappearance finding is fixed with a real failing-before/passing-after regression;102 affected contracts pass normally and optimized. Fresh exact-head author-independent APPROVE/HIGH and Greptile5/5 pass; CodeRabbit also reviewed this exact head without actionable findings. Integration/program and package-impact checks pass; only the full .NET compile/test remains running. Next hosted-custody Task #8736 is queued under8220, Todo / Not Ready / Pending and explicitly blocked by8734 acceptance on main. The prior c358 original-pair/clean-consumer proof is retained at its actual scope; pair/consumer helpers are unchanged. Task8734 remains the sole active leaf: In Progress / In Review / Verification Running. No merge, new producer, upload or authority activation is claimed. See the current Task evidence.
Owner decision — archival sequence, 2026-10-08
The owner selected option 1 in the delivery chat: archive Studio and Extensions after the Core maintenance and publisher handoff is verified, without waiting for the first full consolidated 3.10 release. The archive readiness boundary includes working Core maintenance and publisher capability, completed contributor routing, retired competing source authority and recovery instructions. The full 3.10 release follows as a separate deliverable with its existing applicable acceptance gates preserved.
This selects sequencing. Prepare and verify the concrete archival packet before requesting final operational approval; no repository is archived by this decision record. The earlier choices remain: preserve Studio/Extensions 3.8/3.9 release layouts/history on separate Core maintenance branches, and move both existing Studio npm distributions into Core publishing while preserving package names.
The full 3.10 browser/profile certification in #8643 is no longer a prerequisite to this archive-first sequence; its incomplete browser evidence remains explicit for the later release; the owner selected root-default routing with explicit prefixes. Dependency-update policy is resolved in #8636: coordinated Core/Studio/Extensions PRs are permitted when every affected product receives applicable CI and review. Its corrective implementation and operational inventory/version/feed proof remain incomplete. Refine bounded implementation Tasks against these selected outcomes, preserving the completed structural milestone and deferred Slack/React boundaries.
Owner decision — Studio npm publisher, 2026-10-08
The owner selected option 1 in the delivery chat: publish both existing Studio npm distributions from Core, preserving @elsa-workflows/elsa-studio-wasm and @elsa-workflows/elsa-studio-wasm-react. Move their paired build/pack and controlled publishing workflows into Core; retain exact same-run tarball/dependency validation. This covers the existing npm distributions and wrapper, not a new React Studio implementation.
Together with the preceding maintenance-home decision, Core is the selected home for Studio/Extensions 3.8/3.9 maintenance and the two Studio npm publishers. Implement and verify the replacement before retiring source authority. Actual registry access, publisher identity and nonpublishing artifact proof still need verification; the ownership choice does not itself prove those gates or authorize an upload.
The owner subsequently selected archival after verified maintenance/publisher handoff, before the first full consolidated 3.10 release. Publication and archival remain subject to their concrete execution/approval boundaries. No source publisher setting, credential, package version or repository archival changed as part of recording this decision.
Owner decision — maintenance home, 2026-10-08
The owner selected option 1 in the delivery chat: move Studio and Extensions 3.8/3.9 maintenance into separate product-specific branches in Core, preserving their existing release layouts and history. Implement the history-preserving approach prepared in the maintenance-home proposal. Existing Core maintenance branches must remain intact; source repositories may become read-only after replacement maintenance capability and operational cutover are verified.
This selects the maintenance approach and authorizes its bounded implementation and nonpublishing verification. It does not end 3.8/3.9 support or authorize a package publication or archival action. Studio npm publisher ownership was subsequently selected for Core; archival-before-full-release sequencing was subsequently selected. Preparation/verification estimate remains 1½–2 engineering days plus approval/access delays and any historical-build failures.
Current delivery — 2026-10-11T19:36:50.643184+00:00
Input-preservation correction #8739 merged normally into the shared branch as0240e8aa7f828fec57a1af1929288e5b327199c3, exact reviewed/tested tree64e27ff44d311ef8af9a01b738371465b91b3028. Main PR #8737 now has fresh cumulative author-independent APPROVE/HIGH, two clean lead review passes, Greptile5/5 at exact0240 and zero unresolved review threads. Main remains6d9c58045dfaa197ad8f53d03db773900551acbe; no Task acceptance or main merge yet.
Ordinary CI38168043752 attempt1 failed Compile in unchanged Studio ActivityWrapper.razor19 withRZ1021; Test did not run. Lead verified the entire current synthetic PR merge tree and SDK10.0.401 match the preceding successful644run. Cause remains unproven. Exactly one ordinary failed-job retry is running as attempt2/job114556320621; original failure remains retained and is not called passed. Remaining hosted CI/advisory gates stay required. Detailed checkpoint.
#8734 remains the sole active Task InProgress/InReview/Running. #8736 remains Todo/NotReady/Pending blocked_by8734 actualmain acceptance; its handoff is prepared. Current operational preparation packet records fixed original custody, selected maintenance refs and explicit later authority/retirement/archive gates. Actual644 anonymous original verification and actualc358 consumer replay keep their recorded scopes. Fresh35ref release ancestry and donor delta accounting remain accepted without claiming current donor-tip ancestry. Maintenance8693/allsevencriteria and MySQLdecision, independent product releases and fullprogram outcomes remain open. No publication, authority activation, source retirement or archival occurred.
Current delivery — operational cutover remains open
Structural consolidation and contributor routing remain accepted. Task #8683 is accepted through #8689; #8677 historical maintenance, #8679 paired npm preparation and #8688/#8692 individual-product planning retain their bounded acceptance. Actual Core main is 3cc81c652906fc0e18a2ec0c6732308440f8c720, including the normally merged Studio carryover #8703. All 35 release commits recorded in the latest source-release audit were rechecked as ancestors of that merge; this is not a new remote release advertisement.
Task #8636 is the sole active implementation Task. #8693 is Todo / Not Ready / Verification Pending while the MySQL/.NET10 support decision remains open; all seven acceptance criteria remain unchecked. Its separate controller #8694 is at 29147db1019bd583fd2a3631c2b647a39d80ae42, with independent APPROVE + HIGH, exact-head Greptile 5/5 and CodeRabbit complete; its final consolidated package-proof job is still running. The prior six-product native run failed: Studio jobs/original ZIP audits passed, Core and Extensions failed, and aggregate retrieval/readback were skipped. Passing controller CI cannot replace fresh native acceptance. Authoritative evidence.
Read-only GitHub settings refresh on 2026-10-10 at 23:16–23:27 UTC confirms Actions enabled in all three repositories and no release approval environment configured. Both sources have zero repository-level secrets, but all three repositories still have inherited organization Actions secret names FEEDZ_API_KEY, FEEDZ_API_KEY_BASE64, NPM_API_KEY and NUGET_API_KEY available. No values were read. Name availability does not prove registry identity, write scope or revocation; organization-wide visibility policy was not returned by these repository endpoints. Old workflow retirement or cancellation alone is not proof that loaded credentials have lost authority.
The four replacement Studio/Extensions maintenance refs and their protections remain unfinished. Core maintenance source corrections #8696/#8697 are prepared and reviewed but unmerged because their release-branch merge events would invoke legacy Feedz publication. Controlled NuGet/npm authority, dedicated approval/ref configuration, old plain/encoded credential containment, final inventory/quiescence, recovery and concrete archival approval remain required. Both source repositories remain unarchived. No publication, deployment, permanent maintenance activation, publisher activation or archival occurred.
Full 3.10 certification remains a later deliverable under the selected archive-first sequence. #8643's root-default routing choice is resolved; its browser/profile acceptance remains open. Slack expansion stays deferred and React Studio discovery follows cutover.
Current contribution checkpoint — 2026-10-08
Native Task #8670 is accepted through PR #8675, merged at main 8802a883d6069d689d110008c904787b3b691042. Its four documentation/data files preserve 205 attributed issues and 31 PRs, their dated source identities and bounded dispositions, and Core contributor routing. Exact-head reviews/CI and clean final main-tree equality were verified; acceptance.
Source-side notices/routing are now accepted under #8676 through merged Studio #1128 and Extensions #288, with exact-head review/CI and actual nonpublishing merge-event readbacks. This feature remains open for maintenance/npm ownership and verified publisher/read-only cutover. The owner has selected the maintenance-home option; see the current decision above. Implementation and verification remain pending. No source items were transferred or closed, no source settings changed, and no packages were published or repositories archived. Existing maintenance continues until an explicitly approved replacement is verified. Earlier checkpoints below remain historical evidence.
Program: #8194
Parent: #8197
Planning ID: F2.4
Outcome and scope
Update contribution paths, source ownership, SourceLink, issue/PR migration mapping, and release instructions; document old-repository cutover without premature archiving.
Acceptance criteria
- Deliver the specified capability and demonstrate each behavior above with targeted checks or documented research evidence.
- Preserve existing package/activity identities and supported contracts, or provide an explicit migration.
- Document setup, limitations, dependencies and verification results.
Readiness
Feature in progress. Accepted native child #8626 and subsequent #8631/#8635 provide consolidated package/source provenance and an immutable nonpublishing stable candidate. Contribution/release-owner instructions and the actual publisher handoff remain open under the accepted 2026-09-28 lockstep ADR. Refine remaining Tasks against the concrete cutover rather than redoing the source import.
Follow AGENTS.md, existing test/ conventions and dated ADRs under doc/adr/. Scope is Elsa 3 unless explicitly a portability assessment. Repository consolidation includes Core, all Extensions, and Studio; release boundaries remain explicit and independent.
Hierarchy: native parent/sub-issue relationships verified on 2026-09-23. Explicit blocking dependencies are configured separately; Markdown links remain references. See #8194.
Current cutover boundaries — 2026-10-06
- Source catch-up is merged through Reconcile 3.8/3.9 release history and refresh Studio and Extensions imports #8624. Fresh remote-ref/ancestry audit confirms all 35 advertised 3.8.x/3.9.0 release refs and both source main tips are included in Core main.
- Stable 3.10.0 candidate acceptance binds immutable artifact 11412848210 and the 225 package/symbol pairs. It proves preparation and representative consumers; the SQLite/default-tenant/built-in persisted matrices are accepted through [Task] Prove persisted SQLite upgrades against the accepted stable 3.10.0 candidate #8639/Prove persisted workflow upgrades against stable 3.10.0 packages #8644, while the complete paired compatibility proof remains [Task] Verify stable server and Studio packages across supported browser hosts #8643 and publication remains separate.
- The original repositories still need reviewed all-3.10-and-later NuGet publisher guards while preserving 3.8/3.9 maintenance, an exact-ref/in-flight-run quiescence procedure, and contribution/release documentation for Core ownership. The historical Slack-only handoff is not the first lockstep cutover.
- At this 2026-10-06 checkpoint, ownership of both Studio npm IDs was pending. The explicit 2026-10-08 owner decision above subsequently selected Core; actual paired artifacts and controlled publisher handoff remain separate verification gates.
- No package publication, live publisher cutover, legacy-package deprecation, deployment or repository archival has occurred in this delivery. Prepare the exact changes, evidence and rollback before requesting any required operational approval.
Source PR intake — 2026-10-07
Complete current head-set and disposition record retains 15 open Studio PRs and 16 open Extensions PRs. Studio #1126 is newly open; Studio #809 has an updated head and needs comparison with the current imported OIDC implementation and #8643. The program lead owns these pending migration dispositions. Existing contributor PRs are preserved, not silently merged, abandoned or replaced. Studio #1058 and Extensions #222/#223 are merged and verified ancestors of Core main. Final contribution migration mapping remains required before source archival.
Active contributor delivery — 2026-10-07
Native child #8653 is accepted through Core #8656, merged to the program branch at 9df90490eee034088b4341b149986de6b9d317b0. The original four mapped files preserve Gav's author identity and source blobs from Studio #1126 head 5379ea79fec28705ae888b75cf5f03993ad666f0; reviewed Core head is 68d0e48d1eca94c4bfe2f8d3db5ec3d70159d980. Merge parents and tree equality were verified. Source PR #1126 remains OPEN and unchanged for explicit contribution disposition; no source merge/closure or npm publisher change occurred. #8655 owns final-main promotion and post-merge verification.
Core #8656 acceptance includes exact-head Packages CI (4,870 unit/integration and 226 component passes; 145 explicit skips), 263 frontend tests/typecheck/bundles, eight source guards, nine natural browser cases and four mandatory handler-isolation controls. Independent source/runtime review is APPROVE + HIGH; Greptile 5/5 has no unresolved threads. Copilot was requested without a delivered review. Retained focused receipt. Earlier failed observer receipts remain retained. This does not complete broader contribution ownership, npm publication, source-publisher cutover or #8643 Hosted/package acceptance.
Activity
sfmskywalker commentedon Oct 6, 2026
Current delivery child #8626 is in review and full artifact verification through PR #8627. It supplies full-set packaging/provenance and representative package-consumer evidence without publication. This feature remains open: source publisher cutover, contribution/ownership migration and any remaining release documentation acceptance must be verified separately. Project status is In Progress; the parent is not a worker-queue item.
sfmskywalker commentedon Oct 6, 2026
Publisher inventory refinement: Studio still owns two npm artifacts, @elsa-workflows/elsa-studio-wasm and @elsa-workflows/elsa-studio-wasm-react, with same-run exact dependency pairing. Its automatic Feedz publishing is separate from its guarded public publishing. Core currently has no npm packaging/publishing replacement. The accepted first lockstep release ADR is expressed in terms of packable Elsa.sln/NuGet projects, while earlier consolidation guidance requires one publisher per npm identity too.
The owner is being asked whether the 3.10 cutover moves both npm artifacts to Core or deliberately retains Studio as an npm-only publisher. Do not disable Studio publishing before this boundary is resolved. The active package-proof task #8626 remains scoped to NuGet artifacts and does not claim npm evidence.
sfmskywalker commentedon Oct 6, 2026
Reconciled obsolete source publisher proposals against current main: Extensions #238 and Studio #1072 are closed as superseded by merged Extensions #274 and Studio #1117. Extensions #227 is closed as superseded for the first lockstep release by the accepted 2026-09-28 ADR. No draft was merged and no branch/publisher was deleted or activated. Core #8436 remains retained artifact-only proof for the later independent-release option, not the first 3.10 publisher. Each closure links its replacement evidence and explicitly preserves remaining cutover work.
sfmskywalker commentedon Oct 6, 2026
Native child #8626 is closed after #8627 merged into the shared program branch at
5b6b75fdd64a22d99ac4258311a29258b559055b. The full nonpublishing candidate proof passed for 225 package/symbol pairs, all 668 assembly/framework provenance entries and fresh package-only .NET 8/9/10 consumers; closeout evidence includes the exact tested head and artifact digest.This advances SourceLink/package provenance acceptance. It does not close #8216: current contribution/ownership and release instructions must be reconciled with the accepted first-3.10 lockstep decision and the eventual approved source-publisher cutover. The npm publisher decision remains pending. Persisted-upgrade proof is the ready buffer #8629 under #8219; release recovery and operational checks remain under #8220. No package publication, live publisher switch or repository archival occurred.
sfmskywalker commentedon Oct 7, 2026
Source PR intake refreshed on 2026-10-07 at 15:45 UTC through paginated GitHub REST reads: 15 Studio and 16 Extensions PRs remain open. This is a contributor-work disposition record, not source acceptance.
5379ea79fec28705ae888b75cf5f03993ad666f0fixes duplicate/stuck edge-remove tools. Preserve the existing contributor PR; review and map it into Core before final cutover. It has not been imported or merged by this refresh. The program lead owns this pending disposition under [Feature] F2.4: Migration of contribution/release documentation and source ownership #8216.dc02d1d321c97b655a90c1e42dd3ee2db3c3a7b6. Its redirect-prefix change must be reviewed against the current imported OIDC implementation and [Task] Verify stable server and Studio packages across supported browser hosts #8643; it is not evidence that the paused Hosted routing proof is fixed. Preserve the existing PR and contributor ownership.b38e7523f79297076e51701fd951c426145aa99c; they need no duplicate port.Snapshot SHA-256:
14a690d9de3ccd91182852235eb1220860fd9bddf8018f21f5bda62e496a8c01. Complete current open head set follows for durable traceability; all rows are preserved pending their existing review/ownership decision, not silently incorporated:5379ea79fec28705ae888b75cf5f03993ad666f0d5d7d1dabfea1a7bbbb698586b6528bb1ebdea5fe935ca2646f14c48d8b70e5dfb857713221ddd6c33d8c964231ca8b30cd9a23037f824cb2bea2a107d865818de0fa7ed72b7a1af4ff956da1d77592b74f8f1db182712663a7d4deaf3d94f40a0a3e4c8ee21aae4b15d4d73401b7f4df3c10b577fc9efbb7efc2faabb4787f17dde71cd75690ceb58cfda78dc02d1d321c97b655a90c1e42dd3ee2db3c3a7b655e75c8f11a438b97ad9d419a3dbcf439bd8804fbc5cb5f70338c6de84ecd7083e68133dc735003a21bba822b90bd540c2f6d2b03cc2dd21f1554cdd74e6fdb589851b4f5643bbb893c97a1371d59193fa7a4021370bd85bd68195e160e9a33bc124e485f457ed8a7c44e55785668c454fb9785e24e803eb3121af8f04e6d08afddfb21a8e1844a7cc745497c07d62ad77376a9aed2b07a64decb7fcfa778821c16e92bc36821ad76438687bf260ab5f88224519db6da257b9272eebbe045711d9bcc8fd3e45df668aca91af390ba9ace1d3de558a237d75665f0b674841e29e70acc4a8b29203c085b96e99c533fe7929e350e94256b97ee453dcb19effbe5fe170b15d73e9efd1a9a3491e04e2d43b784632ee2b2e28f8a7166e0b2d5bed1f8c8f48ef80e51b68b3fd0e23ff4661613ccea088f5fe68033ff154a7023dd5906ef525d00f2df16b05ce4dd79cbea50f174f6b1ecf5ff51dab4e8c01ba7aa73fc44877b4ff3346e8702ae372e8aafbe0061d6791a04c6234b3c851fa15bb3559d3c2a61c17d249edcca73dc1ed14e179GetRecurringJobIdsto prevent null reference exception6e199fde2f7e923030b16734da5f56a676a6355d380047e63b91902543fc973512d43e9c1622bafa#8649 remains the sole active delivery Task; #8651 remains ready and unassigned. This intake does not change publication, source-publisher or archival authorization.
sfmskywalker commentedon Oct 8, 2026
Retained-asset documentation reconciliation before feature closeout
The #8655 parent audit at
0da8146aaeaf35cb06feb1a7c87920cf3bb3df20verifies the authoritative JSON ledger has 163/163 explicitly disposed rows: 113 represented in Core, 50 retired from the active tree. Source pins and historical evidence remain preserved.The adjacent Markdown overview still presents the former 102 completed / 61 pending snapshot and former scoped-build/PR-workflow pending states as current. Its later links and authoritative JSON contain the subsequent decisions.
Keep this as an explicit documentation follow-up within #8216's contribution/migration handoff: reconcile the overview against the accepted decisions and current row classification, clearly label historical snapshots, and preserve each original source/decision receipt. Do not reinterpret asset disposition as publisher cutover, live package compatibility or closure of the 31 open source PRs. This editorial drift does not change the exact source or runtime gates of #8657, but must be resolved before claiming the broader feature/documentation handoff complete. #8214/#8216 remain open; no extra active Task is created.
sfmskywalker commentedon Oct 8, 2026
Source intake refinement for Studio #809, inspected at
dc02d1d321c97b655a90c1e42dd3ee2db3c3a7b6against Studio main3d028a4e9a3267b291f3d43d8064b5c81a6f2759and accepted Core main179749636fd4ddce07b186d4fe3456a43fa91162.Disposition: retain as an unresolved contribution requiring a reviewed narrow port or an explicit source-PR decision. Do not label it redundant or merge it wholesale. It is an unmerged proposal, not a missing released 3.8/3.9 change. This refinement does not activate a second delivery Task or require every open source PR to be merged.
The proposed legacy
RedirectUriPrefixoption is absent from Core's current configuration. The PR constructs the authorization and token-exchange redirect URIs identically, but a trailing prefix such as/workflow/yields/workflow//signin-oidc. Its three-file diff adds no tests or host changes; the source branch is diverged and GitHub currently reports conflicts.Any accepted port must preserve the current Core authorization service, including pending-state consumption, replay/expiry validation and local-return checks. The older proposed service lacks those newer protections. The separate Direct OIDC packages are distinct flows and do not prove this legacy change is represented.
Before calling a port complete, settle its supported host/proxy path model, test root/prefix/trailing-slash normalization and identical authorization/exchange callback URIs, preserve the existing invalid-state negatives, and observe a controlled browser authorization/callback/single-code-exchange/local-return flow. HostedWasm's existing base-path heuristic needs explicit coverage; URI string construction alone is insufficient. Preserve valid UTF-8 source during any port.
The 36-record package/browser matrix and required root/prefixed delivery under #8643 remain unchanged. This finding does not silently add every external OIDC mode to that matrix or settle the pending Hosted routing decision. #8658 remains the sole active Task; #8661 remains queued.
Independent source audit SHA-256:
1e0c8f2b797721c032efbaabc69a11a638bf04bdcfbf6d1b671bb4603307e5fc. Lead verified the seven exact Core source bindings and the proposed URI construction. No browser execution or authentication acceptance is claimed.sfmskywalker commentedon Oct 8, 2026
Source disposition refinement for Studio #1126: keep open as already adopted until the 3.8/3.9 maintenance disposition and contributor mapping are recorded. Preferred final disposition is closure as adopted into Core, unless a supported source-line backport is selected. Core promotion #8655 is complete and is no longer a closure blocker; no duplicate Core port is needed.
The credited Core port preserves all four original contribution blobs and Gav's authorship. That port, accepted #8656 head
68d0e48d1eca94c4bfe2f8d3db5ec3d70159d980, and the later stale-edge-leave (36c381e5460ca25d58eb542135772b033dd672f8) and read-only (249e98d672757a7960129cd86696f21eada52b9b) corrections are all in Core main179749636fd4ddce07b186d4fe3456a43fa91162. The current source PR is not the final corrected Core implementation, and Studio main still lacks the helper.Source PR acceptance is separate: its build/test run is
action_requiredwith zero jobs, and it has no submitted reviews. CLA/security/advisory status success does not supply source build/test evidence. Greptile reports the author is outside its allowlist.There is also a concrete publisher boundary: the current Studio Packages workflow uses base version 3.10.0 and automatically permits both NuGet and npm Feedz publishers on
push/release(lines 171 and 318). A main merge can therefore publish previews if its build succeeds. The public-registry dispatch guards do not disable those Feedz lanes. This audit neither accessed credentials nor observed or authorized publication.Before choosing a source-main merge, include the applicable Core corrections/regressions, obtain exact-source-head review and CI, and resolve the automatic publication consequences under #8216. Before closing as adopted, record whether supported 3.8/3.9 lines receive a maintenance backport and retain contributor attribution. Both Studio npm identities and publisher ownership remain explicit cutover work. No source PR was merged or closed by this refinement.
Independent audit SHA-256:
67c5fdf18b4db74e49698092c9c002f07a04bf812c50106b0345a6c508ec74b8. Lead verified the four relevant ancestry checks, original/current blob mappings and the source workflow publisher conditions. #8658 remains the sole active delivery Task.sfmskywalker commentedon Oct 8, 2026
Cutover preparation refreshed on 2026-10-08 while #8667 remains the sole active delivery Task. Slack #8666 stays deferred; React Studio discovery remains after cutover.
The source contribution inventory still contains 31 open PRs: 15 Studio and 16 Extensions. Every current head/base and all PR issue-comment streams were retained. Studio #1126 is already adopted through #8656/#8655; its source-maintenance disposition remains outstanding. Studio #809 remains an unaccepted proposal, not missing released source. No source PR was merged or closed by this audit.
Fresh, fully paginated source issue inventory contains 205 open non-PR issues: 137 Studio and 68 Extensions. Thirteen bodies have explicit Core references; these are related-work links, not assumed migration destinations. The other 192 have no Core reference in their body. Original URLs, authors, metadata and bodies were retained. Source comments/timelines were not exhaustively crawled. A durable destination or explicit disposition is required for the handoff; implementing every proposal is not an archival prerequisite.
The lead also compared ten dependency/source PRs against immutable candidate
5fda9fc597d56acd7db08a856534ef435d8a59c4:These are technical triage findings for the delivery lead, not new individual product-owner approval gates. The remaining maintenance-policy, npm publisher-ownership and operational cutover decisions retain their existing owners. No publication, transfer, closure or archival was performed.
Evidence retained locally: contribution inventory SHA-256
d10d5329d6150b2a01ade470392060ac43b85e9a9cd926cbd38983b31d2c4e68; full active-issue registerb526e2f1ff27b0247af95d724f25755e378e36af6295af1534098adbe080a39e; dependency comparisonsbcd1a922afb4f3ae30e07bd1560399e8d6dcca0730b17b09797eb5937ae7edad. These snapshots will need a delta refresh immediately before cutover.Completed technical triage coverage
All 31 open source PRs now have a bounded disposition assessment. The newer comparisons use
b117406d8e1436855c0ba25a2b4b943044b17002, whose tracked tree exactly equals the earlier 5fda comparison tree. This is source triage, not acceptance of unmerged functionality or final contributor cutover.The lead read all five bounded reports. Retained report SHA-256s: dependency
442ef4433e7ecd8ae8d2a14287f0f5c953b1c322c675b5bfa520e569e770dbc8; Extensions functional five986767c31aa1e81e33b281eeb5517aa7be07e95dd1ba002cb2658ceb4d5feb39; Studio functional fourbe104c3048caa8921e1c38ed3a540a37c371bb26a90ede4e7b9e56a4a52573a0; Studio remaining foured20f15b5155cad77f1e86bc11669a610269863b11877e689e35ce33c68ce05f; Extensions remaining six7aba6ef07a49cc007b962f3747dfcdc8b154639d5b712497c01b67b39eee568b.Next contribution work is to publish a durable, linked destination/disposition register for these PRs and the 205 issue records, preserve attribution, and reconcile source-maintenance instructions. No source proposal was closed, transferred or merged by this preparation. Publisher and archival gates remain separate; #8667 is still the sole active delivery Task.
A fresh semantic check of the 13 source issues with Core links found 14 links to 12 Core identities. All resolve, but none is a verified continuation destination for that source issue's remaining scope: these are related fixes, backend prerequisites or expressly deferred residuals. They must not be marked migrated merely because a referenced Core issue/PR is closed. Audit SHA-256:
32cdd0e32ddc50e168d2f859d41b68f0080cf44c758c8ef8476e2b6b54694771. A unified draft PR register also verifies exactly 31 unique identities (15 Studio, 16 Extensions), with no omissions or duplicates; SHA-256140c6e1d4d61904fe19dbd4820f0a8d8c77302ca76b261536a2b26c47886e1f0. Both are handoff preparation, not completed source-side migration.sfmskywalker commentedon Oct 8, 2026
Read-only preparation for the next operational milestone; #8670 remains the sole active Task. No ownership/support decision or activation is made by this comment.
The smallest identified option for retaining Studio/Extensions 3.8/3.9 maintenance after their repositories become read-only is to preserve their original release trees/history on separate Core maintenance refs. It avoids backporting the consolidated directory layout. Proposed provenance starting points:
9bff3f785fd13bd80a3a7ecf88fec4aec8eef7aemaintenance/studio/3.8.4a30ed7c997dfb3cff1d5d095a4ee19ff03c7fe42maintenance/studio/3.9.0154ba15fb4da85b4bebecfbe43639579cbda1d0dmaintenance/extensions/3.8.489d4eb9b739ae135604aac2a1de18653a289bdb0maintenance/extensions/3.9.0These are starting identities, not safe publishing branch tips. Prepare workflow-only containment descendants and reviewed controller/version/provenance checks before exposing remotely invocable legacy workflows. Core's existing release refs remain untouched; earlier source 3.8.1/3.8.2 refs are neither deleted nor declared unsupported. Preserve original history/tag identities without overwriting Core's same-named tags.
The inspected source workflows already supply the original build recipes: Studio 3.9 and Extensions 3.9. Reusing them unchanged as publishers would retain automatic Feedz paths, unsuitable version/event assumptions and repository-bound trust/credential assumptions. A Core-controlled, nonpublishing checkout/build controller can reuse the builders while those boundaries are prepared. New Core-only maintenance commits also need accurate package/SourceLink provenance.
The active Core workflow/action scan found no pack/publish job for the two Studio npm IDs. The existing Studio paired recipe is reusable: pack the WASM host, feed that same-run tarball to the React wrapper, then verify the exact pair/dependency. This is npm packaging preparation, not React Studio feature work. Registry ownership and publishing identity remain unselected and unverified.
Planning estimate: roughly one focused engineering day for controller/configuration/runbook preparation plus review, then half-to-one day for four historical build/pack paths and paired npm artifact validation if dependencies/builds remain healthy. Approval/access delays and historical build failures can extend elapsed time. This is a larger subsequent deliverable; it is not added to the completed structural milestone or the current contribution-register slice.
The existing maintenance/npm ownership decisions are still required before selecting this route. Preparation report SHA-256
09896b6eaa01f540910e9720ff9a03b9cd223a60ac3f5e9b6686fc255bc9244didentifies retained unpublished evidence. No refs were created, no build was run, no credential or setting changed, and no publisher or source repository was activated/retired/archived by this assessment.sfmskywalker commentedon Oct 8, 2026
Next ready delivery Task: #8679, native child of this feature, Todo / Agent Ready / Verification Pending / P1. It proves both existing Studio npm archives from Core, exact same-run WASM dependency and a real clean consumer, without publishing. Required ownership decisions are resolved. No matching open implementation was found; lockfile-only PRs #8672/#8659 remain separate and must be refreshed before claim. #8677 remains the single active Task; claim #8679 after its acceptance. Publisher/ref activation, all applicable maintenance npm paths and archival readiness remain subsequent required proof, not acceptance implied by npm packaging.
The current maintenance proof run37847789576 has allfour original-source jobs running on reviewed head db15079; no successful current-head proof is claimed yet.
sfmskywalker commentedon Oct 9, 2026
Follow-on maintenance capability is now explicit as native child #8683, queued Todo / Not Ready after the active #8677 and next-ready #8679. No second delivery Task is active.
Read-only source inspection at
cfcf178671f33909d7fa04a0435e41a9964ca549confirms that the four original release roots hard-code their former repository URLs, admission currently selects the original commits, and maintenance source-byte verification is local Git evidence. These are deliberately outside #8677's historical rehearsal: they do not establish truthful Core metadata or continuing admission for future Core maintenance changes.#8683 requires the smallest reviewed Core candidate/anchor admission path, actual package/PDB/remote Core source-byte proof, all four supported original-layout cells, and a subsequent reviewed maintenance descendant. Four frozen bridge proofs alone cannot complete writable maintenance support. Ancestry-only object exposure while preserving the consolidated tree is a candidate technique that still needs validation, not an adopted architecture. Permanent refs, publisher authority, recovery and archival remain separate concrete operational gates. Product-selective production releases remain required under #8217.
No release code, source refs, publisher settings, credentials or publication changed during this refinement. Existing owner decisions remain settled. #8677 still awaits its current main-integration gates; #8679 remains the next implementation Task.
sfmskywalker commentedon Oct 11, 2026
Read-only operational cutover refresh — 2026-10-11 02:04 UTC
The selected destination remains four separate Core maintenance refs: maintenance/studio/3.8.4, maintenance/studio/3.9.0, maintenance/extensions/3.8.4 and maintenance/extensions/3.9.0. All four are still absent; existing Core release/3.8.4 and release/3.9.0 remain intact. Raw source pins are provenance starting points, not safe public workflow tips; reviewed workflow-containment descendants and scoped protection are still required.
Core's current Studio npm-pair workflow is proof-only. Studio and Extensions package workflows remain active, and publisher secret-name availability remains shared through organization access. Names do not establish registry ownership, write scope or credential retirement. Correct repository environment enumeration shows Core copilot and github-pages, and Studio/Extensions copilot only; none has a required-reviewer protection rule or a publisher-specific approval environment. The first draft used an incorrect endpoint; this receipt uses the corrected endpoint independently checked by the lead.
The current action packet preserves all seven #8693 criteria verbatim and distinguishes selected destinations from completed handoff. Order remains: complete current #8636; resolve the MySQL/.NET10 choice and all #8693 proof; prepare protected contained maintenance descendants and the Core paired npm publisher; verify intended Core authority and retire competing source authority; refresh contributor rows/quiescence/recovery; then request explicit final archive approval. Source repos remain unarchived. Independent product releases and the later full3.10 work remain required.
Reviewed packet hashes: JSON78a0679673131529537d48314243272966836b99522a837b39de879a6ed747d1; Markdown0264ea7ee91cff6546b930d329209a6c2e8dce02350002f2ee205cc1c072fe63. Lead preparation review verifies exact seven-criterion equality and independently matches all three environment listings. This is evidence preparation only: no ref creation, permission/credential change, upload, deployment or archival occurred. Task #8636 remains the sole active Task; #8693 is Todo/NotReady/Pending and #8643 remains the ready buffer.