Veraltete Skill-Aufzaehlungen in der Instruction-Schicht nachgezogen (#129, #130)

Files changed:
- CHANGES.md
- VERSION
- instructions/CONTRACT.md
- instructions/bootstrap.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- tools/chemenu/tests/test_instructions_cmd.py

instructions/CONTRACT.md

@@ -244,9 +244,9 @@ than the source, and without the sibling files a relative link might expect. A m
 correct at `instructions/<name>/SKILL.md` (`../session-setup.md`, `../../kb/CONTRACT.md`)
 resolves to a different, usually nonexistent, file once copied: the number of `../` segments
 that reaches a target from `instructions/` does not reach the same target from
-`.claude/skills/`. Fifty-two of the fifty-eight relative links across this repo's seven skills
-broke exactly this way before this rule existed, silently - nothing rendered the copy to notice,
-and no check read a link target.
+`.claude/skills/`. Fifty-two of the fifty-eight relative links across the repo's seven skills at
+the time broke exactly this way before this rule existed, silently - nothing rendered the copy to
+notice, and no check read a link target.
 
 So a `SKILL.md` never writes an outbound reference as a relative markdown link, correct depth or
 not. It names the target as a repo-root-relative **plain path** instead - `` `instructions/session-setup.md` ``, not `[session-setup.md](../session-setup.md)`; `` `kb/CONTRACT.md` `` for a
@@ -320,7 +320,7 @@ marker: the pointer is worth having in the origin repo and resolves nowhere else
 
 Anthropic's skill-authoring guidance suggests, for a "particularly complex workflow", a checklist
 the agent copies into its response and ticks off as it goes. It names no threshold, so this repo
-sets one - otherwise the two skills that have such a block and the three that do not read as an
+sets one - otherwise the skills that carry such a block and the ones that do not read as an
 accident rather than a decision.
 
 A `SKILL.md` carries the block when **one** of its flows runs to eight steps or more *and* that
@@ -332,9 +332,12 @@ because the next call fails without the previous one.
 Two skills qualify today, and the block names each of their numbered steps once, verbatim:
 `wiki-ingest` (twelve steps, of which `## Not Extracted` in step 6, the coverage check in step 10
 and the lint cadence in step 12 all fail quietly) and `wiki-lint` (nine, with steps 3-6 pure
-judgment). The other three do not, and the reason is worth stating so nobody adds one out of
-symmetry: `wiki-manage` has two flows of seven, `wiki-query` six, `wiki-status` five, and none of
-them is long enough for a reader to lose the thread.
+judgment). The rest do not, and the reason is worth stating so nobody adds one out of symmetry:
+`wiki-manage` has two flows of seven, `wiki-query` seven, `wiki-status` five and
+`gtd-weekly-review` five - none of them long enough for a reader to lose the thread.
+<!-- dist:strip-start -->
+Dev-instance-only: `stack-dev` (six) and `stack-close` (four) sit under the same threshold.
+<!-- dist:strip-end -->
 
 The block says that it is to be copied and carried, not read. A checklist read once is the table
 of contents it replaced.

instructions/bootstrap.md

@@ -9,7 +9,7 @@ description: Prepare a fresh clone for work - create the tools venv and publish
 `.agents/skills/` and `.claude/skills/` are generated copies of the skill directories under
 `instructions/`, and both are gitignored. A fresh clone therefore has no skills at all until
 they are published: the agent harness will not offer `wiki-ingest`, `wiki-query`,
-`wiki-manage`, `wiki-lint` or `wiki-status` before this runs.
+`wiki-manage`, `wiki-lint`, `wiki-status` or `gtd-weekly-review` before this runs.
 
 ## When to run
 

instructions/dev/stack-close/SKILL.md

@@ -129,5 +129,6 @@ and a fresh subagent starts without the session's context).
 ## Scope
 
 Follows a `stack-dev` session's publish. Not for wiki content work - use
-`wiki-ingest`/`wiki-query`/`wiki-manage`/`wiki-lint`/`wiki-status` for that, whose own closing
-conventions (`kb/log.md`, page provenance) are unrelated to this tracker-body procedure.
+`wiki-ingest`/`wiki-query`/`wiki-manage`/`wiki-lint`/`wiki-status`/`gtd-weekly-review` for that,
+whose own closing conventions (`kb/log.md`, page provenance) are unrelated to this tracker-body
+procedure.

instructions/dev/stack-dev/SKILL.md

@@ -191,6 +191,7 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
 ## Scope
 
 Not for wiki content work - use `wiki-ingest`/`wiki-query`/`wiki-manage`/`wiki-lint`/
-`wiki-status` for that. Not for setting up a new instance (`instructions/setup-instance.md`) or
+`wiki-status`/`gtd-weekly-review` for that. Not for setting up a new instance
+(`instructions/setup-instance.md`) or
 a fresh clone of this repo (`instructions/bootstrap.md`). Not for closing a work package after
 its publish has landed - that is `stack-close` (`instructions/dev/stack-close/SKILL.md`).