[Change] Ceremony Cockpit (UX layer for findability) — Δ3

[djm81]

Why

Teams think in ceremonies ("standup," "refinement," "planning"). Without ceremony entry points, adoption friction remains high—users must remember backlog daily, backlog refine, backlog sprint-summary instead of ceremony standup, ceremony refinement, ceremony planning. Ceremony aliases plus mode switch (scrum|kanban|safe) and exceptions-first defaults are a pure UX/ergonomics win with minimal implementation cost.

What Changes

• Add ceremony-oriented entry points: specfact ceremony standup → backlog daily, specfact ceremony refinement → backlog refine, specfact ceremony planning → backlog sprint-summary (and optional ceremony flow, ceremony pi-summary when those changes exist).
• Add --mode scrum|kanban|safe at ceremony level so defaults for filters and sections follow framework.
• Exceptions-first default section order (blockers, policy failures, aging, normal) when applicable; integrate with daily-standup-exceptions-first (E1) and Policy Engine ([Change] Unified Policy Engine (DoR/DoD/Flow/PI) — Δ1 #176).
• Documentation (agile-scrum-workflows) for ceremony commands and mode switch.

Acceptance Criteria

• specfact ceremony standup / refinement / planning delegate to backlog daily / refine / sprint-summary with same behavior.
• --mode scrum|kanban|safe at ceremony level passed through to backlog commands.
• Exceptions-first default section order for standup when Policy/flow data available.
• Docs updated (agile-scrum-workflows).

---

OpenSpec Change Proposal: ceremony-cockpit

[djm81]

Archived 2026-02-18 (ceremony-cockpit-01-ceremony-aliases). Closing to match change archive status. Grouped under Feature #363 Ceremony Command Layer.