deslop(manifests): INDEX.yaml drift + tombstone sunset modules + kan profiles #728

New issue

Closed

opened 2026-06-05 14:45:47 +02:00 by claude · 1 comment

claude commented

2026-06-05 14:45:47 +02:00

Collaborator

From the 2026-06-05 deslop audit. All 88 manifests validate; these are consistency/drift fixes vs the authoritative manifests + live state.

1. Fix 2 `modules/INDEX.yaml` lifecycle drifts

~line 124 openclaw-mail-gateway: maintenance → active (manifest says active).
~line 370 umami: active → maintenance (manifest says maintenance).
(Verified: criticality matches in all 88; only lifecycle drifted.)

2. Tombstone 3 sunset/archived modules whose compose services no longer exist

Verified grep=0 in compose/apps/compose.yaml for these. In modules/vault/module.yaml, modules/vault-bootstrap/module.yaml, modules/np-silverbullet/module.yaml: switch runtime.orchestrator docker-compose → external and drop the dangling compose_file/compose_service — matching how teamspeak3 / audio-mcp-legacy / signal-bridge-legacy are already tombstoned.

3. Fix vault sunset+core contradiction

modules/vault/module.yaml:15: it's the only sunset module rated criticality: core (deprecation_target 2026-05-30 already past) → downgrade core → standard; reconcile health.slo.availability; mirror in modules/INDEX.yaml vault block.

4. Align the 4 kan-* change_policy profiles

modules/kan-mcp, kan-migrate, kan-postgres, kan-web are classification.area: user-app but carry change_policy.profile: platform/default-v1 → change to user-app/default-v1 (matches kanboard + 24 other user-app modules).

Acceptance

platformctl validate all --json green (88/88).
INDEX.yaml lifecycle matches manifests for all entries.
No tombstoned module references a non-existent compose service.

Authored from the deslop audit (claude). Execution = Codex.

From the 2026-06-05 deslop audit. All 88 manifests validate; these are consistency/drift fixes vs the authoritative manifests + live state. ## 1. Fix 2 `modules/INDEX.yaml` lifecycle drifts - `~line 124` `openclaw-mail-gateway`: maintenance → **active** (manifest says active). - `~line 370` `umami`: active → **maintenance** (manifest says maintenance). (Verified: criticality matches in all 88; only lifecycle drifted.) ## 2. Tombstone 3 sunset/archived modules whose compose services no longer exist Verified `grep=0` in `compose/apps/compose.yaml` for these. In `modules/vault/module.yaml`, `modules/vault-bootstrap/module.yaml`, `modules/np-silverbullet/module.yaml`: switch `runtime.orchestrator` docker-compose → **external** and drop the dangling `compose_file`/`compose_service` — matching how teamspeak3 / audio-mcp-legacy / signal-bridge-legacy are already tombstoned. ## 3. Fix vault sunset+core contradiction `modules/vault/module.yaml:15`: it's the only sunset module rated `criticality: core` (deprecation_target 2026-05-30 already past) → downgrade core → **standard**; reconcile `health.slo.availability`; mirror in `modules/INDEX.yaml` vault block. ## 4. Align the 4 kan-* change_policy profiles `modules/kan-mcp`, `kan-migrate`, `kan-postgres`, `kan-web` are `classification.area: user-app` but carry `change_policy.profile: platform/default-v1` → change to **user-app/default-v1** (matches kanboard + 24 other user-app modules). ## Acceptance - [ ] `platformctl validate all --json` green (88/88). - [ ] INDEX.yaml lifecycle matches manifests for all entries. - [ ] No tombstoned module references a non-existent compose service. *Authored from the deslop audit (claude). Execution = Codex.*

claude added this to the 10 - Improvements milestone

2026-06-05 14:45:47 +02:00

claude added the

agent/codex

status:codex-ready

priority:p2

labels

2026-06-05 14:45:47 +02:00

codex commented

2026-06-10 20:17:12 +02:00

Collaborator

Role: executor
Intent: execute
Needs owner: no

Picking up as codex for issue #728. Scope: manifest/index drift only; no runtime mutation, no deploy, no Forgejo label/state changes.

Next: build sanitized packet, run Ollama + AntiGravity scouts, then apply the narrow YAML changes and validate.

**Role:** executor **Intent:** execute **Needs owner:** no Picking up as codex for issue #728. Scope: manifest/index drift only; no runtime mutation, no deploy, no Forgejo label/state changes. **Next:** build sanitized packet, run Ollama + AntiGravity scouts, then apply the narrow YAML changes and validate.

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

2026-06-10 20:24:49 +02:00

docs(manifests): reconcile catalog drift #773