4 months ago
c485503live-test surprise #1: the worker never read rule_configs (only the web UI did), so /rules toggles were cosmetic — a disabled rule evaluated anyway. execution ran the hardcoded DEFAULT_WORKFLOW; derive.ts didn't exist. - core/workflow/derive.ts: repos with no saved workflow get a workflow DERIVED from enabled rules (baseline = contracts DEFAULT_WORKFLOW, retired as an executed constant). baseline rule runs unless a toggle disables it; toggle config overrides; enabled non-baseline rule opts in - executor: injected isRuleDisabled(ref) — a disabled rule in a saved workflow records `disabled`, conducts as pass, and is excluded from the degradation floor - worker run-workflows: reads rule_configs, derives or runs saved, passes disabledRefs; DEFAULT_WORKFLOW no longer executed (worker/default-workflow.ts deleted) - web: hasEnabledWorkflow → "managed by your workflow" tag on rule cards - tests: derive unit tests + executor disabled test + toggles integration (off⇒absent, config edit⇒reflected, saved+disabled⇒skipped:disabled) - DECISIONS: derived-default model, fresh-repo overlay decision, display residual checks: biome clean · 12/12 typecheck · boundaries ok · 138 tests, 0 fail
Parentb221093