docs: ausgelieferte Doku zitiert keine Issue-Nummern mehr, docs verify prueft es (schliesst #77)
CI / verify (push) Successful in 59s
Release / release (push) Successful in 37s

Files changed:
- .gitignore
- CHANGES.md
- EVALS.md
- INSTALL.md
- README.md
- VERSION
- docs/pipeline-rationale.md
- instructions/CONTRACT.md
- instructions/bootstrap.md
- instructions/dev/issue-tracking.md
- instructions/evolve-subtypes.md
- instructions/kb-profiles.md
- instructions/mcp-read-server.md
- instructions/wiki-ingest/SKILL.md
- kb/CONTRACT.md
- kb/concepts/COLLECTION.md
- kb/sources/COLLECTION.md
- raw/CONTRACT.md
- tools/.coveragerc
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/tests/test_docs_verify.py
- types/source.schema.yaml
- types/type-spec.md
This commit is contained in:
2026-09-09 18:52:34 +02:00
parent 5820924ffd
commit a51d7a322f
25 changed files with 388 additions and 68 deletions
+5 -5
View File
@@ -61,7 +61,7 @@ validator complains - and the ticked list is the only record that they happened.
`incoming/<type>/` habit) is tolerated and ignored - it carries no meaning any more.
**If this refuses because the name is already claimed** (a file stem or a bundle directory
already occupies the name anywhere under `raw/`, Gitea #64/#67), that is not this session's
already occupies the name anywhere under `raw/`), that is not this session's
call to make: whether the incoming file is a later edition of the existing source or a second,
separate one is a judgment about the world, and the command's message names both routes -
`--replaces` and renaming in `incoming/` - without recommending either. Show the message to
@@ -109,7 +109,7 @@ validator complains - and the ticked list is the only record that they happened.
--set entities=A,B,C --set concepts=D,E
```
`source_type` has no default - `new source` refuses without it (Gitea #66). Pick from what
`source_type` has no default - `new source` refuses without it. Pick from what
`tools/wikitool types describe source` lists, based on what the material *is*, not what it is
about: a session transcript is `transcript` regardless of subject, an LLM's own analysis is
`analysis` even when it reads like an article. Genuinely unclear after reading the source?
@@ -118,9 +118,9 @@ validator complains - and the ticked list is the only record that they happened.
it later without moving or renaming the page.
`fidelity` and `authority` have no default either, and `new source` refuses without them the
same way (Gitea #67) - but here there is no catalog slot to fall back on, for the reason step
1 gives. If step 1 already ran `raw accept` without `--page`, its success message printed the
exact `--set fidelity=... --set authority=...` pair to reuse here verbatim; if it did not (the
same way - but here there is no catalog slot to fall back on, for the reason step 1 gives.
If step 1 already ran `raw accept` without `--page`, its success message printed the exact
`--set fidelity=... --set authority=...` pair to reuse here verbatim; if it did not (the
file was already in `raw/`), ask the user, rather than inferring an answer from the file's
content now. Never pass `unknown` here - that value is backfill-only, written only by
`wikitool touch` on a page predating this rule.