Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
1
In plain terms. Should Gera switch on a new safety check now, or have it made faster first? It catches a docs page buried in wall-to-wall text while the change is still a proposal, instead of after it has already broken the website — which is what happened last time. It is built and tested. The catch: as built it inspects every docs change and adds about seven minutes to each one. Switching it on now gets the protection today and this session can make it faster afterwards. Making it faster first leaves the website unprotected a while longer. Checking only some files would be cheap but would reopen the same blind spot that let the site break.
The full question, as raised
propflow-docs#358 adds the one-pager fold gate, is green and mergeable, but touches .github/ so it needs a human press. onepager-fold has no paths: filter, so it runs on EVERY docs PR at 7m10s (fetch-depth: 0 over a ~1GB pack). Merge as-is, cut the cost first, or narrow its scope?
Why, and what was tried
The session raising this recommends: Switch it on now; make it faster afterwards Checking every file is deliberate and is itself the fix: the older workflow's file filter EXCLUDED the docs pages, and that gap is exactly how the bad page merged with nothing red, then failed every site deploy until it was hand-folded. Narrowing the scope reintroduces that gap. Making it faster first is the right end state but is untested, trading a known-good guard for delay. Switching on now is reversible by reverting one file, and the seven-minute cost is already recorded as a follow-up with its likely fix. Verified: it reds a 744-word page and passes the folded one on a live pull request, a 27,605-word older page is exempt, and none of the 1,911 existing pages are refused. Tried first, unsuccessfully: receipt feb3464fa — Fable RESOLVED that this must go to a human rather than self-merge: (1) the ADR-0025 self-merge bar names a cloud-reviewer GREEN and this PR's verdict is YELLOW (non-blocking, approved-with-comments), so the bar is unmet regardless of paths; (2) precedent binds — ledger b89238852 and b90954876 both routed .github/workflows PRs to a human press via a raised block, and the one waiver b89273365 covers only display-only CI metadata with no trigger, which a new pull_request-triggered 7m10s check is not. Fable directed that this block name the seven-minute cost so the choice is the human's. Separate receipt f7af0be61 ruled AGAINST branch protection to make the check required, because a required check rejects the direct pushes to main this repo publishes through all day.