test: document and triage existing main baseline failures

[pinion05]

Summary

main is not currently green in a fresh worktree. Before treating future feature branches as fully verified, we need to catalog and triage the existing baseline test failures.

Fresh Baseline Evidence

• environment: fresh worktree at /Users/pinion/.config/superpowers/worktrees/codex-claw/feature-telegram-command-sync-always-on
• command: bun test
• result: 137 pass, 15 fail, 1 error

Failures Seen

Config

• tests/unit/config.test.ts
• expected config values do not match runtime output
• TELEGRAM_SYNC_COMMANDS boolean parsing assertions currently fail

Local config store

• tests/unit/local-config.test.ts
• createLocalConfigStore() appears to return an object without read() / write() in current test expectations

Runtime workspace

• tests/unit/runtime-workspace.test.ts
• packaged skill installation and workspace directory assertions fail
• warning-path assertion does not observe the expected warning

Integration wiring

• tests/integration/create-bot.test.ts
• import error for missing createBotHandlers export
• tests/integration/cron-loader.test.ts
• createRuntimeDeps() no longer matches test expectations for startCronRuntime / runTurn

Proposal

• reproduce each failure independently with focused test commands
• determine which failures are stale tests vs actual regressions
• split fixes into small follow-up issues or one repair PR, depending on root cause overlap
• restore a green baseline on main

Acceptance Criteria

• each current failure is categorized as stale test, product regression, or test fixture drift
• repair scope is explicitly tracked
• bun test returns green on main or follow-up issues exist for any intentionally deferred failures