Cockpit readiness: implement selected path and role applicability model

[smota]

Background & Problem Statement

Epic: #156

Cockpit needs to know which roles/checks are applicable for a goal. Without selected-path awareness, it may penalize intentionally skipped roles.

Proposed Solution

Introduce Selected Path model with profile, risk, applicable roles, skipped roles, and reasons.

Requirements

• Infer or read profile: bounded, standard, high-assurance, exploratory.
• Infer or read risk: low, medium, high.
• Map profile/risk to applicable roles/checks.
• Record skipped roles with reasons such as low-risk path, docs-only, not-needed, human-gated.
• Preserve explicit issue/workflow classification over weak inference.

Acceptance criteria

• Selected path model exists with tests.
• Bounded path can intentionally skip architecture/tech-writer/independent review without penalty.
• High-assurance path requires architecture, validation, human review, and PR readiness.
• UI/view model exposes applicable and skipped role sets.

Test plan

• Unit tests for bounded, standard, high-assurance, and missing classification cases.
• Regression test: skipped-by-path role does not count as missing.

Workflow classification

Architect/developer foundation issue.

[github-actions]

Integrated into development by PR #155: #155

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