Home

boring / v2

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

test(e2e): workflow axis — saved graphs through the real PR pipeline

3 months ago

233cf28
Authored
grim7/16/2026, 6:51:48 PM
New harness axis 'workflow' with a workflow_definitions pin/restore sibling
of the rule-configs pin (runner-managed, restores the maintainer's real
rows on exit). Four scenarios: workflow-block (a saved enabled graph's
fail→block edge blocks a clean PR — proves the editor's emission, not the
derived default, drives the verdict), workflow-pass (satisfiable threshold
→ success), workflow-disabled-inert (a DISABLED blocking graph stays inert
— §4 enable-is-explicit, live), and workflow-existing (no pinning: reads
YOUR currently-enabled workflows, asserts each passes enable-time
validation, opens a clean PR and asserts a verdict lands). rule_configs
pin note: the /rules toggle is a kill switch over saved workflows, so
scenarios pin their rule ON. bun run test:workflows runs the axis
headless. Root devDeps gain @tripwire/contracts + @tripwire/utils
(scripts import them now).

Parentc5f5992

6 files changed
  • bun.lock+2−0
  • package.json+3−0
  • scripts/e2e/lib/runner.ts+16−0
  • scripts/e2e/lib/types.ts+12−1
  • scripts/e2e/lib/workflow-pin.ts+91−0
  • scripts/e2e/scenarios.ts+184−0