analysis: complete the systematic claim verification; add F-017 and ADR-0010 draft

verify_claims.py gives all 813 claim rows a mechanical disposition;
the 28 flags were adjudicated by hand (REPORT.md appendix). Two survived
as genuine drift (F-017): a closed issue still described as open in
shared/lab-netzwerk.md, and a 'pending' decision block in hosts/cfgmon.md
whose premise the same file records as executed.

Also: narrow the vendored-path filter (it silently dropped 7 tracked
icon files and produced false path-miss flags), record the confirmed
canonical author identity in F-003, verify the Gitea#48->GitLab#46
numbering shift by title in F-005, and add the ADR-0010 draft under
analysis/drafts/ for the human to git-mv into decisions/.

Branch renamed to Neckbeard-v0.1.1-analyse-1 per the human.

analysis/HANDOFF.md

@@ -7,9 +7,9 @@ neckbeard-based management system in a **new branch**, starting fresh from this
 
 | | |
 |---|---|
-| Analysis branch | `analysis/neckbeard-fieldtest`, branched from `main` at `2f012a6` |
-| Commits | `f6a9b9f` scope · `b8b8531` inventory · `959bf88` SHA + timestamps · `eaa00f0` findings · this file |
-| Deliverables | [SCOPE.md](SCOPE.md) · [REPORT.md](REPORT.md) · [findings/](findings/) (F-001…F-016) · [data/](data/) · [scripts/](scripts/) |
+| Analysis branch | `Neckbeard-v0.1.1-analyse-1`, branched from `main` at `2f012a6` (renamed from `analysis/neckbeard-fieldtest` at session close, per the human) |
+| Commits | `git log main..` on this branch lists them: scope, inventory, SHA/timestamps, findings, report/handoff, reach correction, verification pass |
+| Deliverables | [SCOPE.md](SCOPE.md) · [REPORT.md](REPORT.md) · [findings/](findings/) (F-001…F-017) · [data/](data/) · [scripts/](scripts/) |
 | Read first | REPORT.md executive summary, then the pattern → mechanism → implication table |
 | Neckbeard reference | `v0.1.1` @ `823a08cac6b03a47d7e2f661200a49ac6e09d38d`, `main`, clean |
 
@@ -19,7 +19,7 @@ Nothing outside `analysis/` was modified on this branch. `main` is untouched.
 
 ```bash
 git clone https://git.lab/axion1337.chat/management.git
-cd management && git checkout analysis/neckbeard-fieldtest
+cd management && git checkout Neckbeard-v0.1.1-analyse-1
 bash analysis/scripts/run_all.sh
 ```
 
@@ -79,9 +79,30 @@ The human confirmed their own working copy points at canonical git.lab, not the
    itself makes every commit look non-anonymised.
 8. **Link statuses stayed at the three mandated values**; the nuance moved into a `kind`
    column rather than inventing a fourth status.
+9. **The claim sweep was completed inside Session 1**, after the human asked whether
+   pulling it forward would break the two-session split. It does not: verifying claims is
+   Phase-2 analysis work; only designing/fixing belongs to Session 2. Result: F-017 and
+   the REPORT appendix.
+10. **ADR-0010 exists as a draft under [drafts/](drafts/)**, not under `decisions/` —
+    the human decided it is filed in the old scheme, but this session must not create
+    files outside `analysis/`; placing it is one `git mv` by the human. Deliberately in
+    German, matching the old scheme it belongs to (a stated deviation from this
+    session's English-artifacts rule).
+11. **Session-close corrections by the human**, both binding for Session 2: the Gitea
+    mirror is **private to the owner**, not public (reach of F-002/F-003 rewritten —
+    the exposure is prospective, via a possible future git.lab→GitHub push); canonical
+    author identity is `Thore Cimbal <cfx@riot.8shield.net>` (F-003 addendum).
 
 ## Where Session 2 should start
 
+**Standing directive from the human (session close):** before applying anything, work
+through the failures of *both* approaches — the drift this report found in the
+management approach *and* the seven neckbeard gaps it exposed — and where the old
+approach carries value that fits neckbeard's philosophy (candidates are the four
+works-well findings, the milestone/priority evidence in F-014, the mirror-topology
+prose in F-013), fold that value into neckbeard rather than discarding it. Adoption
+comes after that two-way harvest, not before.
+
 The pattern → mechanism → implication table in REPORT.md is the input. Two things gate
 everything else:
 
@@ -98,11 +119,13 @@ migration is size L, so `WORKFLOW.md` Gates 1–5 with a design doc in `docs/des
 
 In descending order of how much they could mislead Session 2.
 
-1. **Claim extraction is trigger-based, not semantic.** `claims.tsv` holds 813 candidate
-   lines matched by regex patterns, biased toward recall. I verified the claims the
-   mandatory checks and the findings required — not all 813. A claim that is false but
-   matched no trigger, or matched one and was not among the ones I chased, is not in this
-   report. This is the largest hole in the analysis.
+1. **The claim sweep is complete mechanically, not semantically.** Every one of the 813
+   rows now has a disposition (REPORT appendix), and all 28 mechanical failures were
+   adjudicated by hand. What remains open is honest but real: 360 rows carry no
+   mechanically checkable token — their truth is prose about hosts, procedures and
+   history that only a human or a live system can judge. And extraction itself is still
+   trigger-based: a false sentence containing no path, issue, ID, date, count or
+   status word was never in `claims.tsv` to begin with.
 2. **`git ls-remote` against `rohana.axion1337.de/sorb/<name>` is how I concluded
    `game-operating` has no mirror** (F-007). That rests on the naming convention holding,
    which I verified for six repos but cannot prove for the seventh. The contradiction