3 Commits

Author	SHA1	Message	Date
YeonGyu-Kim	b16db15de1	fix(atlas): restrict boulder continuation to sessions in boulder session_ids ... Main session was unconditionally allowed through the boulder session guard, causing continuation injection into sessions not part of the active boulder. Now only sessions explicitly in boulder's session_ids (or background tasks) receive boulder continuation, matching todo-continuation-enforcer behavior.	2026-02-10 22:15:28 +09:00
YeonGyu-Kim	79d70c7edd	fix(atlas): allow boulder continuation for Sisyphus sessions ... When boulderState.agent is not explicitly set (defaults to 'atlas'), allow continuation for sessions where the last agent is 'sisyphus'. This fixes the issue where boulder continuation was skipped when Sisyphus took over the conversation after boulder creation.	2026-02-10 11:41:44 +09:00
YeonGyu-Kim	cea97f896b	refactor: wave 2 - split atlas, auto-update-checker, session-recovery, todo-enforcer, background-task hooks ... - Extract atlas/ into 15 focused modules (hook, event handler, tool policies, types, etc.) - Split auto-update-checker into checker/ and hook/ subdirectories with single-purpose files - Decompose session-recovery into separate recovery strategy files per error type - Extract todo-continuation-enforcer from monolith to directory with dedicated modules - Split background-task/tools.ts into individual tool creator files - Extract command-executor, tmux-utils into focused sub-modules - Split config/schema.ts into domain-specific schema files - Decompose cli/config-manager.ts into focused modules - Rollback skill-mcp-manager, model-availability, index.ts splits that broke tests - Fix all import path depths for moved files (../../ -> ../../../) - Add explicit type annotations to resolve TS7006 implicit any errors Typecheck: 0 errors Tests: 2359 pass, 5 fail (all pre-existing)	2026-02-08 15:01:42 +09:00