Release rings compatibility view (FR-40, FR-41, FR-44, FR-45; refusals FR-42/43) #4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per the release-rings roadmap addendum (docs/superpowers/plans/2026-10-09-ditdash-release-rings-roadmap.md) and the 2026-10-10 addendum in docs/superpowers/plans/2026-10-09-ditdash-handoff-brief.md. FR-40/41/44/45 (compatibility view) + FR-42/43 (refusal handling, folded into v1's converge-action units per the alignment rules).
ditdash reads dito's envelopes only (DR-2): dito ring list/show --json (ring-list.schema.json, dito D4) rendered as hosts/tenants/apps/releases panels with the status vocabulary ok/pending/waiting/held/blocked/warning/unknown; DTO-RING-* refusal objects surfaced by converge actions; entity reads gain the new dito fields (needs_from_host, one_way_crossed, min_host_release, compat_status, frontier, promotes, ...). No dito placement verb exists - tenant host moves stay inside dito tenant converge; the UI presents the converge action, not a move verb.
Acceptance per the roadmap addendum's U-items (U-F5, U-I10, U-I11, U-J3c, U-J5c, U-RB3).