lifecycle: close out remove-inline-standalones (was mis-parked as incomplete)

[Jammy2211]

Summary

Records-only fix. The matplotlib-inline-standalones task was shown on the dashboard as in-flight/parked, with a 2026-08-08 orphaned-prompt-triage note reading "VERIFIED INCOMPLETE, not shipped". That verification was wrong — the code work shipped on 2026-07-24. This PR corrects the registry so the task leaves the board.

Why the triage was wrong

The triage grepped for %matplotlib inline and treated every hit as remaining work. The prompt only ever covered standalone comments, and explicitly excluded the old commented-out pyprojroot bootstrap block.

Ground truth on the two workspace mains:

Repo	%matplotlib inline occurrences
autogalaxy_workspace	0
autolens_workspace	4, all line 1 of a pyprojroot block

The four AutoLens survivors are in the imaging + interferometer potential_correction/start_here script/notebook pairs, each appearing as:

# %matplotlib inline
# from pyprojroot import here
# workspace_path = str(here())

That is precisely the set merged PR autolens_workspace#337 records as out of scope: "The four old-bootstrap potential-correction examples remain deliberately out of scope." The two survivors the triage cited (scripts/{imaging,interferometer}/.../start_here.py) are two of these four.

Corroborating evidence: autogalaxy_workspace#160 closed-completed 2026-07-28; PRs autogalaxy_workspace#161 and autolens_workspace#337 both merged 2026-07-24; the dependent pyprojroot sweep shipped separately as autocti-notebook-bootstrap.

No standalone occurrence survives. Nothing remained to do.

Root cause

Lifecycle drift, not a code gap. The completion record was written under slug remove-inline-standalones, but the originating prompt was never removed from active/. The orphan was later rediscovered and mis-verified.

Changes

• Fold active/matplotlib_inline_standalones.md into complete/2026/07/remove-inline-standalones.md under ## Original prompt — the record was missing that section — plus a dated verified: note recording the ground truth and why the mis-park happened, so the next triage does not repeat it.
• Drop the stale parked.md entry.
• Regenerate dashboard.md (in flight 10 → 9, parked 4 → 3).

Test Plan

• lifecycle.py check — OK
• lifecycle.py orphans — none
• lifecycle.py index --apply — regenerates complete/index.md identically (no diff)
• dashboard.md regenerated via pyauto-brain intake --apply dashboard, not hand-edited

Follow-up (not in this PR)

parked.md still carries pyautoreduce-slacs1430-acs-comparison from the same 2026-08-08 triage, marked "STATE UNVERIFIED" pending a collaborator dataset on the laptop. Given this entry proved a false positive, that one may be worth re-checking too — it cannot be verified from a cloud session.

---

Generated by Claude Code