pdurlej/platform

Fork 0

chore(modules): add first metadata completion batch #577

Merged

pdurlej merged 1 commit from deepseek/m05-first-10-modules into main

2026-05-28 23:13:37 +02:00

codex commented

2026-05-28 22:45:53 +02:00

Collaborator

Canary status: missing - fire canary 3+3 manually before merge

Summary

Closes #561.

Adds the first 10-module source/artifact metadata completion batch for M05. This is metadata-only: no runtime tags changed, no compose changes, no digest changes, no service restart path, and no upgrade execution.

Modules updated

dashboard
shelfmark
excalidraw-app
excalidraw-room
matrix-well-known
ntfy
np-meerkat-frontend
coredns
mirotalk-sfu
voice-transcription

Selection rationale

These modules already had concrete runtime.image_observed values and did not require touching Forgejo, secrets/auth modules, DB-heavy modules, or runtime topology. Public/stateless modules are included only where the change is strictly catalog metadata copied from already observed runtime state.

Digest-only images are marked as manual/pinned instead of pretending there is a known upstream tag. Local images are marked platform-local and platform-local-build.

Validation

UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json - pass
UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli update-report all --json - pass

Update-report after this batch: withSource=19, withArtifact=19, missingSource=69, missingArtifact=69.

Spec sources read

Issue #561 - task scope and acceptance criteria.
schema/module.schema.json - source/artifact field contract.
Existing completed module manifests for local convention examples.
The 10 changed module manifests - exact observed image/source fields.

Out of scope

Runtime upgrades.
Compose changes.
Digest pinning changes.
Module loader behavior.
Secrets/auth module cleanup.
DB-heavy module metadata.

Canary Context Pack

Product story

M05 needs enough source/artifact metadata to make M09 upgrade work systematic instead of ad hoc. This batch increases coverage without changing runtime behavior.

What changed

Added spec.source and spec.artifact metadata for 10 selected modules.

Why it changed

M09 upgrade packets need stable current/candidate source and artifact fields.

Files touched

10 modules/*/module.yaml manifests.

Relevant context

M05 module metadata issues #558-#561 and module schema source/artifact contract.

Runtime evidence

No runtime action. Metadata is copied from existing runtime.image_observed values already present in manifests.

Known constraints

This PR intentionally avoids runtime-impacting modules where metadata requires deeper source archaeology.

Explicit out-of-scope

No runtime migration, no upgrade, no compose edit, no service restart.

Requested decision

Approve as metadata-only M05 batch after required canary/review.

Merge blockers

Schema validation failure, incorrect metadata shape, or evidence that this accidentally changes runtime behavior.

Canary status: missing - fire canary 3+3 manually before merge ## Summary Closes #561. Adds the first 10-module source/artifact metadata completion batch for M05. This is metadata-only: no runtime tags changed, no compose changes, no digest changes, no service restart path, and no upgrade execution. ## Modules updated - `dashboard` - `shelfmark` - `excalidraw-app` - `excalidraw-room` - `matrix-well-known` - `ntfy` - `np-meerkat-frontend` - `coredns` - `mirotalk-sfu` - `voice-transcription` ## Selection rationale These modules already had concrete `runtime.image_observed` values and did not require touching Forgejo, secrets/auth modules, DB-heavy modules, or runtime topology. Public/stateless modules are included only where the change is strictly catalog metadata copied from already observed runtime state. Digest-only images are marked as manual/pinned instead of pretending there is a known upstream tag. Local images are marked `platform-local` and `platform-local-build`. ## Validation - `UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json` - pass - `UV_CACHE_DIR=/private/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli update-report all --json` - pass Update-report after this batch: `withSource=19`, `withArtifact=19`, `missingSource=69`, `missingArtifact=69`. ## Spec sources read - Issue #561 - task scope and acceptance criteria. - `schema/module.schema.json` - source/artifact field contract. - Existing completed module manifests for local convention examples. - The 10 changed module manifests - exact observed image/source fields. ## Out of scope - Runtime upgrades. - Compose changes. - Digest pinning changes. - Module loader behavior. - Secrets/auth module cleanup. - DB-heavy module metadata. ## Canary Context Pack ### Product story M05 needs enough source/artifact metadata to make M09 upgrade work systematic instead of ad hoc. This batch increases coverage without changing runtime behavior. ### What changed Added `spec.source` and `spec.artifact` metadata for 10 selected modules. ### Why it changed M09 upgrade packets need stable current/candidate source and artifact fields. ### Files touched 10 `modules/*/module.yaml` manifests. ### Relevant context M05 module metadata issues #558-#561 and module schema source/artifact contract. ### Runtime evidence No runtime action. Metadata is copied from existing `runtime.image_observed` values already present in manifests. ### Known constraints This PR intentionally avoids runtime-impacting modules where metadata requires deeper source archaeology. ### Explicit out-of-scope No runtime migration, no upgrade, no compose edit, no service restart. ### Requested decision Approve as metadata-only M05 batch after required canary/review. ### Merge blockers Schema validation failure, incorrect metadata shape, or evidence that this accidentally changes runtime behavior.

codex added this to the 05 - Platform modularity foundation milestone

2026-05-28 22:45:53 +02:00

codex added the

labels

2026-05-28 22:45:53 +02:00