Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2675

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

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
development-runtime
Milestone status
ACTIVE
Wave
2
Waiting on
I2672
Holds back
none
Behind it in all
0
Evidence
0 of 2
In the waySubjectDetail
issueI2672I2672 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2675

majordomus plan verify I2675

majordomus plan done I2675

What it is

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.
Now
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.
Wanted
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.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • 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 validatemajordomus bench system.http. --transport system --profile ci --no-write --check
Evidence required
build_cache_screenhealth_check
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/capability/builtin/health.rsapps/majordomus-cli/src/ui/apps/majordomus-cli/src/monitor/
Not
A new streaming transport
Depends on
I2672
Priority
p2
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-13
Updated
2026-10-13
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.