torbenandClaude Opus 5.5
893db6e640
The telemetry, remotes, upload and tasks loaders take field names, defaults, coercions and their Expected: text from the record and accept exactly what they did before. doctor WARNs on a telemetry file the policy silently reads differently. configuration.md carries one generated region per file, also checked in an instance. docs reference --apply now refreshes several regions in one page in sequence instead of keeping only the last. Files changed: - CHANGES.md - VERSION - docs/how-to/set-up-the-mcp-server.md - docs/reference/README.md - docs/reference/commands/instance-health.md - docs/reference/commands/types-instructions-and-docs.md - docs/reference/configuration.md - instructions/dev/doc-pull-through.md - instructions/setup-instance.md - tools/CONTRACT.md - tools/README.md - tools/chemenu/commands/docs_verify.py - tools/chemenu/commands/doctor.py - tools/chemenu/commands/git_publish.py - tools/chemenu/config.py - tools/chemenu/config_shapes.py - tools/chemenu/reference_doc.py - tools/chemenu/tasks/caldav.py - tools/chemenu/tasks/config.py - tools/chemenu/tasks/superproductivity.py - tools/chemenu/telemetry/policy.py - tools/chemenu/tests/test_config_shapes.py - tools/chemenu/tests/test_doctor.py - tools/chemenu/tests/test_reference_doc.py - tools/chemenu/upload.py Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
1.4 KiB
1.4 KiB
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
wikitoolcommand, one page per group, generated from the same records astools/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
wikitoolreads 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.