rdmsm4x-changelog-20260828-1134-dataroo-ecs0-project-routing

Filed the approved Dataroo-to-ECS0 separation contract in the correct canonical project repositories before feature execution, preserving the live Dataroo reference lane and the active Atlas writer boundary.

Scope and reason

• Host: rdmsm4x
• Mode: Production
• Scope: documentation and project-continuity state in isolated linked worktrees only
• Reason: Rich required the approved design, plan, and project-local context to live in their corresponding project folders before implementation begins.

Exact changes

ECS0 repository

• Canonical project: /Users/richh/dev/sites/dev.ecs0.net
• Worktree: /Users/richh/dev/_worktrees/dev-ecs0-net/codex-dataroo-ecs0-migration-design-20260828
• Branch: codex/dataroo-ecs0-migration-design-20260828
• Base planning commit: 016594f21917b147e517e96cf85dcb4ae033206a
• Filing commit: e99bed8d8bd0ef258be6a94871bc8d7268c860c9
• Added the authoritative folder:
  • docs/migration/dataroo-ecs0-separation/README.md
  • docs/migration/dataroo-ecs0-separation/design.md
  • docs/migration/dataroo-ecs0-separation/implementation-plan.md
• Replaced the two previously dispatched docs/superpowers/ documents with compatibility pointers to the authoritative folder.
• Added project-folder filing to the plan's pre-Task-1 stop gate.

Dataroo repository

• Canonical project: /Users/richh/dev/sites/dev.dataroo.net
• Worktree: /Users/richh/dev/_worktrees/dev-dataroo-net/codex-dataroo-ecs0-project-routing-20260828
• Branch: codex/dataroo-ecs0-project-routing-20260828
• Base: a919df835dcd89b4c3a5412a2dc271f3ca2fa9df
• Filing commit: 86126f302165788640e0cd92d6bbf3f9ec8b848b
• Added:
  • AGENTS.md
  • SESSION-STATE.md
  • docs/migration/dataroo-ecs0-separation.md
• The Dataroo record is pointer-only and does not duplicate the cross-project design or plan.

Coordination records

• Project-routing check-in: /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-dataroo-ecs0-project-routing-20260828.json
• Initial scope dispatch: 20260828-112738-E63F525D
• Exact-commit handoff dispatch: 20260828-113346-6A647680
• Dispatch is recorded separately from receipt and acceptance. No Atlas acceptance was inferred.

Commands and verification

• Inspected exact roots, branches, commits, worktrees, dirty paths, and the active Atlas check-in.
• Compared the refiled full documents to their prior committed versions; only the canonical-path annotation, canonical spec link, and expanded pre-execution gate changed.
• Verified both compatibility pointers resolve to committed ECS0 files.
• Ran git diff --check for both documentation sets with no whitespace errors.
• Ran python3 -m unittest -v in the Dataroo routing worktree: 34 tests ran, 34 passed, 0 failed.
• Scanned the new project records for common embedded-secret assignment shapes; none were found.
• Re-read both commits and worktree status after commit.

Preserved state and exclusions

• Neither canonical main checkout was edited or merged.
• Existing untracked Dataroo files were not modified: ISSUES.md, docs/agy-dashboard-publishing.md, published/, quarantine/, and reports/.
• The active Atlas worktree and all Atlas UI, catalog, API, MCP, runtime, and deployment paths were not edited.
• No live content, legacy wiki/data/generator input, authentication, Access policy, DNS, tunnel, certificate, container, scheduler, redirect, or deployment state changed.
• PROJECTS.md was not edited because its shared-file writer lease was not established.

Rollback and recovery

• Both changes are additive commits on isolated local branches. The canonical checkouts and live services remain the recovery lane.
• Before integration, abandon the branches without merging if review declines them; retain the commits and this changelog as provenance.
• After integration, undo through ordinary reviewable reverts of e99bed8d8bd0ef258be6a94871bc8d7268c860c9 and 86126f302165788640e0cd92d6bbf3f9ec8b848b; do not rewrite shared history.

Outstanding gates

• Obtain an explicit Atlas receipt and then a separate acceptance or rejection naming its current branch, HEAD, dirty paths, and integration boundary.
• Do not begin implementation Tasks 1–18 until the full pre-Task-1 gate passes from fresh evidence.
• Any later live operation requires a new exact, time-bounded preflight, rollback, and live verification.
• Apple Notes projection result: pending. The helper exited 3 because this harness is Background, not Aqua, so it could not send AppleEvents. Run from the rdmsm4x Terminal.app desktop session: zsh ~/scripts/notes_changelog.zsh '/Users/richh/dev/LLM/Claude/changelogs/rdmsm4x-changelog-20260828-1134-dataroo-ecs0-project-routing.md'.