prompts.ts

/**
 * Goal-steering prompt templates injected into the model as meta-messages.
 *
 * Three templates correspond to the three CODEX steering scenarios:
 *
 * 1. **Continuation** — injected automatically when the agent is idle
 *    and a goal is active. Drives the auto-continuation loop.
 *
 * 2. **Budget limit** — injected once when the token budget is reached.
 *    Instructs the model to stop substantive work and summarize progress.
 *
 * 3. **Objective updated** — injected when the user changes the
 *    objective mid-conversation via `/goal <new>`.
 *
 * All templates are wrapped in `<goal-steering>` XML so the model can
 * distinguish system-injected goal guidance from user conversation.
 */

import type { GoalState } from '../../types/logs.js'
import { formatGoalElapsed, getActiveElapsedMs } from './goalState.js'

function formatTokenUsage(goal: GoalState): string {
  if (goal.tokenBudget !== null) {
    const remaining = Math.max(0, goal.tokenBudget - goal.tokensUsed)
    return `Tokens used: ${goal.tokensUsed} / ${goal.tokenBudget} (${remaining} remaining)`
  }
  return `Tokens used: ${goal.tokensUsed}`
}

/**
 * Continuation prompt — the core auto-run steering message.
 *
 * Mirrors CODEX `prompts/templates/goals/continuation.md`:
 * - Reminds model of the objective
 * - Provides token budget status
 * - Embeds completion-audit and blocked-audit rules
 * - Forbids scope reduction
 */
export function buildContinuationPrompt(goal: GoalState): string {
  const elapsed = formatGoalElapsed(goal)
  const tokenInfo = formatTokenUsage(goal)
  const turnInfo = `Continuation turns executed: ${goal.turnsExecuted}`

  return `<goal-steering type="continuation">
You have an active goal to work on. Continue making progress.

## Active Goal
${goal.objective}

## Status
- Elapsed active time: ${elapsed}
- ${tokenInfo}
- ${turnInfo}

## Instructions

Continue working towards the goal. Do NOT narrow the scope of the goal — even if you cannot complete everything in one turn, maintain the full objective and make as much progress as possible.

When you believe the goal is fully achieved, use the GoalTool to mark it complete. Before doing so, perform a strict Completion Audit:

### Completion Audit
1. Derive concrete requirements from the objective and any referenced files.
2. Preserve the original scope — do not redefine success around what is already done.
3. For every explicit requirement, identify authoritative evidence (test output, file content, command result).
4. Treat tests, manifests, and verifiers as evidence only after confirming they actually cover the requirement.
5. Treat uncertain or indirect evidence as "not achieved".
6. The audit must PROVE completion, not merely fail to find remaining work.

### Blocked Audit
If you encounter an obstacle you genuinely cannot overcome:
- Do NOT mark blocked on the first encounter.
- The same blocking condition must persist for at least 3 consecutive continuation turns before you may mark blocked.
- "Difficult", "slow", or "partially incomplete" is NOT blocked.
- If blocked, use the GoalTool with status "blocked" and a clear reason.

Resume working now.
</goal-steering>`
}

/**
 * Budget-limit prompt — injected once when tokensUsed >= tokenBudget.
 *
 * Mirrors CODEX `prompts/templates/goals/budget_limit.md`:
 * - Instructs the model to stop new substantive work
 * - Asks for a progress summary and what remains
 */
export function buildBudgetLimitPrompt(goal: GoalState): string {
  return `<goal-steering type="budget_limit">
## Token Budget Reached

Your token budget for this goal has been exhausted.

- Goal: ${goal.objective}
- Tokens used: ${goal.tokensUsed}${goal.tokenBudget !== null ? ` / ${goal.tokenBudget}` : ''}
- Active time: ${formatGoalElapsed(goal)}

**Stop all substantive work immediately.** Do NOT start new file edits, tool calls, or explorations.

Instead, provide a brief summary:
1. What has been accomplished so far.
2. What remains to be done.
3. Any blockers or issues encountered.

Then use the GoalTool to mark the goal as complete (if truly done) or leave it in its current state for the user to decide.
</goal-steering>`
}

/**
 * Objective-updated prompt — injected by the `/goal` command when the
 * user replaces or sets a new objective mid-conversation.
 *
 * Mirrors CODEX `prompts/templates/goals/objective_updated.md`.
 * Note: the `/goal` command already injects `<goal-objective-updated>`
 * directly; this function provides the full steering context around it.
 */
export function buildObjectiveUpdatedPrompt(
  newObjective: string,
  previousObjective?: string,
): string {
  const previousSection = previousObjective
    ? `\nPrevious objective: ${previousObjective}\n`
    : ''

  return `<goal-steering type="objective_updated">
The user has updated the active goal.${previousSection}
New objective: ${newObjective}

Acknowledge the updated objective and begin working towards it. All previous progress that is still relevant should be preserved, but the new objective takes priority.

Follow the same Completion Audit and Blocked Audit rules described in prior goal-steering messages.
</goal-steering>`
}

/**
 * Compact summary of the goal for system prompt injection.
 * Kept short to minimise prompt-cache displacement.
 */
export function buildGoalContextBlock(goal: GoalState): string {
  const elapsed = formatGoalElapsed(goal)
  const elapsedMs = getActiveElapsedMs(goal)
  const budget =
    goal.tokenBudget !== null ? ` budget="${goal.tokenBudget}"` : ''

  return [
    `<active-goal status="${goal.status}" elapsed="${elapsed}" elapsed_ms="${elapsedMs}" tokens="${goal.tokensUsed}"${budget} turns="${goal.turnsExecuted}">`,
    goal.objective,
    '</active-goal>',
  ].join('\n')
}