Split flows/lifecycle.rs along its banners

[blooop]

Question

flows/lifecycle.rs holds five unrelated commands — stop, delete, purge, prune, reconcile — plus refresh and state resolution: 2,811 production lines, 45 top-level types, 13 banner-delimited sections that map 1:1 onto modules never created (the whole crate has zero production submodules). Split into flows/lifecycle/{...}.rs along the existing banners. Blocked on the snapshot re-scope so public-api.txt moves once, not twice.

[blooop]

Re-measured 2026-08-24 at v0.13.0, three months after this was written. The case has grown, and one part of it has moved out.

	when filed	now
total lines	—	7,481
implementation	2,811	3,085 (1,655 excluding comments/blanks)
top-level types	45	47 exported, plus 66 callable entry points
banner sections	13	13

New evidence for the split, beyond size:

• 28% of the crate's reachable surface is this one module. 644 of the 2,301 rows in public-api.rest.txt name flows::lifecycle; the next largest, flows::launch, is 353.
• The file's doc contradicts itself. Line 1 says "everything that removes something"; line 37 admits --reconcile "removes nothing at all". Four of the seven groups remove nothing and serve the launch path instead — the refresh latch (:173-390), the fetch sweep (:392-509), identity and container state (:511-705), and devpod's record format (:2765-2960).
• The test module leaked into crate surface. mod tests is pub(crate) mod tests so flows/provision.rs:4746 and flows/provision/verdict_cache.rs:313 can import tests::devpod_home_with — a fixture promoted because a devpod-home module does not exist.

One refinement to the plan: the :2765-2960 group is not a lifecycle submodule at all. It is a devpod adapter — it reads and writes devpod's own JSON — and its consumers are almost entirely the launch path. #394 takes it to clients/ instead, which also removes the pub(crate) mod tests leak. Worth landing that first so this split has one less section to place.

(Found by a fresh architecture review that did not check the open maps first, so this arrived as duplicate #396, now closed.)

[blooop]

Claimed 2026-08-29: queued in the session working map #299's build tickets (waves behind #340/#349's PRs so the api surface and shared JSON writer move once). Build to follow from an opus agent in an isolated worktree. If you are another session seeing this, do not double-build.