stack: SKILL.md-Links auf repo-root-relative Pfade umgestellt, docs verify/instructions verify pruefen Linkziele

Files changed:
- CHANGES.md
- VERSION
- instructions/CONTRACT.md
- instructions/dev/doc-pull-through.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- instructions/wiki-ingest/SKILL.md
- instructions/wiki-lint/SKILL.md
- instructions/wiki-manage/SKILL.md
- instructions/wiki-query/SKILL.md
- instructions/wiki-status/SKILL.md
- tools/CONTRACT.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/instructions_cmd.py
- tools/chemenu/tests/test_docs_verify.py
- tools/chemenu/tests/test_instructions_cmd.py

instructions/wiki-status/SKILL.md

@@ -10,14 +10,14 @@ semantic review a lint pass does.
 
 **Trigger:** User asks for wiki statistics, "what's new", or a quick health snapshot.
 
-**Before the first `wikitool` call:** [session-setup.md](../session-setup.md) - step 2's `lint` is
+**Before the first `wikitool` call:** `instructions/session-setup.md` - step 2's `lint` is
 not on the budget's exemption allowlist and is counted like any other call, gitignored report or
 not (§ Scope there).
 
 **Hard rule:** read-only with respect to wiki *content*. Never create, modify, or scaffold a
 page, never repair a finding, never publish. One file does get written: the report `lint`
 produces in step 2. That is not an exception being stretched - `reports/` is gitignored and holds
-no wiki page ([reports/CONTRACT.md](../../reports/CONTRACT.md)), so the write leaves nothing
+no wiki page (`reports/CONTRACT.md`), so the write leaves nothing
 behind that the wiki ships. If something looks wrong, point the user at `wiki-lint` or
 `wiki-manage` instead of fixing it here.