OMP Plan Kit v1.3.0

OMP Plan Kit v1.3.0

OMP Plan Kit v1.3.0 introduces deterministic actionable plan contracts for Oh My Pi (OMP) plan mode, ensuring every plan step identifies an exact target and verification contains observable, actionable proof before invoking the AI plan advisor.

Key Changes

1. Approach Step Target Verification (APPROACH_TARGET_MISSING)

• Every step in ## Approach must include an exact target using inline code outside code fences:
  • Path indicators: / or \ (e.g. src/file.ts, GET /api/orders, .\build\run.exe);
  • Anchor / symbol delimiters: # (e.g. src/plan-validator.ts#validatePlanStructure);
  • Namespace delimiters: :: (e.g. crate::module::func);
  • Function calls: name() (e.g. validatePlanStructure());
  • Identifier chains: name.member (e.g. PlanIssue.code, package.json);
  • Interface paths: Name > Child (e.g. Settings > Billing).
• Step breakdown: H3 headings if present; otherwise top-level numbered list items (1. / 1)); otherwise the entire section is evaluated as one step.
• Pinpoints exact line numbers of missing targets and suggests concrete actionable examples.

2. Actionable Verification Proof (VERIFICATION_NOT_ACTIONABLE)

• The ## Verification section must contain at least one verifiable proof in either of two supported forms:
  1. Inline action followed by an observable result: <command or exact surface> → <observable expected result> (also accepts => or ->);
  2. A non-empty fenced code block followed immediately by a non-empty Expected: <observable result> or Ожидаемо: <observable result> line.
• CLI allowlists are deliberately avoided: actions can be shell commands, API routes, browser UI screens (Settings > Billing), TUI states, or manual verification steps.

3. All-Errors Repair Packet & Dependency Suppression

• New checks integrate into the single-pass validator: both missing targets and non-actionable verification are reported together with structural errors in a single repair packet.
• Dependent errors are suppressed: if Approach or Verification is missing, empty, or duplicated, secondary target and actionability errors are omitted.
• Issue signatures remain stable across cosmetic line-number and whitespace shifts.

4. Non-Goals & Architecture Integrity

• No custom non-native sections added: plans strictly follow the five canonical OMP sections (Context, Approach, Critical files & anchors, Verification, Assumptions & contingencies).
• No synthetic identifier schemes (FR/AC/T) enforced.
• No filesystem existence checks performed during plan validation (targets may be created during implementation).
• No LLM free-text meaning analysis in validator: deterministic token checks guard the boundary; semantic critique is handled by the bounded AI advisor.

Installation

Install as a user-scoped OMP plugin:

omp plugin install github:stgmt/omp-plan-kit#v1.3.0

Verify installation:

omp plugin list --json

Rollback

To rollback to v1.2.0:

omp plugin uninstall omp-plan-kit
omp plugin install github:stgmt/omp-plan-kit#v1.2.0