Skip to content

I2675 — Build-cache health, headroom and hit statistics are visible where the mesh is

Show which offers exist, which is selected and why, headroom and the statistics sccache supports, labelling estimates, on the existing health, monitor and UI surfaces.

BLOCKED wave 2 · p2 · implementation profile · runs alone

Part of development-runtime — The runtime has a development surface.

Blocked. This issue cannot start until I2672 is done. The status is derived from that, not declared.

Objective

Show which offers exist, which is selected and why, headroom and the statistics sccache supports, labelling estimates, on the existing health, monitor and UI surfaces.

Why

The owner, 2026-10-13, with full clearance: set up MinIO, an sccache server and every mesh node, verified and validated. The cluster compiles the same Rust on every machine from a cold cache; two declared offload hosts were under their disk minimum that day. See ADR 0157.

Current state

Measured on master b29cf4e487 on 2026-10-13: the UI has no mesh drill-down for services and health.rs has no build-cache check.

Desired state

A check in health, a row in monitor, a UI screen reading mesh.build_cache as a reading, and live updates over the existing event stream.

Scope

  • apps/majordomus-cli/src/capability/builtin/health.rs
  • apps/majordomus-cli/src/ui/
  • apps/majordomus-cli/src/monitor/

Out of scope

  • A new streaming transport

Dependencies

Acceptance criteria

  • A provider stopping is reflected on the screen within the stream's lifetime
  • Estimates are labelled
  • The screen is within the UI latency budget and executes nothing

Validation

  • bin/majordomus plan validate
  • majordomus bench system.http. --transport system --profile ci --no-write --check

Evidence required

  • build_cache_screen
  • health_check

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I2675.yaml. Read it back with majordomus plan show I2675.

Searches the titles and descriptions of every page this site publishes.