Status: clarify optional lineage and Board version

[jeffhuber]

Problem and behavior

Status and Board views could turn missing optional lineage policy into an owner-action blocker, render an empty workflow section as prose, and make the running package version easy to overlook. They now preserve readable PR and gate state when lineage is not configured, label that lineage posture optional with the exact --config code-mower.yml next step, and reserve unavailable for configured lineage that cannot be read. The terminal and Board surfaces render an empty recent-workflow list as none, and the Board primary header explicitly says Serving version: ….

Share-oriented doctor path redaction and its focused fixture landed immediately beforehand in #1059; this PR retains that accepted boundary and completes the remaining #1055 surfaces.

Closes #1055.

Validation

• pytest -q tests/test_lane_status.py tests/test_board.py tests/test_remote_observer_doctor_1053.py tests/test_doctor_output.py — 318 passed, 302 subtests passed
• ruff check src/code_mower/lane_status.py src/code_mower/board.py tests/test_lane_status.py tests/test_board.py — passed
• git diff --check — passed

Risk and privacy

The change is presentation and decision-posture logic over existing metadata. It adds no source, transcript, provider output, token, or local path to Board/status output; the remote observer's no-path contract remains covered by #1059.

[gitar-bot]

Note

Automatic reviews are paused because your team has used its included automatic processing for this billing period (headroom scales with your seat count). You can still comment "Gitar review" to run one anytime, and automatic reviews resume on their own by October 1. Add seats for more headroom.
Learn more

Code Review ✅ Approved

🟡 Medium risk

Clarifies optional lineage policy and Board presentation to prevent missing configuration from blocking owner actions. Status and Board views now preserve readable PR and gate state when lineage is not configured, label that posture optional with the exact next step, and distinguish it from configured lineage that cannot be read. Empty recent-workflow lists render as none and the Board header explicitly displays the serving version. No issues found.

Review coverage

Rules No rules evaluated

Functional validation Not enabled · Set up

Options

Display: compact → Counting what did not apply, without listing it.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[github-actions]

Claude audit (merge-authority lane)

Head SHA: 6debf629c9528e7bc6bf158193bb6765c2b32739
Verdict: PASS
Review details remain in the local audit artifact.
Publication workflow: .github/workflows/local-audit-publication.yml at 8d2538b1f84abaa897baa0205efa85b9c2b52096