I2943 — A mesh this process is not on is said as not observed, never as zero or no

✓DONE wave 0 · p0 · implementation profile · parallel safe

Part of surfaces-never-disagree — Every surface projects the same state, says when it was observed, and keeps no list of its own.

Objective

When mesh.peers answers that cooperation does not run in this process, /ui/mesh and the dashboard's mesh tile and panel say the mesh was not observed, with the runtime's own reason, and draw no machine count, refused-link count, journal clock or 'Mesh active: no'; the kit gains one not-observed KPI and one not-observed panel body that every screen can use.

Why

Owner order (2026-10-18, via a3): the published https://majordomus.dev/ui/mesh/ said 'Mesh active: no, Machines: 0, Journal clock: 0'. The snapshot is read on a Pages runner that is on no mesh, so that was the runner's absence presented as a measured empty mesh (the class of f6's S2 and S3). mesh.peers already answers active=false with a reason; the kit's shown() turns false into 'no' and kpi_count() an empty list into 0 (ui/mesh.rs, ui/dashboard.rs).

Current state

An unobserved mesh is drawn as 'Mesh active: no', 'Machines: 0' and 'Journal clock: 0' on /ui/mesh, and as 'Mesh active: no' on the dashboard.

Desired state

Both say 'not observed: this runtime is not on the mesh (<reason>)' and draw no figure; a running mesh is drawn as before.

Scope

• apps/majordomus-cli/src/ui/view.rs
• apps/majordomus-cli/src/ui/mesh.rs
• apps/majordomus-cli/src/ui/dashboard.rs
• test/cases/3343_an_unobserved_mesh_is_never_zero.sh

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• A served /ui/mesh of a repository whose mesh is off says 'not observed' with the reason, and contains no 'Mesh active', 'Journal clock', machine count or empty-mesh sentence
• The dashboard of the same repository says the mesh was not observed and draws no 'Mesh machines' count
• A running mesh is drawn with its counts as before

Validation

• cargo test --lib ui::
• bash test/run.sh 3343_an_unobserved_mesh_is_never_zero 1089_the_work_and_mesh_screens_answer

Evidence required

• unobserved_mesh_case

Evidence

Timeline

started

2026-10-18T03:06:03Z

verified

2026-10-18T03:06:15Z

completed

2026-10-18T03:06:33Z

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/I2943.yaml. Read it back with majordomus plan show I2943.