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

I2656

The diagram viewer serves the Cockpit and majordomus ui, and a node that is a repository file links to its source

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
surfaces-never-disagree
Milestone status
ACTIVE
Wave
1
Waiting on
I2653
Holds back
none
Behind it in all
0
Evidence
0 of 2
In the waySubjectDetail
issueI2653I2653 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 I2656

majordomus plan verify I2656

majordomus plan done I2656

What it is

Objective
Extend what I2653 built in two directions it left out: let the Cockpit and majordomus ui render a Mermaid diagram through the same viewer instead of a second implementation, and link a node whose label is a tracked file path to that file at the commit the site was built from.
Why
ADR 0152 scoped the viewer to the published site. Rule project.a-diagram-is-drawn-not-typed names four renderings of one relationship (site, Cockpit, terminal, API); the site now has one viewer and the other browser surfaces have none. Diagrams on the site name files (.ai/repo/policy.yaml, scripts/generate-site-data) that the inference leaves as text, although scripts/ci/link-check already decides blob links against git.
Now
share/design/figure.css is imported by the site only; share/cockpit and share/ui load no diagram viewer; the link index holds site routes only.
Wanted
The viewer and its stylesheet are served to the Cockpit and the UI from one source under the content policy those surfaces set, with the design contrast derivation reading figure.css; a node whose whole label is a tracked path links to its blob at the built commit, and scripts/ci/link-check resolves it.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • A diagram in the Cockpit is drawn by site/diagrams.js under the Cockpit content policy
  • A node labelled with a tracked path is listed as a link to that file and link-check passes it; an untracked path is not linked
  • majordomus design contrast measures the pairs figure.css uses
Validation
node --test scripts/lib/diagrams.test.mjsscripts/rust-check
Evidence required
cockpit_viewer_casefile_link_unit_tests
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
site/diagrams.jsshare/design/figure.cssshare/cockpit/src/cockpit.cssshare/ui/src/ui.cssapps/majordomus-cli/src/design/contrast.rsscripts/lib/diagrams.mjsscripts/lib/diagrams.test.mjs.ai/repo/project/issues/I2656.yaml
Not
A second viewer for any surface
Depends on
I2653
Priority
p3
Profile
implementation
Parallel safe
true
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.