docs: source ADR-0029 claims and sync ADRs and hook docs with behaviour

- cite the VS Code prompt-file deprecation and the verbatim apm quote
- add ADR-0029 boundary-clause enforcement and Consequences
- mark superseded ADR-0019 passages; record neutral lock advice, source
  fork and reloadSkills, amend for the hook hardening
- move the ADR-0025 amendment out of the Decision list
- amend ADR-0022 for create keeping 0.1.0
- fix hooks.md merge and event claims, README guard caveat, gates.md Vale
  globs, and pin the research registry URL

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi

docs/adr/0022-skill-metadata-version-is-mandatory.md

@@ -191,6 +191,17 @@ comments (`:9-93`) have described all three correctly since it shipped.
 was wrong for the tree-identical case: the `same_subtree` skip makes a push **pass** that this ADR as
 written requires to **fail**, which is documented behaviour changing, not an implementation detail.
 
+## Amendment (2026-09-29): a new skill stays at `0.1.0` until its first improve
+
+The Decision says `skill-author`'s create/improve bump convention is "unchanged". It has changed
+since. Before, `skill-author` bumped the **minor** version on create, so a skill left its first
+session above the `0.1.0` scaffold. Now create keeps the scaffold's `0.1.0` and does not bump it;
+the first improve is the first bump, a **patch** (`skill-author` `SKILL.md`, `references/create.md`
+and `references/improve.md`; `965208b`, PR #144). This makes `0.1.0` mean what this ADR says it
+means, "created and never yet revised", instead of a value no created skill ever kept. The rules
+above are otherwise unaffected: `metadata.version` is still required, and the push gate still
+compares whatever value is there.
+
 ## Consequences
 
 27 SKILL.md files gain `metadata.version: "1.0.0"`, and a 28th — `bin/write-docs` — reaches the same