Repository navigation
[Task] Promote the verified consolidation checkpoint to Core main #8655
Description
Accepted on main — 2026-10-08
Final main acceptance verifies actual merge 179749636fd4ddce07b186d4fe3456a43fa91162, exact reviewed tree, all five focused main proofs, broad main Packages and both analysis workflows. All promotion criteria are satisfied within their documented scope. #8294 and #8286 are reconciled separately; #8214 and #8194 remain open. No publication, deployment, cutover or archival occurred.
Preserved scope and earlier evidence
Program: #8194
Parent: #8286
Related: #8214, #8216, #8294, #8654
Outcome
Promote the verified codex/elsa-integration-program checkpoint into Core main through a reviewed, history-preserving PR, then verify the merged main source. This owns the missing final-main integration gate for Mongo #8294 and its reopened parent rollups. It is a code-integration checkpoint; remaining release, publisher-cutover, pilot and operational outcomes remain under their existing program issues.
Readiness and sequencing
In Progress / In Review / Verification Running. This is the sole active delivery Task. PR #8657 now has head 0da8146aaeaf35cb06feb1a7c87920cf3bb3df20, tree 6ddb9a8dc1e22b97b4746c5fe5ab2f50c830e580, based on accepted Studio program merge 9df90490eee034088b4341b149986de6b9d317b0. Main/merge-base remains b38e7523f79297076e51701fd951c426145aa99c: 80 ahead and zero behind. All twelve accepted slice landings remain ancestors. The final two-file admission-fixture correction passes 80 affected tests normally and under an optimized 2030 ambient clock, with zero skips and verified cleanup. Lead independently passed 14 focused tests normally and with -O; independent scoped review is APPROVE / HIGH and reviewed/integrated trees match. Fresh focused runtime acceptance verifies 113 Mongo/BPMN, 857 execution and all thirteen Studio browser cases on this exact head, with scoped independent review and lead receipt audits. Broad hosted CI and final automated review are still running. Prior-head results remain historical; #8294 stays open behind post-main acceptance.
On 2026-10-07, main was b38e7523f79297076e51701fd951c426145aa99c, program was 23b852ad6262c4bf07b9f311090c892dbecd740b, and program was 58 commits ahead / zero behind. No matching open program-to-main PR existed. Refresh both remote refs, merge base, ahead/behind counts, existing PRs, board state and acceptance immediately before starting and again before merge. Adopt a matching PR if one appears.
#8294 depends on this sibling Task for final-main evidence. Do not add the reciprocal dependency: the precondition here is the accepted #8654 program merge, not closure of #8294. Keep #8294 open until the post-merge evidence below passes. If GitHub automatically closes it while promoting prior history, reopen it until verification is accepted.
Acceptance
- Verify the accepted Restore atomic MongoDB workflow definition updates #8654 correction is in the selected program head. Refresh the [Story] Build and verify the consolidated source workspace before history import #8286 gates for Secrets compatibility ([Story] Resolve Secrets package and upgrade compatibility #8275), packaging ([Task] Implement and verify the bounded independent-packaging proof #8260) and paired development ([Story] Prove paired backend and Blazor Studio source development #8279); retain scoped historical evidence and reopen any gate whose acceptance no longer applies. Reconcile other open program outcomes without treating them as delivered.
- Review the complete program-to-main delta and contributor/history ledger, including workflow changes. Preserve original source ancestry and contributor work; do not squash or rebase the history-bearing branch. Reconcile any newer main commits in an isolated worktree and rerun affected checks.
- Open or adopt the program-to-main PR with exact head/base/merge-base SHAs and links to accepted slice evidence. Hold for all applicable exact-head checks, including main PR
Compile Test, focusedmongo-atomic-proof, consolidated build/test, integration-program and package-impact checks. Record intentional skips and their reasons. Main currently has zero configured required-check contexts, so the platform's mergeable flag alone is insufficient. - Require lead integration review, independent Elsa 3 APPROVE + HIGH, and Greptile 5/5 on the exact candidate. Refresh review and CI after any source change. No administrative bypass.
- Merge through the PR with a history-preserving merge commit. Record both parents and tree SHA, verify main contains it, and compare the merged tree to the reviewed/tested candidate or merge-result tree. Explain differences and rerun affected gates before acceptance.
- Run the read-only
mongo-atomic-proofworkflow on the exact merged main revision, or retain equivalent exact-main hosted evidence. Require the two intended baseline regressions, complete Mongo project including all twenty CAS cases, ten BPMN consumer cases, actual replica-set/standalone topology and Mongo image identity, and net8/net9/net10 Mongo builds. Record exact source/input hashes, zero skipped acceptance cases and retained sanitized receipt identity. SQLite consumer cases do not substitute for Mongo provider proof. - After the Studio Fix consolidated Studio edge hover tools and prove browser behavior #8656 slice is included, run
studio-clientlib-buildon the exact merged main revision and accept its full ClientLib tests/typecheck/bundles and all nine natural real-X6 browser assertions plus four mandatory destination-handler isolation/negative controls, with the exact-head input/hash receipt. The supplemental controls must demonstrate real event order, old-A model/DOM button presence before target entry, successful clearing when delivered and rejection of that exact clear predicate when the destination callback is omitted. Preserve the prior failed observer receipts and the distinction from paused [Task] Verify stable server and Studio packages across supported browser hosts #8643. - Retain successful automatic main
Packagesunit/integration, component and build/pack evidence. Inspect every workflow triggered by the merge. Confirm no publisher/deployment dispatch, release/tag, production migration or source-repository action occurred. - After main evidence and review pass, close this Task and reconcile [Task] Preserve atomic BPMN edits in Mongo workflow definitions #8294, [Story] Build and verify the consolidated source workspace before history import #8286 and [Feature] F2.2: Incremental import of extensions into core #8214 against their own acceptance and children. Keep all other program outcomes accurately open; do not close [Program index] Elsa consolidation and generation roadmap #8194 from this checkpoint.
Workflow and authority boundary
The inspected program packages.yml runs tests and build/pack on main pushes; Feedz/NuGet publication and coverage deployment require explicit manual opt-ins. The consolidated publisher is also manual. Refresh these conditions against the actual candidate before merge. Do not dispatch publishing/deployment workflows or create releases/tags. Do not use [skip ci] to replace required checks.
update-wiki.yml automatically runs on main pushes and may open or update a wiki-only documentation PR. Record that run and its generated PR separately; merging its output is outside this Task. This existing documentation automation is not package publication or deployment and does not itself require an additional approval step under the program's current merge authority.
Work exclusively in isolated worktrees and preserve existing user changes. Use Sol 6.1 for integration and bounded Luna 6 Extra High review where suitable; final integration/QA stays with the lead. Use hosted heavy verification while the local host remains overloaded. Package publication, source-publisher cutover, deployment and archival remain separately governed outcomes.
Integration-review corrections awaiting hosted verification
CodeQL check 113066924718 on prior head 9df90490eee034088b4341b149986de6b9d317b0 found an unescaped-dot hostname regex. Both dots are corrected at 5d79ef9876e8f9148ee8a341a851434cd8bed8bb with rejection-before-child/count regression coverage and a legitimate-host control. The separate Authorization prefix guard was stricter; no credential-disclosure claim is made. CodeRabbit's checkout credential persistence and Extensions inventory findings are also corrected.
The two fixed-original-artifact upgrade lanes no longer trigger on every matching main push because their inputs expire. Both retain codex/manual triggers and strict expiry/identity/full-matrix checks. Before acceptance, explicitly dispatch BOTH prerelease and stable persisted-upgrade workflows on the exact merged main and independently audit all six cells per lane, run/attempt and artifact hashes while the originals remain valid. Missing/expired inputs are failures, never skips or silent replacements. This supersedes the earlier automatic-main-trigger preflight detail and preserves required verification.
No main merge or publication is accepted while fresh exact-head CI/review gates remain pending.
Synthetic-fixture clock correction awaiting hosted verification
Greptile comment 4213116343 is corrected at 5d79ef9876e8f9148ee8a341a851434cd8bed8bb with a shared test-only clock and controlled-2030 success/restoration regression. Lead 79 affected tests passed normally and with -O; independent source review returned APPROVE + HIGH after two clean passes. Executor/stable expiry negatives remain; production artifact identities/expiry guards are unchanged. Fresh final-head hosted CI/CodeQL/Greptile are pending; prior-head results do not replace them.
Admission-fixture completion
At 0da8146aaeaf35cb06feb1a7c87920cf3bb3df20, synthetic admission tests also control the actual candidate-validation clock. The retained 2030 regression now exercises five actual success paths, including approval and pre-scheduling. Both modes still reject historical expired candidates before environment/approval metadata checks. Only two test files changed; production constants, artifact identities, expiry guards and workflows are unchanged. The old 5d79ef98 CodeQL and Greptile 5/5 results, focused proof receipts and completed broad test runs remain historical. Two still-running superseded package jobs were cancelled after pushing the correction; fresh-head checks govern acceptance.
Activity
sfmskywalker commentedon Oct 7, 2026
Read-only promotion preparation at the current accepted checkpoint: main
b38e7523f79297076e51701fd951c426145aa99cis the merge base of program23b852ad6262c4bf07b9f311090c892dbecd740b, which is 58 commits ahead / zero behind (92 files, +16,745/-122). No additional concrete unreviewed slice was identified in this bounded audit; this is not final-main approval.The ten landed slices below cover that first-parent progression. Lead independently verified every landing is an ancestor of the checkpoint and its tree equals the reviewed source tree. #8630/#8632 are historical single-parent landings; preserve their existing history. Future promotion must use a history-preserving merge.
44083dc4f47d56aa2d5c215b0c7479c0b7290cb05b6b75fdd64a22d99ac4258311a29258b559055b9c3a74a30e62b7150b435225cac2eafe9976126a3413534be6803d81616ca1da1703ca8582512cafa5b1eb711c30331e0708719e1090bae4d280e6f9e69d92f57de4546a4dd9fd4015d8b8eeba7d1b92ba5b348aa2414fdf7c19d9d8806e87b7c91a4205fc967930ac2b47895a4231e4f12352ec6dd955b7488122d37164e8de77ef68c52f7467bf8e4f85ae93d9135deacafa60c94e0e39b624cf738e1d16dd7435c03446c4a748f5aa8bf5238b0f9534792ff3306cbaf5465f7d54d2876b5e4b8a4b6e3a12824b08a8e741c03ffc5e4a823371ec679fbab0cde01ce5b47b0d1c782d59009548cc5f17b9b0e374dd871b3885f21395bc3b9bbe57de7541ceeece43e9018876428f472f3cf22957bec35302ee2470644dc9db6157125ab70361030c0d24e3be99737d7237e8702376b501439e5244a0db8728d12b9da86eb5d95dee771bb7bb497147a47d71aab6a39e5275e62723b852ad6262c4bf07b9f311090c892dbecd740bScope: consolidated package/provenance and consumer proofs; paired-source replay; prerelease and stable SQLite upgrade proofs; immutable candidate/recovery/publisher-admission preparation; Dependabot discovery reconciliation; and execution-cycle ownership across Core/Runtime/Alterations/ProtoActor. Most changed lines are proof/release tooling, workflows and documentation. The original stable artifact remains bound to its own older source; no newer source is implied to be inside its bytes.
Pending Mongo #8654 (
ce99df5c48de6ae3f5086572bbe48956669fdbf1) and queued Studio #8653 are excluded from this accepted-range inventory. Refresh and include their accepted commits when selecting the eventual promotion head. The final head still needs full combined-head CI/review, merge tree/history verification, exact merged-main Mongo and Packages evidence, and inspection of all triggered workflows under this Task's acceptance.Existing operational gates remain separate: #8220 live publisher authority/quiescence/publication/recovery/cutover; #8636 dependency-update ownership/feed acceptance; #8643 paused Hosted routing/browser acceptance. Historical slice proof and intentionally skipped merge CI do not satisfy the final-main gates. #8294 remains the only active delivery Task; this integration Task remains queued.
Restore atomic MongoDB workflow definition updates (#8654) [skip ci]
sfmskywalker commentedon Oct 7, 2026
Readiness pre-review while #8653 remains the sole active Task: independent Sol 6.1 Elsa 3 APPROVE + HIGH for the prospective cumulative source diff, base
b38e7523f79297076e51701fd951c426145aa99c→ candidate2bec5492c234c2f9a4c7300cd6f70fd7cd0cb3a3, treea0a4d6c0e8c502ea85b53e0c05b84693cc4f9329. The lead retains final integration/QA. This is preparation, not promotion or merge acceptance; candidate #8656 still awaits its remaining gates.The reviewer independently confirmed 72 commits ahead / zero behind, 112 changed files and 11 workflows, and found no actionable cumulative source defect across execution ownership, Mongo full-snapshot transaction/tenant preservation, Studio hover/read-only integration, package opt-ins/inventory exclusions and the fail-closed publisher boundary. No fresh binary/API compatibility proof was performed. All exact main-PR checks, Greptile, final head binding and post-main runtime evidence remain required.
After #8656 lands, verify the actual program commit/tree and refresh base/ancestry. Its merge message will omit
[skip ci]so the prospective main PR head cannot silently suppress CI. Main has zero configured required contexts/review count; the project’s explicit gates remain mandatory. Main push does not publish or deploy; existing wiki automation may update its separate PR. Mongo and Studio have no main-push trigger and require exact merged-main dispatch/readback under this Task. Broader Packages tests exclude imported provider/browser paths.Workflow readiness also verified that pinned original proof artifacts remain unexpired: prerelease 11390805430 through 2026-10-13T04:26:20Z and stable 11412848210 through 2026-11-05T12:13:30Z. Recheck before use. Original stable bytes predate the newer source fixes, so #8220 now explicitly owns a fresh release candidate and its own compatibility/publishing acceptance; none of the original byte-specific evidence is silently transferred.
Merge PR #8656: consolidate Studio edge hover correction and browser …
sfmskywalker commentedon Oct 8, 2026
Main promotion landed; exact-main acceptance is running
PR #8657 merged at 2026-10-08T01:12:20Z as
179749636fd4ddce07b186d4fe3456a43fa91162. Parents areb38e7523f79297076e51701fd951c426145aa99cand0da8146aaeaf35cb06feb1a7c87920cf3bb3df20; tree6ddb9a8dc1e22b97b4746c5fe5ab2f50c830e580exactly equals the reviewed/tested candidate. The premerge gates and artifact audit passed before an ordinary history-preserving merge.Five explicitly dispatched workflows report this exact merge SHA:
Automatic main Packages and the other triggered checks are also being inspected. Package-publication gates already passed; no publishing/deployment workflow was dispatched. The automatic wiki run and Dependabot activity are tracked separately.
GitHub auto-closed #8655 and #8194 at merge despite outstanding acceptance. Both were immediately reopened and their project statuses restored to In Progress. #8655 remains the sole active delivery Task, In Review / Verification Running. #8294 remains open and inactive pending exact-main proof; #8658 remains Todo / Not Ready / Pending behind #8655. No parent or program completion is claimed.
sfmskywalker commentedon Oct 8, 2026
Exact-main focused proof acceptance
All five manually dispatched proof workflows passed on main
179749636fd4ddce07b186d4fe3456a43fa91162, attempt 1. Independent scoped audits and lead receipt/hash checks passed. This is a verification checkpoint; automatic main Packages and remaining analysis checks must still finish before #8655 closes.Receipt SHA256 values, in the same order:
04c6fded94cef48097c7eee06ed79c52eb67ae159f1ccc2e81afa297b85f868205d3b56002e8bd8445d79a5f1419ce697b9f40717580fa9e00a44ed7097e3d7baaa6b315920fd61b1839b6153ae2003c3c4122e5dd41b7996616301dbbe476d3210eb072447de69ab338f518ef56570fc427278c3dfdffb2ab912b3d8a43ed90fcdd3a966ed840dc23ab0bccf40def47c183433abc79c53588943e9d9d687445Downloaded ZIP SHA256 values, in the same order:
00b9f9a53bd540347546360696f8b6bbc5fe1e9c6534c4759b7f7c99f6069c822ff7360776795c2625474288f2fc93c5512e64626699ab534c84a4644cad8197e466bc67567eb5ffdd9e2ee12ee1876736a82b229ce9cd320f792e0a028c56a8354d179887c29e7a13398b120e3cb92e28b7fd976fcc3e6a2f4bcd3a9630c860bbf33f947c3e4ec13a5c4b9f0fe3a06b7aa3272631d36d56d63914bfddaeae76The runtime/browser artifacts expire October22; upgrade evidence expires October15. Both original inputs remain the exact unexpired immutable archives: prerelease11390805430 from
44083dc4and stable11412848210 fromba5b348a. Each upgrade matrix covers 3.8.4 and3.9.0 across net8/net9/net10. All336 candidate loaded-assembly observations match the original packages. These runs execute current main fixture code against historical original binaries; they are not a fresh release candidate or proof of every provider/customer workflow.Studio's four supplemental controls independently retain actual event order, old-A model/DOM buttons before target entry, successful clearing when delivered and failure of that exact predicate when omitted; vertices remain. Installed dependency byte evidence comes from the current guarded runner and pinned lock owners. Full host/browser work under #8643 remains separate.
Automatic wiki run37711745142 passed wiki-only and link validation, updating existing #8610 at
2dd8dd031d16659c4969abf62eaf111a9b17c29b(one doc/wiki file). Automatic npm security updater37711764918 passed and opened #8659 atf6a3da31649e3543d9aa6d80285215f55535bf8d. Neither PR was merged. That npm result does not satisfy #8636's separate NuGet ownership/discovery/feed criteria.No package publication, deployment, source cutover or archival was performed. #8655 remains the sole active Task; #8294 and #8194 remain open, and #8658 remains queued behind acceptance.
sfmskywalker commentedon Oct 8, 2026
Main promotion accepted
PR #8657 is accepted at actual main merge
179749636fd4ddce07b186d4fe3456a43fa91162. Its two parents areb38e7523f79297076e51701fd951c426145aa99cand0da8146aaeaf35cb06feb1a7c87920cf3bb3df20; tree6ddb9a8dc1e22b97b4746c5fe5ab2f50c830e580equals the exact independently reviewed/tested candidate. Source and contributor histories remain intact.Premerge acceptance records all exact-head CI, two clean independent Elsa3 APPROVE/HIGH passes, Greptile5/5, resolved threads, 225-package provenance/consumer proof and fresh release/source intake. Post-merge focused acceptance records all five exact-main runtime/browser/original-upgrade workflows and independent plus lead artifact audits.
The remaining main Packages run37711745275, attempt1, has now passed:
3.10.0-preview.5842). Uploaded artifact11523425853 was observed in the successful job log; no independent archive audit of this103-package output is claimed or needed to replace the separate225-package proof.Independent broad audit is APPROVE/HIGH; lead independently verified the64 result rows/counters, build log/source and terminal workflow state. Audit SHA256
98a74aadc0e4ec0a3afdd89faee238db3bf80e78ad86eafcfafd8e964216b7a3.Every merge-triggered workflow has been inspected. Automatic wiki run updated #8610, and npm security updater opened #8659; neither PR was merged. GitHub's repository setting automatically deleted the merged program branch; the lead restored
codex/elsa-integration-programat reviewed0da8146. Its redundant restoration-triggered Packages run37713642360 was cancelled; authoritative main run37711745275 completed successfully. The program branch can now fast-forward to accepted main for the next slice.This closes #8655's promotion acceptance and supplies #8294's exact-main gate. The lead will reconcile #8286's six criteria and native children separately. #8214/#8216/#8220/#8194 remain open for their remaining migration, release, source contribution, publisher, pilot and operational outcomes. Historical original upgrade artifacts are not a fresh candidate for these fixes. No publication, deployment, source-publisher cutover, production migration or archival occurred. Copilot review was not delivered and is not claimed.