OMP Plan Kit v1.6.0
OMP Plan Kit v1.6.0
OMP Plan Kit v1.6.0 makes the machine-readable plan core mandatory for proposals from sessions that entered OMP Plan Mode, while preserving the existing Markdown path for direct and legacy callers.
Key Changes
1. Mandatory plan core at Plan Mode entry
- The public
omp-plan-kit:enter-plan-modeevent now injects the exact exportedPLAN_CORE_TEMPLATEinto the hidden plan-mode instructions. - The same activation records a session-scoped requirement before
xd://proposecan proceed. - The template keeps the stable JSON keys
sections,context,approach,action,target,verification,command, andexpects; values may use any language.
2. Fail-closed handoff
- An activated session without a line-1 JSON core is blocked with
PLAN_CORE_REQUIRED. - Malformed, unterminated, or incomplete required cores are blocked with
PLAN_CORE_INVALIDand field-level diagnostics. - These failures occur before the bounded advisor and before native OMP review.
3. Compatibility and lifecycle
- Sessions that never observe the public Plan Mode event retain the existing Markdown validation contract.
- Requirement state is isolated by session, replaced by newer activations, and cleared on
session_shutdown. - External event subscribers, activation deduplication, late-listener rejection, and both OMP plugin load orders remain covered.
Verification
npm run buildandnpm run checkpass.- Validator and mutation suites pass with every declared mutant killed.
- Real-loader hook and hook-mutation suites pass; all requirement/template mutants are killed with non-zero broker calls.
- Real in-process handoff passes strict missing/malformed/incomplete/valid-core scenarios, native review dispatch, legacy Markdown compatibility, advisor ordering, cache behavior, and convergence behavior.
- Rebuilt
dist/extension.jsis deterministic and included in the release package.
Install
omp plugin install github:stgmt/omp-plan-kit#v1.6.0