cclaw-cli 6.14.4 → 7.0.1

package/dist/artifact-linter/tdd.d.ts

@@ -1,7 +1,7 @@
 import type { DelegationEntry, DelegationEvent } from "../delegation.js";
 import { type LintFinding, type StageLintContext } from "./shared.js";
 /**
- * v6.11.0 — TDD stage linter.
+ * TDD stage linter.
  *
  * Source-of-truth ladder, in order of precedence:
  *
@@ -11,10 +11,9 @@ import { type LintFinding, type StageLintContext } from "./shared.js";
  *    auto-derives Watched-RED / Vertical Slice Cycle from the events
  *    and writes a rendered summary block between auto-render markers
  *    in `06-tdd.md`. Markdown table content is no longer required.
- * 2. **Legacy markdown tables** (Watched-RED Proof + Vertical Slice
- *    Cycle) — used as a fallback when the events ledger has no slice
- *    phase rows for the active run. Existing v6.10 and earlier
- *    artifacts continue to validate via this path.
+ * 2. **Hand-authored markdown tables** (Watched-RED Proof + Vertical
+ *    Slice Cycle) — used as a fallback when the events ledger has no
+ *    slice phase rows for the active run.
  * 3. **Sharded slice files** under `<artifacts-dir>/tdd-slices/S-*.md`.
  *    Per-slice prose lives there. The main `06-tdd.md` is auto-indexed
  *    via `## Slices Index`.
@@ -36,25 +35,23 @@ export declare function evaluateEventsSliceCycle(slices: Map<string, DelegationE
 interface DocCoverageResult {
     missing: string[];
 }
-export declare function evaluateSliceDocumenterCoverage(slices: Map<string, DelegationEntry[]>): DocCoverageResult;
-interface ImplementerCoverageResult {
+export declare function evaluateSliceDocCoverage(slices: Map<string, DelegationEntry[]>): DocCoverageResult;
+interface BuilderCoverageResult {
     missing: string[];
 }
 /**
- * v6.12.0 Phase M — slice-implementer must own GREEN. For each slice
- * that recorded a phase=red event with non-empty evidenceRefs, require a
- * phase=green event whose `agent === "slice-implementer"`. Slices whose
- * GREEN event came from a different agent (e.g. controller wrote GREEN
- * itself and recorded a green row under another agent name) are flagged.
+ * `slice-builder` must own GREEN. For each slice that recorded a phase=red
+ * event with non-empty evidenceRefs, require a phase=green whose agent is
+ * `slice-builder`.
  */
-export declare function evaluateSliceImplementerCoverage(slices: Map<string, DelegationEntry[]>): ImplementerCoverageResult;
+export declare function evaluateSliceBuilderCoverage(slices: Map<string, DelegationEntry[]>): BuilderCoverageResult;
 interface RedCheckpointResult {
     ok: boolean;
     details: string;
 }
 /**
- * v6.13.1 — detect single-slice dispatch when the merged wave plan
- * requires parallel ready slice-implementer fan-out.
+ * Detect single-slice dispatch when the merged wave plan requires parallel
+ * ready slice-builder fan-out.
  */
 export declare function evaluateWavePlanDispatchIgnored(params: {
     artifactsDir: string;
@@ -62,10 +59,10 @@ export declare function evaluateWavePlanDispatchIgnored(params: {
     runEvents: DelegationEvent[];
     runId: string;
     slices: Map<string, DelegationEntry[]>;
-    legacyContinuation: boolean;
 }): Promise<LintFinding | null>;
 /**
- * v6.12.0 Phase W (legacy `global-red` mode) — RED checkpoint enforcement.
+ * Global RED checkpoint enforcement (`global-red` mode).
+ *
  * The wave protocol requires ALL Phase A REDs to land before ANY Phase B
  * GREEN starts. The rule is enforced on a per-wave basis, where a wave is
  * defined by the managed `## Parallel Execution Plan` block in
@@ -75,10 +72,9 @@ export declare function evaluateWavePlanDispatchIgnored(params: {
  * with no other-phase events between them; the rule fires only when the
  * implicit wave has 2+ members.
  *
- * v6.14.0: this function powers the `global-red` checkpoint mode. New
- * projects default to `per-slice` mode (see
- * `evaluatePerSliceRedBeforeGreen`); `legacyContinuation: true` projects
- * auto-keep this behavior. Exported under both `evaluateGlobalRedCheckpoint`
+ * Default mode is `per-slice` (see `evaluatePerSliceRedBeforeGreen`);
+ * this checkpoint applies when a project explicitly opts into
+ * `global-red`. Exported under both `evaluateGlobalRedCheckpoint`
  * (canonical name) and `evaluateRedCheckpoint` (back-compat alias for
  * existing tests/consumers).
  *
@@ -87,26 +83,17 @@ export declare function evaluateWavePlanDispatchIgnored(params: {
  */
 export declare function evaluateGlobalRedCheckpoint(slices: Map<string, DelegationEntry[]>, waveMembers?: Map<string, Set<string>> | null): RedCheckpointResult;
 /**
- * Back-compat alias for `evaluateGlobalRedCheckpoint` (v6.12.0 Phase W
- * behavior). Existing tests/consumers can keep importing
- * `evaluateRedCheckpoint`. The v6.14.0 stream-style mode uses
- * `evaluatePerSliceRedBeforeGreen` instead.
+ * Back-compat alias for `evaluateGlobalRedCheckpoint`. The default mode
+ * uses `evaluatePerSliceRedBeforeGreen` instead.
  */
 export declare const evaluateRedCheckpoint: typeof evaluateGlobalRedCheckpoint;
 /**
- * v6.14.0 — per-slice RED-before-GREEN enforcement (default mode).
+ * Per-slice RED-before-GREEN enforcement (default mode).
  *
  * For each slice with both phase=red and phase=green completed events,
  * fail if any green completedTs precedes the slice's last red completedTs.
  * No global wave barrier — different slices may freely interleave their
  * RED/GREEN/REFACTOR phases.
- *
- * Note: this is intentionally weaker than `evaluateGlobalRedCheckpoint`
- * because the W-02 measurement on hox showed ~6 minutes of barrier
- * overhead when slices were already disjoint (file-overlap scheduler did
- * the parallelism job). The per-slice rule retains the only invariant
- * that mattered for correctness: no slice goes GREEN before its own
- * RED is observed failing.
  */
 export declare function evaluatePerSliceRedBeforeGreen(slices: Map<string, DelegationEntry[]>): RedCheckpointResult;
 export declare function parseVerticalSliceCycle(body: string): ParsedSliceCycleResult;