codebase-snapshot 0.9.9 → 0.9.14

package/dist/mcp.d.cts

@@ -1,3 +1,4 @@
+export { G as GenerateSummary, W as WorkerResults, g as generateInWorker } from './generate-worker-D_mUjgXw.cjs';
 import { Readable, Writable } from 'node:stream';
 
 /**
@@ -100,72 +101,6 @@ interface InputSchema extends JsonSchema {
     properties: Record<string, JsonSchema>;
 }
 
-type ProtocolEra = "legacy" | "modern";
-/** Per-connection state. The modern era has no session, so this stays empty until legacy init. */
-interface SessionState {
-    /** Which era the connection committed to, or null before the first decisive request. */
-    era: ProtocolEra | null;
-    /** The revision in force. Null in legacy until `initialize` has been negotiated. */
-    protocolVersion: string | null;
-    /** True once `initialize` has been answered, which is the legacy lifecycle's gate. */
-    ready: boolean;
-}
-declare function createSession(): SessionState;
-/** The modern request metadata, when a request carries it at all. */
-interface ModernMeta {
-    version: string;
-    clientCapabilities: JsonObject;
-    clientInfo: JsonObject | null;
-}
-type MetaInspection = {
-    kind: "absent";
-} | {
-    kind: "incomplete";
-    missing: string;
-} | {
-    kind: "present";
-    meta: ModernMeta;
-};
-/**
- * Reads `_meta` from a request.
- *
- * `absent` and `incomplete` are different answers: a request with no `_meta` at all is a legacy
- * client, while a request with `_meta` that lacks a required key is a modern client making a
- * mistake — and telling those two apart is what keeps the legacy era from being rejected for a
- * field it never had.
- */
-declare function inspectModernMeta(params: JsonObject | undefined): MetaInspection;
-type EraDecision = {
-    kind: "era";
-    era: ProtocolEra;
-    version: string | null;
-} | {
-    kind: "error";
-    code: number;
-    message: string;
-    data?: unknown;
-};
-/**
- * Decides which era a request belongs to, and whether its version is acceptable.
- *
- * Once a connection commits to an era it stays committed. A legacy client that suddenly sends
- * modern `_meta` is confused rather than clever, and silently switching would answer half a
- * session in each shape.
- */
-declare function classifyRequest(method: string, params: JsonObject | undefined, session: SessionState): EraDecision;
-interface LegacyNegotiation {
-    version: string;
-    /** False when the client asked for something we cannot speak and was negotiated down. */
-    matched: boolean;
-}
-/**
- * Legacy version negotiation: echo a supported request, otherwise answer with our best.
- *
- * A client that asked for a modern revision here gets the newest *legacy* revision, not an error:
- * under this lifecycle the server's answer is the offer, and the client decides.
- */
-declare function negotiateLegacyVersion(requested: unknown): LegacyNegotiation;
-
 /**
  * The capability records the MCP server serves.
  *
@@ -187,7 +122,7 @@ interface ToolContext {
  * Client-facing hints.
  *
  * `readOnlyHint` is the one that changes behaviour rather than appearance: clients use it to
- * auto-approve a call. Six of the seven tools never touch the filesystem, so they are marked
+ * auto-approve a call. Seven of the eight tools never touch the filesystem, so they are marked
  * read-only and only `snapshot_generate` prompts.
  */
 interface ToolAnnotations {
@@ -278,6 +213,72 @@ interface McpServerInfo {
     websiteUrl: string;
 }
 
+type ProtocolEra = "legacy" | "modern";
+/** Per-connection state. The modern era has no session, so this stays empty until legacy init. */
+interface SessionState {
+    /** Which era the connection committed to, or null before the first decisive request. */
+    era: ProtocolEra | null;
+    /** The revision in force. Null in legacy until `initialize` has been negotiated. */
+    protocolVersion: string | null;
+    /** True once `initialize` has been answered, which is the legacy lifecycle's gate. */
+    ready: boolean;
+}
+declare function createSession(): SessionState;
+/** The modern request metadata, when a request carries it at all. */
+interface ModernMeta {
+    version: string;
+    clientCapabilities: JsonObject;
+    clientInfo: JsonObject | null;
+}
+type MetaInspection = {
+    kind: "absent";
+} | {
+    kind: "incomplete";
+    missing: string;
+} | {
+    kind: "present";
+    meta: ModernMeta;
+};
+/**
+ * Reads `_meta` from a request.
+ *
+ * `absent` and `incomplete` are different answers: a request with no `_meta` at all is a legacy
+ * client, while a request with `_meta` that lacks a required key is a modern client making a
+ * mistake — and telling those two apart is what keeps the legacy era from being rejected for a
+ * field it never had.
+ */
+declare function inspectModernMeta(params: JsonObject | undefined): MetaInspection;
+type EraDecision = {
+    kind: "era";
+    era: ProtocolEra;
+    version: string | null;
+} | {
+    kind: "error";
+    code: number;
+    message: string;
+    data?: unknown;
+};
+/**
+ * Decides which era a request belongs to, and whether its version is acceptable.
+ *
+ * Once a connection commits to an era it stays committed. A legacy client that suddenly sends
+ * modern `_meta` is confused rather than clever, and silently switching would answer half a
+ * session in each shape.
+ */
+declare function classifyRequest(method: string, params: JsonObject | undefined, session: SessionState): EraDecision;
+interface LegacyNegotiation {
+    version: string;
+    /** False when the client asked for something we cannot speak and was negotiated down. */
+    matched: boolean;
+}
+/**
+ * Legacy version negotiation: echo a supported request, otherwise answer with our best.
+ *
+ * A client that asked for a modern revision here gets the newest *legacy* revision, not an error:
+ * under this lifecycle the server's answer is the offer, and the client decides.
+ */
+declare function negotiateLegacyVersion(requested: unknown): LegacyNegotiation;
+
 interface McpServerOptions {
     info: McpServerInfo;
     instructions: string;
@@ -297,6 +298,73 @@ declare function createMcpServer(options: McpServerOptions): McpServer;
 /** Every tool this server exposes, in the order a first-time caller should read them. */
 declare function buildTools(): McpTool[];
 
+/**
+ * Reads one file's section back out of a rendered part.
+ *
+ * `snapshot_read` must not open the working tree. The snapshot is the contract: sensitive files
+ * are excluded from it, secret-shaped strings inside ordinary files are redacted on the way in,
+ * and a large file is emitted as a bounded preview. Reading the source directly would hand the
+ * model the `.env` the snapshot deliberately skipped and the credential it masked — so the read
+ * goes through the artifact instead.
+ *
+ * The format it parses is written by `renderFileSection`, and the parser is deliberately tied to
+ * that shape rather than to a regex over the whole document: a file's *content* may legitimately
+ * contain a line that looks like `### FILE: something`, and only fence tracking tells the two
+ * apart. Content fences are four or more backticks (`fenceForContent` never emits three), which
+ * is what makes "the next line equal to this exact fence" an unambiguous terminator.
+ */
+interface PartSection {
+    /** The path as rendered in the `### FILE:` heading. */
+    path: string;
+    /** The `<a id="…">` anchor from the line above the heading, when present. */
+    anchor: string | null;
+    /** The file body, without its fence. Redacted and possibly a bounded preview. */
+    body: string;
+    /** `full`, `preview` or `signatures`. */
+    inclusion: string | null;
+    includedLines: number | null;
+}
+/** Splits a part into one section per emitted file. */
+declare function parsePartSections(partText: string): PartSection[];
+/**
+ * Finds the section for one file.
+ *
+ * The **anchor** is the identifier, not the heading. `anchorForPath` hashes the real
+ * `relativePath`, so it is exact and injective; the heading is the display form, and for a path
+ * with a control character (escaped as `\uXXXX`) or one longer than 300 characters (capped from
+ * the middle) it is not the path at all. The old fallback for those cases was the content
+ * SHA-256, which the part no longer carries — and which could never disambiguate two files with
+ * the same content, the exact case that needs it.
+ *
+ * The heading comparison is kept as a second chance, for a snapshot written before the anchor
+ * was read, or a part whose anchor line was edited by hand.
+ */
+declare function findSection(sections: readonly PartSection[], relativePath: string): PartSection | null;
+interface Window {
+    text: string;
+    fromLine: number;
+    returnedLines: number;
+    totalLines: number;
+    truncated: boolean;
+    nextFromLine: number | null;
+    /**
+     * True when `fromLine` is beyond the last line of the body.
+     *
+     * The start used to be clamped to the last line, so asking for line 9,000 of a 40-line file
+     * returned line 40 with a header that read `Lines 40–40 of 40` — a wrong answer dressed as a
+     * right one. The caller is told the request was out of range instead.
+     */
+    pastEnd: boolean;
+}
+/**
+ * Cuts a line window out of a body.
+ *
+ * Windows are the whole point of this module: a part holds hundreds of kilobytes, and the only
+ * safe default for a tool that returns content is "as little as answers the question". `next` is
+ * an explicit pointer rather than an instruction to keep reading, so an agent decides.
+ */
+declare function windowText(body: string, fromLine: number, lineCount: number): Window;
+
 declare function buildPrompts(): McpPrompt[];
 
 declare function buildResourceProvider(): ResourceProvider;
@@ -409,4 +477,4 @@ declare function validateArguments(schema: InputSchema, value: unknown): string[
  */
 declare function coerceNumericStrings(schema: InputSchema, value: JsonObject): JsonObject;
 
-export { ERROR_CODES, type JsonRpcResponse, type JsonSchema, LEGACY_PROTOCOL_VERSIONS, type LineReaderOptions, MAX_LINE_BYTES, METHOD, MODERN_PROTOCOL_VERSIONS, type McpPrompt, type McpResourceContents, type McpResourceDescriptor, type McpResourceTemplate, type McpServer, type McpServerInfo, type McpServerOptions, type McpTool, type MessageWriter, type ProtocolEra, type ResourceProvider, SERVER_INSTRUCTIONS, SUPPORTED_PROTOCOL_VERSIONS, type ServerOptions, type SessionState, type ToolAnnotations, type ToolContext, type ToolOutcome, buildPrompts, buildResourceProvider, buildTools, classifyRequest, coerceNumericStrings, createLineReader, createMcpServer, createServer, createSession, createWriter, inspectModernMeta, negotiateLegacyVersion, runStdioServer, validateArguments };
+export { ERROR_CODES, type JsonRpcResponse, type JsonSchema, LEGACY_PROTOCOL_VERSIONS, type LineReaderOptions, MAX_LINE_BYTES, METHOD, MODERN_PROTOCOL_VERSIONS, type McpPrompt, type McpResourceContents, type McpResourceDescriptor, type McpResourceTemplate, type McpServer, type McpServerInfo, type McpServerOptions, type McpTool, type MessageWriter, type PartSection, type ProtocolEra, type ResourceProvider, SERVER_INSTRUCTIONS, SUPPORTED_PROTOCOL_VERSIONS, type ServerOptions, type SessionState, type ToolAnnotations, type ToolContext, type ToolOutcome, type Window, buildPrompts, buildResourceProvider, buildTools, classifyRequest, coerceNumericStrings, createLineReader, createMcpServer, createServer, createSession, createWriter, findSection, inspectModernMeta, negotiateLegacyVersion, parsePartSections, runStdioServer, validateArguments, windowText };

package/dist/mcp.d.ts

@@ -1,3 +1,4 @@
+export { G as GenerateSummary, W as WorkerResults, g as generateInWorker } from './generate-worker-D_mUjgXw.js';
 import { Readable, Writable } from 'node:stream';
 
 /**
@@ -100,72 +101,6 @@ interface InputSchema extends JsonSchema {
     properties: Record<string, JsonSchema>;
 }
 
-type ProtocolEra = "legacy" | "modern";
-/** Per-connection state. The modern era has no session, so this stays empty until legacy init. */
-interface SessionState {
-    /** Which era the connection committed to, or null before the first decisive request. */
-    era: ProtocolEra | null;
-    /** The revision in force. Null in legacy until `initialize` has been negotiated. */
-    protocolVersion: string | null;
-    /** True once `initialize` has been answered, which is the legacy lifecycle's gate. */
-    ready: boolean;
-}
-declare function createSession(): SessionState;
-/** The modern request metadata, when a request carries it at all. */
-interface ModernMeta {
-    version: string;
-    clientCapabilities: JsonObject;
-    clientInfo: JsonObject | null;
-}
-type MetaInspection = {
-    kind: "absent";
-} | {
-    kind: "incomplete";
-    missing: string;
-} | {
-    kind: "present";
-    meta: ModernMeta;
-};
-/**
- * Reads `_meta` from a request.
- *
- * `absent` and `incomplete` are different answers: a request with no `_meta` at all is a legacy
- * client, while a request with `_meta` that lacks a required key is a modern client making a
- * mistake — and telling those two apart is what keeps the legacy era from being rejected for a
- * field it never had.
- */
-declare function inspectModernMeta(params: JsonObject | undefined): MetaInspection;
-type EraDecision = {
-    kind: "era";
-    era: ProtocolEra;
-    version: string | null;
-} | {
-    kind: "error";
-    code: number;
-    message: string;
-    data?: unknown;
-};
-/**
- * Decides which era a request belongs to, and whether its version is acceptable.
- *
- * Once a connection commits to an era it stays committed. A legacy client that suddenly sends
- * modern `_meta` is confused rather than clever, and silently switching would answer half a
- * session in each shape.
- */
-declare function classifyRequest(method: string, params: JsonObject | undefined, session: SessionState): EraDecision;
-interface LegacyNegotiation {
-    version: string;
-    /** False when the client asked for something we cannot speak and was negotiated down. */
-    matched: boolean;
-}
-/**
- * Legacy version negotiation: echo a supported request, otherwise answer with our best.
- *
- * A client that asked for a modern revision here gets the newest *legacy* revision, not an error:
- * under this lifecycle the server's answer is the offer, and the client decides.
- */
-declare function negotiateLegacyVersion(requested: unknown): LegacyNegotiation;
-
 /**
  * The capability records the MCP server serves.
  *
@@ -187,7 +122,7 @@ interface ToolContext {
  * Client-facing hints.
  *
  * `readOnlyHint` is the one that changes behaviour rather than appearance: clients use it to
- * auto-approve a call. Six of the seven tools never touch the filesystem, so they are marked
+ * auto-approve a call. Seven of the eight tools never touch the filesystem, so they are marked
  * read-only and only `snapshot_generate` prompts.
  */
 interface ToolAnnotations {
@@ -278,6 +213,72 @@ interface McpServerInfo {
     websiteUrl: string;
 }
 
+type ProtocolEra = "legacy" | "modern";
+/** Per-connection state. The modern era has no session, so this stays empty until legacy init. */
+interface SessionState {
+    /** Which era the connection committed to, or null before the first decisive request. */
+    era: ProtocolEra | null;
+    /** The revision in force. Null in legacy until `initialize` has been negotiated. */
+    protocolVersion: string | null;
+    /** True once `initialize` has been answered, which is the legacy lifecycle's gate. */
+    ready: boolean;
+}
+declare function createSession(): SessionState;
+/** The modern request metadata, when a request carries it at all. */
+interface ModernMeta {
+    version: string;
+    clientCapabilities: JsonObject;
+    clientInfo: JsonObject | null;
+}
+type MetaInspection = {
+    kind: "absent";
+} | {
+    kind: "incomplete";
+    missing: string;
+} | {
+    kind: "present";
+    meta: ModernMeta;
+};
+/**
+ * Reads `_meta` from a request.
+ *
+ * `absent` and `incomplete` are different answers: a request with no `_meta` at all is a legacy
+ * client, while a request with `_meta` that lacks a required key is a modern client making a
+ * mistake — and telling those two apart is what keeps the legacy era from being rejected for a
+ * field it never had.
+ */
+declare function inspectModernMeta(params: JsonObject | undefined): MetaInspection;
+type EraDecision = {
+    kind: "era";
+    era: ProtocolEra;
+    version: string | null;
+} | {
+    kind: "error";
+    code: number;
+    message: string;
+    data?: unknown;
+};
+/**
+ * Decides which era a request belongs to, and whether its version is acceptable.
+ *
+ * Once a connection commits to an era it stays committed. A legacy client that suddenly sends
+ * modern `_meta` is confused rather than clever, and silently switching would answer half a
+ * session in each shape.
+ */
+declare function classifyRequest(method: string, params: JsonObject | undefined, session: SessionState): EraDecision;
+interface LegacyNegotiation {
+    version: string;
+    /** False when the client asked for something we cannot speak and was negotiated down. */
+    matched: boolean;
+}
+/**
+ * Legacy version negotiation: echo a supported request, otherwise answer with our best.
+ *
+ * A client that asked for a modern revision here gets the newest *legacy* revision, not an error:
+ * under this lifecycle the server's answer is the offer, and the client decides.
+ */
+declare function negotiateLegacyVersion(requested: unknown): LegacyNegotiation;
+
 interface McpServerOptions {
     info: McpServerInfo;
     instructions: string;
@@ -297,6 +298,73 @@ declare function createMcpServer(options: McpServerOptions): McpServer;
 /** Every tool this server exposes, in the order a first-time caller should read them. */
 declare function buildTools(): McpTool[];
 
+/**
+ * Reads one file's section back out of a rendered part.
+ *
+ * `snapshot_read` must not open the working tree. The snapshot is the contract: sensitive files
+ * are excluded from it, secret-shaped strings inside ordinary files are redacted on the way in,
+ * and a large file is emitted as a bounded preview. Reading the source directly would hand the
+ * model the `.env` the snapshot deliberately skipped and the credential it masked — so the read
+ * goes through the artifact instead.
+ *
+ * The format it parses is written by `renderFileSection`, and the parser is deliberately tied to
+ * that shape rather than to a regex over the whole document: a file's *content* may legitimately
+ * contain a line that looks like `### FILE: something`, and only fence tracking tells the two
+ * apart. Content fences are four or more backticks (`fenceForContent` never emits three), which
+ * is what makes "the next line equal to this exact fence" an unambiguous terminator.
+ */
+interface PartSection {
+    /** The path as rendered in the `### FILE:` heading. */
+    path: string;
+    /** The `<a id="…">` anchor from the line above the heading, when present. */
+    anchor: string | null;
+    /** The file body, without its fence. Redacted and possibly a bounded preview. */
+    body: string;
+    /** `full`, `preview` or `signatures`. */
+    inclusion: string | null;
+    includedLines: number | null;
+}
+/** Splits a part into one section per emitted file. */
+declare function parsePartSections(partText: string): PartSection[];
+/**
+ * Finds the section for one file.
+ *
+ * The **anchor** is the identifier, not the heading. `anchorForPath` hashes the real
+ * `relativePath`, so it is exact and injective; the heading is the display form, and for a path
+ * with a control character (escaped as `\uXXXX`) or one longer than 300 characters (capped from
+ * the middle) it is not the path at all. The old fallback for those cases was the content
+ * SHA-256, which the part no longer carries — and which could never disambiguate two files with
+ * the same content, the exact case that needs it.
+ *
+ * The heading comparison is kept as a second chance, for a snapshot written before the anchor
+ * was read, or a part whose anchor line was edited by hand.
+ */
+declare function findSection(sections: readonly PartSection[], relativePath: string): PartSection | null;
+interface Window {
+    text: string;
+    fromLine: number;
+    returnedLines: number;
+    totalLines: number;
+    truncated: boolean;
+    nextFromLine: number | null;
+    /**
+     * True when `fromLine` is beyond the last line of the body.
+     *
+     * The start used to be clamped to the last line, so asking for line 9,000 of a 40-line file
+     * returned line 40 with a header that read `Lines 40–40 of 40` — a wrong answer dressed as a
+     * right one. The caller is told the request was out of range instead.
+     */
+    pastEnd: boolean;
+}
+/**
+ * Cuts a line window out of a body.
+ *
+ * Windows are the whole point of this module: a part holds hundreds of kilobytes, and the only
+ * safe default for a tool that returns content is "as little as answers the question". `next` is
+ * an explicit pointer rather than an instruction to keep reading, so an agent decides.
+ */
+declare function windowText(body: string, fromLine: number, lineCount: number): Window;
+
 declare function buildPrompts(): McpPrompt[];
 
 declare function buildResourceProvider(): ResourceProvider;
@@ -409,4 +477,4 @@ declare function validateArguments(schema: InputSchema, value: unknown): string[
  */
 declare function coerceNumericStrings(schema: InputSchema, value: JsonObject): JsonObject;
 
-export { ERROR_CODES, type JsonRpcResponse, type JsonSchema, LEGACY_PROTOCOL_VERSIONS, type LineReaderOptions, MAX_LINE_BYTES, METHOD, MODERN_PROTOCOL_VERSIONS, type McpPrompt, type McpResourceContents, type McpResourceDescriptor, type McpResourceTemplate, type McpServer, type McpServerInfo, type McpServerOptions, type McpTool, type MessageWriter, type ProtocolEra, type ResourceProvider, SERVER_INSTRUCTIONS, SUPPORTED_PROTOCOL_VERSIONS, type ServerOptions, type SessionState, type ToolAnnotations, type ToolContext, type ToolOutcome, buildPrompts, buildResourceProvider, buildTools, classifyRequest, coerceNumericStrings, createLineReader, createMcpServer, createServer, createSession, createWriter, inspectModernMeta, negotiateLegacyVersion, runStdioServer, validateArguments };
+export { ERROR_CODES, type JsonRpcResponse, type JsonSchema, LEGACY_PROTOCOL_VERSIONS, type LineReaderOptions, MAX_LINE_BYTES, METHOD, MODERN_PROTOCOL_VERSIONS, type McpPrompt, type McpResourceContents, type McpResourceDescriptor, type McpResourceTemplate, type McpServer, type McpServerInfo, type McpServerOptions, type McpTool, type MessageWriter, type PartSection, type ProtocolEra, type ResourceProvider, SERVER_INSTRUCTIONS, SUPPORTED_PROTOCOL_VERSIONS, type ServerOptions, type SessionState, type ToolAnnotations, type ToolContext, type ToolOutcome, type Window, buildPrompts, buildResourceProvider, buildTools, classifyRequest, coerceNumericStrings, createLineReader, createMcpServer, createServer, createSession, createWriter, findSection, inspectModernMeta, negotiateLegacyVersion, parsePartSections, runStdioServer, validateArguments, windowText };

package/dist/mcp.js

@@ -1,4 +1,2 @@
-export { ERROR_CODES, LEGACY_PROTOCOL_VERSIONS, MAX_LINE_BYTES, METHOD, MODERN_PROTOCOL_VERSIONS, SERVER_INSTRUCTIONS, SUPPORTED_PROTOCOL_VERSIONS, buildPrompts, buildResourceProvider, buildTools, classifyRequest, coerceNumericStrings, createLineReader, createMcpServer, createServer, createSession, createWriter, inspectModernMeta, negotiateLegacyVersion, runStdioServer, validateArguments } from './chunk-HQBEQ67K.js';
-import './chunk-KUVFTJHK.js';
-//# sourceMappingURL=mcp.js.map
-//# sourceMappingURL=mcp.js.map
+export { ERROR_CODES, LEGACY_PROTOCOL_VERSIONS, MAX_LINE_BYTES, METHOD, MODERN_PROTOCOL_VERSIONS, SERVER_INSTRUCTIONS, SUPPORTED_PROTOCOL_VERSIONS, buildPrompts, buildResourceProvider, buildTools, classifyRequest, coerceNumericStrings, createLineReader, createMcpServer, createServer, createSession, createWriter, findSection, inspectModernMeta, negotiateLegacyVersion, parsePartSections, runStdioServer, validateArguments, windowText } from './chunk-J4W74N4Y.js';
+export { generateInWorker } from './chunk-DUZK5VL2.js';