feat: add boulder-loop time-based autonomous work loop

[Stranmor]

Summary

Boulder Loop is a time-based autonomous work loop that continues until a deadline, unlike Ralph Loop which stops when the agent decides it's complete.

Features

• Time-based execution: Work until a specific time (--until=HH:MM) or for N hours (--hours=N)
• Persistent state: Survives session crashes/restarts
• Deadline enforcement: Automatic continuation prompts until deadline reached
• Commands: /boulder, /cancel-boulder

Usage

/boulder "Refactor and add tests" --until=23:00
/boulder "Work on improvements" --hours=4
/cancel-boulder

Implementation

• src/hooks/boulder-loop/ - Core hook implementation
• src/features/builtin-commands/templates/boulder-loop.ts - Command templates
• Integrated into src/index.ts with chat.message, event, and tool.execute.before handlers
• Persistent storage in .sisyphus/boulder-loop.local.md

Use Case

When you want the agent to work autonomously until a specific time (e.g., "work until I wake up", "work for 4 hours while I'm away") rather than stopping when it thinks it's done.

---

Summary by cubic

Add Boulder Loop, a time-based autonomous work loop that keeps working until a deadline. This enables “work until HH:MM or for N hours,” with persistent state and automatic continuation.

• New Features
  • Slash commands: /boulder "task" --until=HH:MM or --hours=N; /cancel-boulder
  • Persistent state in .sisyphus/boulder-loop.local.md (survives crashes/restarts)
  • Deadline enforcement with idle-event prompts; auto stop with final toast and message
  • Config: boulder_loop { enabled, default_hours, state_dir }
  • Skip questions during Boulder Loop to avoid blocking
  • Wait for background tasks to finish before injecting the next continuation
  • CI: daily upstream sync workflow with build and release

^{Written for commit a9ef5c5. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA. Thank you! ✅
_{Posted by the CLA Assistant Lite bot.}

[Stranmor]

I have read the CLA Document and I hereby sign the CLA

[cubic-dev-ai]

1 issue found across 13 files

Confidence score: 5/5

• Low-severity maintainability note: deadline parsing/calculation is duplicated between chat.message and slashcommand handlers in src/index.ts, which could require synchronized edits later
• This PR appears safe to merge since the issue is about refactoring potential rather than user-facing behavior
• Pay close attention to src/index.ts - duplicated deadline parsing logic across handlers.

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="src/index.ts">

<violation number="1" location="src/index.ts:639">
P3: Deadline parsing and calculation logic is duplicated between chat.message and slashcommand handlers; changes would need to be synchronized in two places. Consider extracting a shared helper for parsing deadline options.</violation>
</file>

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

2 issues found across 1 file (changes from recent commits).

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name=".github/workflows/sync-upstream.yml">

<violation number="1" location=".github/workflows/sync-upstream.yml:76">
P2: Release tags are date-only, so multiple runs in the same day reuse the same tag and action-gh-release will fail with an `already_exists` error. This can break manual re-runs or multiple upstream updates in one day.</violation>

<violation number="2" location=".github/workflows/sync-upstream.yml:89">
P2: Release instructions reference `oh-my-opencode-boulder.js`, but the only uploaded asset is `dist/index.js`, so users won’t find the documented filename in the release assets.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}