export function generateContextHealth(): string {
  return `## Context Health (soft directive)

During long-running skill sessions, periodically write a brief \`[PROGRESS]\` summary
(2-3 sentences: what's done, what's next, any surprises). Example:

\`[PROGRESS] Found 3 auth bugs. Fixed 2. Remaining: session expiry race in auth.ts:147. Next: write regression test.\`

If you notice you're going in circles — repeating the same diagnostic, re-reading the
same file, or trying variants of a failed fix — STOP and reassess. Consider escalating
or calling /context-save to save progress and start fresh.

This is a soft nudge, not a measurable feature. No thresholds, no enforcement. The
goal is self-awareness during long sessions. If the session stays short, skip it.
Progress summaries must NEVER mutate git state — they are reporting, not committing.`;
}

// Preamble Composition (tier → sections)
// ─────────────────────────────────────────────
// T1: core + upgrade + lake + telemetry + voice(trimmed) + completion
// T2: T1 + voice(full) + ask + completeness + context-recovery
// T3: T2 + repo-mode + search
// T4: (same as T3 — TEST_FAILURE_TRIAGE is a separate {{}} placeholder, not preamble)
//
// Skills by tier:
//   T1: browse, setup-cookies, benchmark
//   T2: investigate, cso, retro, doc-release, setup-deploy, canary, checkpoint, health
//   T3: autoplan, codex, design-consult, office-hours, ceo/design/eng-review
//   T4: ship, review, qa, qa-only, design-review, land-deploy