ingest-documentlisted
Install: claude install-skill savnik/lindner-sommerauer-pellet-expert
# Ingest a source document
## First rule: stop, do not resolve
When anything in the source is not certain, you stop and log it. You never
best-guess. This applies to, at minimum:
- a value that is illegible, partially cut off, or could be read two ways
- a menu path that is ambiguous, incomplete, or differs between screenshots
- a parameter whose model or firmware applicability is not stated on the page
- a unit that is missing or implied
- a page whose model designation is not printed on it
For each such case you write one line to `verification.md` (see step 7),
leave a gap marker in the reference file at the place the content would go,
and tell Peter what was skipped and why at the end of the run. You do not
fill the gap from other pages of the same document, from other documents,
or from your own training knowledge. The gap is the deliverable.
## Inputs
- The path to one source document, supplied by Peter. Source PDFs and photos
live outside the repo tree and are never copied into it.
- The model and firmware the document applies to, as stated by Peter or
printed on the document. If neither states it, stop (first rule).
## Steps
1. **Read the document once, fully, before writing anything.** Note the
model, firmware, and section numbers as printed. If the document covers
more than one model, list them.
2. **Choose the target reference file.** Hydraulics, buffer, return
temperature, sensors, wiring topology and commissioning sequences go to
`referenc