Home

boring / v2

publicBoring-Software-Inc/v2
Overview Code History Branches Pull requestsIssuesInsights Campfire Docs
main
HomeOverview Code PRsIssues

feat(core): keep rules a forge cannot run out of its gate

2 months ago

5360bf3
Authored
grim8/23/2026, 1:28:32 AM
An open-git repo could never pass. The derived default gate is built from the
baseline rules with no forge awareness, and every baseline rule except
english-only declares forges: ["github"]. So the gate carried four rules that
could only ever skip — and one skip trips the fail-closed floor, which sent
every pull request to review no matter what the rules found. english-only
passed underneath and it made no difference.

deriveDefaultWorkflow now takes the repo's forge and leaves those rules out.
Skipping is for a read that might come back; a rule the catalog declares
unusable on this forge is settled, and adding it only to skip it is a dead
gate. Omitting the argument filters nothing, so every other caller is unchanged.

Also: the e2e harness arms the repo for the run and restores the prior value.
Repos land armed: false and the worker logged 'repo not armed — event ingested,
run skipped', producing no verdict at all.

Verified live against open-git.com/boring/playground: a non-latin title blocks
(check failed), a latin title passes (check success).

Parentf12fe28

8 files changed
  • apps/worker/src/jobs/run-workflows.ts+1−0
  • bun.lock+1−8
  • package.json+2−1
  • packages/core/src/workflow/derive.test.ts+43−0
  • packages/core/src/workflow/derive.ts+25−2
  • scripts/e2e/lib/opengit.ts+151−21
  • scripts/e2e/lib/workflow-pin.ts+10−3
  • scripts/e2e/opengit.ts+225−14