@shipispec/tsfix 0.2.0 → 0.3.0

package/CHANGELOG.md

@@ -4,8 +4,25 @@ All notable changes to `@shipispec/tsfix` are documented here. Format follows [K
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-05-07
+
+Phase 2 contract release. **Establishes the public types `MendContext`, `LayerEvent`, and `Diagnostic` so a downstream LLM-mend package (e.g. `@shipispec/tsmend`) can consume tsfix's output without redefining the shape.** No behavior changes; purely additive types. Also collapses several dev-only improvements that landed since v0.2.0 into a single release.
+
 ### Added
-- **Project-shape matrix** (`scripts/run-matrix.mjs`, `npm run matrix`) — pre-publish gate that builds the local tarball and exercises it cold against 6 distinct project shapes: `monorepo-refs` (project references — pinned as a documented limitation), `next-app` (App Router, `paths` alias, `jsx: preserve`), `plain-ts-bundler` (esnext + bundler), `plain-ts-commonjs` (legacy CJS + ES2015 + node10), `plain-ts-nodenext` (nodenext resolution), `react-vite` (TSX + `jsx: react-jsx`). Each sample has an `expected.json` asserting `errorsBefore`, `errorsAfterMax`, `lspFixesAppliedMin/Max`, `mustPass`, and `expectFileContains` post-fix. 6/6 pass on 2026-05-05. Dev-only — not shipped in the tarball.
+- **`MendContext` interface** — public type defining the input contract for a Layer 2–4 LLM-mend agent. Required fields: `workspaceRoot`, `diagnostics`, `erroredFiles`. Optional fields: `taskDescription`, `featureSpecText`, `acceptanceCriteria`, `siblingTasks`, `priorTaskExports`, `installedTypes`.
+- **`LayerEvent` interface** — per-layer event shape for streaming telemetry. Designed for an `onLayerEvent` callback in a future minor release; the type is published now so downstream callers can construct events themselves.
+- **`Diagnostic` type alias** — public re-export of `InProcessTscResult["diagnostics"][number]`. Convenience for consumers building `MendContext`.
+- **Project-shape matrix** (`scripts/run-matrix.mjs`, `npm run matrix`) — pre-publish gate that builds the local tarball and exercises it cold against 6 distinct project shapes: `monorepo-refs` (project references — pinned as a documented limitation), `next-app` (App Router, `paths` alias, `jsx: preserve`), `plain-ts-bundler` (esnext + bundler), `plain-ts-commonjs` (legacy CJS + ES2015 + node10), `plain-ts-nodenext` (nodenext resolution), `react-vite` (TSX + `jsx: react-jsx`). 6/6 pass. Dev-only — not shipped in the tarball.
+- **Capture script** (`scripts/capture-fixture.mjs`, `npm run capture`) — Phase 3b tooling for snapshotting real broken workspaces into `fixtures/real-<name>/`. Awaits first real failure to produce fixtures.
+- **GitHub Actions CI** (`.github/workflows/test.yml`) — runs check-types, vitest, benchmark, and the matrix on every PR + main push.
+
+### Changed
+- **Repository moved.** `tsc-defense-stack/` was extracted from the `spectoship-meta` monorepo into its own repository at <https://github.com/owgreen-dev/tsfix>. All `repository.url`, `homepage`, `bugs.url` fields point at the new repo. Internal git history pre-2026-05-06 lives in the original monorepo; the CHANGELOG narrates v0.1.0–v0.2.0 in detail.
+- **Public README rewritten** for an OSS audience — tagline, before/after, 30-second cold start, four-layer model, library API, trust model, contributing protocol. Previous internal-orientation README preserved at `docs/internal-orientation.md`.
+
+### Engines
+- Node `>=20.9.0` (unchanged)
+- TypeScript `>=5.0.0` peer (unchanged)
 
 ## [0.2.0] - 2026-05-04
 
@@ -80,7 +97,8 @@ Initial public release. **Layers 0–1 only** (deterministic detection + auto-fi
 - Node `>=20.9.0` (matches VS Code Extension Host runtime)
 - TypeScript `>=5.0.0` (peer dep, must be installed in the consuming workspace)
 
-[Unreleased]: https://github.com/owgreen-dev/tsfix/compare/v0.2.0...HEAD
+[Unreleased]: https://github.com/owgreen-dev/tsfix/compare/v0.3.0...HEAD
+[0.3.0]: https://github.com/owgreen-dev/tsfix/compare/v0.2.0...v0.3.0
 [0.2.0]: https://github.com/owgreen-dev/tsfix/compare/v0.1.1...v0.2.0
 [0.1.1]: https://github.com/owgreen-dev/tsfix/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/owgreen-dev/tsfix/releases/tag/v0.1.0

package/README.md

@@ -1,170 +1,178 @@
-# TSC Defense Stack — `@shipispec/tsfix`
+# tsfix
 
-Standalone npm package implementing **Layers 0–1** of the TypeScript error-recovery stack: in-process tsc validation + deterministic LSP auto-fix. Layers 2–4 (LLM mend) currently live in `spectoship2/src/pipeline/` and will move to a sister package `@shipispec/tsmend` per the roadmap.
+> Headless TypeScript error recovery — auto-resolve `TS2304`, `TS2305`, `TS2551`, `TS2552`, `TS2724` before they reach a human.
 
-Read first:
-- `STATUS.md` — what's working, what's planned, current gaps
-- `ARCHITECTURE.md` — why the package is shaped the way it is
-- `tsc-defense-roadmap.md` — phased plan with open decisions
-- `CLAUDE.md` — working principles (small allowlist, fixture-pinned trust model)
+`@shipispec/tsfix` borrows the same TypeScript Language Service that powers VS Code's "Quick Fix" lightbulb and runs it as a CLI. Point it at a workspace, it fixes typos, missing imports, and did-you-mean errors deterministically — no LLM, no calls home, no config.
 
----
+Built for the case where you've just generated a few hundred files of TypeScript with an LLM and `tsc --noEmit` is screaming at you.
 
-## Source-of-truth map
+## Before / after
 
-This package owns its TypeScript-error handling code outright. The shims in `spectoship2/` re-export from here, not the reverse.
+```
+$ tsc --noEmit
+src/api.ts:5:2  - error TS2552: Cannot find name 'consol'. Did you mean 'console'?
+src/api.ts:8:5  - error TS2305: Module '"react"' has no exported member 'ueState'.
+src/api.ts:12:14 - error TS2551: Property 'lenght' does not exist on type 'string[]'. Did you mean 'length'?
 
-| Path | Role |
-|---|---|
-| `src/index.ts` | Public API (`runValidationLoop`, `runInProcessTsc`, `runLSPFixerPass`, `discoverTsFiles`) |
-| `src/validatorInProcess.ts` | In-process tsc with lib-path workaround (Layer 0) |
-| `src/tsLanguageServiceFixer.ts` | LSP auto-fixer using `getCodeFixesAtPosition` (Layer 1) |
-| `cli/run-stack.ts` | CLI: `tsx cli/run-stack.ts --workspace <path>` |
-| `benchmark/run-benchmark.ts` | Fixture harness (auto-discovers `fixtures/*/`) |
-| `fixtures/` | 14 hand-authored synthetic fixtures across 3 tiers |
-| `spectoship2/src/pipeline/validatorInProcess.ts` | **Re-export shim** → `@shipispec/tsfix` |
-| `spectoship2/src/pipeline/tsLanguageServiceFixer.ts` | **Re-export shim** → `@shipispec/tsfix` |
+Found 3 errors in 1 file.
 
----
+$ npx @shipispec/tsfix --workspace .
+[ts-lsp-fixer] applied 3 fixes across 1 file
 
-## How the layers fit together
+$ tsc --noEmit
+$ # 0 errors
+```
 
-Per `ARCHITECTURE.md`, a TSC error has up to four chances to die before reaching a user. Layers -1 (prevention) and 2-4 (mend) live outside this package.
+## 30-second cold start
 
-```
-                    ┌─────────────────────────────────────────────────┐
-                    │ Layer -1: PREVENTION (in spectoship2/, not here)│
-                    │   packageGotchas, installedExports, priorExports│
-                    │   codeGenPrompts (rules injected into prompt)    │
-                    └────────────────────┬────────────────────────────┘
-                                         │ files written to disk
-                                         ▼
-  ┌────── @shipispec/tsfix ───────┴──────────────────────────┐
-  │                                                                  │
-  │   ┌─────────────────────────────────────────────┐               │
-  │   │ Layer 0: src/validatorInProcess.ts           │               │
-  │   │   in-process tsc → structured diagnostics    │               │
-  │   │   workspace lib-path override                │               │
-  │   └─────────────────────┬───────────────────────┘               │
-  │                         │ if errors                              │
-  │                         ▼                                        │
-  │   ┌─────────────────────────────────────────────┐               │
-  │   │ Layer 1: src/tsLanguageServiceFixer.ts       │               │
-  │   │   getCodeFixesAtPosition (5 SAFE codes)      │               │
-  │   │   signature-set progress check, max 5 iters  │               │
-  │   └─────────────────────┬───────────────────────┘               │
-  │                         │ re-validate; if errors remain          │
-  └─────────────────────────┼─────────────────────────────────────────┘
-                            ▼
-                 ┌─────────────────────────────────┐
-                 │ Layers 2-4: LLM MEND            │
-                 │   mendAgent / mendArchitect /   │
-                 │   multiFileMend / repairAgent   │
-                 │   (in spectoship2/, not here;   │
-                 │    moves to @shipispec/tsmend│
-                 │    in v0.2 per roadmap)         │
-                 └─────────────────────────────────┘
+```bash
+cd your-broken-project
+npx @shipispec/tsfix --workspace .
 ```
 
----
+No config file. Exit code conventions:
 
-## What to read first
+| Code | Meaning |
+|---|---|
+| 0 | Workspace is clean |
+| 1 | Errors remain (printed to stderr) |
+| 2 | Bad arguments / harness error |
 
-1. **`STATUS.md`** — current state, fixture catalog, recent fixes
-2. **`ARCHITECTURE.md`** — why the package is shaped the way it is (12 sections)
-3. **`tsc-defense-roadmap.md`** — phased plan with open decisions
-4. **`src/index.ts`** — public API entry point (`runValidationLoop`)
-5. **`src/tsLanguageServiceFixer.ts`** — Layer 1 fixer; understand `SAFE_FIXABLE_CODES`, the signature-set progress check, and the iteration loop
-6. **`src/validatorInProcess.ts`** — in-process tsc with the lib-path workaround that makes the package work inside the VS Code Extension Host
+Preview what *would* change without writing to disk:
 
----
+```bash
+npx @shipispec/tsfix --workspace . --dry-run
+```
 
-## Standalone harness
+Machine-readable output for piping into other tools:
 
-```
-cli/run-stack.ts             # CLI: run stack on any workspace
-benchmark/run-benchmark.ts   # benchmark across all fixtures
-fixtures/                    # 14 hand-authored synthetic workspaces
-  _shared/                   # shared node_modules symlink target
-  clean-baseline/            # regression check (must stay green)
-  synthetic-*/               # 9 LSP-behavior fixtures (positive + negative)
-  api-drift-*/               # 4 version-drift fixtures (Zod 3 vs 4, React 18 vs 19, etc.)
+```bash
+npx @shipispec/tsfix --workspace . --json
 ```
 
-### Use as a library (today's recommended path)
+### All flags
 
-`@shipispec/tsfix` ships its source as `.ts`. Plain Node 22+ refuses to type-strip files in `node_modules`, so consumers need a TypeScript-aware loader (`tsx`, `ts-node`, or `jiti`) until v0.2 ships an esbuild bundle. Most LLM-tooling projects already use one of these.
+| Flag | Meaning |
+|---|---|
+| `--workspace <path>` | Required. Directory containing your `tsconfig.json`. |
+| `--dry-run` | Run the fixer in memory, report counts, write nothing. |
+| `--no-lsp` | Validate only — skip auto-fix. |
+| `--files <a.ts,b.ts>` | Restrict fixing to a comma-separated list. |
+| `--json` | Machine-readable output. |
+| `--verbose` | Per-fix logging. |
+| `--help` | Print usage. |
 
-```sh
-npm install @shipispec/tsfix typescript
-```
+## What it fixes
 
-```js
-// run-fix.mjs
-import { runValidationLoop } from "@shipispec/tsfix";
+| TS code | Meaning | What tsfix does |
+|---|---|---|
+| `TS2304` | Cannot find name | Auto-imports |
+| `TS2305` | Module has no exported member | Did-you-mean rename |
+| `TS2551` | Property does not exist on T, did you mean Y | Spelling fix |
+| `TS2552` | Cannot find name, did you mean Y | Spelling fix |
+| `TS2724` | Module member did-you-mean | Import rename |
 
-const result = runValidationLoop({ workspaceRoot: "./my-project" });
-console.log(result.errorsBefore, "→", result.errorsAfter);
-console.log("LSP fixes:", result.lspFixer.fixesApplied);
-```
+Against a 14-fixture benchmark spanning typos, did-you-mean cases, multi-file ripples, and 4 API-drift scenarios: **14/14 fixtures pass and 14/25 errors are auto-fixed (56%).** The remaining errors are intentionally outside Layer 0's scope (see below).
 
-```sh
-npx tsx run-fix.mjs    # tsx loads the package's .ts source
-```
+## What it does *not* fix
+
+By design, tsfix only applies fixes that are **deterministic** and **non-structural**. It will refuse to:
 
-### Use as a CLI (after `npm link` from a clone)
+- Add or remove function declarations
+- Insert type annotations or change types
+- Modify control flow (`await` insertions, async propagation)
+- Rewrite JSX trees
+- Add object-literal stub properties
 
-The bin's `npx` cold-start is blocked on the v0.2 esbuild bundle (see roadmap § 1a). For now, clone-and-link works:
+The internal allowlist is two-layered: error codes (`SAFE_FIXABLE_CODES`) and Quick Fix names (`SAFE_FIX_NAMES = ['import', 'fixImport', 'spelling', 'fixSpelling']`). When the language service offers anything outside that allowlist, tsfix abstains and surfaces the error in the result so a higher layer (LLM, human) can pick it up.
 
-```sh
-git clone https://github.com/owgreen-dev/spectoship-meta
-cd spectoship-meta/tsc-defense-stack
-npm install
-npm link
+## The four-layer model
 
-tsfix --workspace ./your-project
+tsfix is **Layer 0–1** of a larger error-recovery stack. The other layers are LLM-driven and live elsewhere (in your own code, or in companion packages):
+
+```
+Layer 0 — Prevention      (prompt rules, exported-API injection — your problem)
+Layer 1 — tsfix           (this package: deterministic auto-fix)
+─────────────────────────────────────────────────────────────────────────
+Layer 2 — Single-file LLM mend (architect + editor split)
+Layer 3 — Multi-file LLM mend  (blast-radius search/replace)
+Layer 4 — Stub-and-continue    (escape hatch)
 ```
 
-Flags: `--json`, `--no-lsp`, `--verbose`, `--files <comma-list>`. Exit codes: `0` = clean, `1` = errors remain, `2` = bad args / harness error.
+The bet: roughly half of TypeScript errors in LLM output are deterministically fixable. By catching them in Layer 1, you dodge the LLM tax (latency, cost, nondeterminism) on the easy half.
+
+## Library API
 
-### Run the benchmark (contributor-only)
+```typescript
+import { runValidationLoop } from '@shipispec/tsfix';
 
-From inside the package directory after `npm install`:
-```sh
-npm run benchmark              # all 14 fixtures
-npm run benchmark -- --fixture synthetic-typo-ts2552    # one fixture
+const result = runValidationLoop({
+  workspaceRoot: '/path/to/your/project',
+  // Optional:
+  // targetFiles: ['src/api.ts'],
+  // dryRun: true,
+  // logger: { info: console.log, warn: console.warn, error: console.error },
+});
+
+result.errorsBefore;          // number
+result.errorsAfter;           // number
+result.lspFixer.fixesApplied; // number
+result.lspFixer.filesEdited;  // string[]
+result.passed;                // boolean — true if errorsAfter === 0
 ```
 
-### Current baseline
+Other exports:
 
-**14/14 synthetic fixtures pass. LSP fixer auto-resolves 14/25 errors (56%).** The remaining errors are intentional non-fixes — TS7006 implicit-any, TS2741 missing prop, API-drift errors that need the mend layer. See `STATUS.md` § Fixture catalog for the full list.
+- `runInProcessTsc(opts)` — validation only, no fixer. Returns structured diagnostics.
+- `runLSPFixerPass(opts)` — Layer 0 fixer alone, no validation loop wrapper.
+- `discoverTsFiles(workspaceRoot)` — file-walking helper. Skips `node_modules`, `.next`, `dist`, `build`, `out`, `coverage`, `.git`.
 
-### Capturing real-failure fixtures
+## Trust model
 
-Phase 3b in the roadmap. When a real spec-pipeline run produces a TSC error Layer 0-1 doesn't fix, snapshot the broken `.ts(x)` files into `fixtures/real-<timestamp>-<hash>/` with an `expected.json`. The fixture set then grows from production failures, not just synthetic ones.
+tsfix loads `typescript` from your workspace's `node_modules` — it does **not** bundle its own. This is intentional: it ensures the fixer behaves identically to the `tsc` your project actually compiles with.
 
----
+> **Run tsfix only on workspaces you trust.** Loading `typescript` from an attacker-controlled `node_modules` is equivalent to running `node_modules/.bin/tsc` against it.
 
-## Troubleshooting
+Other surface:
 
-**`ERR_MODULE_NOT_FOUND: Cannot find package 'typescript'`** — your package manager didn't install the peer dependency. Run `npm install typescript` (or yarn/pnpm equivalent). Modern npm (v7+) auto-installs peers, so you'll usually only see this with older npm or with `auto-install-peers=false`.
+- No network calls.
+- No telemetry.
+- No background processes.
+- No config files written or modified outside `--workspace`.
 
-**`Cannot find module '<workspace>/tsconfig.json'`** — you pointed `--workspace` at a directory with no `tsconfig.json`. Pass a directory whose root has the project's tsconfig (typically the project root, not a sub-package).
+## Engines
 
----
+- Node `>=20.9.0`
+- TypeScript `>=5.0.0` (peer dep — must be installed in your workspace)
 
-## Trust model
+If your workspace has no `node_modules/typescript`, tsfix will fail with a clear error:
+
+```
+error: this workspace has no TypeScript installed.
+run: npm install --save-dev typescript
+```
+
+## Contributing
+
+The contract for adding a fix:
 
-`@shipispec/tsfix` loads `typescript` from your workspace's `node_modules` (this is required for the lib-path workaround that makes the package work inside esbuild bundles). That means a malicious workspace's `typescript` install can execute arbitrary code at validate time.
+1. **Probe** — write a tiny test workspace with the exact error you want fixable. Drop it under `fixtures/<descriptive-name>/` with an `expected.json` declaring `errorsBefore`, `errorsAfterMax`, `lspFixesAppliedMin/Max`, and `mustPass`.
+2. **Verify** — run `npm run benchmark -- --fixture <name>` and inspect what the language service offers (the `fix.fixName` field).
+3. **Allowlist change** — if `fixName` is unsafe (`fixMissingFunctionDeclaration`, `addMissingPropertyAndOptional`, etc.), document why we don't trust it. Otherwise, add the error code to `SAFE_FIXABLE_CODES` and the fix name to `SAFE_FIX_NAMES` in `src/tsLanguageServiceFixer.ts`.
+4. **Lock it in** — confirm all existing fixtures still pass (`npm run benchmark`). Open a PR.
 
-**Only run `tsfix` on workspaces you trust.** This is the same trust boundary as ESLint, Prettier, Vitest, and other tools that load the workspace's TypeScript.
+Each new code/fix-name pair gets its own fixture. We don't trust the language service blindly — we trust it under specific, pinned conditions.
 
-There is no telemetry, no outbound HTTP, and no exec calls outside the local `node` ↔ `tsx` invocation in the bin wrapper. The only filesystem writes are LSP edits to files you pass in via `targetFiles` (or files discovered under `workspaceRoot`).
+`npm run matrix` runs the same package against 6 distinct project shapes (Next.js, Vite + React, plain `nodenext`, plain `bundler`, plain CommonJS, monorepo with project references). It builds the local tarball and exercises it cold; pre-publish gate.
 
----
+## License
 
-## What's in the package vs what's only for contributors
+MIT.
 
-The published tarball ships `src/`, `cli/`, `bin/`, plus `README.md` / `LICENSE` / `CHANGELOG.md`. Everything else (`benchmark/`, `fixtures/`, `tsconfig.json`, the dev-only npm scripts in `package.json`, the design docs in `docs/`) is contributor-side and either excluded from the tarball via `package.json#files` or just not part of the consumer-facing surface.
+## See also
 
-**Heads-up for consumers:** the published `package.json` includes `scripts.benchmark`, `scripts.test`, and `scripts.setup-fixtures`. Those reference `tsx`, `vitest`, and `fixtures/_shared/` — none of which ship to consumers. Don't run them from your `node_modules/@shipispec/tsfix/` directory; clone the repo if you want to contribute.
+- `CHANGELOG.md` — release notes per version.
+- `ARCHITECTURE.md` — internal design rationale (the four-layer model, the workspace lib-path workaround).
+- `STATUS.md` — current snapshot, gaps, and roadmap state.
+- `tsc-defense-roadmap.md` — phased plan.
+- `docs/internal-orientation.md` — the original SpecToShip-context README, kept for contributors who want the design history.

package/dist/index.d.ts

@@ -31,12 +31,15 @@
  * - `runInProcessTsc` — just type-check, returns structured diagnostics
  * - `runLSPFixerPass` — just the auto-fix pass, edits files in place
  *
- * ## What it doesn't do (yet)
+ * ## Public types for downstream LLM-mend integrations
  *
- * LLM-driven repair (the mend-agent layers from the spectoship pipeline) is
- * not exported here yet. They depend on internal types (ParsedTask) that need
- * to be redesigned as opaque interfaces before they can be moved into this
- * package. v0.2 target.
+ * - `Diagnostic` — single tsc error (re-exported from `runInProcessTsc`)
+ * - `MendContext` — input contract for a Layer 2–4 LLM-mend agent
+ * - `LayerEvent` — per-layer event shape for streaming telemetry
+ *
+ * The mend agents themselves (`@shipispec/tsmend`, planned) consume these
+ * types but are not shipped from this package — `tsfix` stays Layer 0–1
+ * deterministic.
  */
 export { runInProcessTsc, isInProcessTscEnabled, resetInProcessTscCache } from "./validatorInProcess.js";
 export type { InProcessTscOptions, InProcessTscResult } from "./validatorInProcess.js";
@@ -101,3 +104,73 @@ export declare function discoverTsFiles(workspaceRoot: string): string[];
  * Throws on missing `tsconfig.json` or workspace path.
  */
 export declare function runValidationLoop(opts: ValidationLoopOptions): ValidationLoopResult;
+/**
+ * Single tsc diagnostic. Re-exported from `runInProcessTsc`'s result type
+ * so consumers building a `MendContext` don't have to dig the shape out of
+ * `InProcessTscResult["diagnostics"][number]`.
+ */
+export type Diagnostic = InProcessTscResult["diagnostics"][number];
+/**
+ * Input contract for a Layer 2–4 LLM-mend agent.
+ *
+ * Pattern:
+ *   1. Run `runValidationLoop` (Layer 0/1).
+ *   2. If `result.errorsAfter > 0`, build a `MendContext` from the
+ *      surviving diagnostics + whatever task/spec context your pipeline has.
+ *   3. Hand off to a mend agent (e.g. `@shipispec/tsmend`).
+ *
+ * Required fields: `workspaceRoot`, `diagnostics`, `erroredFiles`.
+ * Everything else is optional — leave fields out if your pipeline doesn't
+ * carry them.
+ */
+export interface MendContext {
+    /** Absolute path to the workspace (must contain `tsconfig.json`). */
+    workspaceRoot: string;
+    /** Diagnostics that survived Layer 0/1 and need higher-layer repair. */
+    diagnostics: Diagnostic[];
+    /** Absolute paths of files containing the surviving diagnostics. */
+    erroredFiles: string[];
+    /** Optional one-line summary of what the failing code was supposed to do. */
+    taskDescription?: string;
+    /** Optional Markdown spec the code is implementing. Helps the LLM understand intent. */
+    featureSpecText?: string;
+    /** Optional testable acceptance criteria from the spec. */
+    acceptanceCriteria?: string;
+    /** Other tasks in the same feature, with their files and current status. */
+    siblingTasks?: Array<{
+        description: string;
+        files: string[];
+        status: "pending" | "completed" | "failed";
+    }>;
+    /** Public API surface from earlier completed tasks (helps prevent re-defining symbols). */
+    priorTaskExports?: string;
+    /** Compact type signatures of installed npm dependencies (helps prevent API hallucination). */
+    installedTypes?: string;
+}
+/**
+ * Per-layer event for streaming telemetry across the validate → fix → mend
+ * chain. Designed for an `onLayerEvent` callback (added in a future minor
+ * release) rather than accumulating in a result array — a workspace with
+ * 200 errors emits ~1000 events.
+ *
+ * Layer assignments:
+ *   0 = prevention (prompt rules, exported-API injection — caller's problem)
+ *   1 = tsfix LSP fixer (this package)
+ *   2 = single-file LLM mend
+ *   3 = multi-file LLM mend (blast-radius search/replace)
+ *   4 = stub-and-continue (escape hatch)
+ */
+export interface LayerEvent {
+    /** Which layer ran. */
+    layer: 0 | 1 | 2 | 3 | 4;
+    /** TypeScript error code being acted on (e.g. 2304, 2339, 7006). */
+    errorCode: number;
+    /** True if the error was resolved by this layer. */
+    fixed: boolean;
+    /** Wall-clock time spent on this attempt. */
+    latencyMs: number;
+    /** USD cost (LLM tokens). Undefined for deterministic layers. */
+    costUsd?: number;
+    /** `Date.now()` at emission. */
+    ts: number;
+}

package/dist/types/index.d.ts

@@ -31,12 +31,15 @@
  * - `runInProcessTsc` — just type-check, returns structured diagnostics
  * - `runLSPFixerPass` — just the auto-fix pass, edits files in place
  *
- * ## What it doesn't do (yet)
+ * ## Public types for downstream LLM-mend integrations
  *
- * LLM-driven repair (the mend-agent layers from the spectoship pipeline) is
- * not exported here yet. They depend on internal types (ParsedTask) that need
- * to be redesigned as opaque interfaces before they can be moved into this
- * package. v0.2 target.
+ * - `Diagnostic` — single tsc error (re-exported from `runInProcessTsc`)
+ * - `MendContext` — input contract for a Layer 2–4 LLM-mend agent
+ * - `LayerEvent` — per-layer event shape for streaming telemetry
+ *
+ * The mend agents themselves (`@shipispec/tsmend`, planned) consume these
+ * types but are not shipped from this package — `tsfix` stays Layer 0–1
+ * deterministic.
  */
 export { runInProcessTsc, isInProcessTscEnabled, resetInProcessTscCache } from "./validatorInProcess.js";
 export type { InProcessTscOptions, InProcessTscResult } from "./validatorInProcess.js";
@@ -101,3 +104,73 @@ export declare function discoverTsFiles(workspaceRoot: string): string[];
  * Throws on missing `tsconfig.json` or workspace path.
  */
 export declare function runValidationLoop(opts: ValidationLoopOptions): ValidationLoopResult;
+/**
+ * Single tsc diagnostic. Re-exported from `runInProcessTsc`'s result type
+ * so consumers building a `MendContext` don't have to dig the shape out of
+ * `InProcessTscResult["diagnostics"][number]`.
+ */
+export type Diagnostic = InProcessTscResult["diagnostics"][number];
+/**
+ * Input contract for a Layer 2–4 LLM-mend agent.
+ *
+ * Pattern:
+ *   1. Run `runValidationLoop` (Layer 0/1).
+ *   2. If `result.errorsAfter > 0`, build a `MendContext` from the
+ *      surviving diagnostics + whatever task/spec context your pipeline has.
+ *   3. Hand off to a mend agent (e.g. `@shipispec/tsmend`).
+ *
+ * Required fields: `workspaceRoot`, `diagnostics`, `erroredFiles`.
+ * Everything else is optional — leave fields out if your pipeline doesn't
+ * carry them.
+ */
+export interface MendContext {
+    /** Absolute path to the workspace (must contain `tsconfig.json`). */
+    workspaceRoot: string;
+    /** Diagnostics that survived Layer 0/1 and need higher-layer repair. */
+    diagnostics: Diagnostic[];
+    /** Absolute paths of files containing the surviving diagnostics. */
+    erroredFiles: string[];
+    /** Optional one-line summary of what the failing code was supposed to do. */
+    taskDescription?: string;
+    /** Optional Markdown spec the code is implementing. Helps the LLM understand intent. */
+    featureSpecText?: string;
+    /** Optional testable acceptance criteria from the spec. */
+    acceptanceCriteria?: string;
+    /** Other tasks in the same feature, with their files and current status. */
+    siblingTasks?: Array<{
+        description: string;
+        files: string[];
+        status: "pending" | "completed" | "failed";
+    }>;
+    /** Public API surface from earlier completed tasks (helps prevent re-defining symbols). */
+    priorTaskExports?: string;
+    /** Compact type signatures of installed npm dependencies (helps prevent API hallucination). */
+    installedTypes?: string;
+}
+/**
+ * Per-layer event for streaming telemetry across the validate → fix → mend
+ * chain. Designed for an `onLayerEvent` callback (added in a future minor
+ * release) rather than accumulating in a result array — a workspace with
+ * 200 errors emits ~1000 events.
+ *
+ * Layer assignments:
+ *   0 = prevention (prompt rules, exported-API injection — caller's problem)
+ *   1 = tsfix LSP fixer (this package)
+ *   2 = single-file LLM mend
+ *   3 = multi-file LLM mend (blast-radius search/replace)
+ *   4 = stub-and-continue (escape hatch)
+ */
+export interface LayerEvent {
+    /** Which layer ran. */
+    layer: 0 | 1 | 2 | 3 | 4;
+    /** TypeScript error code being acted on (e.g. 2304, 2339, 7006). */
+    errorCode: number;
+    /** True if the error was resolved by this layer. */
+    fixed: boolean;
+    /** Wall-clock time spent on this attempt. */
+    latencyMs: number;
+    /** USD cost (LLM tokens). Undefined for deterministic layers. */
+    costUsd?: number;
+    /** `Date.now()` at emission. */
+    ts: number;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@shipispec/tsfix",
-	"version": "0.2.0",
+	"version": "0.3.0",
 	"description": "Reusable TypeScript error-recovery agent. Validates LLM-generated TS code, auto-fixes deterministic error classes via the TS Language Service, and exposes hooks for LLM-driven repair.",
 	"keywords": [
 		"typescript",
@@ -48,6 +48,7 @@
 	"scripts": {
 		"build": "node scripts/build.mjs",
 		"matrix": "node scripts/run-matrix.mjs",
+		"capture": "node scripts/capture-fixture.mjs",
 		"prepack": "npm run build",
 		"setup-fixtures": "node -e \"require('fs').existsSync('fixtures/_shared/node_modules')||require('child_process').execSync('npm install --prefix fixtures/_shared',{stdio:'inherit'})\"",
 		"prebenchmark": "npm run setup-fixtures",