chore(audit): L4.3 module manifests audit — count v1→v2 gap #62

Closed
opened 2026-05-05 01:07:00 +02:00 by glm · 1 comment

Audit-only: count how many of 81 module.yaml files are v1 vs v2. No schema_version or predecessor fields found in any module. Phase 03 blocked until 30+ modules reach v2.

Spec sources

  • modules/*/module.yaml (81 manifests)
  • schema/module.schema.json (v1)
  • schema/module.schema.v2.json (v2: predecessor, alternatives, todo_cap, drift_audit)
  • PLATFORM_CHARTER.md §3

Extracted context

Issue #59: Phase 03 depends on L4.3 being at least 30 modules in v2.
glm audit 2026-05-05: 0/81 modules have schema_version or predecessor fields.

What done looks like

  • Comment listing all 81 modules with schema version classification
  • Gap analysis: how many need v2 upgrade for 30-module threshold

Scope: audit only, no manifest changes

Risk: risk/process

Trace: Issue #59 item 1, decomposed by glm 2026-05-05, parent #59

Audit-only: count how many of 81 module.yaml files are v1 vs v2. No schema_version or predecessor fields found in any module. Phase 03 blocked until 30+ modules reach v2. ## Spec sources - modules/*/module.yaml (81 manifests) - schema/module.schema.json (v1) - schema/module.schema.v2.json (v2: predecessor, alternatives, todo_cap, drift_audit) - PLATFORM_CHARTER.md §3 ## Extracted context > Issue #59: Phase 03 depends on L4.3 being at least 30 modules in v2. > glm audit 2026-05-05: 0/81 modules have schema_version or predecessor fields. ## What done looks like - [ ] Comment listing all 81 modules with schema version classification - [ ] Gap analysis: how many need v2 upgrade for 30-module threshold ## Scope: audit only, no manifest changes ## Risk: risk/process ## Trace: Issue #59 item 1, decomposed by glm 2026-05-05, parent #59
Collaborator

Closing as duplicate of #61

Same scope and title as #61 (chore(audit): L4.3 module manifests audit — count v1→v2 gap). Issue #61 has the more detailed body and was opened first. Keeping #61 as canonical; closing this one.

If the audit work needs to be re-done after #61 amendment, it will happen in #61, not here.

## Closing as duplicate of #61 Same scope and title as #61 (`chore(audit): L4.3 module manifests audit — count v1→v2 gap`). Issue #61 has the more detailed body and was opened first. Keeping #61 as canonical; closing this one. If the audit work needs to be re-done after #61 amendment, it will happen in #61, not here.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#62
No description provided.