reindex

name	reindex
description	Rebuild scans/README.md from the frontmatter of every scan in scans/. Use when the user says "rebuild the index", "the index is out of date", "reindex the scans", or after adding or revising a scan by hand. Also validates that every scan's frontmatter parses and uses a legal verdict.

reindex

Regenerate the table in scans/README.md from the scans themselves, so the index cannot drift from what is on disk.

Procedure

1. Read the frontmatter of every scans/*.md except _TEMPLATE.md and README.md.

2. Validate each. Report problems rather than silently skipping — a scan missing from the index is invisible, which defeats the repo:

   • verdict must be one of the eight in docs/verdicts.md
   • date must be YYYY-MM-DD and match the filename prefix
   • slug must match the filename after the date
   • confidence must be present for build and native
   • question must be present and non-empty

3. Sort by date descending, then slug.

4. Replace everything between <!-- INDEX:START --> and <!-- INDEX:END --> with:

   | Date | Scan | Verdict | Question |
   |---|---|---|---|
   | 2026-08-12 | [Amazon delivery scraping](2026-08-12-amazon-delivery-scraping.md) | `build` | Scrape Amazon listings and check geo-specific delivery options |
   

   Mark revised scans by appending ·rev YYYY-MM-DD to the date cell, using the last entry in revised. Truncate question at ~90 characters on a word boundary.

5. Touch nothing outside the markers.

6. Report: how many indexed, how many revised, and any validation failures with the file and the field.