docs: troubleshoot names doctor's telemetry WARN; ownership-and-templates says the configuration shapes are rendered from tools/ too (#193)
CI / verify (push) Successful in 6m12s
CI / pwsh (push) Successful in 1m59s

Files changed:
- docs/explanation/ownership-and-templates.md
- docs/how-to/troubleshoot.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-07 09:05:32 +02:00
1 parent 893db6e640
commit 1559f4b405
2 files changed
+12 -2

No files matched your search

+3 -2
View File
@@ -181,8 +181,9 @@ matches, and refuses rather than overwrite what does not.
A generated verbatim file adds one more way to touch it without meaning to. The reference pages A generated verbatim file adds one more way to touch it without meaning to. The reference pages
under `docs/reference/` are verbatim, and `wikitool docs reference --apply` rewrites their under `docs/reference/` are verbatim, and `wikitool docs reference --apply` rewrites their
generated regions in whatever tree it runs in. Most of them render the command records in generated regions in whatever tree it runs in. Most of them render records in `tools/` - the
`tools/`, which an instance leaves alone, so they come out the same everywhere. The skill command records, and the shapes of the configuration files an operator writes - which an instance
leaves alone, so they come out the same everywhere. The skill
catalogue and the page types would render material an instance does own: its adopted type-specs catalogue and the page types would render material an instance does own: its adopted type-specs
and any instructions it added. Regenerated there, they would turn a shipped page into a locally and any instructions it added. Regenerated there, they would turn a shipped page into a locally
changed one, and the next upgrade would refuse to replace it. So those two pages describe the changed one, and the next upgrade would refuse to replace it. So those two pages describe the
+9
View File
@@ -44,6 +44,15 @@ older instance, that is the only step to catch up on.
`ENVIRONMENT.md.template`) and remove the line, or delete the file. It is optional, and `absent` is `ENVIRONMENT.md.template`) and remove the line, or delete the file. It is optional, and `absent` is
a valid state. a valid state.
## `doctor` reports `telemetry: WARN`
`.wikitool-telemetry.json` holds something telemetry does not read as written: unreadable JSON, a
value that is not an object, an `enabled` that is not `true` or `false`, a cap that is not a
positive whole number, or a key it does not know. Telemetry itself never stops on this. It ignores
the file or the value, or reads `"no"` as on, and the line names the field. Correct the file to the
shape in the [configuration reference](../reference/configuration.md#telemetry), or delete it to
get the default back.
## `new` stops with "No author configured" ## `new` stops with "No author configured"
Neither `$WIKI_AUTHOR` nor `git config user.name` is set. Run `git config user.name "<Name>"`, or Neither `$WIKI_AUTHOR` nor `git config user.name` is set. Run `git config user.name "<Name>"`, or