Files
chemenu/docs/reference
torbenandClaude Code f25ee6a1ce
CI / verify (push) Successful in 7m58s
CI / pwsh (push) Successful in 2m31s
Release / release (push) Successful in 35s
Release / wiki-mirror (push) Skipped
doctor: the structure check's description names sites/CONTRACT.md, which doctor has required since the instance's site handlers (#210 close); 10.0.0-beta.5
Files changed:
- CHANGES.md
- VERSION
- docs/reference/commands/instance-health.md
- tools/CONTRACT.md
- tools/chemenu/commands/doctor.py

Co-Authored-By: Claude Code <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
2026-10-11 16:06:05 +02:00
..

Reference

Lookup pages: the command surface, exit codes and gates, the skill catalogue, the page types. A reference page describes what is, not how to use it or why it is so - and wherever a source for it exists in the code, it is generated from that source and checked against it rather than written by hand.

  • Command reference - every wikitool command, one page per group, generated from the same records as tools/wikitool <command> -h.
  • Exit codes and gates - which commands can stop and wait for a person, and why.
  • Skill catalogue - the skills the stack ships, what each does and which requests start it, generated from their SKILL.md.
  • Page types - every page type the stack ships for kb/, its subtypes, where its pages are written and its required fields, generated from the type-specs.
  • Configuration - the environment variables wikitool reads and the per-checkout files an operator may create. The shape of each file is generated from the record its loader reads it with; the environment variables and what each setting does are written by hand.

The skill catalogue and the page types describe the stack's shipped defaults, which an instance may change or extend; tools/wikitool instructions list and tools/wikitool types describe <type> show what one instance has.