chore(source-control): replace the provenance-gated floor with the full fix #8278

Activity

1. kyle-sexton

   added

   status: confirmedA maintainer confirmed the item is real and in scope; ready to be worked.A maintainer confirmed the item is real and in scope; ready to be worked.

   needs-specNeeds a Brief or plan before anyone can build it.Needs a Brief or plan before anyone can build it.

   on Oct 18, 2026
2. kyle-sexton

   added the

   Task

   issue type on Oct 18, 2026
3. kyle-sexton

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   and removed

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 18, 2026
4. kyle-sexton commented on Oct 25, 2026

   

   kyle-sexton

   on Oct 25, 2026

   MemberAuthor

   More actions

   Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

   To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.
5. kyle-sexton

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 25, 2026
6. kyle-sexton commented on Oct 25, 2026

   

   kyle-sexton

   on Oct 25, 2026

   MemberAuthor

   More actions

   Hold restored: the 2026-10-25 release took needs-human off, but this issue does need a person under the owner's stop rule. Reason (security): Done when: "The owner has re-decided the floor's scope with an agent identity in place." (security floor scope; also blocked on #7711)
7. kyle-sexton commented on Oct 29, 2026

   

   kyle-sexton

   on Oct 29, 2026

   MemberAuthor

   More actions

   Decision recorded.

   Closed as superseded. The owner has re-decided the floor's scope, which is what this issue's done-when asks for. Judged on origin/main 184c64786e.

   This issue's done-when: "The owner has re-decided the floor's scope with an agent identity in place." The owner re-decided it on 2026-10-29, and he made the decision without waiting on an agent identity.

   • Owner, Q15, 2026-10-29, verbatim: "We shouldn't really have any path restrictions at all... like that is just bullshit friction", then "We can go in and harden later".
   • Owner, Q16, 2026-10-29, verbatim: "There should be no path restrictions. We can add that in later. Just get this shit going: low member, low friction, highest throughput." Also verbatim: "it isn't me, our bots, our apps, or our GitHub apps... we don't have that scenario, so we're adding unnecessary friction."
   • Owner standing direction §10, 2026-10-29, verbatim: "Hardening (re-adding holds, pins, reviews) is deferred to after that, as configuration edits".

   That answers the question this issue left open: the floor does not apply to every lane PR, and it does not come back scoped by provenance. It stays off. The full fix's step 1, an agent identity (#7711), was only a precondition for re-asking the owner. The owner answered without it, so step 1 no longer gates this issue.

   Where the work stands:

   • The HIGH path floor has been off on main since feat(pr-pipeline): stop holding on trusted paths and lane-clearable refusals #9826 (2026-10-26): docs/conventions/pr-pipeline.yaml:1094 reads high-path-floor: false.
   • feat(pr-pipeline): turn path-based merge holds off behind one switch (owner Q15) #11058 (open) turns the remaining path-based merge holds off behind one switch, per Q15.

   Scope of this close: only the path floor's scope. This close decides no other hold. Q15 (2026-10-29) kept both review lanes, ci-status checks, gitleaks, do-not-merge, cost holds, the breaker and kill switch, the App's missing workflows permission and the hub post-merge audit. If the hardening pass after open issues and PRs reach 0 brings a floor back, it does so as a configuration edit (§6, §10), tracked in a new issue.

   • The owner has re-decided the floor's scope: no path floor for now, hardening later. (owner decision Q15/Q16, 2026-10-29)
   • The agent-identity precondition is dropped. (body, amended: the owner re-decided without it, so it no longer gates the scope decision)
8. kyle-sexton commented on Oct 29, 2026

   

   kyle-sexton

   on Oct 29, 2026

   MemberAuthor

   More actions

   Closed as superseded by owner Q15/Q16; see the record above.
9. kyle-sexton

   closed this as not plannedon Oct 29, 2026