docs: design — shadow-review auto-merge gate + daily ship-report #404
No reviewers
Labels
No labels
Agent
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No assignees
2 participants
Notifications
Total time spent: 20 seconds
Due date
igor
20 seconds
No due date set.
Dependencies
No dependencies set
Reference
joshtronic/igor!404
Loading…
Reference in a new issue
No description provided.
Delete branch "design/automerge-review-gate-shipreport"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design doc for the shadow-review auto-merge gate + daily ship-report (the "get Josh out of the per-PR loop safely" project).
Please review the design here before we write the implementation plan. Nothing is implemented yet — this is the spec.
Key decisions captured:
agent.jsonautomerge.require_human(carve-outs = joshing.you, igor.bot; igor kept never-merge via no smoke.url +AUTOMERGE_SELF_REPO).APPROVE-only gates the default;COMMENTstill routes to you; all existing CI/mergeable/behind/RC gates unchanged.Spec:
docs/superpowers/specs/2026-07-20-automerge-review-gate-and-ship-report-design.md🤖 Review —
APPROVE(automated)CI for
fb72bd47: successDoc-only PR: adds a single 152-line design spec (
docs/superpowers/specs/2026-07-20-automerge-review-gate-and-ship-report-design.md) for the shadow-review auto-merge gate + daily ship-report project. Nothing is implemented; this is the spec. Verdict: approve.require_humanselector, APPROVE-only gate, flags-first rollout, scripted ship-report above the health gate) maps to a corresponding section in the doc. No fabricated work claims.success.One substantive note for whoever writes the implementation (not blocking, since it's not code yet): the design flips the fleet-wide auto-merge default from human-gated to shadow-
APPROVE-gated. That's the whole point, but it's also the highest-risk decision here — worth Josh explicitly signing off on the carve-out list (joshing.you, igor.bot, porksicle.com, igor) being complete before the gate logic PR lands, since a repo that should be human-gated but isn't flagged will silently ship unattended. The doc's fail-closed reasoning (smoke.url onboarding gate) mitigates new repos but not an existing onboarded repo that simply wasn't flagged. Flag that as the review focus on PR #3, not here.Approving the spec as-is.
Independent review by the harness on
claude-opus-4-8(effort: high). The human reviewer is requested once Igor has reviewed; a human still merges.