Beagle SCM

COMMIT-002: commit: should inline the full diff as relayed hunks

COMMIT-001 (landed dac9dab7) made be commit:?<sha> append a navigable diff:?<sha> link after the metadata, keeping keeper diff-free. In use that is one click too many: the user wants commit: to read like git show — commit metadata immediately followed by the FULL diff, inline, as dog/HUNK hunks. Since keeper owns commit: and graf owns diff: (separate dog binaries, DOG routes), keeper must NOT re-roll diff rendering; instead the dispatcher RUNS graf's diff:?<sha> for the SAME resolved sha and RELAYS its hunk stream after the commit-metadata hunk — exactly the capture-and-replay mechanism the sub recursion already uses. This supersedes COMMIT-001's link.

Input

Context

• commit:→keeper, diff:→graf in DOG_PROJECTORS (dog/DOG.c:36,41); they are separate executables, so keeper cannot call graf's renderer.
• Current link emit: KEEPProjCommit (keeper/PROJ.c ~501-508) appends a diff:?<sha40> U tok32 click-target after headers+message.
• BE dispatches a projector to its dog at beagle/BE.cli.c:1104 (DOGProjectorDog(u->scheme) → exec). A capture-and-relay primitive already exists for subs: beagle/SUBS.c be_recurse_capture (fork + execvp self, capture child TLV, re-emit) and dog/HUNK.c HUNKu8sRelay (rebases each child hunk's uri, re-emits in the parent's HUNKMode).
• User intent (verbatim): "commit: should include full diff, not a link to a diff. As hunks. Just run it, relay hunks. Would that work?" — yes.

Goals

• be commit:?<sha> emits: (1) the commit-metadata hunk (headers + message, subject bold per the landed tweak), then (2) the full unified diff of that commit as the hunks graf's diff:?<sha> produces — relayed, not re-rolled.
• Works in every render mode (Color/Text/Html/TLV) and composes under sub recursion the same way a bare diff: does (so sub-pin-bump commits inherit DIFF-001's structural sub-diff for free).
• Drop the now-redundant diff:?<sha> link from KEEPProjCommit (or keep it only as the machine-mode U nav anchor if TLV consumers still want it — decide during impl).

Constraints

• Dog boundary intact: NO diff rendering in keeper; the diff comes from graf via exec+relay. The sha relayed to diff: is the one commit: resolved (keeper already resolves it; reuse that, don't re-resolve in two places).
• Read-only dog/HUNK stream; no mutation; all four URI slots still compose.
• Reuse HUNKu8sRelay / be_recurse_capture; do not invent a second relay.

WIP

Design decisions (to confirm in session)

• Where to chain. Option A (preferred): BE dispatcher special-cases commit: — run keeper commit:?<sha> for the metadata hunk, then run graf diff:?<sha> and relay its hunks into the same output, single resolved sha threaded through. Option B: keeper keeps emitting the link and BE expands any diff:? U-link into the actual relayed hunks (more general, more surface). Lean A — it is literally "run it, relay hunks".
• Ordering vs subs. A plain commit: on a parent must emit parent metadata + parent diff, THEN recurse into subs (mirror diff:'s existing sub fan-out so pins render once, in order) — audit against the DIFF-001 diff-sub relay so the two stay coherent.

TODOs

• Confirm Option A vs B with a quick spike on BE.cli.c:1104 dispatch.
• Thread the resolved commit sha from the commit: step into a diff:?<sha> graf run; relay via HUNKu8sRelay.
• Remove/keep the COMMIT-001 link per the TLV-consumer decision.
• Test: extend test/commit/01-diff-link (or a new commit/02-inline-diff) — assert be commit:?<sha> output contains BOTH the metadata header AND the diff body (e.g. the changed token), in Color/Text/TLV; sub case asserts the sub's pin-range diff is relayed under the subpath.

Blockers and bummers

• The inlined diff inherits whatever diff: shows — DIFF-001 (landed 018a59c4) already fixed sub-pin-bump commits, so commit-show on a pin bump should now render the sub's content diff once chained.
• Relay timing vs sub recursion: flush the parent's commit+diff hunks BEFORE forking subs, or the sub hunks interleave ahead of the parent diff (same hazard BRO-002 called out for status tables).

Outcome

• Landed df596d0f (Option A): be dispatcher resolves ?<ref>→sha40 once (becommit_resolve_sha), runs keeper commit:?<sha> as a reaped pre-producer for metadata, then relays graf diff:?<sha> hunks after via the existing diff sub-fanout (BERunPipeSubs pre-producer leg). COMMIT-001 link dropped from KEEPProjCommit. Tests 01 rewritten + 02/03 added; 372/372 green.