[Epic] E2: Repository consolidation and developer experience #8197

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 #8213, #8214, #8215, #8623, #8743 and #8744 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)

Program: #8194
Parent: #8194
Planning ID: E2

Features

• F2.1: Architecture decision for folder, dependency, and release boundaries.
• F2.2: Incremental import of extensions into core.
• F2.3: Root solution, solution filters, samples, and debugging workflows.
• F2.4: Migration of contribution/release documentation and source ownership.

Tasks/requirements

• Inspect repository instructions and branch/release policy before changes.
• Choose and document history-preservation strategy and migration order.
• Preserve package/activity identities and existing release support.
• Establish a single authoritative source and publisher per migrated package.
• Update project references, SourceLink/repository metadata, CI paths, tests, and documentation.
• Map old issues/PRs and avoid losing active work. Freeze/archive the old repository only after migration completion is assessed, not as a first step.
• Verify one focused connector filter brings in the needed core source dependencies for debugging.

Exit: migrated work builds and debugs in core, active changes are accounted for, old consumer contracts are preserved, and rollback/cutover guidance exists.

Delivery management

Planning container; not a claim of completed work. Dependencies are tracked separately from parentage. Implementation requires evidence from E0. Discovery may overlap.

Follow repository AGENTS.md; use existing test/ and doc/adr/ conventions. Do not mass-move core paths for cosmetic consistency. Child links will be added below.

Hierarchy: native parent/sub-issue relationships verified on 2026-09-23. Explicit blocking dependencies are configured separately; Markdown links remain references. See #8194.

Studio consolidation

Include Elsa Studio in the target monorepo. Audit paired backend/Blazor modules in Extensions and preserve their identities. Define atomic cross-stack PRs and filters, server/Studio protocol and package compatibility tests, frontend build tooling, and shell release ownership. A tightly coupled backend/Studio pair may share a release unit; do not force all Studio and server packages onto one version. Preserve history, active work, tests, samples, docs, and publishing ownership for both source repositories.

Children

• [Feature] F2.1: Architecture decision for folder, dependency, and release boundaries #8213 — Architecture decision for folder, dependency, and release boundaries
• [Feature] F2.2: Incremental import of extensions into core #8214 — Incremental import of extensions into core
• [Feature] F2.3: Root solution, solution filters, samples, and debugging workflows #8215 — Root solution, solution filters, samples, and debugging workflows
• [Feature] F2.4: Migration of contribution/release documentation and source ownership #8216 — Migration of contribution/release documentation and source ownership

Dependencies (separate from hierarchy)

• [Epic] E0: Program initialization and current-state audit #8195 — prerequisite evidence; discovery may overlap.

Architecture rollup — 2026-10-09

#8213 is closed again after its owner-approved layout follow-up #8667 and prior architecture reconciliation #8628 were verified accepted. Current main 8802a88 retains the accepted structural merge 658a9da, all nine Core/Extensions/Studio src/test/docs boundaries and the accepted dated layout ADR. Only contributor-routing records changed after that structural acceptance. Feature closeout. This supersedes the earlier folder-location guidance only.

E2 remains open: the remaining Features retain their own completion gates, including replacement maintenance/publisher capability and actual cutover. #8677 is the sole active delivery Task, with new-head hosted verification running; #8679 remains next-ready. Closing an accepted architecture Feature does not accept publication, archival, runtime compatibility or independent product release implementation.