YeonGyu-Kim 73453a7191 docs(agents): update hook counts 44→46, add hashline-edit documentation

- Update root AGENTS.md: hook count 44→46, commit fcb90d92, generated 2026-02-24
- Update src/AGENTS.md: core hooks 35→37, session hooks 21→23
- Update src/hooks/AGENTS.md: 46 hooks total, add modelFallback/noSisyphusGpt/noHephaestusNonGpt/runtimeFallback, jsonErrorRecovery moved to tool-guard (tier 2)
- Create src/tools/hashline-edit/AGENTS.md (93 lines): documents three-op model, LINE#ID format, execution pipeline
- Refresh timestamps: 2026-02-21→2026-02-24 on 28 files
- Update plugin/AGENTS.md hook composition counts

🤖 Generated with assistance of [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)

2026-02-25 00:02:05 +09:00

2.8 KiB

Raw Blame History

src/hooks/atlas/ — Master Boulder Orchestrator

Generated: 2026-02-24

OVERVIEW

17 files (~1976 LOC). The atlasHook — Continuation Tier hook that monitors session.idle events and forces continuation when boulder sessions (ralph-loop, task-spawned agents) have incomplete work. Also enforces write/edit policies for subagent sessions.

WHAT ATLAS DOES

Atlas is the "keeper of sessions" — it tracks every session and decides:

Should this session be forced to continue? (if boulder session with incomplete todos)
Should write/edit be blocked? (policy enforcement for certain session types)
Should a verification reminder be injected? (after tool execution)

DECISION GATE (session.idle)

session.idle event
  → Is this a boulder/ralph/atlas session? (session-last-agent.ts)
  → Is there an abort signal? (is-abort-error.ts)
  → Failure count < max? (state.promptFailureCount)
  → No running background tasks?
  → Agent matches expected? (recent-model-resolver.ts)
  → Plan complete? (todo status)
  → Cooldown passed? (5s between injections)
  → Inject continuation prompt (boulder-continuation-injector.ts)

KEY FILES

File	Purpose
`atlas-hook.ts`	`createAtlasHook()` — composes event + tool handlers, maintains session state
`event-handler.ts`	`createAtlasEventHandler()` — decision gate for session.idle events
`boulder-continuation-injector.ts`	Build + inject continuation prompt into session
`system-reminder-templates.ts`	Templates for continuation reminder messages
`tool-execute-before.ts`	Block write/edit based on session policy
`tool-execute-after.ts`	Inject verification reminders post-tool
`write-edit-tool-policy.ts`	Policy: which sessions can write/edit?
`verification-reminders.ts`	Reminder content for verifying work
`session-last-agent.ts`	Determine which agent owns the session
`recent-model-resolver.ts`	Resolve model used in recent messages
`subagent-session-id.ts`	Detect if session is a subagent session
`sisyphus-path.ts`	Resolve `.sisyphus/` directory path
`is-abort-error.ts`	Detect abort signals in session output
`types.ts`	`SessionState`, `AtlasHookOptions`, `AtlasContext`

STATE PER SESSION

interface SessionState {
  promptFailureCount: number  // Increments on failed continuations
  // Resets on successful continuation
}

Max consecutive failures before 5min pause: 5 (exponential backoff in todo-continuation-enforcer).

RELATIONSHIP TO OTHER HOOKS

atlasHook (Continuation Tier): Master orchestrator, handles boulder sessions
todoContinuationEnforcer (Continuation Tier): "Boulder" mechanism for main Sisyphus sessions
Both inject into session.idle but serve different session types

2.8 KiB Raw Blame History