Skip to content

OMP Plan Kit v1.5.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Sep 19:32
· 11 commits to main since this release
v1.5.0
1ffb3e1

OMP Plan Kit v1.5.0

OMP Plan Kit v1.5.0 removes the last language-coupled surface of plan validation: plans may now carry an optional machine-readable JSON core, and when it is present the validator checks the data instead of parsing prose.

Key Changes

1. Machine-readable plan core (opt-in, JSON front-matter)

  • A plan may start with a --- { ... } --- JSON block describing sections.context, sections.approach (steps with exact targets), and sections.verification (proofs with command and observable expects).
  • With a valid core, the validator validates the DATA and skips Markdown entirely: a plan whose headings and body are entirely in Russian (or any language) passes with zero issues.
  • Keys are format literals (like YAML keys) and are not translated; values are free language. Unknown extra keys are ignored.

2. Fail-closed core handling

  • The block must start at line 1 and close within the first 100 lines.
  • Invalid JSON inside the block produces PLAN_CORE_INVALID with the exact violated field named in the repair packet — it is never silently parsed as Markdown.
  • A leading --- without a closing fence falls back to the Markdown path.

3. Design basis

  • Closes the critique that marker-token whitelists (v1.3.1) and even positional rules (v1.4.0) left heading literals language-coupled: with the core, validation becomes schema checking — the same validation-by-construction technique used by GitHub Spec Kit templates and Copilot Workspace's structured plan objects.
  • Competitor and literature research with sources: audit-reports/research-competitor-plan-validation-2026-09-05.md (LLM-Modulo external-verifier principle; Gherkin language registry evaluated and not needed; LLM extraction rejected as nondeterministic).

Compatibility

  • Strictly opt-in: plans without front-matter validate exactly as in v1.4.0. Works with OMP >= 17.3.7; no new runtime dependencies (the core is plain JSON).

Verification

  • Full battery green: npm run check, validator e2e (incl. core-path cases), convergence controller, programmer mutations, advisor contract, real in-process handoff, BDD mutation suite (12/12 mutants killed, including M-drop-core-path, M-core-lenient-context, M-core-skip-expects, clean-environment run).
  • Build is deterministic: committed dist/extension.js equals a fresh bun run build.

Install

omp plugin install github:stgmt/omp-plan-kit#v1.5.0
Assets 3
Loading