Auditing the other primitive dispatches for correctness beyond existence #103

New issue

Open

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

jbr870 commented

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

Owner

Spawned from finding F-PO-47-2-8 (out-of-scope) on issue #47 during decision D-PO-47-2-8.

Original scope note: Flagged as out of scope in the approved PREQ: this feature makes an absent primitive answerable, but does not review what each PRESENT primitive returns. Unlike the other out-of-scope items this one has no sibling issue and was not rejected on its merits — it is genuinely unexamined work of the same family as #47 (an output is trustworthy only once you can tell what it is an output about). Recommending defer-to-issue.

Disposition rationale: The other primitive dispatches have never been checked for what they RETURN, only for whether they exist — and this feature is direct evidence the gap is real: pipeline_status was present, dispatched fine, and returned an answer about the wrong commit for months. Unlike the other out-of-scope items on this issue, this one was not rejected on its merits and has no sibling tracking it, so accepting it would drop genuinely unexamined work. There is already at least one known instance in the tree (#18: issue-link.sh silently downgrades an unsupported relation), which is the same shape one layer over. Spawning rather than folding into #18: #18 is a specific instance, and folding the general audit into it would make a single-bug ticket look like the topical home and attract further wrong 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-8` (out-of-scope) on issue #47 during decision D-PO-47-2-8. **Original scope note:** Flagged as out of scope in the approved PREQ: this feature makes an absent primitive answerable, but does not review what each PRESENT primitive returns. Unlike the other out-of-scope items this one has no sibling issue and was not rejected on its merits — it is genuinely unexamined work of the same family as #47 (an output is trustworthy only once you can tell what it is an output about). Recommending defer-to-issue. **Disposition rationale:** The other primitive dispatches have never been checked for what they RETURN, only for whether they exist — and this feature is direct evidence the gap is real: pipeline_status was present, dispatched fine, and returned an answer about the wrong commit for months. Unlike the other out-of-scope items on this issue, this one was not rejected on its merits and has no sibling tracking it, so accepting it would drop genuinely unexamined work. There is already at least one known instance in the tree (#18: issue-link.sh silently downgrades an unsupported relation), which is the same shape one layer over. Spawning rather than folding into #18: #18 is a specific instance, and folding the general audit into it would make a single-bug ticket look like the topical home and attract further wrong 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:12 +00:00

jbr870 referenced this issue

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

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