Kjell Tore Guttormsen 1486368a2b chore(release): ultraplan-local v3.1.0

Quality program release. Spor 0+1+2+3 all delivered.

- 109 zero-dep tests gate fork-readiness
- 5 validators wired into 4 commands as CLI shims
- HANDOVER-CONTRACTS.md: single source of truth for 5 pipeline handovers
- PreCompact-hook (P0) closes progress.json drift; --resume now works
- Semantic plan-critic catches paraphrased deferred decisions
- examples/01-add-verbose-flag/: hand-calibrated end-to-end pipeline demo
- 4 hooks total (pre-bash, pre-write, session-title, post-bash-stats, pre-compact-flush)
- SECURITY.md + Extending-the-plugin docs

CC v2.1.x feature adoption: F8 (MCP_CONNECTION_NONBLOCKING),
F9 (sessionTitle), F3 (duration_ms), F12 (disableSkillShellExecution).
F2 (hook 'if'-field) deferred — universal protection wins.

Pre-flight verification:
- npm test → 109 pass
- plan-validator --strict templates/plan-template.md → READY
- plan-validator --strict tests/fixtures/plan-fase-narrative.md → FAIL (expected)
- grep smallCodebase|mediumCodebase|largeCodebase → 0 hits

Version bumped: package.json, plugin.json, README badge, root README,
root CLAUDE.md.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-01 06:31:42 +02:00

630 B

Raw Blame History

Bad plan — narrative drift fixture

plan_version: 1.7

This fixture exists ONLY to verify that plan-validator --strict rejects Opus 4.7-style narrative drift (Fase / Phase / Stage / Steg headings instead of ### Step N:). It MUST FAIL strict validation.

Context

This is what an LLM might produce when it ignores the literal-step schema and falls back to narrative phasing. The validator should catch this and refuse.

Fase 1: Forberedelse

Vi må først forstå koden. Les filene under src/.

Fase 2: Implementering

Skriv ny kode i nye filer.

Fase 3: Verifisering

Kjør testene og fiks eventuelle feil.

630 B Raw Blame History