Probe gate: auto-file a regression issue, or print the command? nf-lzac ← Beads

open priority 2 task unassigned

Twinned from https://github.com/cfsh/ninefold/issues/409 by tools/beads/import_github.py's reconcile pass.

From #407 (the post-merge UI gate). When a merge regresses a probe on main, probe_gate.sh currently prints a ready-to-paste gh issue create rather than running it. The PR body raises this and offers to flip it; lifting it out of the prose so it can be answered from the issue list.

A — print the command (recommended default, ships today). Filing stays a deliberate keystroke. Auto-filing is outward-facing, and a flaky probe would open noise unattended, at merge time, with nobody reading.

B — file it automatically, one issue per regressing merge, and print the URL. Guarantees the regression is never lost to a scrolled-past terminal — which is the exact failure mode #389 exists to fix.

Default ships if unanswered — nothing is blocked on this.

Dependencies

None.

Comments

No comments.

Add a comment