feat: a subtype gets its own page skeleton from types/<type>.<value>.md (#117)

Files changed:
- AGENTS.md
- CHANGES.md
- README.md
- VERSION
- docs/ownership-and-templates.md
- instructions/evolve-subtypes.md
- instructions/setup-instance.md
- instructions/subtype-templates.md
- instructions/upgrade-instance.md
- tools/CONTRACT.md
- tools/chemenu/commands/dist_cmd.py
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/new_page.py
- tools/chemenu/tests/test_dist_cmd.py
- tools/chemenu/tests/test_docs_verify.py
- tools/chemenu/tests/test_new_page.py
- tools/chemenu/tests/test_toc.py
- tools/chemenu/tests/test_type_resolver.py
- tools/chemenu/toc.py
- tools/chemenu/type_resolver.py
- types/concept.decision.md
- types/entity.guidance.md
- types/entity.md
- types/entity.person.md
- types/type-spec.md

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

instructions/setup-instance.md

@@ -146,6 +146,12 @@ one it needs before that.
       *this* instance writes, so they belong to it: frontmatter, template and language may all
       be rewritten. `instruction`, `lint-report`, `type-spec` and `type-guidance` describe stack
       artifacts and arrive unchanged - none of them ships as a `.template` in the first place.
+      The subtype templates beside them (`types/entity.person.md`, `types/concept.decision.md`:
+      the page skeleton `wikitool new` uses for that one subtype instead of the type's
+      `## Template` block) are adopted the same way and are page material like that block, so
+      they are translated with it. Whether this instance wants further ones is a question for
+      later, once pages exist to show it - [subtype-templates.md](subtype-templates.md), not
+      part of this setup.
 
       A `root: kb` type-spec's generic authoring guidance (when to use the type, when not to)
       is not part of this adoption at all: it lives in a sibling `types/<name>.guidance.md`