forked from Ports/goldeneye-pc-port
findings.md: header documents the ctx-opt migration + CSV lookup path + 4 known index gaps
Cell 1 of the §F table is frozen, so four rows (D69·D78–D84, RC3·D167, the D88.x range row, D118d) are invisible to findings-index.csv — LABEL_RE can't parse their label format. Documented in the file header alongside the lookup convention and a record of what the 2026-09-15 migration did (including the one non-verbatim step: D250/D252/D255 derived statuses).
This commit is contained in:
1 parent
9c9d4a0997
commit
8687846bee
1 file changed
+13
-2
+13
-2
@@ -1,8 +1,19 @@
|
||||
# PC port — finding log
|
||||
|
||||
The raw, chronological engineering record for the port: every runtime bug,
|
||||
its root cause, and the fix. Kept unedited for transparency. Recurring
|
||||
patterns are distilled in [../porting-notes.md](../porting-notes.md).
|
||||
its root cause, and the fix. Kept unedited for transparency — with one
|
||||
documented exception: on 2026-09-15 (ctx-opt) ~122 fat §F table cells were
|
||||
moved verbatim into `## Dxx` sections at the end of this file (nothing
|
||||
deleted; three rows, D250/D252/D255, gained a status derived from their own
|
||||
verdict text — flagged in-section). Recurring patterns are distilled in
|
||||
[../porting-notes.md](../porting-notes.md).
|
||||
|
||||
**Lookup:** use `docs/dev/findings-index.csv` (label, one-liner, status;
|
||||
regenerate with `tools_pc/gen_findings_index.py`), then read only the specific
|
||||
`## Dxx` entry — never linear-read this file. Known index gaps: four rows whose
|
||||
label format the CSV generator's `LABEL_RE` can't parse (`D69 · D78–D84`,
|
||||
`RC3 · D167`, `D88.1–D88.3 · D88.5–D88.6`, `D118d`) — grep this file directly
|
||||
for those.
|
||||
|
||||
---
|
||||
## 11. Scaffolding review: findings & resolutions
|
||||
|
||||
Reference in new issue
Block a user