processor

type Config ¶

type Config struct {
	PlanFile         string         // path to plan file (required for full mode)
	PlanDescription  string         // plan description for interactive plan creation mode
	ProgressPath     string         // path to progress file
	Mode             Mode           // execution mode
	MaxIterations    int            // maximum iterations for task phase
	Debug            bool           // enable debug output
	NoColor          bool           // disable color output
	IterationDelayMs int            // delay between iterations in milliseconds
	TaskRetryCount   int            // number of times to retry failed tasks
	CodexEnabled     bool           // whether codex review is enabled
	AppConfig        *config.Config // full application config (for executors and prompts)
}

Config holds runner configuration.

type Executor ¶

type Executor interface {
	Run(ctx context.Context, prompt string) executor.Result
}

Executor runs CLI commands and returns results.

type InputCollector ¶ added in v0.4.0

type InputCollector interface {
	AskQuestion(ctx context.Context, question string, options []string) (string, error)
}

InputCollector provides interactive input collection for plan creation.

type Logger ¶

type Logger interface {
	SetPhase(phase Phase)
	Print(format string, args ...any)
	PrintRaw(format string, args ...any)
	PrintSection(section Section)
	PrintAligned(text string)
	LogQuestion(question string, options []string)
	LogAnswer(answer string)
	Path() string
}

Logger provides logging functionality.

type Mode ¶

type Mode string

Mode represents the execution mode.

const (
	ModeFull      Mode = "full"       // full execution: tasks + reviews + codex
	ModeReview    Mode = "review"     // skip tasks, run full review pipeline
	ModeCodexOnly Mode = "codex-only" // skip tasks and first review, run only codex loop
	ModePlan      Mode = "plan"       // interactive plan creation mode
)

type Phase ¶ added in v0.4.0

type Phase string

Phase represents execution phase for color coding.

const (
	PhaseTask       Phase = "task"        // execution phase (green)
	PhaseReview     Phase = "review"      // code review phase (cyan)
	PhaseCodex      Phase = "codex"       // codex analysis phase (magenta)
	PhaseClaudeEval Phase = "claude-eval" // claude evaluating codex (bright cyan)
	PhasePlan       Phase = "plan"        // plan creation phase (info color)
)

type QuestionPayload ¶ added in v0.4.0

type QuestionPayload struct {
	Question string   `json:"question"`
	Options  []string `json:"options"`
	Context  string   `json:"context,omitempty"`
}

QuestionPayload represents a question signal from Claude during plan creation

func ParseQuestionPayload(output string) (*QuestionPayload, error)

type Runner ¶

type Runner struct {
	// contains filtered or unexported fields
}

Runner orchestrates the execution loop.

func New(cfg Config, log Logger) *Runner

func NewWithExecutors(cfg Config, log Logger, claude, codex Executor) *Runner

func (r *Runner) Run(ctx context.Context) error

func (r *Runner) SetInputCollector(c InputCollector)

type Section ¶ added in v0.4.0

type Section struct {
	Type      SectionType
	Iteration int    // 0 for non-iterated sections
	Label     string // human-readable display text
}

Section carries structured information about a section header. instead of parsing section names with regex, consumers can access the Type and Iteration fields directly.

use the provided constructors (NewTaskIterationSection, etc.) to create sections with proper Type/Iteration/Label consistency.

func NewClaudeEvalSection() Section

func NewClaudeReviewSection(iteration int, suffix string) Section

func NewCodexIterationSection(iteration int) Section

func NewGenericSection(label string) Section

func NewPlanIterationSection(iteration int) Section

func NewTaskIterationSection(iteration int) Section

type SectionType ¶ added in v0.4.0

type SectionType int

SectionType represents the semantic type of a section header. the web layer uses these types to emit appropriate boundary events:

• SectionTaskIteration: emits task_start/task_end events
• SectionClaudeReview, SectionCodexIteration: emits iteration_start events
• SectionGeneric, SectionClaudeEval: no boundary events, just section headers

invariants:

• Iteration > 0 for SectionTaskIteration, SectionClaudeReview, SectionCodexIteration
• Iteration == 0 for SectionGeneric, SectionClaudeEval

prefer using the constructor functions (NewTaskIterationSection, etc.) to ensure these invariants are maintained.

const (
	// SectionGeneric is a static section header with no iteration.
	SectionGeneric SectionType = iota
	// SectionTaskIteration represents a task execution iteration.
	SectionTaskIteration
	// SectionClaudeReview represents a Claude review iteration.
	SectionClaudeReview
	// SectionCodexIteration represents a Codex review iteration.
	SectionCodexIteration
	// SectionClaudeEval represents Claude evaluating codex findings.
	SectionClaudeEval
	// SectionPlanIteration represents a plan creation iteration.
	SectionPlanIteration
)