Scott Werner e9c35911bb Require finalization for every Fabro run ... FabroHooks always declares required run finalization instead of only when the run publishes or checkpoints. Every run takes one path, the best-effort diff branch in run_finished goes away, and a fork always declares what its worker's hooks will declare on resume, so the fork no longer carries its source's flag across. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-09 12:08:28 -04:00
..
assets/brand
demo
licenses
product
cargo-target-apfs-churn-plan.md
cli-workflow-coupling-audit.md
error-handling-strategy.md
event-schema-competitive-analysis.md
events-strategy.md	Commit publication failures through required run finalization	2026-10-08 12:45:24 -04:00
fabro-event-schema-v2-proposal.md
llm-client-resolution.md
logging-strategy.md	Move fabro-mcp's pebble mapping and test client into fabro-cli	2026-09-18 10:57:07 -04:00
mcp-server-qa-test-plan.md
migrations-strategy.md	Run the server's lifecycle over platform records instead of run_events	2026-09-18 12:32:06 -04:00
panic-policy.md
parallel-strategy.md
plan-events-as-source-of-truth-follow-ups.md
plan-events-as-source-of-truth.md
react-effects-policy.md
run-directory-keys.md	Restore configured artifact storage for workflow captures	2026-09-24 13:53:46 -04:00
run-finalization.md	Require finalization for every Fabro run	2026-10-09 12:08:28 -04:00
server-secrets-strategy.md
slow-test-opportunities-2026-04-07.md
testing-strategy.md	Describe the run stream where the docs described the legacy event log	2026-09-18 14:45:13 -04:00
updating-web-screenshots.md