rdmsm4x changelog — dataMOB remote ecs0lib adoption owner-gated

Verified a real ecs0lib import/use on dataMOB's replacement remote commit while preserving the six-entry dirty canonical tree; canonical adoption remains pending explicit owner integration.

Scope and files

• Host: rdmsm4x
• Canonical app inspected read-only: /Users/richh/dev/apps/dataMOB
• Scratch verification clone: /tmp/datamob-ecs0lib-verify.AKxPzs/repo
• Metadata updated: /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-ecs0lib-portfolio-monitor-20260901.json
• Coordination evidence: /Users/richh/Documents/Codex/2026-09-01/mon/work/datamob-remote-adoption-monitor-reply-20260901-2050.md

Measured state

• Canonical dataMOB remains at 88195b26c16018d553ef289d378d01c6e17750f0 with six porcelain entries:
  • modified DataMob.xcodeproj/project.pbxproj
  • modified DataMob.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
  • modified DataMobCLI/Sources/main.swift
  • modified project.yml
  • untracked DataMob.xcodeproj/project.pbxproj.bak-20260831
  • untracked Support/
• Replacement commit 03528918c735d7c081277593dbb85b949d4fa49c supersedes the no-longer-remote 1f6ece4 after an authorized author rewrite for GitHub email privacy.
• GitHub backup refs/heads/main independently resolves to 0352891. Direct git ls-remote to git.ecs0.net failed with Too many authentication failures, so fleet-main equality remains peer-reported in this pass.
• A depth-2 scratch clone shows 0352891 changes three files relative to 88195b2: DataMob.xcodeproj/project.pbxproj, DataMob/Sources/DataMobApp.swift, and project.yml.
• The commit declares ECS0AppKit, ECS0AppSettings, ECS0Persistence, and ECS0System and adds a concrete import ECS0System plus ECSSyslog.shared.log(...) call in DataMobApp.swift. This is real library use, not declaration-only linkage.
• FEAT-20260831-59 remains open. At inspection time its latest comment still named superseded commit 1f6ece4.

Commands and verification

• Ran read-only canonical git rev-parse HEAD, git status --porcelain=v1, and git remote -v.
• Ran git ls-remote against fleet and backup remotes; backup succeeded at 0352891, fleet failed at SSH authentication before repository access.
• Created a temporary depth-2 backup clone and inspected git log, git show --stat, git diff, and source/module references with rg.
• Sent independent evidence and owner-gate guidance to claude@rdmbair15m5; receipt 20260901-204709-4653F475.
• Updated the monitor check-in. No canonical app file or Git ref was changed.

Fleet signing follow-up

• Read-only coordination evidence 20260901-204238-202C55A5 reports the four remaining spoke keychains repaired, 5/5 spoke unlock-then-sign probes passing, and seven build scripts updated to unlock first because keychain unlock state does not survive a fresh SSH session.
• This monitor did not read secret values, access keychains, sign artifacts, or modify build scripts.

Undo and owner actions

• There is no product rollback from this monitor pass; the scratch clone may be discarded later as monitor-owned temporary data.
• dataMOB owner must preserve or integrate the six canonical dirty entries before any fast-forward to 0352891; no automatic merge or reset is safe.
• The current ticket owner should update FEAT-20260831-59 with replacement SHA 0352891 and app-specific verification evidence.
• Portfolio counts for the canonical estate remain unchanged until owner acceptance lands in /Users/richh/dev/apps/dataMOB.