Epic: Cockpit domain model and GitHub workflow mapping

[smota]

Background & Problem Statement

Epic: #119

Cockpit must understand AgentFlow concepts natively: goals, epics, child issues, phases, role-pass evidence, handover comments, validation, review gates, PR readiness, and follow-ups. A generic issue list will not support goal-oriented SDLC.

Proposed Solution

Define canonical Cockpit domain model and GitHub mapping. Parse issue body sections, labels, markers, workflow-status comments, handovers, PR manifests, and relationship links into an AgentFlow read model.

Requirements

• Define entities: Goal, Epic, Workstream, Issue, Phase, RolePass, EvidenceRef, ValidationRun, ReviewFinding, Gate, PR, FollowUp, SteeringIntent.
• Define comment markers for workflow status, handover, role-pass summaries, human review requests, validation summaries, and follow-up proposals.
• Define status derivation rules from GitHub truth, not local UI-only state.
• Define relationship edges: implements, closes, blocks, depends-on, spawned-follow-up, validated-by, reviewed-by, returned-to-dev.
• Preserve docs/issue-standards.md section-targeted update discipline.

Acceptance criteria

• Domain model documented.
• GitHub issue/comment/PR mapping documented.
• Status derivation rules documented with precedence and stale-state handling.
• Comment marker schema documented.
• Parser fixtures cover epic, child issue, handover, validation, review, PR manifest.

Test plan

• Unit tests for issue-section parser and marker extraction.
• Fixture tests against representative epic/child issue/PR bodies.
• Negative tests for malformed or missing sections.

Workflow classification

High-assurance foundation. Architect and tester required; security review only if parser consumes untrusted HTML/markdown rendering.

[github-actions]

Integrated into development by PR #126: #126

Merge commit: a579156d0b0568f70dfcf3691c1ae8eff164ee22
Release/promotion to main is tracked separately.