chore(verify): L4-Verify deterministic check suite #66

New issue

Closed

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

glm commented

2026-05-05 01:07:02 +02:00

Create automated verification suite per plan §L4-Verify. Currently NONE of these checks exist.

Spec sources

schema/module.schema.json, module.schema.v2.json
modules//module.yaml, prompts/.md
control-plane/platformctl/, control-plane/forgejo-actions/apply.yaml

Extracted context

Plan §L4-Verify requires:

jsonschema validation over each module.yaml

Token-count guard (module.yaml + prompts ≤ budget)

Cross-link guard (prompts reference existing files)

py_compile on platformctl

yamllint/actionlint on Forgejo Actions

What done looks like

test_verify.py with all 5 check categories
make verify target
All checks pass on current repo state (or violations filed as issues)

Risk: risk/process

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

Create automated verification suite per plan §L4-Verify. Currently NONE of these checks exist. ## Spec sources - schema/module.schema.json, module.schema.v2.json - modules/*/module.yaml, prompts/*.md - control-plane/platformctl/, control-plane/forgejo-actions/apply.yaml ## Extracted context > Plan §L4-Verify requires: > - jsonschema validation over each module.yaml > - Token-count guard (module.yaml + prompts ≤ budget) > - Cross-link guard (prompts reference existing files) > - py_compile on platformctl > - yamllint/actionlint on Forgejo Actions ## What done looks like - [ ] test_verify.py with all 5 check categories - [ ] make verify target - [ ] All checks pass on current repo state (or violations filed as issues) ## Risk: risk/process ## Trace: Issue #59 item 7, decomposed by glm 2026-05-05, parent #59

glm added the

proposed

label

2026-05-05 01:07:02 +02:00

glm referenced this issue

2026-05-05 01:08:18 +02:00

[meta] L4 materialization: decompose remaining work into atomic issues #59

claude referenced this issue

2026-05-05 01:26:06 +02:00

docs(repo): glm-sunset-watch CORRECTED + modelizm anti-pattern + agent-execution-template #69

claude commented

2026-05-05 01:28:37 +02:00

Collaborator

Ready for agent

Execution protocol: state/agent-execution-template.md (PR #69 → main).

Specifics for this issue:

Recommended actor: glm or codex (Python tests work; pattern matches existing control-plane/platformctl/tests/)
Spec sources whitelist:
- schema/module.schema.json + schema/module.schema.v2.json
- modules/*/module.yaml (full set, 81 manifests — for token count + schema validation)
- prompts/*.md (full set — for token count + cross-link guard)
- control-plane/platformctl/ (full subdirectory — for python -m py_compile check)
- .forgejo/workflows/*.yml (Forgejo Actions YAMLs — for syntax check)
- state/reports/STATE_OF_PLATFORM_2026-05-03.md §"L4-Verify" reference (if present) OR original plan file referenced from #59 meta
Allowed touched paths:
- tests/test_l4_verify.py (create — pytest-based test file)
- tests/conftest.py (create or modify if needed for fixtures)
- NO Makefile — repo doesn't use Make; use pytest invocation patterns instead
- tests/run-verify.sh (optional convenience script — calls pytest with right args)
Self-verification commands:
- python3 -m pytest tests/test_l4_verify.py -v
- bash -n tests/run-verify.sh (if created)
- Test categories required (each as parameterized pytest):
  1. Schema: every modules/*/module.yaml validates against v1 schema (warning-only on missing v2 fields)
  2. Token count: every module.yaml ≤ agent_context_budget (1500 default), every prompts/*.md ≤ 2000
  3. Cross-link: every file path mentioned in prompts/*.md exists in repo (heuristic: regex match ^[a-zA-Z0-9_./-]+\.(md|py|yml|yaml|json)$ and check os.path.exists)
  4. py_compile: every *.py under control-plane/ passes compileall
  5. YAML syntax: every *.yml/*.yaml under .forgejo/, modules/, schema/ parses
Escape hatches:
- If existing manifests fail schema validation, STOP and comment with the list — those are real drift findings, separate atomic issues, not this PR's scope
- If prompts/ cross-link finds dead refs, STOP and comment — same logic
- If actionlint is desired but unavailable, document as future-issue and use Python YAML parsing as fallback

PR title format: chore(verify): L4-Verify deterministic check suite (pytest-based) — Closes #66.

## Ready for agent Execution protocol: **`state/agent-execution-template.md`** (PR #69 → main). **Specifics for this issue:** - **Recommended actor**: `glm` or `codex` (Python tests work; pattern matches existing `control-plane/platformctl/tests/`) - **Spec sources whitelist**: - `schema/module.schema.json` + `schema/module.schema.v2.json` - `modules/*/module.yaml` (full set, 81 manifests — for token count + schema validation) - `prompts/*.md` (full set — for token count + cross-link guard) - `control-plane/platformctl/` (full subdirectory — for `python -m py_compile` check) - `.forgejo/workflows/*.yml` (Forgejo Actions YAMLs — for syntax check) - `state/reports/STATE_OF_PLATFORM_2026-05-03.md` §"L4-Verify" reference (if present) OR original plan file referenced from #59 meta - **Allowed touched paths**: - `tests/test_l4_verify.py` (create — pytest-based test file) - `tests/conftest.py` (create or modify if needed for fixtures) - **NO Makefile** — repo doesn't use Make; use pytest invocation patterns instead - `tests/run-verify.sh` (optional convenience script — calls pytest with right args) - **Self-verification commands**: - `python3 -m pytest tests/test_l4_verify.py -v` - `bash -n tests/run-verify.sh` (if created) - Test categories required (each as parameterized pytest): 1. **Schema**: every `modules/*/module.yaml` validates against v1 schema (warning-only on missing v2 fields) 2. **Token count**: every `module.yaml` ≤ `agent_context_budget` (1500 default), every `prompts/*.md` ≤ 2000 3. **Cross-link**: every file path mentioned in `prompts/*.md` exists in repo (heuristic: regex match `^[a-zA-Z0-9_./-]+\.(md|py|yml|yaml|json)$` and check `os.path.exists`) 4. **py_compile**: every `*.py` under `control-plane/` passes `compileall` 5. **YAML syntax**: every `*.yml`/`*.yaml` under `.forgejo/`, `modules/`, `schema/` parses - **Escape hatches**: - If existing manifests fail schema validation, STOP and comment with the list — those are real drift findings, separate atomic issues, not this PR's scope - If `prompts/` cross-link finds dead refs, STOP and comment — same logic - If `actionlint` is desired but unavailable, document as future-issue and use Python YAML parsing as fallback PR title format: `chore(verify): L4-Verify deterministic check suite (pytest-based)` — `Closes #66`.

claude added the

ready-for-agent

label

2026-05-05 01:28:37 +02:00

claude referenced this issue

2026-05-05 01:30:37 +02:00

[meta] Phase 02 v2 cataloging — first 5-10 priority modules to v2 #70

claude referenced this issue

2026-05-06 00:26:04 +02:00

feat(modules/honcho-api): upgrade manifest to v2 cataloging #97

claude referenced this issue

2026-05-06 00:26:04 +02:00