[Program] Transfer Elsa 3 releases and retire source repositories #8741

Activity

1. sfmskywalker

   added a sub-issue on Oct 11, 2026

   • [Epic] E3: Independent versioning, packaging, and compatibility #8198
2. sfmskywalker commented on Oct 11, 2026

   

   sfmskywalker

   on Oct 11, 2026

   MemberAuthor

   More actions

   Apps source-import handoff from #8746 / PR #8747.

   CodeRabbit identified the following inherited behaviors for later bounded Apps maintenance and publication/deployment review. Independent readback confirms all five files still match the original donor blobs; source consolidation preserves these files and records the observations. Focused reproduction should establish the actual affected configurations before a support or security claim is made.

   • Database fallback: the shared connection-string fallback is SQLite-shaped even for another selected provider. The source gate verifies SQLite/default; broader provider acceptance remains separately owned.
   • NGINX caching: inspect immutable caching of stable framework/content URLs during an image upgrade.
   • Standalone WASM backend default: preserve the localhost default and verify/document remote deployment configuration in a dedicated follow-up.
   • Backend URL serialization: assess JavaScript-context serialization of the configured backend URL in the retained host page.
   • IIS Express launch path: inspect the retained /swagger launch URL on the Studio host as a small developer-path follow-up.

   Existing OIDC source issue elsa-workflows/elsa-apps#3 and the recorded ApplicationInsights/Pomelo warnings remain explicit. HTTP-container redirection is part of the pending exact-head image smoke evidence; no unexecuted check is called passing. These observations do not transfer publication, registry/trust, source retirement or archival authority, and no source behavior fix or operational acceptance is claimed by this handoff. The lead will finish #8740 source acceptance independently of later #8741 delivery.
3. sfmskywalker commented on Oct 11, 2026

   

   sfmskywalker

   on Oct 11, 2026

   MemberAuthor

   More actions

   Apps source-import handoff from #8746 / #8740 to operational owner #8741, particularly candidate/publication/recovery #8220:

   The accepted original candidate/archive inventory is 225 packages and 124 exclusions. Its immutable artifact identity, original evidence, executor, approval-summary and recovery guards remain preserved. An attempted addition of nine Apps nonpackable exclusions to that same baseline broke the original-artifact helper contracts; that source-task change is being reverted, without changing historical validators or fixtures.

   Apps' nine projects are independently built image consumers with IsPackable=false. The ordinary nonpublishing package-proof workflow can record their current exclusions without comparing the historical candidate baseline. Its fresh final-head evaluated inventory remains a source CI gate; no evaluated final inventory or full release candidate is claimed yet.

   Before a future candidate preparation/release, explicitly reconcile the current-solution inventory with the original baseline (Apps currently adds nine exclusions, expected 133 versus original124). Keep the original archive contract immutable and version/select the new candidate's inventory/evidence coherently through preparation, approval, executor and recovery. Do not merely raise the old archive counts or attach its original evidence to newly added rows. Include the subsequent Templates source disposition when defining the actual future candidate scope.

   This is retained operational work. #8740 neither prepares/publishes that candidate nor claims this future candidate gate accepted. It must not expand source acceptance into full release delivery. Repository source/build/nonpublishing CI still must pass independently.
4. sfmskywalker commented on Oct 11, 2026

   

   sfmskywalker

   on Oct 11, 2026

   MemberAuthor

   More actions

   Measured source-proof clarification for #8741/#8220: Apps PR #8747 is accepted on shared merge 1d5bc1e1deaba8f2d90920109061a3504a945106; actual-main source closeout remains with #8740. Native proof38179158250 at exact dc27edc05f83ecd8feb18d894a501e0694774d98 measured 232 current packages and132 exclusions, including all9 Apps projects as nonpackable. Artifact11717839407 SHA256 7671f492594cafb76689811e6533e4a084984ecd53c44855f04d48345cb86ea7; receipt published=false, source inputs unchanged, remote SourceLink/SDK metadata verified, representative and6 admission consumer cells passed. Actual SDK10.0.401 andNode22.23.3.

   This corrects the earlier forecast of225 current packages/133 exclusions. The original historical candidate baseline225/124 and its strict archive/recovery/approval identities were restored unchanged and remain protected. Ordinary current-source proof succeeds independently of that historical baseline. Future candidate preparation must compare/version the then-current inventory, including subsequent Templates disposition, and preserve old archive compatibility. This remains explicit operational work under #8741/#8220; no baseline rewriting, publication, cutover or retirement is accepted or performed here.
5. sfmskywalker commented on Oct 12, 2026

   

   sfmskywalker

   on Oct 12, 2026

   MemberAuthor

   More actions

   Templates source-import advisory handoff from #8748 / PR #8750. These findings are retained source behavior, not introduced runtime changes or claimed production certification.

   • CodeRabbit Monaco finding: both combined WASM host pages retain the original donor loader scripts without an explicit editor.main.js reference. A browser reproduction and any required correction belong to runtime/release verification here. Generated-output compilation does not prove browser editor initialization.
   • CodeRabbit signing-key finding: original server/combined settings contain placeholder static and shell JWT signing keys with Development overrides. The unchanged server startup binds these settings without an explicit production placeholder rejection. Before production use, configure deployment-owned secure secrets at Identity:Tokens:SigningKey and CShells:Shells:Default:Features:Identity:SigningKey. Production guard implementation and verification remain required follow-up work under [Program] Transfer Elsa 3 releases and retire source repositories #8741; the source import does not certify production safety.

   The lead independently verified seven relevant original/current asset blobs against donor main 891759727db053a37911b616ace4a5599e1005d0: both combined WASM pages, server Program, and server/combined base plus Development settings. All seven are byte-identical to the donor. Current Templates guide and product README explicitly document these limitations. Original source/history and supported build matrix remain preserved. No browser runtime, production token-forgery guard, deployment, publication or retirement proof is claimed.

   The independent Templates package/release boundary and publisher decision remain under #8725 and #8741. Source Program #8740 will require corrected exact-head starter pack/install/generate/build CI, review and final source freshness; it will not silently present these inherited operational findings as fixed.
6. sfmskywalker commented on Oct 12, 2026

   

   sfmskywalker

   on Oct 12, 2026

   MemberAuthor

   More actions

   Clarification to the Templates advisory handoff above: the later CodeRabbit assessment reports repository-side options validation and uncertainty about how the released3.9 consumer dependency enforces it. The verified source fact here is byte identity of the retained template settings/startup assets and absence of an explicit check in those starter Program files. This is not proof of unconditional exploitation or that the dependency lacks validation. Before adding a production guard, verify the exact released dependency's existing startup behavior; harden only what that evidence shows is missing. The documented requirement to supply deployment-owned secure keys remains valid. Source import still makes no production/runtime certification claim.
7. sfmskywalker

   added a commit that references this issue on Oct 12, 2026

   Retain final Studio and Extensions donor history for source cutoff

   ...

   d3ed761
8. sfmskywalker commented on Oct 12, 2026

   

   sfmskywalker

   on Oct 12, 2026

   MemberAuthor

   More actions

   Final source-review handoff from PR #8751

   Recorded operational handoff; no operational action is activated here. Evidence targets 3b977a5bc2554463b55afdb21a0d733a215c1e94. The source goal preserves released Elsa 3.9 consumer behavior and original donor evidence; it does not certify production deployment or modernize inherited runtime behavior. Owners #8219 and #8643 retain the following explicit checks and any separately reviewed fixes:

   Finding	Source-grounded boundary	Required operational follow-up
   Apps public JWT signing key, comment 4244154256	All three Apps server settings files are exact original donor blobs (86b6adbfae74270061b6f45ad20f9975cee2ccc9, 24331a83f7e73838566c8d6d6d6bca11bae3338a, 17bab0e34ef6badd66afa0d96f46dac4c8bf36eb). They retain the same public 40-character default key.	Require a deployment-owned secure signing secret and verify default-key rejection/configuration with the actual released 3.9 identity packages and selected deployment. The risk is conditional on a deployment retaining that public key. Static source comparison is not proof of a deployed exploit or released-package validator behavior.
   Standalone Studio server non-Development compression, comment 4244154285	Original 60963cfea2ac718c619f25e42745b830a77aad3f and current 6e641f701ded9457e129521c77295141906990d0 both call UseResponseCompression outside Development without a direct AddResponseCompression call. The current diff contains only the accepted custom-element namespace/registration additions.	Exercise Production/Staging startup against released 3.9 dependencies, inspect effective service registration and apply the minimal registration fix if required. Generation/build proof does not establish runtime startup or transitive DI behavior.
   Hybrid IDE solution composition, comment 4244154280	Original solution blob 8a3c9aa11797fe9e827bbdd94b16c06135ef73dd lists only Host for hybrid. Original Host project a7df77e08a4b3fe3c02b912ae667e4848463971d references Wasm. Native hybrid cases compile that project closure.	Verify intended IDE composition and add explicit Wasm solution membership if needed; this is not a missing compiled project in the accepted hybrid build.
   Retained standalone legacy host, comment 4244154270	templates/Program.cs remains original blob 734b9c8b8b41115f4d9195341ea91946dd9feb4d, outside the supported product solution/starter matrix.	Reproduce any authentication/middleware-order defect with the pinned CShells 0.0.28 path before selecting a fix. Current graph source is not released-package runtime proof; endpoint-mapping call order alone is insufficient.
   Combined WASM Monaco, comment 4244154274	Both pages retain original blobs df040c473f53d7b3200eb2f9db028bc0f2dfc092 and 00f29e7338babcd637cc5f323d66e7c884f83bc6, with loader.js but no editor.main.js.	Continue the existing browser-runtime handoff (#8741 (comment)) and verify editor initialization before runtime certification.

   The verifier ref-name/main-count guard and fixture stderr-draining comments are future hardening items. Current 17 ref-name/SHA/type/commit tuples match the retained intake; independent Git reads confirm 29 source-main commits and 41 commits across the retained ref union. Those are different counts. The original stderr pattern is retained; fixed git rev-parse HEAD succeeded in native source validation, with no claim about every failure mode.

   No introduced regression was established by these inherited findings. This handoff does not waive exact-head source CI or grant publisher, deployment, registry, credential/trust, support-policy or retirement authority. Production identity and browser/runtime proof remain separate from source adoption.

   Lead independently rechecked all11 supplied blob records and the29 original-main history count. Source acceptance remains pending finalCI and actual-main merge/readback. This handoff does not add full3.10 certification as a new prerequisite to the owner-selected archive-first sequence; each affected deployment/profile retains its own verified acceptance.
9. sfmskywalker commented on Oct 12, 2026

   

   sfmskywalker

   on Oct 12, 2026

   MemberAuthor

   More actions

   Source Program #8740 is complete and closed, with its Task #8749 → Feature #8214 → Epic #8197 accepted and closed. Board #52 records these source items Done / Accepted / Passed. The final actual-main acceptance receipt and activated source cutoff is the authoritative requirement-by-requirement record.

   Normal PR #8751 merged at 6179e6c360a1beeb01a717d6ef39fbc98a0e919a, preserving the exact reviewed tree and source/history evidence. Main has core/, studio/, extensions/, apps/, templates/; relevant 3.8.x/3.9.0 releases, later donor refs and outstanding contributions have recorded coverage/dispositions. New Elsa 3 development belongs in Core/main; later donor arrivals need dated, attributed Core continuations. Existing 3.8/3.9 maintenance procedures remain until their approved replacements are verified. No donor has been archived or made read-only.

   Exact-head independent reviews, Greptile 5/5 and applicable CI passed. Final main CI also passed: 15 successful checks and six conditional skips, with no failures or pending checks. Feedz, NuGet and Pages deployment jobs were skipped. The current consolidated source proof verified 232 packages /132 exclusions (including nine nonpackable Apps); this does not rebaseline the historical 225/124 candidate/archive contracts or accept compatibility of an operational candidate. Templates retains independent package identity and release ownership; Apps retains released 3.9.0 consumption. Product release selection must preserve independent release boundaries.

   Remaining operational ownership is unchanged:

   • [Feature] F2.4: Migration of contribution/release documentation and source ownership #8216: contribution authority, maintenance routing and source retirement prerequisites.
   • [Feature] F3.3: Published-package compatibility validation #8219: compatibility and independent product release selection.
   • [Feature] F3.4: Artifact provenance, release notes, and recovery procedures #8220: candidate/archive/artifact contracts, credentials, publication and recovery.
   • [Task] Restore Dependabot discovery for imported Extensions and Studio projects #8636: dependency updater.
   • [Task] Verify stable server and Studio packages across supported browser hosts #8643: full 3.10 Hosted/browser/profile certification.
   • 3.10 cut gate: real tag publish still packs Core only; Studio npm pair has no publish job #8725: release verification.

   Concrete inherited runtime and hardening observations and Templates key-validation uncertainty remain explicit operational follow-up. The source gate is not production identity, browser, ARM, MySQL, deployed authorization or full release certification. Existing green build warnings remain recorded rather than treated as resolved.

   All three #8741 milestone definitions and acceptance criteria remain byte-for-byte intact. Full 3.10 certification remains a later operational milestone, not an added prerequisite to the owner's archive-first sequence. #8741 stays open; #8736 remains Todo / Agent Ready / Pending. No operational task or new program is activated by this completed source goal. Publication, publisher cutover, deployment and archival still require their concrete verified action and applicable authorization.
10. sfmskywalker

    added

    enhancementNew feature or requestNew feature or request

    epicAn 'issue of issues', representing a large or conceptual enhancementAn 'issue of issues', representing a large or conceptual enhancement

    on Oct 12, 2026
11. sfmskywalker

    added the

    Feature

    issue type on Oct 12, 2026
12. sfmskywalker

    added

    elsa 3This issue is specific to Elsa 3This issue is specific to Elsa 3

    prio highIs on the roadmap for the near-futureIs on the roadmap for the near-future

    triaged

    area:operationsQuality loop area: operationsQuality loop area: operations

    on Oct 12, 2026
13. sfmskywalker commented on Oct 12, 2026

    

    sfmskywalker

    on Oct 12, 2026

    MemberAuthor

    More actions

    #8736 bounded custody closeout

    Task #8736 is accepted and closed: all seven criteria and independent evidence. PR #8766 normally merged at fd98ccf807b24f88d1e847948ea2c1fb6ee6feb5 after fresh exact-head independent APPROVE/HIGH, Greptile 5/5, zero unresolved threads and applicable CI. The single native custody run 38308812342, attempt 1, succeeded; original/transfer/evidence artifacts, exact original ZIP/packet/receipt, clean executor and actual job permissions were independently read back. Both registry observations were anonymous-public missing-pair results with zero uploads.

    This closes hosted nonpublishing original custody only. The fixed proof version remains permanently unpublishable. Actual maintenance artifacts/consumers, publisher trust/grants/intended-reader access/serialization/dist-tags/source-retirement, controlled publication/recovery, full release certification and archival remain open under #8741 and the relevant existing owners. No credential/trust, maintenance-policy, deployment or archival action was taken.

    Project #52 #8736 is Done / Accepted / Verification Passed. The lead stops at this verified closeout; no next Task is activated. Recommend resolving #8693's MySQL/.NET10 support decision before resuming its existing #8694 maintenance artifact/consumer work. Feature #8220 and Program #8741 remain open, with their criteria unchanged.