Not a real issue. Nothing is wrong with any schema.
This was created accidentally on 2026-07-20 by a local test harness for the schema reporting script in #9. A stubbed gh failed to shadow the real CLI, so a test run filed against this repository instead of the fake.
Kept rather than deleted so the numbering stays intact. It carries no schema-problem label and is closed, so the reporting workflow will never pick it up as its tracking issue — a genuine report will be opened fresh, with a table of the files actually affected.
Nothing here needs action.
Not a real issue. Nothing is wrong with any schema.
This was created accidentally on 2026-07-20 by a local test harness for the schema reporting script in #9. A stubbed
ghfailed to shadow the real CLI, so a test run filed against this repository instead of the fake.Kept rather than deleted so the numbering stays intact. It carries no
schema-problemlabel and is closed, so the reporting workflow will never pick it up as its tracking issue — a genuine report will be opened fresh, with a table of the files actually affected.Nothing here needs action.