Skip to content

[Program] Consolidate Elsa 3 source in one repository #8740

Closed
1 of 1 issue completed
Closed

Description

@sfmskywalker

Outcome

Make the existing elsa-workflows/elsa-core repository the verified source of truth for Elsa 3 Core, Studio, Extensions, Apps and .NET project Templates. Major Elsa generations have separate repositories. Keep current repository names during consolidation; no generation folders or repository rename is part of this program.

Owner-approved program split: delivery chat, 2026-10-11. Portfolio/history and deferred connector roadmap: #8194. Shared execution board: https://github.com/orgs/elsa-workflows/projects/52.

Milestones and acceptance

  • Reconcile and retain accepted Core/Studio/Extensions import, source/history, 3.8.x/3.9.0 release catch-up (Reconcile 3.8/3.9 release history and refresh Studio and Extensions imports #8624), and product-directory/developer-workflow evidence. Do not repeat accepted implementation or reopen [Task] Relocate Core, Extensions and Studio into separate root product directories #8667/Promote consolidated product directories and package surfaces to main #8669 merely to reframe the program.
  • Import the standalone Elsa Apps source/history, tests, Docker/build assets, documentation and applicable contribution changes into apps/. Preserve existing application/image contracts and verify applicable builds/container smoke checks without publishing.
  • Import Elsa 3 .NET project Templates into templates/, preserving Elsa.Templates package identity and the existing elsa-server, elsa-studio, elsa-combined commands. Verify packing, isolated installation, generation and applicable generated-output builds without publishing.
  • Update root navigation, product instructions, solutions/filters and affected CI/build paths. Verify source mappings, changed files and pending source-repository issues/PRs; preserve user changes and source attribution.
  • Verify no new source arrivals were lost at closeout and publish a requirement-by-requirement completion record. Source repositories remain operational until the separate cutover program accepts replacement capability and approves retirement.

Existing work and boundaries

Adopt existing E2 #8197 and its accepted children. Accepted contribution register #8670 and routing notices #8676 are source evidence; their broader ownership/cutover Feature #8216 belongs to the operational program. New Apps/Templates imports require fresh scoped evidence; existing Core sample hosts are not proof that the standalone Apps repository was imported.

Core, Studio, Extensions, Apps and Templates keep logical product boundaries and individually releasable outputs. Shared repository membership does not require one product release to republish the others. Shared infrastructure remains shared where appropriate; no cosmetic internal restructuring is required.

Explicit non-goals

No new Slack/connector capability, React Studio implementation, Elsa 4 migration, Elsa 1/2 extraction, legacy modernization, full 3.10 release certification, registry upload, publisher activation, source retirement or archival. Those have separate owners/programs. Source consolidation completion must not imply operational cutover completion.

Accepted source outcome

All five source acceptance criteria are verified in the actual-main acceptance receipt. Final PR #8751 merged normally into actual main at 6179e6c360a1beeb01a717d6ef39fbc98a0e919a after independent exact-head review, Greptile 5/5 and applicable CI. The merged tree matches the reviewed source; final main verification and donor reconciliation are recorded in the receipt.

Apps #8746/#8743 and Templates #8748/#8744 are accepted; final Task #8749, Feature #8214 and Epic #8197 are closed against their source criteria. Existing accepted imports and #8624 release catch-up were retained. The source cutoff is activated by #8749's external receipt; the immutable prepared inventory remains unchanged.

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.

Board #52 records the source Program, Epic, Feature and Task as Done / Accepted / Passed. No active delivery Task remains after this bounded goal. Portfolio/history #8194 and the separately owned future programs remain open.

Activity

  1. sfmskywalker commented on Oct 11, 2026

    @sfmskywalker
    MemberAuthor

    Owner-selected bounded delivery goal

    The owner has explicitly replaced the broad portfolio delivery objective with Program #8740 only: deliver the Elsa 3 source consolidation end to end. The source home remains elsa-workflows/elsa-core with sibling core/, studio/, extensions/, apps/, and templates/. Preserve current repository names; separate Elsa generations remain separate repositories.

    Sequence: finish Apps #8746, then Templates #8744, then requirement-by-requirement source/history/release-freshness, developer-workflow and nonpublishing validation audit. Account for relevant 3.8.x/3.9.0 releases, subsequent donor changes and outstanding source PRs, and record an exact source-of-truth cutoff. Accepted work including #8624 and #8667/#8669 is retained rather than repeated.

    Publication, publisher cutover, deployment, archival, full release delivery, Slack, React Studio and Elsa 4 are outside this goal. Retained operational requirements remain open with #8741 or their separate program; they do not become source prerequisites without an actual source dependency. This selection does not grant new publication/retirement authority or imply those outcomes passed.

    Refreshed GitHub program, board, native children/dependencies, donor branch heads and open PRs before resuming. Exactly one active Task remains #8746 (In Progress / Assigned / Pending). Core main and remote shared target codex/elsa-integration-program are both c46850de361cb84f267845ba66394c87262e2aab.

    Apps intake is complete and lead-approved: preserve the complete original 89-file tree and all 76 original commits; PR #9 is retained as explicitly non-content history, not accepted dependency content. Preserve released-package consumption and six existing image profiles, with scoped build configuration and narrow nonpublishing validation. Sol 6.1 High implementation is assigned in an isolated worktree. Lead retains final integration/QA; a Luna 6 Extra High read-only audit reconciles previously accepted source evidence without starting a second implementation task.

    The built-in goal tracker rejected replacement because the old objective is unfinished. Its old record is still paused and has not been falsely marked complete. This issue and the owner instruction define the current execution scope; the tracker limitation does not block authorized source work.

  2. sfmskywalker commented on Oct 11, 2026

    @sfmskywalker
    MemberAuthor

    Existing source evidence refreshed

    Read-only Luna 6 Extra High audit, reviewed by the lead against its Git/GitHub evidence, found no new functional source gap in the previously accepted Core/Studio/Extensions migration at Core c46850de361cb84f267845ba66394c87262e2aab.

    There is a history-only closeout item: current Studio d57fc46fd3605b7b2ee839306c7420a170c17ddd and Extensions 2611ee6d9b6fb5e50f4c0b3fbc9cc15b355b4751 contain later original commits not yet in Core ancestry. After Apps and Templates, the lead will refresh the donors and retain these original tips as explicitly non-content ancestry, preserving Core's current mapped content. No new publisher authority or source-item acceptance is implied.

    Apps #8746 remains the sole active Task. Apps product restore/Release build and focused helper/solution checks have passed locally; independent exact-head review and native nonpublishing six-profile CI remain required. Templates implementation has not started. Program acceptance remains incomplete.

  3. sfmskywalker commented on Oct 12, 2026

    @sfmskywalker
    MemberAuthor

    Final source integration PR #8751 merged normally into actual main at 6179e6c360a1beeb01a717d6ef39fbc98a0e919a on 2026-10-12 at 02:53:11 UTC. Ordered parents are baseline c46850de361cb84f267845ba66394c87262e2aab and reviewed head 3b977a5bc2554463b55afdb21a0d733a215c1e94; tree f7b0585366b010a2592037fc9c616f86dde8f1d7 exactly matches the reviewed source. Lead and independent readbacks confirm the five roots, retained import history, immutable ledgers and all 240 contribution pointers. The full postmerge donor read (02:53:49–02:53:54 UTC) found no ref or recorded issue/PR identity changes.

    The exact-head gate receipt records independent APPROVE/HIGH, Greptile 5/5, all review dispositions and 32 successful checks with three conditional skips. Artifact11723244726 has been downloaded and independently verified, including all464 package hashes, all17,178 remote provenance documents against the pinned source manifest, clean net8/net9/net10 consumers and six admission cells; publication=false.

    Final actual-main verification remains running: Packages38197558111 and security/quality analysis. The component coverage job has passed. Task #8749 was reopened after automatic PR closure so final verification remains accurately owned; it is still the sole active delivery Task. The source cutoff is prepared and has not yet been activated by the required final acceptance receipt. #8740, #8197 and #8214 remain open. #8741 operational obligations remain open and #8736 stays queued; no publication, deployment, publisher cutover or archival occurred.

  4. sfmskywalker commented on Oct 12, 2026

    @sfmskywalker
    MemberAuthor

    Source acceptance complete on actual main 6179e6c360a1beeb01a717d6ef39fbc98a0e919a through 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions