* feat(layout): collapse LayoutNode to container | segment (2de.11)

[LAW:one-type-per-behavior] LayoutNode is now exactly `container | segment`.
The `inline` and `stepper` node kinds are deleted: interaction, state-driven
display, and multi-region clickability all live in a segment's TEMPLATE (via
widgets today; the `actions:` model in .12), so they were variability the node
type should never have carried. A `segment` is THE unit of rendering — one ref
into the named segments map, rendered to one strip item (the 2de.10 structural
join). `cells` and `layout` rows survive as authoring SUGAR, lowered at the
loader to `container(horizontal, [segment…])` so nothing downstream sees more
than two kinds [LAW:one-source-of-truth].

Deleted (their surface is gone, not relocated yet):
- InlineNode/StepperNode/InlineCell/ClickWrite types + nodeStateUse projection
- node-registry inline/stepper arms, the composite "HUE PIN", setStateUrl/glyphs
- validateInlineNode/InlineCell/ClickWrite/StepperNode loader validators
- deriveNodeValidators/nodeContributions/nodeDeriveSpecs; deriveValidators is
  now widget-only (the actions surface merges in at .12)
- the node-set-write session.id trigger + node backing-var cross-ref loop

Hue rotation is retained but purely DECORATIVE — each segment advances the
cursor by one, a container by none; it carries no structural meaning now that
cohesion is one-segment-one-item.

Tests: dsl-inline-cell + dsl-stepper-node deleted (they pinned the removed
surfaces); segment-render-unit #1/#2 re-expressed through the segment surface
(a link-bearing template; an empty template) [LAW:behavior-not-structure]; node
builders in the suite construct the canonical container|segment tree.

dsl-spine snapshot byte-identical; full suite green (1057); live daemon renders
the real config (widgets, hue, OSC-8) unchanged.

* refactor(layout): drop stale loader comment; delegate deriveValidators

[LAW:comments-explain-why-only] Remove a stale WHAT-comment above
layoutRowsToNode — it still described the lowering as "a vertical container of
cells leaves" and sat directly above the correct description, two divergent
copies back-to-back.

[LAW:one-source-of-truth] deriveValidators delegates to deriveWidgetValidators
rather than duplicating its body. The widget surface IS the whole writable-key
surface today, so one body means no drift; when the actions table lands (.12)
this single site becomes the widget+action merge.

Addresses PR #70 review (both nits). lint + typecheck clean; validator/loader
suites green.

---------

Co-authored-by: elton-prawn <264370887+elton-prawn@users.noreply.github.com>

… absence policy (2l6) (#96)

Sheriff findings #2+#8: git/cache providers swallowed ~10 failure paths
(stash failure rendered as 0, repoName failure as basename, failed status
as a clean fallback branch) and projectGitInfo coerced absence to ''/0
while MetricsPayload preserved it — two opposite absence rules in one file,
with render-payload's "providers log their own rejections" comment false
for exactly these two providers.

[LAW:types-are-the-program] New Outcome<T> = ok | absent | failed(reason)
(src/utils/outcome.ts). execGitAsync returns the LaunchResult instead of
flattening it to a throw; one classifier maps it per command — a non-zero
exit that is the domain answering "there is none" (no upstream, no tags,
no remote) is absent; transport failures are failed. GitInfo's on-demand
fields are Outcome-typed; getGitInfo returns Outcome<GitInfo>; the
basename repoName survives only as the explicit no-remote policy, never
as an error fallback. readTail/cacheExpiresAt distinguish ENOENT (absent)
from real read errors (failed).

[LAW:effects-at-boundaries][LAW:single-enforcer] Failure flows as a value
to each consumption surface's edge and is logged exactly once there:
buildRenderPayload (pull path, via deps.log=dlog) and GitDataProvider's
subscribe delivery fold. projectGitInfo is now a pure fold returning
{git?, failures[]}; absent and failed both project as MISSING payload
fields into applyInput's default + last_error chain.

[LAW:one-type-per-behavior] GitPayload adopts MetricsPayload's
preserve-absence policy (all fields optional); the coerce-to-''/0 shim is
gone, so "no stashes" and "stash count unknown" are no longer the same
rendered 0.

Verified live against an isolated daemon: healthy repo renders with zero
warnings (absent logs nothing), a corrupt .git produces exactly one warn
line with the real git error while the bar still renders.

Ticket: brandon-git-segment-2l6 (epic brandon-law-remediation-58c)

Co-authored-by: elton-prawn <264370887+elton-prawn@users.noreply.github.com>