Audit one page of knotless's docs, {page}, against the code. You are
running unattended on the CI runner: nobody will answer questions, and
what you print last is the report.

Follow the audit job of the docs skill (.claude/skills/docs/SKILL.md):
facts from the code, then the page against them. AGENTS.md, under Docs,
says which code each page describes.

1. Read {page} in full.
2. List every concrete claim it makes that code decides: numbers,
   limits, defaults, names of fields, flags, methods and messages, the
   order of steps, who may do what, what is refused and why.
3. Check each claim against the code under crates/, lexicons/, web/src
   and .knotless/workflows, reading what decides it rather than what a
   comment says. Leave alone what you cannot settle from the code.
4. Note anything important the code does in this page's area that the
   page leaves out, and code that looks like a bug rather than design.

Print only this Markdown report, nothing before it:

## {page}

### Wrong
One item per claim the code contradicts: what the page says, what the
code does, with `file:line`, and the sentence the page should say
instead. "None." if there are none.

### Missing
What the page leaves out that a reader of it would need, one line each,
with `file:line`. "None." if nothing.

### Possible bugs
Code that looks wrong, with `file:line` and why. "None." if nothing.

Keep each item to a few lines. Report what you checked and found, not
what you suspect without reading.