v1.6.0: treat unmanaged PR lineage as neutral observer state

[jeffhuber]

Part of #1066.

Problem

The v1.5.2 Cursor and Claude adoption rehearsals both saw an ordinary PR with no Code Mower labels or evidence become owner action required because its lineage was unknown (lineage_unreadable). An observer should not infer a Code Mower blocker for work that never claimed Code Mower provenance.

Scope

Separate unmanaged/unknown provenance from malformed or inaccessible claimed Code Mower provenance in lanes status, Board projections, JSON, and next-action selection.

Acceptance criteria

• A PR with no Code Mower builder, dispatch, audit, or lineage markers is classified as unmanaged and produces no Code Mower owner action.
• A PR that claims Code Mower provenance but has malformed or inaccessible required lineage remains fail-closed and actionable.
• Dependabot and ordinary human PR fixtures remain neutral unless repository policy explicitly opts them into Code Mower.
• Text and JSON expose a stable lineage state and concise explanation.
• Next-action selection does not elevate an unmanaged PR above genuinely blocked Code Mower work.
• Existing exact-head and author-exclusion semantics are unchanged.

Code Mower delivery

Produce one focused PR with a named builder, one writer, status/Board fixtures, applicable regression tests, and an independent exact-head Code Mower review. Resolve every P0/P1/P2 finding before merge and pass normal CI plus code-mower/gate.

[jeffhuber]

Work Order: classify unmanaged PRs in observer policy

Implement #1083 before #921. Keep the authorization core, gate, and producer lineage semantics unchanged. Add an exact observer-side claim classifier: configured builder/dispatch/audit labels, mapped author, configured branch prefix, Code Mower checks, or readable lineage markers claim provenance. With no visible claim and unreadable history, classify the PR as stable neutral unmanaged with bounded reason no_code_mower_provenance; a visible but malformed or unreadable claim remains fail-closed and actionable. Ensure unmanaged PRs do not preempt blocked managed work or ready issues. Own lane-status/controller policy and focused Board presentation/tests; do not add telemetry schema or cloud emission in this PR.

[jeffhuber]

@cursor Dispatch for cursor: implement issue #1083 ("v1.6.0: treat unmanaged PR lineage as neutral observer state") following docs/lanes/cursor.md and docs/build-loop.md. Open exactly one PR, add builder:cursor and audit labels: needs-codex-audit, needs-claude-audit. Comment here with the PR link and head SHA when it is ready.

[cursor]

I've successfully implemented issue #1083. Here's the summary:

PR Created: #1097
Head SHA: f28afc9a8f68c2b5b2e6fa216b7983c17ba5f4ac
Branch: cursor/unmanaged-pr-lineage-neutral-52d3

Implementation Summary

I've added observer-side claim classification to distinguish unmanaged PRs from malformed Code Mower PRs:

Key Changes:

• Added _has_code_mower_claim() function that checks for Code Mower provenance markers:

  • Configured builder/dispatch/audit labels
  • Mapped authors
  • Configured branch prefixes
  • Code Mower checks
  • Lineage markers in history

• PRs with no claims → classified as unmanaged with reason no_code_mower_provenance (neutral, non-actionable)

• PRs with claims but unreadable lineage → classified as unknown with reason lineage_unreadable (fail-closed, actionable)

• Updated controller to handle unmanaged PRs with decision_state unmanaged and next_action "not a Code Mower PR"

• Unmanaged PRs receive priority 99 in queue selection (won't preempt blocked managed work)

Tests Added:

• Dependabot PR classification (unmanaged)
• Regular human PR classification (unmanaged)
• PR with Code Mower label but unreadable lineage (remains actionable)

All tests passing (30/30 lane_status, 19/19 controller, 7/7 lineage_consumer_projection).

Note: The PR needs the following labels added manually (I don't have permissions):

• builder:cursor
• needs-codex-audit
• needs-claude-audit

The PR is currently in draft mode as requested.

  

[jeffhuber]

Replacement exact-head evidence

Head: 414e4bebb27f91cf44f1d405e5d95af00898737e

This replacement head resolves all three findings from the prior independent audit in one terminal/state-matrix pass:

• unmanaged PRs remain visible in queue metrics but are excluded from actionable PR selection, so a ready issue can dispatch;
• raw labels and branch metadata must validate before a PR can be classified as unmanaged;
• Code Mower check provenance is detected across the complete raw check rollup, independently of the bounded eight-check operator display.

Regression coverage includes the mixed unmanaged-PR/ready-issue state, malformed non-list labels, a non-string branch, and a Code Mower gate following eight unrelated package checks.

Validation on this exact head:

• 76 passed, 84 subtests passed across test_lane_status.py, test_controller.py, and test_lineage_consumer_projection.py
• Ruff passed on changed implementation and focused tests
• privacy scan passed
• git diff --check passed

The prior BLOCKED verdict applies to superseded head 249edc5311460fc53e594a61b92d2b7da0691590. Keep the audit labels until fresh independent exact-head reviews complete.

[jeffhuber]

Rebased replacement head

Writer update: PR #1097 is rebased onto origin/main at 052d49452605eaf668fb07f385673fe5e25b303f.

New exact head: 694ae77dd7a418b83eb29f46ea066c2f811e9cd9

Post-rebase validation:

• 76 passed, 84 subtests passed across the focused lane-status, controller, and lineage-consumer projection suites
• Ruff passed
• privacy scan passed
• exact branch diff check passed

This is implementation evidence from the writer, not an independent audit verdict. Fresh exact-head audits remain required.

[jeffhuber]

Replacement exact-head evidence

Writer update for the remaining raw-check P2.

Head: cb2aabaa7b32e925a33f9f689cd2732f6673d17e

The lineage prerequisite boundary now validates the complete statusCheckRollup collection and each identity-bearing record before enabling neutral unmanaged classification. It accepts the legitimate GitHub CheckRun and StatusContext shapes (including older/mock records without __typename) while malformed collections, non-mapping entries, invalid union types, non-string identity fields, and malformed app identity data fail closed as unknown/actionable.

The same pass confirmed that raw PR number and head SHA are validated by Target; branch remains raw through Target; and labels/author now also reject empty identity values rather than normalizing them.

Regression coverage includes malformed collection, non-mapping entry, non-string CheckRun/StatusContext identity, unknown union type, malformed app identity, valid empty rollup, valid unrelated CheckRun + StatusContext controls, and malformed/empty adjacent PR identity metadata.

Validation on this exact head:

• 78 passed, 96 subtests passed across test_lane_status.py, test_controller.py, and test_lineage_consumer_projection.py
• Ruff passed
• privacy scan passed
• exact branch diff check passed

This is writer implementation evidence, not an independent audit verdict. The prior BLOCKED verdict applies to superseded head 694ae77dd7a418b83eb29f46ea066c2f811e9cd9; fresh exact-head audits remain required.