Bryan Helmkamp 1c30332636 Key the fold's stages by a typed FiringKey instead of a formatted string ... stage_key formatted "<execution>:<firing>" and five places re-derived or re-parsed that string: the engine, progress and platform folds, the projector's ordering rule, and fork.rs's stage_labels, which split it back apart. FiringKey is the fact itself, with of_event for the event side and From<StagePosition> for the platform-record side. It still serializes as "<execution>:<firing>", so the fold_json a stored view holds keeps its shape and needs no migration; a unit test pins that. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-09-20 15:05:32 -04:00
..
apps	Share one poison-tolerant lock helper from fabro-util	2026-09-20 14:47:46 -04:00
components	Key the fold's stages by a typed FiringKey instead of a formatted string	2026-09-20 15:05:32 -04:00
foundation	Name the fold's repeated shapes once: completion, model usage, pause, conclusion	2026-09-20 15:01:14 -04:00
packages/fabro-api-client	Forward every configured sandbox plugin to the Petri worker	2026-09-19 14:45:42 -04:00