carlos / platform Public

Publish per-app liveness into the aggregate feed so the apps list can say "All good" Feature Request open

Migrated from github.com/carlosframework/platform issue #127, opened 2026-08-09. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".

Still outstanding: No per-app process liveness feed, so the apps list cannot honestly say "All good".

---

The console-clarity batch (PR: console-clarity-batch branch) adds a health verdict chip. On the app Overview it can honestly say All good because the page runs the per-app metrics sweep. On the apps list it deliberately says Deployed instead — the list has no liveness source, and claiming "All good" from registry provisioning data alone would reproduce the exact false positive the batch removes (dead process behind an issued cert reading as healthy).

FleetApp.Healthy in status/fleet.json won't do: it derives from the same provisioning enum (r.Status != "ready", internal/status/fleet.go:446).

Gap: boxes should publish per-app process-liveness (e.g. reporting/asleep/expected counts per app, from the same source the instances-metrics sweep reads) into the aggregate feed, so the account home can render the full verdict without N per-app sweeps.

From the 2026-08-09 ease-of-understanding critique (P0: "no health verdict anywhere"), scope-out (1) of the clarity batch.