feat(#2788): carry Skipped to the wire as its own state

A node ruled out by its own dependency edges settles `Skipped` host-side,
but the wire folded it into `Cancelled` and `dag_view` filtered it out
entirely, so a client never saw which branch a run didn't take. Post-#2785
that is not a rare shape: every approval DAG has two not-taken tails and
every rebuild has one, on the happy path as much as on failure.

`State` gains `Skipped`, and it counts as terminal — the wait loops in
hivectl's progress display and the daemon's dag-settled check decide
"finished" with `all(is_terminal)`, so omitting it would hang them on
essentially every DAG.

`dag_view` now emits skipped nodes but no longer lets them keep a DAG
alive. Serialization and completion were the same expression: a DAG left
the snapshot because its nodes had all been filtered away. Keeping skipped
nodes on the wire under that rule would pin every finished deploy in the
queue view forever, so the completion test is now its own flag.

`rollupState` in the dashboard gains the matching arm. It has no `done`
case — `done` is inferred by falling off the wire — so its trailing
`return 'queued'` catches anything it doesn't recognise, and a green
deploy would have read as permanently queued the moment the backend
started emitting the new state. The Rust and JS roll-ups have silently
disagreed before; they are edited together here and say so.

hive-c0re/src/job_queue/mod.rs

@@ -135,19 +135,14 @@ impl Default for JobQueue {
 
 /// Map a crate node state onto the wire state (`Pending` ↔ `Queued`;
 /// `Finishing` — own logic done, sub-nodes still running — reads as `Running`).
-///
-/// `Skipped` has no wire counterpart and folds into `Cancelled`: to a reader
-/// both mean "this never ran". The distinction is a *scheduling* one — it
-/// decides whether a parent's roll-up counts the node — and the wire carries no
-/// roll-up input, only display state. In practice a client never sees it either:
-/// `dag_view` drops skipped nodes from the snapshot along with `Done` ones.
 fn to_wire_state(state: JobState) -> State {
     match state {
         JobState::Pending => State::Queued,
         JobState::Running | JobState::Finishing => State::Running,
         JobState::Done => State::Done,
         JobState::Failed => State::Failed,
-        JobState::Cancelled | JobState::Skipped => State::Cancelled,
+        JobState::Cancelled => State::Cancelled,
+        JobState::Skipped => State::Skipped,
     }
 }
 
@@ -599,11 +594,17 @@ impl QueueInner {
     /// off each `hive_jobq::Node`; the client derives the DAG label, roll-up
     /// state, and DAG timestamps from the node set. Non-derivable per-node
     /// payload (`approval_id`, meta `inputs`) rides the owning node. Returns
-    /// `None` when every work node is `Done` — a fully-completed DAG drops
-    /// out of the snapshot entirely (a `Failed` one lingers until aged out).
+    /// `None` when every work node is `Done` or `Skipped` — a fully-settled
+    /// DAG drops out of the snapshot entirely (a `Failed` one lingers until
+    /// aged out).
     fn dag_view(&self, container: NodeId) -> Option<DagView> {
         let meta = self.dag_meta(container)?;
         let mut nodes = Vec::new();
+        // Whether anything in this DAG still has an outcome worth showing.
+        // Kept separate from `nodes` being non-empty: skipped nodes ride the
+        // wire so the dashboard can mark the branches that weren't taken, but
+        // they must not by themselves hold a finished DAG in the snapshot.
+        let mut any_unsettled = false;
         // DAG-level timestamps are taken over *all* subtree nodes (including the
         // `Done` ones excluded from the wire) — the client can't derive them
         // from a `Done`-filtered node set, so the host computes them here.
@@ -619,13 +620,13 @@ impl QueueInner {
             if let Some(f) = node.finished_at {
                 finished.push(f);
             }
-            // `Done` nodes drop off the wire (a finished step isn't interesting),
-            // and so do `Skipped` ones: a branch that was never taken is noise on
-            // the dashboard, and surfacing it would also drag the client-side
-            // roll-up toward `Cancelled` for a run that went fine.
-            if matches!(node.state, JobState::Done | JobState::Skipped) {
+            // `Done` nodes drop off the wire — a finished step isn't
+            // interesting. `Skipped` ones stay: which branch a run *didn't*
+            // take is the readable half of an outcome-branched DAG.
+            if matches!(node.state, JobState::Done) {
                 continue;
             }
+            any_unsettled |= !matches!(node.state, JobState::Skipped);
             let deps: Vec<u64> = node
                 .deps
                 .iter()
@@ -671,7 +672,7 @@ impl QueueInner {
                 parent,
             });
         }
-        if nodes.is_empty() {
+        if !any_unsettled {
             return None;
         }
         let is_terminal = self.dag_is_terminal(container);