nordisk/dwarves

dwarves — server-side git RegisterPipeline + live RunReport Pipeline tab

Two additive capabilities that finish the two follow-ups the SSH-source + warehouse work explicitly deferred: (a) the SERVER clones on register, and (b) the demo Pipeline tab renders a REAL forge run. Both reuse shared leaves (L5), keep the SSH-only law (L6), and add no nornir crate dep (that edge is a cycle).

(a) Server-side git source on RegisterPipeline

Before, RegisterPipeline(repo_root) only registered a repo the server ALREADY had on disk; a git@… clone was a client-side CLI verb (dwarves repo add). Now the server can clone on register.

• Proto. dwarf.v1 RegisterRequest gains string source = 2; — a git@… / ssh://git@… SSH remote. When set it wins over repo_root; empty keeps the original local-path behaviour (additive, no regression).
• Handler. DwarfSvc::register_pipeline, given a source, clones/fetches it over SSH (deploy-key auth) into the forge's repos root (<repos>/<host>/<owner>/<repo>, the warehouse's sibling repos/ dir), then discovers + registers the brokkr.toml at the checkout — exactly the pipeline the cloned repo declares. The clone runs in spawn_blocking (network I/O off the async reactor).
• Reuse, never twin (L5). The clone is the SHARED crate::repo::add_repo → edda/crates/nornir-git (ssh::parse_ssh_url + gitio::clone_or_fetch, gix + russh) with the /home/dwarves/.ssh/id_ed25519 deploy key — the SAME seam dwarves repo add already used. Never the git binary (L9).
• SSH-only (LAW L6). An https:///git:// source is rejected before any I/O (inside add_repo) ⇒ InvalidArgument. The forge never authenticates over https.
• CLI seam extended. dwarves repo add <ssh-url> --server <url> now ships the url as RegisterRequest.source so the FORGE does the clone (thin mode); local (fat) mode still clones here. One verb, two placements.

(b) Live RunReport → the Pipeline tab

The dwarves-gui Pipeline tab rendered a hand-typed ledger fixture (invented Running/Passed cells). It now renders a real forge run.

• pipeline_view() runs the forge's build pipeline through the ACTUAL brokkr engine (brokkr::engine::run_pipeline, the same engine dwarves-server drives) with the toolchain-free DemoRunner, producing a genuine RunReport (parent row + a row per step, real per-step durations).
• That report feeds ForgePipelineAdapter::from_report(&dag, &report) (the constructor that already existed) → PipelineView::from_adapter — the REUSED engine-agnostic viewer (one viewer, many adapters). Steps → nodes, needs → edges.
• Because a real completed run greens every step, the tab shows all 5 nodes Done (0 running / 0 idle) — honest status, never an invented in-flight cell. Swapping DemoRunner for RealRunner makes the same pane a live cargo build with no adapter change.

Testability (L4 — observed from outside, RED-when-broken)

• register+source (server): an injected network-free clone seam materialises a checkout with a brokkr.toml; a RegisterRequest{ source } is asserted to clone → discover → register (RED if source were ignored — repo_root is empty). A second test proves an https:// source is refused as InvalidArgument before any network I/O (the SSH-only law at the register surface).
• live report (demo): the Pipeline pane, fed the real RunReport, is asserted to hold 5 nodes / 5 edges and all-Done status counts (0,0,5,0) — driven headless over the tabbed host's state_json/update_json robot seam, emitting a nornir-testmatrix cell.