ditdash U-I3b: live panels sha-to-sha (store_ref never compares) #3

Merged
jsutter merged 1 commit from ditdash-u-i3b-live-panels into main 2026-10-10 02:13:24 +00:00
Owner

The #live panel compares recorded vs observed deployed-commit shas; a store_ref alone never yields drift (unknown instead). Previews render token-free on page and twin; pre-N5 bundles render honest absence; the recorded cell gains the rollback marker + newer-release rung; the observed cell shows the display-only store_ref. 8 snapshot digests refreshed via the suite mechanism. Critic gate: C3 approve (INFO only); full cargo test + clippy -D warnings green (dispatcher-run).

The #live panel compares recorded vs observed deployed-commit shas; a store_ref alone never yields drift (unknown instead). Previews render token-free on page and twin; pre-N5 bundles render honest absence; the recorded cell gains the rollback marker + newer-release rung; the observed cell shows the display-only store_ref. 8 snapshot digests refreshed via the suite mechanism. Critic gate: C3 approve (INFO only); full cargo test + clippy -D warnings green (dispatcher-run).
Wire the app page's live/branches/previews panels to the frozen U-R3N5
contract rows. The recorded-vs-observed agreement compares git shas
(recorded rev-parse against U-O5's deployed-commit series); the legacy
store path/image rides the observed side as display-only `store_ref` and
never enters the comparison — an observed side carrying only `store_ref`
(sha null) renders `unknown` with the named sha-absent gap, never `drift`.
The recorded cell renders the rollback marker and the row-level
`newer_release`; `#branches` renders the branch table (forge link, head,
ahead/behind + compare link, open PR, preview state, merged-undeleted,
truncation note); `#live` renders preview rows after the channel table
(a link-kind row never carries an address, FR-19). The development tab
stays gapped naming U-F4. The two U-R3N5-naming gap strings become
data-absence statements for rows the bundle genuinely does not carry.

Assisted-by: worker-local:sage-ai/sage
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
deepnet/ditdash!3
No description provided.