pr_status.pipeline_state gains no commit attribution in this slice #104

New issue

Open

opened 2026-08-25 14:59:25 +00:00 by jbr870 · 0 comments

jbr870 commented

2026-08-25 14:59:25 +00:00

Owner

Spawned from finding F-PO-47-2-10 (in-scope-deferrable) on issue #47 during decision D-PO-47-2-10.

Original scope note: Reviewer suggestion acknowledged but not actioned in this SREQ — see Expert Review > Noted (not actioned). pr_status also returns a pipeline_state drawn from the same enum, and /dev:promote's branch-pr path consumes it. It INHERITS the fall-through fix for free (it shares GL_JQ_PIPEMAP, which this slice rewrites with no catch-all), but stays ref/head-scoped rather than commit-attributed. Partially covered by this slice and partially real follow-up work; the PREQ scopes the feature to the monitor primitive. Proposing defer-to-issue for the attribution half.

Disposition rationale: pr_status returns a pipeline_state drawn from the same enum and /dev:promote's branch-pr path gates on it, so the identical false-green mechanism #47 documents exists on that path — an answer about a head pipeline with no commit a caller can check. It inherits this slice's fall-through fix for free (it shares GL_JQ_PIPEMAP, rewritten here with no catch-all), which is precisely why the remaining gap needs its own ticket rather than an accept: half of it silently got fixed, and the unfixed half would otherwise look done. The PREQ scopes this feature to the monitor primitive, so it cannot be widened here. No eligible candidate covers pr_status or commit attribution, so this spawns rather than folds. Resolved autonomously under the operator's explicit instruction in this session to resolve every decision with its recommended option.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /dev:requirements --issue={new-number} to flesh it out before planning.

Spawned from finding `F-PO-47-2-10` (in-scope-deferrable) on issue #47 during decision D-PO-47-2-10. **Original scope note:** Reviewer suggestion acknowledged but not actioned in this SREQ — see Expert Review > Noted (not actioned). pr_status also returns a pipeline_state drawn from the same enum, and /dev:promote's branch-pr path consumes it. It INHERITS the fall-through fix for free (it shares GL_JQ_PIPEMAP, which this slice rewrites with no catch-all), but stays ref/head-scoped rather than commit-attributed. Partially covered by this slice and partially real follow-up work; the PREQ scopes the feature to the monitor primitive. Proposing defer-to-issue for the attribution half. **Disposition rationale:** pr_status returns a pipeline_state drawn from the same enum and /dev:promote's branch-pr path gates on it, so the identical false-green mechanism #47 documents exists on that path — an answer about a head pipeline with no commit a caller can check. It inherits this slice's fall-through fix for free (it shares GL_JQ_PIPEMAP, rewritten here with no catch-all), which is precisely why the remaining gap needs its own ticket rather than an accept: half of it silently got fixed, and the unfixed half would otherwise look done. The PREQ scopes this feature to the monitor primitive, so it cannot be widened here. No eligible candidate covers pr_status or commit attribution, so this spawns rather than folds. Resolved autonomously under the operator's explicit instruction in this session to resolve every decision with its recommended option. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/dev:requirements --issue={new-number}` to flesh it out before planning.

jbr870 added the

labels

2026-08-25 14:59:25 +00:00

jbr870 referenced this issue

2026-08-25 14:59:26 +00:00

release-pipeline-status.sh --ref returns a stale pipeline — a false green immediately before a production tag #47