Skip to content

[Task] Reconcile consolidation records with merged architecture and verified debugging #8628

Description

@sfmskywalker

Objective

Reconcile the consolidation architecture and paired-development records with the source/history import and boundary decisions already merged. Parent: #8213. Program: #8194; board 52.

Context and dependencies

The history ADR still describes a proposed rehearsal. Actual import #8409, retained-asset/Secrets decisions #8524/#8525, solution grouping and Foundation reference boundary #8547, and release/source catch-up #8624 are merged and their commits are ancestors of Core main 6dbfc58624c28e147a90e2d2b0d1a610817012e2. #8214 and #8286 are closed. Live #8213 has no open native dependencies or child tasks; no matching open PR was found.

The accepted doc/adr/2026-09-28-lockstep-consolidated-release-and-publisher-cutover.md governs the first consolidated 3.10 release. Later independent connector release streams remain program scope. The npm publisher decision remains separate and must not be inferred here.

Scope and acceptance

  • Update the existing dated history ADR and its relevant architecture cross-references to distinguish historical rehearsal from the landed import, retaining original evidence and rationale.
  • Record actual source folder mapping, solution grouping and project-reference boundaries with links to Import Extensions and Studio histories into consolidated source #8409/[skip ci] Group Elsa.sln into Foundation, optional domains, Studio and Apps with focused filters #8547 and their repository evidence; do not propose or perform new source moves.
  • Retain the lead-observed paired browser/debugger replay from clean Core main 6dbfc58624c28e147a90e2d2b0d1a610817012e2 as a small portable receipt and update the existing paired-development guide. Refs [Feature] F2.3: Root solution, solution filters, samples, and debugging workflows #8215/[Story] Prove paired backend and Blazor Studio source development #8279. The lead observed HTTP 200, updates 0→1→2, both imported source breakpoints and clean debugger/listener teardown; the separate full-solution Debug build passed with 0 errors and 470 warnings on the same clean main SHA (build only, no full test run). The lead retains observed-main-replay.json for the assigned worker; inspect the final receipt and full-build result before claiming acceptance. Preserve draft receipts as history, exclude raw debugger logs and local absolute paths, and keep synthetic-host authorization limits explicit.
  • Reconcile release language with the accepted first-3.10 lockstep decision, continuing source-repository 3.8/3.9 maintenance and later E3 independent streams.
  • Keep full artifact/runtime compatibility, publication, publisher cutover, deprecation, archival and the two Dependabot operational checks as separate gates. Do not reinterpret the frozen pre-supplement legacy ledger as current missing-work counts.
  • Verify every delivery claim against current merged Git ancestry and existing receipts/issues. Link the documentation PR to this task and reference [Feature] F2.1: Architecture decision for folder, dependency, and release boundaries #8213; keep the parent open until its complete acceptance has been checked after merge.

Validation and delivery

Documentation-only change in elsa-workflows/elsa-core, isolated worktree, slice base codex/elsa-integration-program. Read before editing. Run scripts/adr/generate-toc.sh if headings/files change and scripts/adr/generate-toc.sh --check; verify links/paths, Git ancestry and focused diff. No build is required for unchanged production code. Obtain independent review and exact-head repository checks before merge.

Historical activation context: this was the sole active delivery task. #8626 is closed after reviewed and verified #8627 merged into the shared program branch at 5b6b75fdd64a22d99ac4258311a29258b559055b. Start this documentation slice from that exact program-branch baseline. No source import, release policy invention, publication or live cutover is authorized by this documentation slice.

Accepted closeout — 2026-10-06

Accepted through merged PR #8630 into codex/elsa-integration-program (merge SHA: 3413534). The exact reviewed head was 9c3a74a30e62b7150b435225cac2eafe9976126a; independent APPROVE + HIGH, Greptile 5/5 and all applicable CI passed before merge. The lead verified the full diff, 24 local Markdown links, ADR index, five merge-ancestry checks and the portable receipt against retained browser/debugger observations and the full-build log digest. Hosted .NET 10 unit/integration tests reported 4,834 passed / 144 skipped / 0 failed; component tests 226 passed / 1 skipped / 0 failed. The production package build also passed. This documentation-only slice records existing main implementation; its new records are on the program branch pending final integration. No publication or cutover occurred.

Activity

  1. changed the title [-][Task] Reconcile consolidation architecture records with merged delivery[/-] [+][Task] Reconcile consolidation records with merged architecture and verified debugging[/+] on Oct 6, 2026
  2. sfmskywalker commented on Oct 6, 2026

    @sfmskywalker
    MemberAuthor

    Implementation is in PR #8630, targeting codex/elsa-integration-program at head 9c3a74a30e62b7150b435225cac2eafe9976126a. Independent review is APPROVE + HIGH and lead documentation/evidence checks pass. Exact-head CI and Greptile remain required. This remains the sole active delivery Task; #8629 is the ready buffer. The issue and parent features remain open until merge and acceptance read-back.

  3. sfmskywalker commented on Oct 6, 2026

    @sfmskywalker
    MemberAuthor

    Acceptance verified and recorded above. Merged #8630 at 3413534be6803d81616ca1da1703ca8582512caf on the shared program branch; final integration into main and remaining program gates stay open.

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