Verify 209-CAB-48 (1 items)

[github-actions]

Verification pass from the issue form.

field	value
location	209-CAB-48 — Cabinet 48
confirmed present	1
marked missing	0
verified_by	maddybernstein
last_verified	2026-08-06

Filed by @maddybernstein in #65.

_{Editing that issue rebuilds this branch from scratch, so any commits pushed here by hand would be discarded — make corrections in the issue, or merge and follow up separately.}

Closes #65

[sr320]

Closing this unmerged — it would recreate the data damage it's failing on, rather than fix it.

This branch was cut from a main that already contained the rows it adds. Its diff is pure additions, so merging it would duplicate itm-00114–itm-00122 and locations 209-CAB-48 / 209-CAB-49. That's what the 18 duplicate-id errors in the red check are reporting — the check ran against the merge result, not against this branch alone.

It would also move data backwards. main currently has:

itm-00114,Glass filter supplies,...,present,2026-08-06,maddybernstein

and this PR re-adds it as unverified,2021-08-29.

Rebasing wouldn't help much: the branch's whole contribution is rows that already exist, so there'd be nothing left of it. Regenerating is cleaner.

What happens next: #72 repairs the duplicate rows already on main. Once that lands, issue #65 can be re-triggered and issue-to-pr will build a correct branch from the fixed base. Issue #65 stays open — closing this PR doesn't close it.

Root cause is tracked in #72: a PR opened with GITHUB_TOKEN doesn't trigger validate.yml, so nothing re-validates a bot branch at merge time and a stale one can land dirty.