CANP-WP-0002 T06: revision v0.2, and section 23 rewritten

Closes the workplan. The format becomes `canned-prompt/v0.2`, and packages
declaring v0.1 remain valid — everything added across T01-T05 is additive, so
a v0.1 package means exactly what it always meant. That is the MINOR case
section 17 itself describes.

The spec file loses its version suffix: CannedPromptFormat-v0.1.md becomes
CannedPromptFormat.md, with the revision stated inside. One stable path that
never breaks a link, and no rename per revision; the version belongs in the
`format` string where tools actually read it.

Section 23 is rewritten into three parts rather than the planned two.
"Settled since v0.1" tables the five resolved questions against where each
rule now lives. "Still deferred" carries the eight unpromoted items plus
pattern-matching render checks. "Decided against" holds template inheritance
alone, because calling it deferred would misdescribe it — reopening it means
overturning a decision and answering four recorded objections, not filling a
gap.

Section 23 also names the two habits the five decisions turned out to share,
so later revisions follow them rather than rediscover them: separate the
deterministic half from the rest, and a package never asserts what it cannot
back.

The eval-rubric and registry-manifest schemas keep their own v0.1. They are
new in this revision and sit on their own version lines.

Reference CLI: ACCEPTED_FORMATS; an unknown revision is rejected naming what is
accepted. Tests 78 -> 81.

Example packages declare v0.2 and are bumped 0.1.0 -> 0.1.1 and 0.2.0 -> 0.2.1
as section 17 PATCH — metadata corrections with behavior unchanged.

Also refreshes section 22's worked example, which had drifted: it showed
pqrst-estimate at 0.1.0 with no composition, contradicting the package
actually in the repo. It now mirrors the real package and doubles as a
composition illustration.

CANP-WP-0002 is finished. CANP-WP-0003 carries forward the one residual: the
default registry's basename-derived name reads as `registry:`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bjefh8NUiEiahN4JLwoSKM

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 388925@bnt-lap001
Assistant-Session: 3507023f-e0fd-4a1e-9d90-a0d4217d1502

README.md

@@ -5,7 +5,7 @@
 This bundle contains a first project seed for `canned-prompts`:
 
 - [`INTENT.md`](INTENT.md) — project mission, boundaries, principles, and success criteria.
-- [`CannedPromptFormat-v0.1.md`](CannedPromptFormat-v0.1.md) — experimental package-format specification.
+- [`CannedPromptFormat.md`](CannedPromptFormat.md) — the package-format specification, currently revision v0.2.
 - [`reference/`](reference/) — deliberately small Python CLI implementing the basic lifecycle.
 - [`examples/pqrst-estimate/`](examples/pqrst-estimate/) — a real package that can be used to exercise the implementation.
 - [`examples/house-style/`](examples/house-style/) — a `type: fragment` package that `pqrst-estimate` composes.
@@ -67,7 +67,7 @@ or command-level `--catalog` / `--registry` options.
 
 ## Resolution vs rendering
 
-The format separates the two steps (`CannedPromptFormat-v0.1.md` § 5.1).
+The format separates the two steps (`CannedPromptFormat.md` § 5.1).
 Resolution decides a value for every input and parameter and may be
 non-deterministic; rendering substitutes those values and always is. An input
 may declare a default that is either a static value or a *derived* one — a
@@ -165,7 +165,7 @@ requires (this tool cannot verify these):
 
 ## Registries and identity
 
-An id names a package *within a registry* (`CannedPromptFormat-v0.1.md`
+An id names a package *within a registry* (`CannedPromptFormat.md`
 § 3.2). The same id obtained from two registries may be two different
 packages, so the catalog keeps them apart and a bare id that matches more than
 one is reported as ambiguous rather than guessed. Qualify it when you need to: