Remove the popup-states flowchart diagram and its generator (#760)

The five-state decision the popup makes is already specified in prose in
requirements.md §12–§16 and in popup.js's chooseContent comment, so the
hand-authored PNG was a second, drift-prone copy of the same information.

Deletes dev/requirements/shared/popup-states-flowchart.png and the
gen-states-flowchart.js that existed only to regenerate it, plus the four
references (requirements.md embed, requirements/README.md tree entry,
fileDescriptions.md row, popup.js comment pointer). @resvg/resvg-js stays —
the UI snapshot renderer still uses it.


Claude-Session: https://claude.ai/code/session_01VNBDf82WMVkNPvahd4b9mg

Co-authored-by: Claude <noreply@anthropic.com>

Author: missingbulb

dev/procedures/fileDescriptions.md

@@ -55,5 +55,4 @@ extension does.
 | `.claudinite/local/packs/gcec/tasks/generic-extractor-improvements/task.mjs` | The task declaration + precondition (per-project-scheduling §1): frequency `weekly`, model `opus`, outcome `open-pr`; the precondition is the old freshness gate, now pure code over the `commits` signal (fires only on a substantive change) |
 | `.claudinite/local/packs/gcec/tasks/generic-extractor-improvements/task.md` | The agentic worker spec: measure the baseline, iterate on one or more generic wins, validate, finalize. The measure→edit→re-measure loop and the genericity/trap constraints live here; the scheduler runs the precondition, so the worker starts from "a meaningful change landed" |
 | `.claudinite/local/packs/gcec/tasks/generic-extractor-improvements/postconditions.sh` | Post-work validation of a candidate win: diff-scope, full `npm test`, a real improvement over the committed baseline, and (per value arg) the jsdom-artifact check. Any non-zero exit means the run failed and must not retry or open a PR |
-| `dev/requirements/shared/gen-states-flowchart.js` | Regenerates `dev/requirements/shared/popup-states-flowchart.png` (the five-states diagram) via an SVG + resvg |
 | `dev/build/release/shipping-files.test.js` | Asserts the shipping list covers every runtime file and excludes dev/test files |

dev/requirements/README.md

@@ -125,7 +125,6 @@ dev/requirements/
     ui-requirements.js           parses requirements.md into leaf ids
     build-requirements-gallery.js + requirements-gallery.test.js   the two-column gallery
     snapshot-artifacts-dir.js    where snapshot diffs are written on failure
-    gen-states-flowchart.js + popup-states-flowchart.png
     render/                      the popup+icon rendering/diff engine
       render-snapshot.js popup-renderer.js icon-renderer.js fake-chrome.js actions.js
       refresh-snapshots.js (npm run refresh:ui)  visual-snapshots.test.js  fonts/

dev/requirements/requirements.md

@@ -1670,8 +1670,6 @@ is covered by unit tests only.
 
 When opened, the popup lands in one of **five states**, decided by the host's classification and what the extractors found (`chooseContent` + the host classifier); *how* each state renders is §1–§3, and those renderings are already pinned there by snapshots: the denylisted empty state (`2.3`), the nothing-found "Disagree?" state (`2.2`/`3.2`), and an unlisted host's event with "Suggest Correction" (`3.1`). This section pins only the two slices §1–§3 don't — each a **real popup snapshot** driven through the production `chooseContent`: whether a **supported** host shows the "Suggest Correction" label (`12.4`), and the completeness rule that decides whether a scraped event is shown at all (`12.6`).
 
-![Flowchart of the popup's five states](shared/popup-states-flowchart.png)
-
 - `12.4` **Supported host — the "Suggest Correction" label.** A supported host always shows its events (icon stays green); whether it *also* offers "Suggest Correction" depends on whether the host's own extractor contributed them. A host supported by the core generic extractor alone (no per-site file) never shows the label — the generic extractor *is* its support, so nothing was missed:
 
 <table>

dev/requirements/shared/gen-states-flowchart.js

@@ -257,7 +257,7 @@ export function makeTruncationLabel(shownCards, totalCards, shownEvents, totalEv
 // buttons to show (possibly empty), `request` is the prefill for a "request
 // support" button (or null), `policyLink` is whether to show the "Disagree?"
 // link. The five states, in the order they're decided (specified in
-// dev/requirements/requirements.md §12–§16; diagram in dev/requirements/shared/popup-states-flowchart.png):
+// dev/requirements/requirements.md §12–§16):
 //
 //   State 1 — supported host (its host is in `supportedDomains`): show its
 //     events. That's the same list the toolbar icon colors itself from, so the