rafcode 2.1.0 → 2.2.0

package/RAF/ahrtxf-session-sentinel/plans/01-capture-session-id.md

@@ -1,41 +0,0 @@
-# Task: Capture Session ID from Claude CLI Output
-
-## Objective
-Extract and store the Claude session ID from stream-json output in both verbose and non-interactive execution modes.
-
-## Context
-Claude CLI emits a `session_id` in its `system.init` NDJSON event when using `--output-format stream-json`. RAF currently discards this event entirely. We need to capture and surface this ID so it can be used for session resumption and debugging.
-
-## Requirements
-- Unify both `run()` (non-interactive) and `runVerbose()` methods to use `--output-format stream-json` so that the system init event is always available
-- In non-verbose mode, parse NDJSON events silently (extract textContent for output accumulation and detect completion markers) without rendering anything to stdout
-- In verbose mode, continue rendering stream events to stdout as before
-- Extract `session_id` from the `system.init` event (first event in the stream)
-- Add `sessionId?: string` field to the `RunResult` type returned by both `run()` and `runVerbose()`
-- Modify `renderStreamEvent()` in `stream-renderer.ts` to return the session_id when it encounters a system init event, rather than discarding it
-- When a session is interrupted (Ctrl+C, timeout, context overflow), print the session ID to terminal: `Session ID: <id>` so the user can copy it
-- Add tests for the session ID extraction from system init events
-- Add tests verifying session ID is included in RunResult
-
-## Implementation Steps
-1. Update the `RunResult` type to include an optional `sessionId` field
-2. Modify `renderStreamEvent()` to extract and return `session_id` from system init events (add a new field to the return type, e.g. `sessionId?: string`)
-3. Refactor `run()` to use `--output-format stream-json` internally, parsing NDJSON lines the same way `runVerbose()` does, but without writing display output to stdout
-4. In both `run()` and `runVerbose()`, capture the session_id from the first system init event and include it in the returned `RunResult`
-5. In the shutdown handler and timeout/overflow paths, print the captured session ID to the terminal before exiting
-6. Write unit tests for session ID extraction from stream events
-7. Write integration-style tests verifying RunResult includes sessionId
-
-## Acceptance Criteria
-- [ ] `run()` uses stream-json format internally and parses events silently
-- [ ] `runVerbose()` continues to display stream events as before
-- [ ] Both methods return `sessionId` in `RunResult` when available
-- [ ] On interruption (Ctrl+C, timeout, overflow), session ID is printed to terminal
-- [ ] Existing tests continue to pass
-- [ ] New tests cover session ID extraction
-
-## Notes
-- The system init event format is: `{ type: 'system', subtype: 'init', session_id: string, tools: string[], model: string }`
-- Currently `stream-renderer.ts` line 96 returns `{ display: '', textContent: '' }` for all system events — this is where extraction should happen
-- The `run()` method currently uses plain text output with `child_process.spawn` — it needs to switch to stream-json parsing similar to `runVerbose()`. Consider extracting shared NDJSON parsing logic to avoid duplication.
-- Be careful: `run()` has its own completion marker detection and timeout logic that must continue to work with the new stream-json parsing

package/RAF/ahrtxf-session-sentinel/plans/02-resume-flag.md

@@ -1,51 +0,0 @@
-# Task: Add --resume Flag to raf do Command
-
-## Objective
-Add a `--resume` option to `raf do` that resumes an interrupted Claude session for a specific task.
-
-## Context
-After task 01 captures the session ID and displays it on interruption, users need a way to actually resume the interrupted session. This task adds `raf do <project> --resume <session-id>` which passes Claude CLI's `--resume` flag to continue a session from where it left off.
-
-## Dependencies
-01
-
-## Requirements
-- Add `--resume <session-id>` option to the `raf do` command in Commander.js
-- When `--resume` is provided, RAF should:
-  1. Identify the task to resume — find the first task that is in-progress (has no outcome file, or has a partial/missing completion marker)
-  2. Skip the normal task execution flow and instead spawn Claude with `--resume <session-id>` flag
-  3. Do NOT pass `-p` (prompt), `--append-system-prompt`, or `--model` flags — rely on Claude's session state to restore these
-  4. DO pass `--dangerously-skip-permissions` as it's required for non-interactive operation
-  5. Still use `--output-format stream-json` so we can capture the new session's events and detect completion
-  6. Continue monitoring for completion markers and outcome file as usual
-- After the resumed session completes, normal post-task flow should apply (outcome validation, commit verification, next task, etc.)
-- If `--resume` is used with `--worktree`, ensure the CWD is set to the worktree path
-- Print a clear message indicating which task is being resumed: `Resuming task <id> with session <session-id>`
-- Add a new method to `ClaudeRunner` (e.g. `runResume(sessionId, options)`) that spawns Claude with the `--resume` flag
-- Cover the new flag and resume method with tests
-
-## Implementation Steps
-1. Add `--resume <session-id>` option to the `do` command definition in `src/commands/do.ts`
-2. Add a `runResume()` method to `ClaudeRunner` that spawns Claude with `--resume <session-id> --dangerously-skip-permissions --output-format stream-json` and the same completion monitoring as existing methods
-3. In the task execution loop, when `--resume` is provided:
-   - Determine the current task (first task without a valid outcome)
-   - Call `runResume()` instead of the normal `run()`/`runVerbose()` method
-   - After the resumed task completes, clear the `--resume` flag so subsequent tasks use normal execution
-4. Handle edge cases: invalid session ID format, all tasks already complete, resumed session fails
-5. Write tests for the new `runResume()` method
-6. Write tests for the `--resume` flag integration in the do command
-
-## Acceptance Criteria
-- [ ] `raf do <project> --resume <session-id>` resumes the interrupted session
-- [ ] Claude is spawned with `--resume` flag and without prompt/model/system-prompt flags
-- [ ] Completion monitoring works the same as normal execution
-- [ ] After resumed task completes, subsequent tasks run normally
-- [ ] Works with `--worktree` mode
-- [ ] Clear user-facing message on resume start
-- [ ] Tests cover resume path
-
-## Notes
-- Claude CLI's `--resume` flag restores the full session context including the system prompt, so we must NOT pass those flags again (they may conflict or be rejected)
-- The `--resume` flag only applies to a single task — after it completes (or fails), remaining tasks use normal execution
-- Consider what happens if the user provides a session ID for a task that already completed — should gracefully handle this
-- Check Claude CLI docs/help to verify exact `--resume` flag syntax: `claude --resume <session-id>`