chore(healthchecks): add health metadata for 34 docker-compose modules #835

New issue

Open

opened 2026-06-26 08:41:29 +02:00 by codex · 0 comments

codex commented

2026-06-26 08:41:29 +02:00

Collaborator

Acting as codex (id=4).

Parent: #765
Evidence report: state/reports/platform-catalog-inventory-2026-06-26.md

Scope

Add or explicitly classify missing health metadata for the 34 docker-compose modules found by #765.

Recommended order:

Core/important active platform dependencies first: postgres, redis, honcho-postgres, honcho-redis, infisical-redis, git-mirror, gmail-private-mcp, gmail-triage-mcp, matrix-well-known, openclaw-mail-worker, agent-plane-shadow-control, agent-plane-shadow-postgres.
Standard active modules next.
Parked modules last; if still intentionally parked, mark with explicit health policy rather than adding false checks.

Missing health metadata

agaria-api
agaria-postgres
agaria-redis
agaria-web
agaria-worker
agent-plane-shadow-control
agent-plane-shadow-honcho-status
agent-plane-shadow-postgres
agent-plane-shadow-projection
audio-mcp
coredns
deploy-control
git-mirror
gmail-private-mcp
gmail-triage-mcp
honcho-deriver
honcho-postgres
honcho-redis
infisical-redis
iskra-things-sync
karakeep-meilisearch
matrix-well-known
n8n-worker
np-meerkat-frontend
np-openhabittracker
np-tududi
openclaw-mail-worker
openclaw-searxng-mcp
playwright-mcp
postgres
redis
safe-session-api
safe-session-web
storage-ro-mcp

Acceptance criteria

Each listed module either has spec.health.compose.required_healthy, spec.health.http.url, or an explicit documented reason it should not get a docker-compose healthcheck now.
platformctl lint --cross-refs --json remains clean of errors.
No runtime mutation, no container restart, no deploy, no secret reads.

Suggested labels

domain:runtime, risk/runtime, flow/intake, judge/p2, kind/chore, priority:p2, source/agent-generated, size/medium.

Out of scope

Changing live Docker compose services.
Adding healthchecks to runtime before manifest review.
Touching non-docker-compose modules from the NOT_APPLICABLE bucket.

Acting as codex (id=4). Parent: #765 Evidence report: `state/reports/platform-catalog-inventory-2026-06-26.md` ## Scope Add or explicitly classify missing health metadata for the 34 docker-compose modules found by #765. Recommended order: 1. Core/important active platform dependencies first: `postgres`, `redis`, `honcho-postgres`, `honcho-redis`, `infisical-redis`, `git-mirror`, `gmail-private-mcp`, `gmail-triage-mcp`, `matrix-well-known`, `openclaw-mail-worker`, `agent-plane-shadow-control`, `agent-plane-shadow-postgres`. 2. Standard active modules next. 3. Parked modules last; if still intentionally parked, mark with explicit health policy rather than adding false checks. ## Missing health metadata - `agaria-api` - `agaria-postgres` - `agaria-redis` - `agaria-web` - `agaria-worker` - `agent-plane-shadow-control` - `agent-plane-shadow-honcho-status` - `agent-plane-shadow-postgres` - `agent-plane-shadow-projection` - `audio-mcp` - `coredns` - `deploy-control` - `git-mirror` - `gmail-private-mcp` - `gmail-triage-mcp` - `honcho-deriver` - `honcho-postgres` - `honcho-redis` - `infisical-redis` - `iskra-things-sync` - `karakeep-meilisearch` - `matrix-well-known` - `n8n-worker` - `np-meerkat-frontend` - `np-openhabittracker` - `np-tududi` - `openclaw-mail-worker` - `openclaw-searxng-mcp` - `playwright-mcp` - `postgres` - `redis` - `safe-session-api` - `safe-session-web` - `storage-ro-mcp` ## Acceptance criteria - Each listed module either has `spec.health.compose.required_healthy`, `spec.health.http.url`, or an explicit documented reason it should not get a docker-compose healthcheck now. - `platformctl lint --cross-refs --json` remains clean of errors. - No runtime mutation, no container restart, no deploy, no secret reads. ## Suggested labels `domain:runtime`, `risk/runtime`, `flow/intake`, `judge/p2`, `kind/chore`, `priority:p2`, `source/agent-generated`, `size/medium`. ## Out of scope - Changing live Docker compose services. - Adding healthchecks to runtime before manifest review. - Touching non-docker-compose modules from the NOT_APPLICABLE bucket.

codex added the

source/agent-generated

labels

2026-06-26 08:42:14 +02:00

codex referenced this issue