Problem
workspace worktree add successfully created and bootstrapped a worktree, then emitted an uncaught RedisException while WorktreeDemandCalibration::record_bootstrap() called update_option().
The command continued and printed Success, producing a mixed error/success result even though the authoritative worktree was created.
Observed command
wp datamachine-code workspace worktree add extrachill-events fix-758-promoter-navigation --from=origin/main
Trace boundary
WorktreeDemandCalibration.php:78 -> update_option()
WorktreeDemandCalibration::record_bootstrap()
WorkspaceWorktreeLifecycle::worktree_add_with_capacity_lock()
- Redis read error from
object-cache.php
Expected
- Successful worktree creation remains successful when non-authoritative calibration persistence fails.
- Calibration failure is caught and reported as bounded warning/evidence, not an uncaught exception stack.
- The command emits one unambiguous terminal result.
- Authoritative worktree state and bootstrap evidence remain inspectable after the warning.
- Tests cover object-cache/option persistence failure after successful filesystem and Git bootstrap.
No production data was affected. The worktree was registered successfully at extrachill-events@fix-758-promoter-navigation.
Problem
workspace worktree addsuccessfully created and bootstrapped a worktree, then emitted an uncaughtRedisExceptionwhileWorktreeDemandCalibration::record_bootstrap()calledupdate_option().The command continued and printed
Success, producing a mixed error/success result even though the authoritative worktree was created.Observed command
wp datamachine-code workspace worktree add extrachill-events fix-758-promoter-navigation --from=origin/mainTrace boundary
WorktreeDemandCalibration.php:78->update_option()WorktreeDemandCalibration::record_bootstrap()WorkspaceWorktreeLifecycle::worktree_add_with_capacity_lock()object-cache.phpExpected
No production data was affected. The worktree was registered successfully at
extrachill-events@fix-758-promoter-navigation.