New-WSL Dagu 2.18.2 and mise 2026.10.1 (clean-release waiver); stack and trading hosting stay on the held Dagu 2.16.6 - #740

… to the merge base before the final hot-file commit

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…its on the merge base (hot-file protocol: every hot-file edit in the last commit)

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…keep the trading-lane Dagu hold, move only the new-WSL rows, correct the migration and rollback record

This one commit merges origin/main and carries round r2's repairs. The sandbox could not write the linked worktree's Git metadata, so the builder staged the merge in a scratch clone; the coordinator committed it there and fast-forwarded the branch.

The Claude Opus read of r1 found 2 P1s. The command center and the trading lane resolved them with option (a):
- **The standing trading-lane hold stands** (docs/decisions/2026-09-25-workstation-sota-refresh.md:459-486). manifests/stack.json, the trading hosting recipe, dagu-equities.service.example, blueprints/us-equities/manifest.json and every stack-bound mirror stay at Dagu 2.16.6. None of the hold's overturn conditions is met: at v2.18.2 the config exposes only paths.artifact_dir, so the anonymous GET /api/v1/artifacts route under auth:none cannot be disabled. The hosting cutover remains the trading lane's.
- **New-WSL rows only.** The new-WSL profile, install plan, scripts, owners, SOURCES, handbook and the profile-bound edition rows move to Dagu 2.18.2, which is what NativeStack2604 runs. mise moves to 2026.10.1.
- **Migration record.** The decision record replaces the "no migration notes" claim with the real items: #2784 (suspend flags under data_dir), #2776 (partitioned and indexed artifacts), #2858 (DAG definition index under data_dir), and the repository's own observation that 2.17.x deletes the legacy dags/.dag.index, so binary and unit must move together. The 2604 rollback text requires a pre-upgrade DAGU_HOME copy. The follow-up round records the command center's correction of its earlier "no data migration" statement, and that host's actual one-way state.
- **The six P2s:**
  - the SHA-only SDK acceptance-plan mirror;
  - landscape snapshot consistency and its releases/latest provenance;
  - baseline evidence naming the executed 2.16.6 binary;
  - main integration and registry reconciliation;
  - mise 2026.10.0 CHANGELOG coverage;
  - the saturation mirror no longer claims 2.18.2 is installed for the stack component.

Built by GPT-6.1 Sol through the packaged SDK worker (round dagu-pin-r2); committed by the coordinator.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…ion and NativeStack2604's one-way upgrade

- docs/decisions/2026-10-05-dagu-mise-pin-move.md now carries a dated correction, quoted from and attributed to the command center. It withdraws the earlier "no data migration in 2.17.0-2.18.2" statement. It names the missed #2784, #2776 and #2858, and cites the 2026-09-25 record (:477-479) on the deleted legacy dags/.dag.index.
- It also records NativeStack2604's actual state, from the command center's read-only probe. No pre-upgrade DAGU_HOME data copy exists; the two dagu.service backups hold unit bytes only, and the older home is not a backup of the current state. That host's move to 2.18.2 is therefore one-way, with rollback only by re-provisioning. No private path is recorded.

Built by GPT-6.1 Sol through the packaged SDK worker (round dagu-pin-r2b); committed by the coordinator.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

… to the merge base before the final hot-file commit

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…its on the merge base (hot-file protocol: every hot-file edit in the last commit)

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…ack mirror; the held stack component untouched; merge recorded; 2.17.2 attribution

- The new-WSL profile (and the regenerated handbook), install plan, SOURCES and the qualification receipt (with its registry mirror) now describe a pre-upgrade DAGU_HOME copy-restore only as conditional guidance for a future existing-home upgrade. They state that NativeStack2604 is already on Dagu 2.18.2 without a pre-upgrade copy, so its rollback is re-provisioning, and link the decision's command-center section.
- manifests/stack.json is byte-identical to main again: the 2.18.2 qualification receipt is removed from the held 2.16.6 component's evidence_ids and from the saturation public_receipts. The receipt is referenced by the new-WSL profile, which it actually qualifies. The PR therefore stays lane:foundation.
- The decision record carries a dated coordinator note that the merge is committed as 6410e5d (parents f523942 and c148e04). Only the installed-Gitleaks containment control was left open for the coordinator.
- The legacy dags/.dag.index deletion is attributed to 2.17.2, as the 2026-09-25 record says.

Built by GPT-6.1 Sol through the packaged SDK worker (round dagu-pin-r3); committed by the coordinator.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…fore the final hot-file commit

Co-Authored-By: Claude Opus 5.5 <[email protected]>

… (hot-file protocol: every hot-file edit in the last commit)

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…epository-relative decision link

- evidence/receipts/dagu-mise-pin-qualification-20261005.json keeps the dated r2 open list and adds a dated r3 block that records:
  - the coordinator's merge 6410e5d, with parents f523942 and c148e04;
  - the coordinator's run of the installed-Gitleaks containment control: tests.test_runtime_worker_openhands_resolver, run with a writable runtime lock at 9e6ab1c plus the r3 working tree. Exit 0; returned lines 'Ran 138 tests in 15.762s' and 'OK (skipped=2)'.

  The decision record now states that nothing remains open.
- The receipt's NativeStack2604 limitation links the decision section by repository-relative path instead of a branch-only commit. Its registry mirror matches.

Built by GPT-6.1 Sol through the packaged SDK worker (round dagu-pin-r4); committed by the coordinator.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…fore the final hot-file commit

Co-Authored-By: Claude Opus 5.5 <[email protected]>

… (hot-file protocol: every hot-file edit in the last commit)

Co-Authored-By: Claude Opus 5.5 <[email protected]>