feat(platformctl): implement `drift-check` command to compare declared vs live image digests #771

New issue

Closed

opened 2026-06-08 23:19:52 +02:00 by ollama · 0 comments

ollama commented

2026-06-08 23:19:52 +02:00

Collaborator

Spec sources (whitelist)

modules/*/module.yaml — spec.runtime.image_observed field on each module
compose/apps/compose.yaml, compose/edge/compose.yaml, compose/infra/compose.yaml — compose service definitions
control-plane/platformctl/cli.py — where to add subcommand
control-plane/platformctl/plan.py — reference: existing drift detection logic
2-3 modules with known drift for testing (e.g., honcho-api: 3.0.6 declared, 3.0.3 live)

Extracted context

Module manifests carry spec.runtime.image_observed as manual audit snapshots. There is no automated comparison against live Docker state. Drift (like honcho-api 3.0.6 vs 3.0.3) goes unnoticed until a manual audit burns tokens re-checking.

Scope

Implement platformctl drift-check [module...] command that:

For each module (or all if no args):
- Reads spec.runtime.host, spec.runtime.orchestrator, spec.runtime.compose_service
- If orchestrator=docker-compose: SSH to host, run docker inspect on the compose container
- Extract actual image digest from docker inspect --format '{{index .RepoDigests 0}}'
- Compare against spec.runtime.image_observed
Output mode: --json for machine-readable, default human-readable table
Exit codes: 0=all match, 2=drift detected, 5=remote unreachable, 8=partial state
Skip modules where orchestrator=external (nothing to check)

Acceptance criteria

platformctl drift-check --json runs against RS2000
Detects honcho-api 3.0.3-vs-3.0.6 drift correctly
Reports "OK" for modules with matching digests
Handles unreachable hosts gracefully (exit 5)
715+ existing tests still green

Do NOT read

Full repo — only the files listed above
Do NOT modify any module manifests (drift detection is read-only)

Agent notes

Recommended executor: Gemini 3.1 Pro (new platformctl command)
Size: Medium (~150-200 lines)
Review tier: tier/medium (new production command)
Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §DR5

## Spec sources (whitelist) - `modules/*/module.yaml` — `spec.runtime.image_observed` field on each module - `compose/apps/compose.yaml`, `compose/edge/compose.yaml`, `compose/infra/compose.yaml` — compose service definitions - `control-plane/platformctl/cli.py` — where to add subcommand - `control-plane/platformctl/plan.py` — reference: existing drift detection logic - 2-3 modules with known drift for testing (e.g., honcho-api: 3.0.6 declared, 3.0.3 live) ## Extracted context Module manifests carry `spec.runtime.image_observed` as manual audit snapshots. There is no automated comparison against live Docker state. Drift (like honcho-api 3.0.6 vs 3.0.3) goes unnoticed until a manual audit burns tokens re-checking. ## Scope Implement `platformctl drift-check [module...]` command that: 1. For each module (or all if no args): - Reads `spec.runtime.host`, `spec.runtime.orchestrator`, `spec.runtime.compose_service` - If orchestrator=docker-compose: SSH to host, run `docker inspect` on the compose container - Extract actual image digest from `docker inspect --format '{{index .RepoDigests 0}}'` - Compare against `spec.runtime.image_observed` 2. Output mode: `--json` for machine-readable, default human-readable table 3. Exit codes: 0=all match, 2=drift detected, 5=remote unreachable, 8=partial state 4. Skip modules where orchestrator=external (nothing to check) ## Acceptance criteria - [ ] `platformctl drift-check --json` runs against RS2000 - [ ] Detects honcho-api 3.0.3-vs-3.0.6 drift correctly - [ ] Reports "OK" for modules with matching digests - [ ] Handles unreachable hosts gracefully (exit 5) - [ ] 715+ existing tests still green ## Do NOT read - Full repo — only the files listed above - Do NOT modify any module manifests (drift detection is read-only) ## Agent notes - Recommended executor: Gemini 3.1 Pro (new platformctl command) - Size: Medium (~150-200 lines) - Review tier: tier/medium (new production command) - Audit ref: state/audit/deepseek-2026-06-08-multiperspective.md §DR5

ollama referenced this issue from a pull request that will close it,

2026-06-08 23:31:21 +02:00

feat(platformctl): automated truth-verification layer — lint --cross-refs + drift-check #772