[Roadmap] Gira 3.0: UI layer over stable workflow state contracts

[StatPan]

Goal

Define Gira 3.0 as the UI and dashboard layer that sits on top of the stable Gira 2.0 workflow state contracts.

Gira 2.0 should focus on completing the CLI-first control-plane core: state-aware ticket/PR resolution, evidence-based finish, workflow drift audit, milestone lifecycle, workspace queues, and stable JSON outputs.

Gira 3.0 should make those computed states visible and operational through a UI.

Related: #521, #524

Version Boundary

Gira 2.0

Core workflow state and evidence contract.

Representative outputs:

• current ticket and PR state
• review packet
• finish readiness
• finish receipt
• drift audit
• milestone/work-batch status
• workspace queues
• deterministic JSON contracts

Gira 3.0

UI layer over the 2.0 control-plane core.

The UI should not become the source of truth. GitHub remains the source of truth, and Gira CLI/state contracts remain the computation layer.

The UI should consume Gira-computed state rather than reimplement workflow logic.

Product Framing

Gira 3.0 is not a Jira clone UI.

It should be an operational surface for AI-assisted software delivery convergence:

• what is ready for an agent
• what needs human review
• what is blocked
• what failed checks
• what can finish
• what has workflow drift
• what milestone or work batch is at risk
• what evidence is missing

Candidate UI Surfaces

Workspace Dashboard

Shows a repo or multi-repo operating view:

• agent-ready queue
• review-needed queue
• finish-ready queue
• blocked queue
• failed-check queue
• stale queue
• workflow drift count
• milestone/work-batch progress

Ticket Detail View

Shows one work order as an evidence card:

• issue goal, scope, and acceptance criteria
• current branch and PR
• checks and review state
• blockers
• provenance and telemetry metadata
• finish readiness
• next safe Gira command

Review View

Shows the reviewer packet in UI form:

• issue intent
• PR context
• changed files and diff links
• checks
• repo-local review rules
• goal-fulfillment verdict fields
• residual risk and test gap capture

Milestone View

Shows a work batch boundary:

• open/closed/done progress
• ready/in-progress/in-review/blocked breakdown
• finish-ready items
• spillover candidates
• rollover recommendation

Audit View

Shows workflow nonconformance:

• closed issue with active status label
• open issue with done status
• multiple status labels
• in-review issue without linked PR
• merged PR with non-converged issue
• missing evidence or provenance

3.0 Preconditions

Before starting UI implementation, Gira should have stable 2.0 contracts for:

• gira status --json
• gira ticket status --json
• gira ticket review --json
• gira ticket finish --dry-run --json
• gira milestone status --json
• gira workspace status --json
• drift/audit report JSON

Non-Goals

• Do not make UI the source of truth.
• Do not replace GitHub Issues, PRs, checks, labels, milestones, or comments.
• Do not build a generic project-management UI.
• Do not start with hosted multi-tenant complexity before the local/CLI state contract stabilizes.
• Do not include non-public backend strategy in this public issue.

Acceptance Criteria For This Roadmap Item

• Confirm that Gira 3.0 means UI over stable 2.0 state contracts.
• Identify the minimum JSON contracts required before UI work starts.
• Choose the first UI surface: workspace dashboard, ticket detail, review view, milestone view, or audit view.
• Create follow-up design/implementation issues after the 2.0 contract stabilizes.
• Keep GitHub as the source of truth in the public OSS path.

Product Statement

Gira 2.0 makes workflow state computable.

Gira 3.0 makes that state visible and operational.