Repository navigation
[Feature] F2.2: Incremental import of extensions into core #8214
Description
Accepted source boundary — 2026-10-12
Source Program: #8740. Portfolio/history: #8194. The actual-main acceptance receipt verifies this source outcome on actual main 6179e6c360a1beeb01a717d6ef39fbc98a0e919a through normal PR #8751, preserving the reviewed tree and donor history. Native children #8275, #8286 and #8749 are accepted and closed.
All five product roots, source/release catch-up, attributed contribution dispositions, developer/build workflows and the source-of-truth cutoff are verified. Accepted earlier implementation and evidence remain intact.
Operational requirements remain open under #8741: #8216 contribution and maintenance authority, #8219 compatibility and release selection, #8220 candidate/artifact/publication/recovery, #8636 updater, #8643 full 3.10 Hosted/browser certification and #8725 release verification. Source acceptance grants no publication, deployment, publisher activation, retirement or archival authority. #8736 stays queued; no operational Task activates automatically.
The scope and older current-status statements below are dated provenance. The approved smaller-program boundary and this actual-main receipt govern current source acceptance; historical operational gates remain with their explicit owners.
Earlier scope and dated evidence (retained)
Current closeout boundary — 2026-10-08
Native children #8275 and #8286 are accepted and closed. Import story closeout records its six criteria and actual main 179749636fd4ddce07b186d4fe3456a43fa91162; #8655 and #8294 supply final-main runtime/build acceptance.
This feature remains open. Independent outcomes still include #8216 contribution/source-PR disposition, source3.10+ publisher guards preserving3.8/3.9 maintenance, exact-ref/in-flight quiescence, both Studio npm identities and publisher handoff; #8643 complete package-host/Hosted acceptance; and #8636 dependency-update/feed ownership and operational proof. #8220 retains a fresh candidate and separately governed publication/recovery/cutover. No publication, deployment, deprecation or archival is implied by child closure.
Original scope and earlier checkpoints
Program: #8194
Parent: #8197
Planning ID: F2.2
Outcome and scope
Migrate every Extensions module, test, sample, build asset, and relevant document; track active changes and preserve consumer contracts. Establish one publisher per package before cutover. Include Elsa Studio and paired backend/Blazor extensions; preserve history and active work in both source repositories.
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. The history-preserving import and release/source catch-up are on Core main through #8409 and #8624. Secrets compatibility #8275 and paired development #8279 are accepted at their recorded bounded scopes. The Mongo correction #8654 is accepted on the program branch; final-main verification under #8655 and the wider contribution/publisher-cutover outcomes remain open. Preserve prior import evidence and refine only the remaining acceptance gaps.
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.
Secrets compatibility implementation slice
- [Story] Resolve Secrets package and upgrade compatibility #8275 — package/API ownership and supported persistence transition. First task [Task] Reproduce the published Secrets SQLite upgrade from 3.8.1 to 3.8.4 #8276 characterizes the public SQLite 3.8.1→3.8.4 path before any schema conversion is designed. See evidence PR docs: map Secrets collision compatibility contracts #8274.
Activity
sfmskywalker commentedon Sep 29, 2026
Delivered: #8275 and #8286 are closed, and the incremental import landed on
mainthrough #8409 (8b34ab1e71c22c853e1aa340774231c80e92e677).sfmskywalker commentedon Oct 7, 2026
Reopened the parent rollup because child #8294 does not satisfy its final imported MongoDB atomicity and replica-set acceptance. Lead and independent audit. Completed history-import and other child evidence is preserved; this parent cannot remain accepted while the required child is open. #8294 is queued for correction; #8651 remains the sole active implementation Task.
Restore atomic MongoDB workflow definition updates (#8654) [skip ci]
sfmskywalker commentedon Oct 10, 2026
Source ingress refresh for Program #8194, observed 2026-10-10 17:34 UTC:
All 35 advertised Core/Studio/Extensions 3.8-family and 3.9 release refs are unchanged and verified as ancestors of Core main
570aaa95b09a7043273df2bcd4f533f216804694. Core and Extensions default heads are unchanged since the preceding refresh.Studio main received
d57fc46fd3605b7b2ee839306c7420a170c17ddd: nine previously blank Russian resource values. These are still blank in Core main and pending source-forward PR #8698. Exact comparison verified the Studio parent and Core resource are byte-identical (blob327ed4385ca229e096805316f8eba1153082a67f); the new Studio blob isc7e51c8a0e8368221e1ed2bc00d3ebfe12fcd59b.The carryover is prepared for
studio/src/framework/Elsa.Studio.Translations/Translations.ru.resx. Lead verification passed: the same 505 resource keys, only nine blank-to-translated values changed, literal source wording retained, XML valid, and temporary patch application reproduces the exact Studio bytes. This patch is unapplied and unmerged. Carry it into the final main integration and verify it before source cutover; original release-ref containment does not cover this later arrival.Task #8693 remains the sole active delivery Task; this ingress preparation does not start another Task or alter its historical release sources. PR #8698's ordinary PR tests and Packages workflow passed, with its consolidated proof still running. The controller's native matrix remains incomplete: Extensions 3.8 has a confirmed MySQL/EF dependency conflict under diagnosis, and the other five cells are running. No publisher activation, registry upload, deployment or archival occurred. Feature #8214 and Program #8194 remain open for their remaining outcomes.
sfmskywalker commentedon Oct 10, 2026
Source ingress checkpoint, 2026-10-10 21:10 UTC: fresh live refs and exact Git containment verify all35 advertised3.8/3.9 release branches/tags (including peeled annotated tags) as ancestors of Coremain
31450da77b4ea5719797719e50d4df1adf211dbb. All three repositories still advertise latest stable release3.9.0. Studio main remainsd57fc46 and Extensions main2611ee6; no additional code arrival was found. Core #8698's two mapped files match actual main exactly; Extensions contributor-routing semantics remain represented in consolidated guidance.The only missing source arrival is now carried by PR #8699, head
5a5e8eac42bb2381ea1fdee600e900d4d7a8d26e, with author-independent APPROVE + HIGH. Its Russian resource blob exactly matches Studio sourcec7e51c8a0e8368221e1ed2bc00d3ebfe12fcd59b: all505 keys retained, nine blank values filled, all other bytes preserved. Fresh hosted CI and Greptile are pending; shared/final-main integration remains required, so actual main synchronization is still incomplete. This source-ingress update does not close active selected-artifact Task #8693 or any publisher/archival gate.sfmskywalker commentedon Oct 10, 2026
Latest Studio source catch-up is now on Core main through normally merged #8703, commit3cc81c652906fc0e18a2ec0c6732308440f8c720. Nine previously blank Russian values from pinned Studio source d57fc46 are present, with one explicitly reviewed grammar correction; raw source bytes remain in #8699 ancestry. Exact-head459 approval, two lead passes, Greptile5/5, CodeRabbit and all25 terminal checks passed (20 SUCCESS/five expected SKIPPED). Independent/current-main integration review and lead post-merge verification confirmed actual parents/tree and preservation of the separate main documentation addition. Merge evidence. This accepts the bounded source update, not maintenance artifact, publisher or archival acceptance; #8693 remains the sole active delivery Task.
sfmskywalker commentedon Oct 12, 2026
Source acceptance complete on actual main
6179e6c360a1beeb01a717d6ef39fbc98a0e919athrough normal PR #8751. All required source criteria and native children are verified; see the requirement-by-requirement acceptance and activated cutoff receipt. Closing this source item as completed. Operational requirements remain open under #8741; #8736 stays queued, with no automatic activation or publication/deployment/archival approval.