Remove the popup-states flowchart diagram and its generator

[missingbulb]

Removes dev/requirements/shared/popup-states-flowchart.png and every reference to it.

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.

Changes

• Deleted dev/requirements/shared/popup-states-flowchart.png.
• Deleted dev/requirements/shared/gen-states-flowchart.js — it existed solely to regenerate that PNG.
• Dropped the four references: the requirements.md §12 image embed, the dev/requirements/README.md layout-tree entry, the dev/procedures/fileDescriptions.md row for the generator, and the diagram pointer in the extension/events-popup/popup.js comment (the §12–§16 spec pointer stays).

@resvg/resvg-js remains a dev dependency — the UI snapshot renderer (dev/requirements/shared/render/popup-renderer.js) still uses it.

Verification

npm test — 517 tests, 0 failures, 8 skipped. A repo-wide grep for popup-states-flowchart and gen-states-flowchart returns nothing.

---

Generated by Claude Code

[missingbulb]

Conversation extract — source dialogue. Rule added: "No pack prose and no owner preferences in context means the SessionStart hook never fired — re-run it before acting on owner shorthand" (gcec RULES.md → Working rules, via #766). Capture date 2026-07-26, session cb18114b-caf1-55e6-be43-5041873ff1fd.

---

Owner:

Eliminate popup-states-flowchart.png and references.

---

Assistant:

I'll find the file and its references.
Now the text references:
All 517 pass (8 skipped). Committing and pushing.
Done — PR #760.

What was removed:

• dev/requirements/shared/popup-states-flowchart.png
• dev/requirements/shared/gen-states-flowchart.js — existed only to regenerate that PNG
• The four references: the §12 image embed in requirements.md, the layout-tree line in dev/requirements/README.md, the generator's row in dev/procedures/fileDescriptions.md, and the diagram pointer in the chooseContent comment at extension/events-popup/popup.js:260 (the §12–§16 spec pointer stays).

@resvg/resvg-js stays a dev dependency — the UI snapshot renderer still uses it. npm test passes: 517 tests, 0 failures, 8 skipped; grep for both names is clean.

Want me to watch the PR for CI failures and review comments?

---

Owner:

lgtm

---

Assistant:

Thanks. PR #760 is open and ready for review — say the word if you'd like me to merge it, or subscribe to watch CI and review comments.

---

Owner:

did you load my preferences?

---

Assistant:

No — they weren't. My session context this turn had only CLAUDE.md, your email, and the date; the Claudinite SessionStart injection (preferences + pack prose) never landed. I've now run the injection step manually and read them. That changes one thing materially: "LGTM" is your merge-to-main command, not just approval — so I should have merged instead of asking. Doing that now: this repo's divergence is CI-green-first, then squash with (#N).
Both Tests runs on 78aa0513 (push + pull_request) are green. Merging.

---

Generated by Claude Code

[missingbulb]

Rule added — "Cap and qualify every GitHub MCP list/search call" in .claudinite/local/packs/gcec/RULES.md (Working rules), plus its row in the pack README's rules table. Captured 2026-07-26 from session cb18114b-caf1-55e6-be43-5041873ff1fd (conversation-extract dispatch #783, PR #784).

The exchange: after the flowchart removal landed in PR #760, the session went to confirm CI before merging. get_status reported total_count: 0, so it fell back to listing the workflow runs for the branch — actions_list with perPage: 10 and no other narrowing. The response was 155,418 characters on one line and hard-failed the tool-result cap; the run list never reached the model. Recovery was a hand-written python3 snippet that opened the saved tool-result file and printed name/status/conclusion/sha per run — one extra call and ~6 s to learn a single fact ("both Tests runs on 78aa0513 are green").

Why the rule follows: it is the same failure mode the tracker-issue lookups hit in the #734 and #753 sessions — an unbounded GitHub MCP list/search whose payload dwarfs the one field actually wanted. The rule now says to qualify the query and cap the page size on every such call, and to prefer get_check_runs over listing workflow runs when the question is just "is this PR's CI green".

---

Generated by Claude Code