From 1559f4b405c232f4ef618f1e08887905d04666b0 Mon Sep 17 00:00:00 2001 From: Torben Nehmer Date: Wed, 7 Oct 2026 09:05:32 +0200 Subject: [PATCH] docs: troubleshoot names doctor's telemetry WARN; ownership-and-templates says the configuration shapes are rendered from tools/ too (#193) Files changed: - docs/explanation/ownership-and-templates.md - docs/how-to/troubleshoot.md Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2 --- docs/explanation/ownership-and-templates.md | 5 +++-- docs/how-to/troubleshoot.md | 9 +++++++++ 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/explanation/ownership-and-templates.md b/docs/explanation/ownership-and-templates.md index ee38f10..8596a01 100644 --- a/docs/explanation/ownership-and-templates.md +++ b/docs/explanation/ownership-and-templates.md @@ -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 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 -`tools/`, which an instance leaves alone, so they come out the same everywhere. The skill +generated regions in whatever tree it runs in. Most of them render records in `tools/` - the +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 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 diff --git a/docs/how-to/troubleshoot.md b/docs/how-to/troubleshoot.md index 5f0c646..4088fed 100644 --- a/docs/how-to/troubleshoot.md +++ b/docs/how-to/troubleshoot.md @@ -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 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" Neither `$WIKI_AUTHOR` nor `git config user.name` is set. Run `git config user.name ""`, or