ccgx-workflow 2.4.1 → 2.5.0

package/dist/index.d.ts

@@ -203,6 +203,12 @@ interface SkillMeta {
      * Empty array = always active.
      */
     paths: string[];
+    /**
+     * P0-2: Gates Taxonomy classification from frontmatter `gate-type`.
+     * Only the 4 legal values are accepted; anything else → undefined.
+     * SSoT: src/utils/verify-orchestrator.ts GATE_REGISTRY.
+     */
+    gateType?: 'pre-flight' | 'revision-loop' | 'escalation' | 'abort';
 }
 /**
  * Parse YAML frontmatter from a markdown file.
@@ -327,6 +333,11 @@ declare function checkForUpdates(): Promise<{
     latestVersion: string | null;
 }>;
 
+/**
+ * `--fix --auto` 多轮收敛上限（CCG 全体系硬规约，与 plan-checker / verify-work
+ * 一致）。3 轮后未收敛 → 停止 + 升级人工介入。
+ */
+declare const AUTO_CONVERGE_CAP = 3;
 /**
  * 单轮收敛状态。
  */
@@ -340,6 +351,31 @@ interface ConvergeRound {
         info: number;
     };
 }
+/**
+ * 多轮收敛判定：是否继续 / 收敛 / 升级。
+ *
+ *   - `continue`：上一轮 finding 数下降，仍 < cap → 继续 fix + re-review
+ *   - `converged`：finding 数为 0（critical+warning），或 stable 多轮 → 完成
+ *   - `escalate`：达到 cap（默认 3 轮）或 stall（连续 2 轮 finding 数没下降） → 升级
+ */
+type ConvergeDecision = 'continue' | 'converged' | 'escalate';
+/**
+ * Blocking 模式——哪些 severity 计入"未收敛"：
+ *
+ *   - `'critical_warning'`（默认，现行为不变）：critical+warning 全清才 converged
+ *     —— `--fix --auto` 严格收敛
+ *   - `'critical'`：只看 critical —— 普通 `--fix` 的 Ralph auto-retry
+ *     （无 Critical 即 pass through，Warning 留报告不阻塞）
+ */
+type ConvergeBlocking = 'critical' | 'critical_warning';
+/**
+ * 判定下一步动作。
+ *
+ * @param history  已完成轮次的 finding 历史（轮 1, 轮 2, ...）
+ * @param cap      上限（默认 AUTO_CONVERGE_CAP=3）
+ * @param blocking 收敛口径（默认 'critical_warning'，与历史行为一致）
+ */
+declare function decideConverge(history: readonly ConvergeRound[], cap?: number, blocking?: ConvergeBlocking): ConvergeDecision;
 
 /**
  * Ralph Loop fix-log persistence (RFC-8 follow-up to fork v2.3.1).
@@ -551,6 +587,74 @@ declare function formatAsMarkdown(approved: readonly SpecCandidate[], meta: {
     isoDate: string;
 }): string;
 
+/**
+ * Generic O_EXCL file-lock primitive (P1-6).
+ *
+ * Protects multi-writer read-modify-write cycles on shared state files
+ * (`.context/<phase>/SUMMARY.md` merged by parallel team-exec Builders,
+ * `.ccg/state.md` written by the Lead each wave, P1-4 `.context/tasks/`).
+ *
+ * Mechanism (aligned with GSD bin/lib/state.cjs acquireStateLock):
+ *   - `openSync(lockPath, O_CREAT | O_EXCL | O_WRONLY)` + write pid — atomic
+ *     create-or-fail on every mainstream filesystem.
+ *   - EEXIST → only steal when the lock file's mtime is older than
+ *     `staleThresholdMs` (crashed holder). The steal itself is an atomic
+ *     renameSync to a `.steal-*` tombstone — two waiters can both observe
+ *     staleness, but exactly one rename succeeds; the loser must never
+ *     unlink (it would nuke the winner's freshly created lock → double
+ *     hold). Nuking a fresh lock held by a slow-but-live writer causes
+ *     lost updates.
+ *   - Transient errno whitelist (Windows AV, Docker overlay-fs, NFS) retries
+ *     instead of propagating; truly fatal codes (ENOSPC / EROFS / EACCES)
+ *     throw immediately.
+ *   - Synchronous sleep between retries via Atomics.wait (short-lived CLI /
+ *     test processes only — this module must NEVER be imported from hooks,
+ *     which have a <100ms budget).
+ *   - Module-level held-locks set + process 'exit' hook prevents a crashed
+ *     locked region from leaving a stale file behind.
+ *
+ * Contract: locks are held for milliseconds inside a single process
+ * (`withLock(target, fn)` wraps the whole read→transform→write cycle). The
+ * 10s staleness threshold is only valid under that contract — an LLM holding
+ * a lock across tool calls would be mis-detected as crashed. Templates must
+ * route all RMW through single-process CLI subcommands
+ * (templates/scripts/ccg-state-lock.cjs), never split acquire/release.
+ */
+interface LockOptions {
+    /** Delay between acquisition retries (default 200ms; 0-50ms jitter added). */
+    retryDelayMs?: number;
+    /** Lock files older than this are considered crashed and stolen (default 10s). */
+    staleThresholdMs?: number;
+    /** Give up and throw after waiting this long in total (default 30s). */
+    maxWaitMs?: number;
+}
+declare const RETRY_DELAY_MS = 200;
+declare const STALE_THRESHOLD_MS = 10000;
+declare const MAX_WAIT_MS = 30000;
+/**
+ * Transient errno codes that indicate a temporary filesystem condition under
+ * concurrent O_EXCL races. Recoverable — acquireLock retries instead of
+ * propagating. Fatal codes (ENOSPC, EROFS, EACCES, EMFILE) are NOT listed and
+ * throw immediately.
+ */
+declare const LOCK_RETRY_ERRNOS: ReadonlySet<string>;
+/** Lock file path convention: `<target>.lock` (sibling of the protected file). */
+declare function lockPathFor(target: string): string;
+/**
+ * Acquire the lock guarding `target`. Returns the lock path for releaseLock.
+ * Throws after `maxWaitMs` of total waiting (message includes waited ms), or
+ * immediately on a fatal (non-whitelisted) errno.
+ */
+declare function acquireLock(target: string, opts?: LockOptions): string;
+/** Release a lock previously returned by acquireLock. Idempotent. */
+declare function releaseLock(lockPath: string): void;
+/**
+ * Run `fn` while holding the lock for `target`. The lock covers the entire
+ * read→transform→write cycle (lost-update protection); released in `finally`
+ * even when `fn` throws.
+ */
+declare function withLock<T>(target: string, fn: () => T, opts?: LockOptions): T;
+
 /**
  * Phase-scoped context state machine (v4.0 Phase 2).
  *
@@ -569,6 +673,7 @@ declare function formatAsMarkdown(approved: readonly SpecCandidate[], meta: {
  * tokens of orchestrator context (the `summaryTokenEstimate` helper makes this
  * empirically verifiable in unit tests).
  */
+
 interface PhaseContext {
     phase: string;
     plan: string;
@@ -584,6 +689,11 @@ interface PhaseSummary {
     provides: string[];
     affects: string[];
     keyFiles: string[];
+    /**
+     * P1-6: 本 phase 创建/修改的测试文件清单（每波 cross-phase 回归门的清单来
+     * 源）。可选字段：旧 SUMMARY.md 无该行时 readSummary 返回 []（向后兼容）。
+     */
+    tests?: string[];
     completed: boolean;
     completedAt?: string;
     notes?: string;
@@ -650,11 +760,57 @@ declare function readSummaryFrontmatter(workdir: string, phase: string): string
  * tight enough that test assertions stay valid against real tokenizers.
  */
 declare function summaryTokenEstimate(frontmatter: string): number;
+/** Per-task patch a Builder contributes to the shared phase SUMMARY.md. */
+interface SummaryTaskPatch {
+    taskId: string;
+    provides?: string[];
+    affects?: string[];
+    keyFiles?: string[];
+    tests?: string[];
+    completed?: boolean;
+    notes?: string;
+}
+/** Token budget per SUMMARY frontmatter (Step 5.5 contract: < 200 tokens). */
+declare const SUMMARY_TOKEN_BUDGET = 200;
+/**
+ * Pure merge core: fold one task patch into an existing summary (or a fresh
+ * skeleton when `existing` is null). List fields union-dedup preserving
+ * order; notes append as a `[<taskId>] <notes>` segment (newlines collapsed —
+ * frontmatter scalars are single-line); `completed` keeps the existing value
+ * unless the patch sets it, and a true result refreshes `completedAt`.
+ */
+declare function mergeSummaryFields(existing: PhaseSummary | null, phase: string, plan: string, patch: SummaryTaskPatch, nowIso?: string): PhaseSummary;
+/**
+ * Locked read-modify-write of `.context/<phase>/SUMMARY.md`:
+ * lock (O_EXCL) → read existing → mergeSummaryFields → budget-truncate notes
+ * → atomic write (tmp+rename) → release. Returns the merged summary.
+ */
+declare function mergeSummary(workdir: string, phase: string, plan: string, patch: SummaryTaskPatch, opts?: LockOptions): PhaseSummary;
+/**
+ * Heuristic test-file detector for the regression gate's key_files fallback.
+ * Matches: `*.test.*` / `*.spec.*`, `*_test.go|py`, `test_*.py`,
+ * `__tests__/` members, and files under a `test/` or `tests/` directory.
+ */
+declare function isTestFilePath(p: string): boolean;
+/**
+ * Collect the regression test inventory from prior completed phases:
+ * scan `<workdir>/.context/<phase>/SUMMARY.md` (frontmatter only via
+ * readSummary), skip reserved dirs and `excludePhases` (typically the phase
+ * currently executing), keep phases with `completed: true`, and resolve each
+ * phase's test list as: frontmatter `tests` when non-empty, else `keyFiles`
+ * filtered through isTestFilePath. Phases resolving to an empty list are
+ * omitted. Deterministic: phases sorted by directory name.
+ */
+declare function collectRegressionTests(workdir: string, excludePhases?: string[]): {
+    phase: string;
+    tests: string[];
+}[];
 
 /**
  * Wave Scheduler (CCG v4.1 Phase 14).
  *
- * `/ccg:autonomous --parallel` 的依赖图调度核心。把扁平的 phase 序列按
+ * `/ccg:autonomous` 的依赖图调度核心（workflow 默认路径经 flattenWaves 展平
+ * 串行；附录 A `--legacy` 按 wave 并行）。把扁平的 phase 序列按
  * `Depends on` 字段拓扑排序成 wave（无依赖 → wave 1，依赖 wave 1 → wave 2，
  * ...），波内 phase 没有依赖关系可主线一次性并行 spawn `Agent(phase-runner)`。
  *
@@ -665,8 +821,8 @@ declare function summaryTokenEstimate(frontmatter: string): number;
  *   - 失败用 throw + 明确错误信息（依赖循环 / 引用未知 phase）
  *
  * 调用方：
- *   - `templates/commands/autonomous.md` Step 4.0（解析 roadmap）
- *   - `templates/commands/autonomous.md` Step 4.2（按 wave 并行 spawn）
+ *   - `templates/commands/autonomous.md` 附录 A Step 4.0（解析 roadmap）
+ *   - `templates/commands/autonomous.md` 附录 A Step 4.2（按 wave 并行 spawn）
  *
  * 不做：
  *   - 不实际 spawn Agent（那是主线 LLM 的职责，本 helper 只决定 wave 划分）
@@ -689,6 +845,12 @@ interface RoadmapPhase {
     status: PhaseStatus;
     /** 依赖的 phase id 列表。`(none)` 表示空 */
     dependsOn: string[];
+    /**
+     * P0-2: phase 分配的需求 ID 列表（来自 `- **Requirements**: REQ-01, REQ-02` 行）。
+     * 可选字段：roadmap 无该行时保持 undefined（向后兼容老格式与既有调用方）。
+     * `(none)` 显式表示空列表 []。
+     */
+    requirements?: string[];
 }
 /**
  * Wave 调度结果。`waves[i]` 是第 i+1 wave 内的 phase id 列表（顺序无意义，波内
@@ -766,12 +928,59 @@ interface ScheduleOptions {
 /**
  * 一站式调度：解析 → cascade skip → 拓扑分波 → 可选批分组。
  *
- * 完整 schedule 流程，autonomous Step 4.0 直接调用即可。
+ * 完整 schedule 流程，autonomous 附录 A Step 4.0 直接调用即可。
  *
  * @param phases 已解析的 phase 列表（来自 parseRoadmap）
  * @param options 调度参数
  */
 declare function schedule(phases: RoadmapPhase[], options?: ScheduleOptions): WaveSchedule;
+/** plan `tasks:` yaml 块中单个任务的结构化记录（camelCase 内部形态）。 */
+interface PlanTask {
+    /** 任务标识，例如 "T1" */
+    id: string;
+    /** 该任务允许创建/修改的文件列表（文件范围隔离约束） */
+    files: string[];
+    /** 依赖的任务 id 列表 */
+    dependsOn: string[];
+    /** plan 作者（LLM）手工声明的 wave；仅作交叉核对，导出结果为权威 */
+    declaredWave?: number;
+    /** 断点续跑状态；缺省 'pending' */
+    status?: PhaseStatus;
+}
+/** 任务级 wave 调度结果。 */
+interface TaskWaveSchedule {
+    /** waves[0] = wave 1（最先跑），波内任务文件零交叉、可并行 */
+    waves: string[][];
+    /** 因上游 failed/skipped 而 cascade 标 skipped 的任务 id */
+    skipped: string[];
+    /** declared/derived 不一致、文件交叉拆分等非致命提示 */
+    warnings: string[];
+}
+/**
+ * 校验任务图的结构合法性。返回错误列表（空数组 = 合法）：
+ *   - 重复 id
+ *   - depends_on 引用未知 id
+ *   - 自依赖
+ *
+ * 依赖循环不在此检查（buildWaves 的 Kahn 算法检测并 throw）。
+ */
+declare function validateTaskGraph(tasks: PlanTask[]): string[];
+/**
+ * 同 wave 文件交叉的安全网：贪心 first-fit 把任务装入首个与其 files 零交叉的
+ * 子波，装不进则开新子波。子波按序串行执行，波内仍并行。
+ *
+ * 纯函数、确定性：按 waveTaskIds 输入顺序处理。
+ */
+declare function splitWaveByFileOverlap(waveTaskIds: string[], filesById: Map<string, string[]>): string[][];
+/**
+ * 任务级拓扑分波（team-exec Step 2 的权威实现）：
+ *   1. validateTaskGraph 非空 → throw（消息逐条列出）
+ *   2. PlanTask → RoadmapPhase 复用 schedule()（自动获得 cascadeSkip +
+ *      completed 过滤 + Kahn 拓扑分波；依赖循环由 buildWaves throw 透传）
+ *   3. 每个 wave 过 splitWaveByFileOverlap，拆出的子波按序展平为连续 wave
+ *   4. declaredWave 与导出 wave 不一致 / 文件交叉拆分 → warnings（非致命）
+ */
+declare function buildTaskWaves(tasks: PlanTask[]): TaskWaveSchedule;
 
 /**
  * Multi-Model Routing — Single Source of Truth (CCG v4.2 Phase 21).
@@ -1005,7 +1214,7 @@ declare function renderAuditMarkdown(report: AuditReport): string;
  *   - 失败用 throw + 明确错误信息（输入非法 / 类型未知）
  *
  * 调用方（概念上）：
- *   - `templates/commands/autonomous.md` Step 4.4 challenger 分支
+ *   - `templates/commands/autonomous.md` 附录 A Step 4.4 challenger 分支
  *
  * 不做：
  *   - 不实际 spawn Agent（主线 LLM 的职责，本 helper 只产出 spawn 计划）
@@ -1248,7 +1457,7 @@ declare function bothPluginsInstalled(homeDir?: string): boolean;
  *   - 类型全部从 multi-model-routing SSoT 导入
  *
  * 调用方：
- *   - templates/commands/autonomous.md Step 4.0（解析 quality flag → wave 计划）
+ *   - templates/commands/autonomous.md 附录 A Step 4.0（解析 quality flag → wave 计划）
  *
  * 不做：
  *   - 不实际 spawn Agent（主线 LLM 职责）
@@ -1381,7 +1590,7 @@ interface PlanWavesOptions {
      *   - impl wave 走 `Agent(subagent_type="phase-runner")`（v4.0~v4.4 行为）
      *   - verify wave 走 Agent spawn（v4.4.1 及以前的 sonnet wrapper 路径）
      *
-     * 默认 true（autonomous Step 4.0+ 启用）时：
+     * 默认 true（autonomous 附录 A Step 4.0+ 启用）时：
      *   - impl wave 走 Bash 直调，subprocess RSS 与主进程隔离
      *   - verify wave 走 plugin script 直调，跳过 sonnet wrapper
      */
@@ -1391,7 +1600,7 @@ interface PlanWavesOptions {
      * 包装 `claude -p` 调用而非直接裸 spawn。解锁 Phase 2 supervisor 全部能力：
      * atomic state.json / process-tree kill-tree / cancel.flag 协作 / reconciler。
      *
-     * autonomous Step 4.2-4.3 默认开启。Test / dev workflow 可关闭走 P1a 裸 spawn 路径。
+     * autonomous 附录 A Step 4.2-4.3 默认开启。Test / dev workflow 可关闭走 P1a 裸 spawn 路径。
      * 默认 false 时保持 P1a 裸 `claude -p` BC（v4.5.0 → v4.5.1 升级路径）。
      */
     useLauncherWiring?: boolean;
@@ -1416,7 +1625,7 @@ declare function planWavesForTier(tier: QualityTier, phase: PhaseMeta, plugins:
 /**
  * One-shot 入口：解析 flag → 算 tier → 构 wave。
  *
- * 主线 autonomous Step 4.0 直接调这个，得到完整执行计划。
+ * 主线 autonomous 附录 A Step 4.0 直接调这个，得到完整执行计划。
  *
  * v4.5 P1a: `options.useDirectBashInvocation=true` 时 impl wave + verify wave
  * 都切到 Bash 直调（subprocess RSS 隔离 + verify wave silent fallback 治理）。
@@ -1442,7 +1651,7 @@ declare function buildQualityPlan(resolveInput: ResolveInput, phase: PhaseMeta,
  *   - 失败容错：单路解析失败仍用其他 N-1 路（不抛错）
  *
  * 调用方：
- *   - templates/commands/autonomous.md Step 4.x triple/debate 模式 plan wave 后
+ *   - templates/commands/autonomous.md 附录 A Step 4.x triple/debate 模式 plan wave 后
  *
  * 不做：
  *   - 不解析 phase-runner 摘要（phase-runner.ts 职责）
@@ -1640,6 +1849,64 @@ declare function synthesizeVerifyResults(reports: VerifyReport[]): VerifyDecisio
  * 修订轮要求：仅修复 critical 项，不重做整个 phase。
  */
 declare function synthesizeVerifyFeedback(reports: VerifyReport[]): string;
+/** 4 类 gate 失败路径类型 */
+type GateType = 'pre-flight' | 'revision-loop' | 'escalation' | 'abort';
+/** 单个 gate 的分类声明 */
+interface GateClassification {
+    /** kebab-case gate 标识 */
+    gate: string;
+    /** 常规失败路径类型 */
+    gateType: GateType;
+    /** critical finding 时覆盖路径（仅 verify-security → 'abort'） */
+    criticalOverride?: GateType;
+    /** revision-loop 专用迭代上限（统一 3） */
+    maxLoops?: number;
+    /** 确定性失败处理路径描述（模板引用的人类可读 SSoT） */
+    failurePath: string;
+}
+/** 全工作流 gate 分类注册表（单一真相源） */
+declare const GATE_REGISTRY: readonly GateClassification[];
+/** 按 gate 名查分类（大小写不敏感线性查找；未命中 → undefined） */
+declare function getGateClassification(gate: string): GateClassification | undefined;
+/** revision-loop 的轮次状态（调用方维护并喂入） */
+interface GateLoopState {
+    /** 当前已完成的轮数（首轮前传 0） */
+    currentLoop: number;
+    /** 迭代上限（缺省 3） */
+    maxLoops?: number;
+    /**
+     * 上一轮的 critical 数。传入后启用 stall detection：本轮 critical 数
+     * 不下降（>=）→ 不等耗尽提前升级。不传 = 关闭（与旧调用路径行为一致）。
+     */
+    previousCriticalCount?: number;
+}
+/** 类型化失败路径解析结果 */
+interface GateFailureAction {
+    gateType: GateType;
+    action: 'advance' | 'revise' | 'escalate' | 'abort';
+    currentLoop: number;
+    maxLoops: number;
+    message: string;
+    /** action='revise' 时 = synthesizeVerifyFeedback(reports) */
+    feedback?: string;
+    /** action='escalate' 时 = ESCALATION_OPTIONS */
+    options?: readonly string[];
+}
+/** escalation 三选（与 uat-session.decideConvergence / plan-checker 模板一致） */
+declare const ESCALATION_OPTIONS: readonly ["force: 接受当前结果并记录风险", "guide: 提供指导再试一轮", "abort: 中止并保留状态"];
+/**
+ * 综合 verify reports + 轮次状态，解析类型化失败路径（GSD Revision gate 语义）。
+ *
+ *   ① 钳制：maxLoops = max(1, floor(loop.maxLoops ?? 3))；cur = max(0, floor(currentLoop))
+ *   ② reports 空 / 任一 error      → escalate（无法判定，升级用户）
+ *   ③ 0 critical                  → advance
+ *   ④ cur >= maxLoops             → escalate（轮次耗尽，文案同 decideConvergence）
+ *   ⑤ stall（previousCriticalCount 传入且本轮 criticals >= 上轮）→ 提前 escalate
+ *   ⑥ 否则                        → revise（feedback = synthesizeVerifyFeedback）
+ *
+ * 复用 synthesizeVerifyResults/Feedback，不改其行为。
+ */
+declare function resolveVerifyGateAction(reports: VerifyReport[], loop?: GateLoopState): GateFailureAction;
 
 /**
  * Pipeline Check (CCG v4.3 Phase 25).
@@ -1659,7 +1926,7 @@ declare function synthesizeVerifyFeedback(reports: VerifyReport[]): string;
  *   - Cross-platform：用 child_process.execSync + node:fs + node:path 内建模块
  *
  * 调用方（主线）：
- *   - autonomous.md Step 4.4 phase 完成后（runPipelineCheck → 任何 critical → blocker 路径）
+ *   - autonomous.md 附录 A Step 4.4 phase 完成后（runPipelineCheck → 任何 critical → blocker 路径）
  *   - 用户手动跑 `node -e "..."` 验证
  *
  * 不做：
@@ -1704,7 +1971,7 @@ interface PipelineCheckOptions {
 /**
  * 跑 `pnpm pack` 在 workdir 下，返回生成的 tarball 绝对路径。
  *
- * pnpm pack 输出最后一行是 tarball 文件名（如 "ccg-workflow-4.3.0.tgz"）。
+ * pnpm pack 输出最后一行是 tarball 文件名（如 "ccgx-workflow-2.5.0.tgz"）。
  * 失败 → throw 给上层 catch。
  */
 declare function runPnpmPack(workdir: string): string;
@@ -1775,7 +2042,7 @@ declare function renderPipelineReport(report: PipelineCheckReport): string;
  *   - 输出 schema 自描述（含 sampledAt timestamp + 来源路径）
  *
  * 调用方：
- *   - autonomous.md Step 4.0 启动时 sampleAll + writeGroundTruth
+ *   - autonomous.md 附录 A Step 4.0 启动时 sampleAll + writeGroundTruth
  *   - phase-runner 的子任务（间接通过 prompt Read latest.json）
  *   - P28 测试 fixtures 自动生成（基于真采样输出）
  *
@@ -1940,7 +2207,7 @@ declare function summarizeGroundTruth(gt: GroundTruth): string;
  *     调用方决定语义
  *
  * 调用方：
- *   - templates/commands/autonomous.md Step 4.4 verify wave 综合
+ *   - templates/commands/autonomous.md 附录 A Step 4.4 verify wave 综合
  *   - quality-router.ts.buildVerifyWave (triple/debate spawns 内追加 interface-auditor)
  *
  * 不做：
@@ -2004,5 +2271,431 @@ declare function majorFindings(report: InterfaceAuditReport): InterfaceAuditFind
  */
 declare function hasBlockingFindings(report: InterfaceAuditReport): boolean;
 
-export { ALL_LAYERS, CONTEXT_BUDGET_THRESHOLD, DESCRIPTION_SOFT_LIMIT, FIX_LOG_RELATIVE_PATH, MAX_STATEMENT_CHARS, MIN_RATIONALE_CHARS, ROUTING_SCHEMA_VERSION, aggregatePlans, appendFixLogEntry, auditSkillDescriptions, auditSkillsDirectory, auditTarballContents, batchByMaxConcurrent, bothPluginsInstalled, buildQualityPlan, buildWaves, cascadeSkip, categorizeStatement, changeLanguage, checkForUpdates, checkQuality, collectInvocableSkills, collectSkills, compareVersions, contextPath, convergeHistoryFromLog, createDefaultConfig, createDefaultRouting, decideFromSummaries, detectPlugin, detectPluginAvailability, estimateBriefLength, estimateTokens, extractCandidates, extractFrontmatter, formatAsMarkdown, generateCommandContent, getCcgDir, getConfigPath, getCurrentVersion, getLatestVersion, getWorkflowById, getWorkflowConfigs, i18n, init, initI18n, installAceTool, installAceToolRs, installSkillCommands, installWorkflows, criticalFindings as interfaceAuditCriticals, hasBlockingFindings as interfaceAuditHasBlocking, majorFindings as interfaceAuditMajors, isLayer, loadConvergeHistory, migrateToV1_4_0, needsMigration, parseChallengerSummary, parseDependsOn, parseFrontmatter, parseFrontmatterFields, parseInterfaceAuditorReport, parseQualityFlag, parseRoadmap, parseRoleFlag, parseVerifyReport, phaseDir, planChallengerSpawns, planVerifyWave, planWavesForTier, promptFilePath, readCcgConfig, readContext, readFixLog, readSummary, readSummaryFrontmatter, renderAuditMarkdown, renderPipelineReport, resolveFixLogPath, resolveQualityTier, routeSpecialist, runPipelineCheck, runPnpmPack, sampleAll, sampleHookSchema, samplePackageStructure, samplePluginList, sampleSkillList, sanitizePhase, schedule, serializeBriefForPrompt, showMainMenu, summarizeGroundTruth, summaryPath, summaryTokenEstimate, synthesizeRevisionFeedback, synthesizeVerifyFeedback, synthesizeVerifyResults, uninstallAceTool, uninstallWorkflows, update, verifyAllCommandsIncluded, writeCcgConfig, writeContext, writeSummary };
-export type { AceToolConfig, AuditReport, AuditRow, CcgConfig, ChallengeInput, ChallengerAgent, ChallengerDecision, ChallengerPlan, ChallengerSummary, CliOptions, CollaborationMode, DesignBrief, Divergence, ExtractInput, FastContextConfig, Finding, FindingCounts, FindingSeverity, FixLogEntry, FixLogEntryKind, FixLogRecord, GroundTruth, PluginInfo as GroundTruthPluginInfo, SkillInfo as GroundTruthSkillInfo, HookInfo, InitOptions, InstallResult, InterfaceAuditCategory, InterfaceAuditFinding, InterfaceAuditReport, Layer, Model, ModelRouting, ModelType, PackageStructureInfo, PhaseContext, PhaseMeta, PhaseStatus, PhaseSummary, PipelineCheckOptions, PipelineCheckReport, PipelineError, PipelineErrorCategory, PlanContribution, PlanVerifyWaveOptions, PluginAdvisor, PluginAvailability, PluginAvailability as PluginDetectionAvailability, PluginDetectionResult, PluginName, QualityPlan, SpawnEntry as QualitySpawnEntry, QualityTier, WavePlan as QualityWavePlan, ResolveInput, ReviewLogEntry, RoadmapPhase, Role, PluginAvailability as RoutingPluginAvailability, RoutingStrategy, SampleOptions, ScheduleOptions, SkillCategory, SkillMeta, SkillRuntimeType, SpawnEntry$1 as SpawnEntry, SpecCandidate, SpecCategory, SpecialistCritic, SpecialistLayer, SpecialistModel, SpecialistRole, SpecialistRoute, SupportedLang, VerifyDecision, VerifyInvocationMode, VerifyMode, VerifyReport, VerifySpawnEntry, VerifyWavePlan, WaveKind, WaveSchedule, WorkflowConfig };
+/**
+ * Plan 中提取的 frontmatter 结构（仅关心 plan-checker 用得上的字段）。
+ *
+ * 约定的 plan 文件 frontmatter 格式：
+ * ```
+ * ---
+ * plan: <name>
+ * requirements: [REQ-01, REQ-02]
+ * ---
+ * ```
+ */
+interface ParsedPlanFrontmatter {
+    /** plan 名（可选） */
+    plan?: string;
+    /** plan 声明覆盖的需求 ID 列表（来自 frontmatter `requirements`） */
+    requirements: string[];
+}
+/** 单条已提取的需求条目（id + 描述文本） */
+interface RequirementItem {
+    id: string;
+    text: string;
+}
+/**
+ * 从需求文本（proposal.md / requirements.md / roadmap 段落）确定性提取 REQ-ID。
+ *
+ * 双格式（GSD gap-checker.cjs parseRequirements 同源规则）：
+ *   - checkbox：`- [ ] **REQ-01** <描述>`
+ *   - 表格首列：`| REQ-01 | <描述> | ... |`（跳过分隔行与其上方表头行）
+ *
+ * 去重保序；空文本 / 非字符串 → []。
+ */
+declare function extractRequirementIds(text: string): RequirementItem[];
+/**
+ * 从 roadmap.md 提取指定 phase 的 `- **Requirements**: REQ-01, REQ-02` 行。
+ *
+ * 定位 `## Phase <id>:` 块（到下一个 `## Phase` 或 EOF）。
+ * `(none)` / 缺行 / phase 不存在 → []。
+ *
+ * 与 wave-scheduler.parseRoadmap 的 requirements 字段解析同源（SSoT 在各自
+ * 模块内冗余但规则冻结：split(',') + trim + filter(Boolean)）。
+ */
+declare function extractPhaseRequirementIds(roadmapContent: string, phaseId: string): string[];
+/** 单个 REQ-ID 的覆盖状态 */
+interface RequirementsCoverageEntry {
+    id: string;
+    /**
+     * - covered: REQ-ID 在某 plan 的 frontmatter `requirements` 中显式声明
+     * - mentioned-only: 仅 plan 正文 word-boundary 命中，未在 frontmatter 声明（不算通过）
+     * - uncovered: 两者皆无
+     */
+    status: 'covered' | 'mentioned-only' | 'uncovered';
+    /** 声明覆盖的 plan 名（frontmatter.plan 或 `plan#<idx>`） */
+    coveredBy: string[];
+}
+/** Requirements Coverage Gate 判定结果 */
+interface RequirementsCoverageResult {
+    /** 与 GATE_REGISTRY 'requirements-coverage' 对齐：失败路径 = escalation 三选 */
+    gateType: 'escalation';
+    /** 仅当 uncovered 与 mentioned-only 均为 0 */
+    passed: boolean;
+    /** phaseReqIds 为空 → true 且 passed=true（GSD: Skip if null/TBD） */
+    skipped: boolean;
+    entries: RequirementsCoverageEntry[];
+    counts: {
+        total: number;
+        covered: number;
+        mentionedOnly: number;
+        uncovered: number;
+    };
+}
+/**
+ * 确定性 Requirements Coverage 检查：phase 分配的 REQ-ID 逐个对照所有 plan。
+ *
+ *   - covered: REQ-ID（大小写不敏感）∈ 任一 plan.frontmatter.requirements
+ *   - mentioned-only: 未声明但任一 plan.body word-boundary 命中（REQ-1 不误配
+ *     REQ-10）——刻意计为不通过，强制 frontmatter 显式声明（与 Dim 1 语义一致）
+ *   - uncovered: 两者皆无
+ *
+ * phaseReqIds 为空 → skipped=true 且 passed=true（存量项目 roadmap 无
+ * Requirements 行时 gate 整体 SKIP，零行为变化）。
+ */
+declare function checkRequirementsCoverage(phaseReqIds: readonly string[], plans: readonly {
+    frontmatter: ParsedPlanFrontmatter;
+    body?: string;
+}[]): RequirementsCoverageResult;
+/**
+ * 渲染 Requirements Coverage 报告（GSD §13 风格）。
+ *
+ *   - 通过：`✓ Requirements coverage: N/N REQ-IDs covered by plans`
+ *   - 失败：`## ⚠ Requirements Coverage Gap` + `| REQ-ID | Status | Covered By |`
+ *     表（natural sort）+ 三选项文案块（与 GATE_REGISTRY failurePath 一致）
+ */
+declare function formatRequirementsCoverageReport(result: RequirementsCoverageResult): string;
+
+/**
+ * Task persistence container + project lifecycle projection (P1-4).
+ *
+ * Mirrors the `jobs.ts` dir-per-id filesystem pattern and the upstream
+ * `task-utils.js` semantics (terminal-status synonym tolerance, newest
+ * non-terminal = active, archive by rename into `archive/YYYY-MM/`):
+ *
+ *   <workdir>/.context/tasks/<task-id>/task.json   — TaskRecord (write-side truth)
+ *   <workdir>/.context/tasks/archive/YYYY-MM/<id>/ — archived tasks
+ *   <workdir>/.context/STATE.json                  — ProjectState (derived projection)
+ *
+ * Design contracts:
+ *   - artifacts[] stores POINTERS only. Registration never moves / copies the
+ *     artifact file; the path may not even exist yet (register-then-write is
+ *     legal). Dedup key is `type + normalized path`, so re-registration is
+ *     idempotent.
+ *   - STATE.json is a PURE derived projection of the active task. Every
+ *     mutating function here ends with `syncProjectState`, so readers
+ *     (ccg-statusline.js) only ever need a single small file — no directory
+ *     scan. It can be rebuilt at any time via `syncProjectState`.
+ *   - `registerArtifactForActiveTask` is ADVISORY: it never throws and
+ *     returns null when there is no active task. Callers on hot paths
+ *     (appendFixLogEntry) rely on this.
+ *   - Status reads are TOLERANT (models write free text); status writes use
+ *     the canonical TaskStatus union.
+ *
+ * No daemon, no lock, no DB — just files (same rationale as jobs.ts).
+ */
+/** Container root, relative to the project workdir. */
+declare const TASKS_RELATIVE_PATH = ".context/tasks";
+/** Project-level lifecycle projection file, relative to the workdir. */
+declare const STATE_RELATIVE_PATH = ".context/STATE.json";
+/** Canonical write-side statuses. */
+type TaskStatus = 'in_progress' | 'completed' | 'archived' | 'cancelled';
+type ArtifactType = 'fix-log' | 'spec-evolution' | 'review' | 'plan' | 'summary' | 'generic';
+interface TaskArtifact {
+    type: ArtifactType;
+    /** Workdir-relative, '/'-separated pointer. The file may not exist yet. */
+    path: string;
+    status: 'active' | 'final' | 'stale';
+    /** ISO 8601 — preserved across idempotent re-registration. */
+    registered_at: string;
+    note?: string;
+}
+interface TaskProgress {
+    total_phases: number;
+    completed_phases: number;
+    /** Derived as round(completed/total*100) when omitted by the writer. */
+    percent?: number;
+}
+interface TaskRecord {
+    schema_version: 1;
+    id: string;
+    title: string;
+    status: TaskStatus;
+    /** Orchestrator-in-flight phase id; null when idle. */
+    active_phase?: string | null;
+    /** Idle-time recommended command, e.g. "/ccg:execute phase-03". */
+    next_action?: string | null;
+    /** Phase-dimension progress (not plan-dimension). */
+    progress?: TaskProgress;
+    branch?: string;
+    created_at: string;
+    updated_at: string;
+    completed_at?: string;
+    artifacts: TaskArtifact[];
+}
+interface ProjectState {
+    schema_version: 1;
+    active_task_id: string | null;
+    active_phase: string | null;
+    next_action: string | null;
+    progress: TaskProgress | null;
+    /** Optional lifecycle word (discussing/planning/executing/...). */
+    status?: string;
+    updated_at: string;
+}
+interface CreateTaskInit {
+    id: string;
+    title: string;
+    branch?: string;
+    active_phase?: string | null;
+    next_action?: string | null;
+    progress?: TaskProgress;
+}
+type TaskUpdatePatch = Partial<Pick<TaskRecord, 'title' | 'status' | 'active_phase' | 'next_action' | 'progress' | 'branch'>>;
+interface RegisterArtifactInput {
+    type: ArtifactType;
+    path: string;
+    status?: TaskArtifact['status'];
+    note?: string;
+}
+declare function tasksRoot(workdir: string): string;
+declare function taskDir(workdir: string, taskId: string): string;
+declare function taskJsonPath(workdir: string, taskId: string): string;
+declare function projectStatePath(workdir: string): string;
+/**
+ * Sanitize a task-id so it is filesystem-safe on every platform. Same regex
+ * as `sanitizeJobId`. Throws on empty input.
+ */
+declare function sanitizeTaskId(taskId: string): string;
+/**
+ * Read-tolerant terminal check. Non-string / empty → NOT terminal (an
+ * unreadable status must not hide a task from `getActiveTask`).
+ */
+declare function isTerminalStatus(status: unknown): boolean;
+/**
+ * Create a new task. Throws if a task with the same (sanitized) id already
+ * exists — silent overwrite would drop its artifacts[].
+ */
+declare function createTask(workdir: string, init: CreateTaskInit): TaskRecord;
+/**
+ * Read a single task. Returns null if the task dir / task.json is missing.
+ * Throws on corrupt JSON (same loud-on-probe contract as jobs.ts getJob).
+ */
+declare function getTask(workdir: string, taskId: string): TaskRecord | null;
+/**
+ * List all live tasks (skips the `archive/` subtree and corrupt entries),
+ * sorted by `created_at` descending (newest first).
+ */
+declare function listTasks(workdir: string): TaskRecord[];
+/**
+ * Newest non-terminal task, or null. Upstream getActiveTask semantics with
+ * read-tolerant terminal matching (stale-pointer detection comes for free:
+ * dirs without task.json are skipped by listTasks).
+ */
+declare function getActiveTask(workdir: string): TaskRecord | null;
+/**
+ * Merge a partial patch into an existing task, refresh `updated_at`, persist
+ * atomically. Throws when the task does not exist.
+ */
+declare function updateTask(workdir: string, taskId: string, patch: TaskUpdatePatch): TaskRecord;
+/**
+ * Register (or refresh) an artifact pointer on a task. Idempotent: dedup key
+ * is `type + normalized path`; re-registration only updates status / note and
+ * keeps the original `registered_at`. The pointed-at file does not need to
+ * exist (register-then-write is legal).
+ */
+declare function registerArtifact(workdir: string, taskId: string, artifact: RegisterArtifactInput): TaskRecord;
+/**
+ * ADVISORY variant: register an artifact on the current active task. Returns
+ * null (and never throws) when there is no active task or anything fails —
+ * hot-path callers (appendFixLogEntry) must not be affected by registry
+ * problems.
+ */
+declare function registerArtifactForActiveTask(workdir: string, artifact: RegisterArtifactInput): TaskRecord | null;
+/**
+ * Convenience wrapper for RFC-9: pin the SPEC_EVOLUTION.md pointer of an
+ * OpenSpec change onto the active task. Advisory (never throws).
+ */
+declare function registerSpecEvolution(workdir: string, changeId: string): TaskRecord | null;
+/**
+ * Mark a task completed: status='completed', completed_at=now,
+ * active_phase=null. `opts.next_action` (when provided, including null)
+ * overrides the stored recommendation. Throws when the task is missing.
+ */
+declare function completeTask(workdir: string, taskId: string, opts?: {
+    next_action?: string | null;
+}): TaskRecord;
+/**
+ * Archive a task: persist status='archived' first (so the task is terminal
+ * even if the move fails), then rename the task dir into
+ * `.context/tasks/archive/YYYY-MM/<id>` (UTC month of `now`, injectable for
+ * deterministic tests). Returns the destination dir, or null when the task
+ * is missing or the rename fails (advisory — e.g. EXDEV on a symlinked
+ * archive dir; never throws for those cases).
+ */
+declare function archiveTask(workdir: string, taskId: string, now?: Date): string | null;
+/**
+ * Read the project lifecycle projection. Missing / corrupt / non-object →
+ * null (the projection is derived; a broken file is just rebuilt by the next
+ * syncProjectState).
+ */
+declare function readProjectState(workdir: string): ProjectState | null;
+/**
+ * Write the projection, filling schema_version + updated_at. Atomic rename
+ * write (same crash contract as jobs.ts state.json).
+ */
+declare function writeProjectState(workdir: string, partial: Partial<ProjectState>): ProjectState;
+/**
+ * Rebuild STATE.json from the active task (pure projection — any lifecycle
+ * `status` word previously set via writeProjectState is intentionally NOT
+ * preserved; orchestrators set it as their last call when needed). With no
+ * active task the projection is the all-null idle state.
+ */
+declare function syncProjectState(workdir: string): ProjectState;
+
+/**
+ * phase-runner subagent 协议的主线侧 helper（v4.0 Phase 1.5）
+ *
+ * autonomous 主线 spawn `Agent(phase-runner)` 后接到的 ≤200 token 摘要，
+ * 由本模块解析为结构化对象，供主线决策 phase 推进 / 暂停 / cascade。
+ *
+ * 同时提供 phase Type → rescue subagent_type 的路由映射，给 phase-runner
+ * subagent 模板里 `routePhaseType()` 行为做单元测试覆盖。
+ */
+
+type PhaseRunnerStatus = 'completed' | 'partial' | 'failed' | 'degraded';
+interface PhaseRunnerSummary {
+    status: PhaseRunnerStatus;
+    commit: string | null;
+    tests: {
+        passed: number;
+        total: number;
+        delta: number;
+    } | null;
+    typecheck: 'pass' | 'fail' | 'unknown';
+    handoffTaken: string[];
+    contextDelta: string;
+    notes: string;
+    raw: string;
+}
+
+/**
+ * workflow-autonomous (P1-5): `/ccg:autonomous` 原生 Workflow 编排的主线侧 helper。
+ *
+ * autonomous 默认路径不再轮转 prompt spawn phase-runner，而是把依赖正确的串行
+ * phase 序烘焙成一个 Workflow JS 脚本（for 循环逐 phase `await agent(...)`），
+ * 交给 Workflow 工具后台运行；中断后以 resumeFromRunId 断点恢复（已完成的
+ * agent() 调用命中缓存重放，不重跑）。
+ *
+ * 本模块只做纯函数（生成脚本字符串 / 校验结构化摘要 / milestone 裁决）：
+ *   - 不读文件系统、不调 Workflow 工具（那是主线 LLM 的职责）
+ *   - buildWorkflowScript 同输入字节级相同输出（resume 缓存命中的根基）
+ *   - 生成的脚本内零时间 / 随机 API（Workflow 可重放约束）
+ *
+ * 调用方：templates/commands/autonomous.md Step 4（workflow 默认路径）。
+ * 降级路径（--legacy prompt 轮转）不经过本模块。
+ */
+
+/**
+ * Workflow `agent()` 调用的 schema 参数——强制 phase-runner 返回结构化 JSON。
+ * 字段名小写下划线（status/commit/tests/typecheck/handoff_taken/context_delta/notes），
+ * 语义与 phase-runner.md Phase G 文本摘要字段 1:1 对应。
+ */
+declare const PHASE_SUMMARY_SCHEMA: {
+    readonly type: "object";
+    readonly additionalProperties: false;
+    readonly required: readonly ["status", "commit", "tests", "typecheck", "handoff_taken", "context_delta", "notes"];
+    readonly properties: {
+        readonly status: {
+            readonly type: "string";
+            readonly enum: readonly ["completed", "partial", "failed", "degraded"];
+        };
+        readonly commit: {
+            readonly type: "string";
+            readonly description: "sha7 或 \"none\"";
+        };
+        readonly tests: {
+            readonly type: "string";
+            readonly description: "\"<pass>/<total> passed (delta +<n>)\" 或 \"n/a\"";
+        };
+        readonly typecheck: {
+            readonly type: "string";
+            readonly enum: readonly ["pass", "fail", "unknown"];
+        };
+        readonly handoff_taken: {
+            readonly type: "array";
+            readonly items: {
+                readonly type: "string";
+            };
+            readonly maxItems: 8;
+        };
+        readonly context_delta: {
+            readonly type: "string";
+            readonly maxLength: 100;
+        };
+        readonly notes: {
+            readonly type: "string";
+            readonly maxLength: 160;
+        };
+    };
+};
+/** 单个 phase 的脚本输入。`prompt` 是烘焙好的 phase-runner YAML 契约全文（仅 immutable 字段）。 */
+interface WorkflowPhaseSpec {
+    /** phase 标识，例如 "2" / "2.5" */
+    id: string;
+    /** meta.phases 用的人类可读标题，例如 "Phase 2: 实现 user API" */
+    title: string;
+    /** phase-runner 输入契约 YAML 全文（禁含 roadmap status / 时间戳等可变字段） */
+    prompt: string;
+}
+/** 脚本 meta 字面量来源；禁含时间戳（可重放约束）。 */
+interface WorkflowScriptOptions {
+    /** meta.name，例如 'ccg-autonomous-<milestone-slug>' */
+    name: string;
+    /** meta.description，例如 'CCG autonomous: <project> (<N> phases, serial)' */
+    description: string;
+}
+type MilestoneOutcome = 'completed' | 'partial' | 'escalated';
+/**
+ * 把 wave-scheduler 的 WaveSchedule 按 wave 顺序展开成串行 phase id 序。
+ * wave 内顺序保留（parseRoadmap 声明顺序），wave 间先后即依赖先后——
+ * 展平结果即依赖正确的串行执行序。
+ */
+declare function flattenWaves(s: WaveSchedule): string[];
+/**
+ * 生成 autonomous 串行编排的 Workflow 脚本（.mjs 源码字符串）。
+ *
+ * 确定性保证：
+ *   - 同输入两次调用输出字节级相同（无时间戳 / 随机量进入产物）
+ *   - 所有字符串经 JSON.stringify 烘焙（反引号 / 引号 / 换行 / ${} 不会击穿语法）
+ *   - 产物内不含任何时间 / 随机 API 调用（Workflow 可重放约束）
+ *
+ * 产物结构：export const meta（纯字面量）+ const PHASES + const SUMMARY_SCHEMA
+ * + export default async function run(args)。`agent` 由 Workflow 运行时注入，
+ * 仅在函数体内引用——import 该模块不执行任何 agent 调用。
+ *
+ * @throws phases 为空时
+ */
+declare function buildWorkflowScript(phases: WorkflowPhaseSpec[], opts: WorkflowScriptOptions): string;
+/**
+ * 把 Workflow agent() 返回的 schema 结构化对象校验 + 转换为 PhaseRunnerSummary。
+ *
+ * 抛错场景：非对象 / 缺 required 字段 / status 非法。
+ * 宽容处理（与 parsePhaseRunnerSummary 语义 lockstep）：
+ *   - commit "none" → null；其余抽 sha7-40 hex，抽不出 → null
+ *   - tests "n/a" 或不匹配 "<pass>/<total> passed" 正则 → null
+ *   - typecheck 非 pass/fail → 'unknown'
+ */
+declare function summaryFromWorkflowResult(v: unknown): PhaseRunnerSummary;
+/**
+ * 由 workflow run 返回的 results 裁决 milestone 终态：
+ *   - 任一 escalated / failed → 'escalated'（优先级最高，blocker 路径）
+ *   - 否则任一 partial → 'partial'（灰区暂停）
+ *   - 其余（completed / degraded 视同 completed）→ 'completed'
+ */
+declare function decideMilestoneOutcome(results: Array<{
+    status: string;
+    escalated?: boolean;
+}>): MilestoneOutcome;
+
+export { ALL_LAYERS, AUTO_CONVERGE_CAP, CONTEXT_BUDGET_THRESHOLD, DESCRIPTION_SOFT_LIMIT, ESCALATION_OPTIONS, FIX_LOG_RELATIVE_PATH, GATE_REGISTRY, LOCK_RETRY_ERRNOS, MAX_STATEMENT_CHARS, MAX_WAIT_MS, MIN_RATIONALE_CHARS, PHASE_SUMMARY_SCHEMA, RETRY_DELAY_MS, ROUTING_SCHEMA_VERSION, STALE_THRESHOLD_MS, STATE_RELATIVE_PATH, SUMMARY_TOKEN_BUDGET, TASKS_RELATIVE_PATH, acquireLock, aggregatePlans, appendFixLogEntry, archiveTask, auditSkillDescriptions, auditSkillsDirectory, auditTarballContents, batchByMaxConcurrent, bothPluginsInstalled, buildQualityPlan, buildTaskWaves, buildWaves, buildWorkflowScript, cascadeSkip, categorizeStatement, changeLanguage, checkForUpdates, checkQuality, checkRequirementsCoverage, collectInvocableSkills, collectRegressionTests, collectSkills, compareVersions, completeTask, contextPath, convergeHistoryFromLog, createDefaultConfig, createDefaultRouting, createTask, decideConverge, decideFromSummaries, decideMilestoneOutcome, detectPlugin, detectPluginAvailability, estimateBriefLength, estimateTokens, extractCandidates, extractFrontmatter, extractPhaseRequirementIds, extractRequirementIds, flattenWaves, formatAsMarkdown, formatRequirementsCoverageReport, generateCommandContent, getActiveTask, getCcgDir, getConfigPath, getCurrentVersion, getGateClassification, getLatestVersion, getTask, getWorkflowById, getWorkflowConfigs, i18n, init, initI18n, installAceTool, installAceToolRs, installSkillCommands, installWorkflows, criticalFindings as interfaceAuditCriticals, hasBlockingFindings as interfaceAuditHasBlocking, majorFindings as interfaceAuditMajors, isLayer, isTerminalStatus, isTestFilePath, listTasks, loadConvergeHistory, lockPathFor, mergeSummary, mergeSummaryFields, migrateToV1_4_0, needsMigration, parseChallengerSummary, parseDependsOn, parseFrontmatter, parseFrontmatterFields, parseInterfaceAuditorReport, parseQualityFlag, parseRoadmap, parseRoleFlag, parseVerifyReport, phaseDir, planChallengerSpawns, planVerifyWave, planWavesForTier, projectStatePath, promptFilePath, readCcgConfig, readContext, readFixLog, readProjectState, readSummary, readSummaryFrontmatter, registerArtifact, registerArtifactForActiveTask, registerSpecEvolution, releaseLock, renderAuditMarkdown, renderPipelineReport, resolveFixLogPath, resolveQualityTier, resolveVerifyGateAction, routeSpecialist, runPipelineCheck, runPnpmPack, sampleAll, sampleHookSchema, samplePackageStructure, samplePluginList, sampleSkillList, sanitizePhase, sanitizeTaskId, schedule, serializeBriefForPrompt, showMainMenu, splitWaveByFileOverlap, summarizeGroundTruth, summaryFromWorkflowResult, summaryPath, summaryTokenEstimate, syncProjectState, synthesizeRevisionFeedback, synthesizeVerifyFeedback, synthesizeVerifyResults, taskDir, taskJsonPath, tasksRoot, uninstallAceTool, uninstallWorkflows, update, updateTask, validateTaskGraph, verifyAllCommandsIncluded, withLock, writeCcgConfig, writeContext, writeProjectState, writeSummary };
+export type { AceToolConfig, ArtifactType, AuditReport, AuditRow, CcgConfig, ChallengeInput, ChallengerAgent, ChallengerDecision, ChallengerPlan, ChallengerSummary, CliOptions, CollaborationMode, ConvergeBlocking, ConvergeDecision, ConvergeRound, CreateTaskInit, DesignBrief, Divergence, ExtractInput, FastContextConfig, Finding, FindingCounts, FindingSeverity, FixLogEntry, FixLogEntryKind, FixLogRecord, GateClassification, GateFailureAction, GateLoopState, GateType, GroundTruth, PluginInfo as GroundTruthPluginInfo, SkillInfo as GroundTruthSkillInfo, HookInfo, InitOptions, InstallResult, InterfaceAuditCategory, InterfaceAuditFinding, InterfaceAuditReport, Layer, LockOptions, MilestoneOutcome, Model, ModelRouting, ModelType, PackageStructureInfo, PhaseContext, PhaseMeta, PhaseStatus, PhaseSummary, PipelineCheckOptions, PipelineCheckReport, PipelineError, PipelineErrorCategory, PlanContribution, PlanTask, PlanVerifyWaveOptions, PluginAdvisor, PluginAvailability, PluginAvailability as PluginDetectionAvailability, PluginDetectionResult, PluginName, ProjectState, QualityPlan, SpawnEntry as QualitySpawnEntry, QualityTier, WavePlan as QualityWavePlan, RegisterArtifactInput, RequirementItem, RequirementsCoverageEntry, RequirementsCoverageResult, ResolveInput, ReviewLogEntry, RoadmapPhase, Role, PluginAvailability as RoutingPluginAvailability, RoutingStrategy, SampleOptions, ScheduleOptions, SkillCategory, SkillMeta, SkillRuntimeType, SpawnEntry$1 as SpawnEntry, SpecCandidate, SpecCategory, SpecialistCritic, SpecialistLayer, SpecialistModel, SpecialistRole, SpecialistRoute, SummaryTaskPatch, SupportedLang, TaskArtifact, TaskProgress, TaskRecord, TaskStatus, TaskUpdatePatch, TaskWaveSchedule, VerifyDecision, VerifyInvocationMode, VerifyMode, VerifyReport, VerifySpawnEntry, VerifyWavePlan, WaveKind, WaveSchedule, WorkflowConfig, WorkflowPhaseSpec, WorkflowScriptOptions };