fix(pstack): write FeatureMap through pstack_create_verification

[shishiv]

Why

pstack_create_verification already writes feature-map.md. The create and maintain skills still taught a four-H2 features/ tree that receipts cannot parse.

Scope

skills/create-verification-skill/SKILL.md interviews the repo, then calls pstack_create_verification with a FeatureMap. It does not hand-write Launch, Doctor, or Drive as a second on-disk format.

skills/maintain-verification-skill/SKILL.md locates .pi/skills/verify-<app>/feature-map.md. Source wave is one read-only child per FeatureEntry id.

skills/create-verification-skill/references/feature-map-example/feature-map.md is a Notes map that parseFeatureMapMarkdown accepts. The four-H2 files are gone.

test/verification/verification.test.mjs round-trips that example and rejects leftover four-H2 markdown.

test/resources/resources.test.mjs bans How to get to it (user POV) and features/README.md.

src/verification/feature-map.ts is unchanged. There is no second parser.

Tradeoffs

The generated stub still contains an HTML comment from renderFeatureMapMarkdown. The shipped example does not copy that comment.

Blast Radius

Agents that create or audit a verify skill write and edit feature-map.md. Receipts can bind that file. Benny still uses its own feature-map path.

Verification

parseFeatureMapMarkdown plus validateFeatureMap accepted the Notes example (create-note, search-notes).

npm run verify:deterministic passed (format, lint, typecheck, 75 tests, manifest).

Made with Cursor