v0.270.0: no update for a current app (R-679); an interrupted install is reported (R-681); a restore brings back the pinned version's health check (R-669); R-674

Five red-proofs. MinAgent 0.131.0 unchanged.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

controller/README.md

@@ -718,6 +718,12 @@ tested digest; an INSTALLED app keeps the digest it runs until a guarded update
 over and never renders a newer one (v0.269.1, `CarryDigests`). An update judges the new
 version by its own `.felhom.yml` (the step's, or the catalog's). A stranded app's Remove keeps the data.
 
+**No update for a current app; interrupted installs (v0.270.0).** An Update on an app already at the catalog
+head answers `409 already_current` and moves nothing (R-679). An install cut off by a controller restart is
+finished at the next start: what it started is removed (volumes kept), `app_deploy_failed` is sent, and the
+apps page says the install was interrupted until the next install (R-681). The recovery unit keeps the pinned
+version's `.felhom.yml`, and a restore makes it the applied record (R-669).
+
 **Start/restart never answer "completed" (v0.263.0, R-642)** — they answer what was requested and the
 state the containers are in at that moment; whether the app works is the health probe's to say.