refactor(#2815): derive the transient pill from the running node

The dashboard pill was declared once per DAG at submit time, so a rebuild
reported `rebuilding` for its entire life — through the prebuild, the
stop, the swap, the tail and the reconcile. It named the intent of the
request, not what was happening.

It is now read off the nodes actually running. A node lights a pill when
it is `Running` and declares the agent's own resource. Declaring is the
test, not targeting: `Prebuild` and `MetaSync` name an agent but are
lease-exempt on purpose (the container keeps serving), so they must not
light one. It is also not the lease *owner* — `resource_state()` answers
"who holds the slot", which is a different question from "what is
running", and a descendant that borrows an ancestor's grant never
appears in that map.

`TransientKind` is gone entirely rather than being re-derived. The label
is the node's own wire tag (`NodeKind::as_str`) — the same vocabulary
`NodeView.kind` already ships, so a pill and a DAG node name an operation
identically and there is no second taxonomy to keep in step. Work with no
node behind it (destroy, migration) supplies its own literal.

`DagSpec::transient`, `Claim::transient`, `DagMeta::transient` and
`NodeKind::Dag`'s `transient` field all go with it.

## the safety half, which is deliberately not the display half

`crash_watch::is_deliberate_stop` used to match a `TransientKind` to
decide whether a vanished container was intentional or a crash. That made
a pill's display vocabulary decide an alerting question, so renaming or
adding a label would silently move the alerting boundary.

`TransientState` now carries two independent fields: `label` (rendered,
nothing branches on it) and `deliberate_stop` (read only by the crash
watcher). The producer sets the second, because the producer is the only
thing that knows — it is not recoverable from the first.

For queue work that value is `NodeKind::takes_container_down()`, and it
is emphatically not "holds a lease": `Create` and `Start` hold the
agent's lease exactly like `Stop` does, and a container dying *while
starting* is a real crash that must keep reporting as one. The default is
`false` on purpose — a wrong `false` costs a spurious crash event, a
wrong `true` swallows a real crash silently.

## known cost, accepted on the issue

A restart no longer reads `restarting`. No `NodeKind` is unique to a
restart — `restart_chain` reuses `Signal` / `StopForUpdate` / `Drain` /
`Reconcile` — because "restart" is a property of the DAG's shape, not of
any node. A restart now reads `signal` / `stop_for_update`, then the
agent returns.

`Start` / `Stop` / `PostSwap` run inside a lease-holding ancestor and
re-declare nothing, so they light no pill and the agent reads idle for
those windows. Closing that is the resources-where-constructed work
(#2818), not this change.

Checked with clippy (`--all-targets -D warnings`), `cargo test -p
hive-c0re -p hive-jobq` (321 + 40 passed) and `nix fmt`.

hive-c0re/src/job_queue/submit.rs

@@ -27,7 +27,7 @@ use std::sync::Arc;
 use super::model::{DagSpec, Dep, NodeKind, NodeSpec};
 use super::templates::{RebuildOpts, after_ok, child, node, rebuild_nodes};
 use super::{Source, templates};
-use crate::coordinator::{Coordinator, TransientKind};
+use crate::coordinator::Coordinator;
 use crate::lifecycle;
 
 fn submit_and_emit(coord: &Arc<Coordinator>, spec: super::DagSpec) -> u64 {
@@ -198,16 +198,10 @@ fn concat_subgraphs(chains: Vec<Vec<NodeSpec>>) -> Vec<NodeSpec> {
 /// Wrap assembled power-op `nodes` in a `DagSpec`. No tail node: a power op's
 /// effect is its nodes (`SetWanted` + `Reconcile`), with nothing left to do once
 /// they settle.
-fn power_dag(
-    transient: TransientKind,
-    source: Source,
-    reason: String,
-    nodes: Vec<NodeSpec>,
-) -> DagSpec {
+fn power_dag(source: Source, reason: String, nodes: Vec<NodeSpec>) -> DagSpec {
     DagSpec {
         source,
         reason,
-        transient: Some(transient),
         nodes,
     }
 }
@@ -228,18 +222,15 @@ pub(crate) fn stop_spec(
         .iter()
         .map(|(agent, running)| stop_chain(agent, graceful, *running))
         .collect();
-    power_dag(
-        TransientKind::Stopping,
-        source,
-        reason,
-        concat_subgraphs(chains),
-    )
+    power_dag(source, reason, concat_subgraphs(chains))
 }
 
 /// Assemble the start DAG from explicit `(agent, running, stale)` targets.
-/// Transient is `Rebuilding` when any down+stale agent grew a rebuild
-/// subgraph (crash-watch suppression during its Swap), else `Starting`;
-/// applied per-agent at claim time, so each agent still shows its own pill.
+///
+/// No DAG-level pill: each agent's dashboard label is derived from the node
+/// running under its lease, so a down+stale agent that grew a rebuild subgraph
+/// reports `rebuilding` during its swap and `starting` at its reconcile,
+/// without the DAG having to guess one label covering every target.
 pub(crate) fn start_spec(
     targets: &[(String, bool, bool)],
     source: Source,
@@ -249,13 +240,7 @@ pub(crate) fn start_spec(
         .iter()
         .map(|(agent, running, stale)| start_chain(agent, *running, *stale))
         .collect();
-    let any_rebuild = targets.iter().any(|(_, running, stale)| !running && *stale);
-    let transient = if any_rebuild {
-        TransientKind::Rebuilding
-    } else {
-        TransientKind::Starting
-    };
-    power_dag(transient, source, reason, concat_subgraphs(chains))
+    power_dag(source, reason, concat_subgraphs(chains))
 }
 
 /// Assemble the restart DAG from explicit `(agent, running)` targets.
@@ -269,12 +254,7 @@ pub(crate) fn restart_spec(
         .iter()
         .map(|(agent, running)| restart_chain(agent, graceful, *running))
         .collect();
-    power_dag(
-        TransientKind::Restarting,
-        source,
-        reason,
-        concat_subgraphs(chains),
-    )
+    power_dag(source, reason, concat_subgraphs(chains))
 }
 
 /// Restart a single agent. Thin wrapper over [`restart_many`].