codebase-snapshot 0.9.0 → 4.5.0

package/CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to `codebase-snapshot`.
 
 ---
 
-## 0.9.0
+## 4.5.0
 
 ### The package is now `codebase-snapshot`, unscoped
 
@@ -14,13 +14,13 @@ The old name is **deprecated, not unpublished**, so existing instructions keep w
 
 ```bash
 npx @ankurhalder/codebase-snapshot generate   # still resolves, now prints a deprecation notice
-npx codebase-snapshot generate                # the supported name from 0.9.0
+npx codebase-snapshot generate                # the supported name from 4.5.0
 ```
 
 Why: npm's search index ranks on text match rather than downloads — a package with a few thousand
 weekly downloads outranks one with a hundred million when the query matches its name better — so a
 name that *is* the phrase people search is the strongest free signal available. Doing this at
-version 0.9.0 with no dependents costs one migration; doing it after documentation, articles and
+version 4.5.0 with no dependents costs one migration; doing it after documentation, articles and
 tutorials all point at the scoped name costs far more.
 
 The rename is not cosmetic. The package name is written into every ownership marker and every

package/README.md

@@ -50,7 +50,7 @@ npx codebase-snapshot generate      # no install, one-off
 npm install -D codebase-snapshot    # or add it to a project
 ```
 
-This is a **0.x** release. Version numbers follow semver's 0.x conventions, so the CLI surface may change in a minor release until 1.0.0 — pin an exact version if you need a fixed surface today.`n`nAny npm-compatible client works — npm, yarn (classic and Berry with strict PnP), pnpm and bun —
+Any npm-compatible client works — npm, yarn (classic and Berry with strict PnP), pnpm and bun —
 each verified against the packed tarball before release. Requires **Node.js 18+**.
 
 Published from GitHub Actions with [build provenance](https://docs.npmjs.com/generating-provenance-statements): npm shows the tarball was built from this repository at a tagged commit, and `npm audit signatures` verifies it.

package/dist/bin.js

@@ -4294,7 +4294,7 @@ function gitignorePath(cwd, filePath) {
 
 // src/version.ts
 var GENERATOR_NAME = "codebase-snapshot";
-var GENERATOR_VERSION = "0.9.0";
+var GENERATOR_VERSION = "4.5.0";
 var LEGACY_GENERATOR_NAMES = ["@ankurhalder/codebase-snapshot"];
 function isOurGeneratorName(name) {
   if (typeof name !== "string") return false;
@@ -8136,7 +8136,7 @@ function buildAgentContract() {
       bins: ["codebase-snapshot", "snap"],
       notes: [
         `The bare package name also works: npx ${PACKAGE_NAME} <command>.`,
-        "Pin an exact version \u2014 for example `codebase-snapshot@0.9.0` \u2014 when you need the same build on every machine. A major range is not enough before 1.0: npm's caret on a 0.x version pins the minor, and 0.x minors are breaking by convention.",
+        "Pin @latest (or @4) when you need the exact same version on every machine.",
         "Both bin names point at the same file. npm resolves a package by its bin entries, so they must stay aliases of one executable.",
         "Human progress goes to stderr. With --format json the payload on stdout is pure JSON.",
         "A failing run also writes pure JSON to stdout: { error: { message, exitCode } }. The exit code and the stderr line are unchanged."
@@ -8151,7 +8151,7 @@ function buildAgentContract() {
         // floating tag may print 4.0.7 today and 4.0.9 next week, and an agent
         // must not conclude that a working tool is broken because of a patch.
         expect: `prints v${MAJOR_VERSION} or newer on stdout and exits 0 (this build is v${GENERATOR_VERSION}: compare the major version, not the patch)`,
-        notes: `If it prints an older major than this contract's, the @latest tag is behind the release: pin the exact version with \`npx ${PACKAGE_NAME}@${GENERATOR_VERSION} --version\` instead of retrying @latest. If it prints nothing, clear the npm cache and retry, or use \`npx -p <pkg> codebase-snapshot\`.`
+        notes: `If it prints an older major than this contract's, the @latest tag is behind the release: pin the major with \`npx ${PACKAGE_NAME}@${MAJOR_VERSION} --version\` instead of retrying @latest. If it prints nothing, clear the npm cache and retry, or use \`npx -p <pkg> codebase-snapshot\`.`
       },
       {
         step: 2,
@@ -8551,7 +8551,7 @@ another model, and reading files one by one would not fit in context.
 This tool is a Node CLI. It needs **Node.js 18 or newer**. You do not need to install it
 globally, and you do not need to clone anything.
 
-**Pin a version** \u2014 \`npx ${PACKAGE_NAME2}@${GENERATOR_VERSION} <command>\` \u2014 when you
+**Pin a version** \u2014 \`npx ${PACKAGE_NAME2}@${MAJOR_VERSION2} <command>\` (or an exact release) \u2014 when you
 need the same version on every machine. The bare package name works too: this package ships
 one executable file, published under two names (\`codebase-snapshot\` and \`snap\`), which is what
 lets npm pick it. If a command exits 0 printing nothing,
@@ -8562,8 +8562,8 @@ is broken.
 
 1. **Verify the tool.** Run \`npx ${PACKAGE_NAME2}@latest --version\`. Expect \`v${MAJOR_VERSION2}\` or
    newer on stdout \u2014 compare the major version, not the patch, because the
-   \`@latest\` tag can lag this release. If what it prints is older, pin the exact
-   release (\`@${GENERATOR_VERSION}\`) instead of retrying. Empty output means you hit the
+   \`@latest\` tag can lag this release. If the printed major is older, pin the
+   major (\`@${MAJOR_VERSION2}\`) instead of retrying. Empty output means you hit the
    bare-spec problem above.
 
 2. **Read the contract, not the prose.** Run

package/dist/{chunk-FJ4RQYY2.js → chunk-SSCFLILW.js}

@@ -5421,7 +5421,7 @@ function validateSnapshot(configInput) {
 
 // src/version.ts
 var GENERATOR_NAME = "codebase-snapshot";
-var GENERATOR_VERSION = "0.9.0";
+var GENERATOR_VERSION = "4.5.0";
 var LEGACY_GENERATOR_NAMES = ["@ankurhalder/codebase-snapshot"];
 function isOurGeneratorName(name) {
   if (typeof name !== "string") return false;
@@ -7881,5 +7881,5 @@ async function generateSnapshotAsync(configInput, options) {
 }
 
 export { ARTIFACT_NAMES, DEFAULT_ANSWERS, DEFAULT_SECRET_PATTERNS, GENERATOR_NAME, GENERATOR_VERSION, LANGUAGE_PROFILES, MIN_MAX_PART_BYTES, PRESETS, PromptCancelled, SCHEMA_VERSION, anchorForPath, appendGitignoreEntries, assertReplaceable, assertUsableConfigInput, collectFiles, compareManifests, countInvalidUtf8Bytes, countLines, decodeText, defineConfig, describeManifestShapeProblem, detectLanguage, detectPreset, escapeControls, explainPath, fenceForContent, fenceForText, formatNumber, generateProjectTree, generateSnapshot, generateSnapshotAsync, getPreset, gitignorePath, globToRegExp, isBinaryBuffer, isBinaryExtension, isBinaryFile, isDiscoveryMode, isInteractive, isResolvedConfig, isSensitivePath, listPresetNames, loadConfigFile, loadConfigFileDetailed, loadManifest, markResolvedConfig, matchRule, matchesExclude, normalizeResolvedConfig, parseByteSize, partitionFiles, profileForPath, renderConfig, renderDiffText, renderExplainText, renumberParts, resolveConfig, resolveSafeOutputDirs, runInit, scanAndRedactSecrets, stripJsonComments, summarizeJson, summarizeMarkdown, summarizeTypeScriptSource, summarizeWithProfile, supportsTypeScriptImports, truncatePreview, truncateToBytes, unknownPresetMessage, validateSnapshot };
-//# sourceMappingURL=chunk-FJ4RQYY2.js.map
-//# sourceMappingURL=chunk-FJ4RQYY2.js.map
+//# sourceMappingURL=chunk-SSCFLILW.js.map
+//# sourceMappingURL=chunk-SSCFLILW.js.map

package/dist/cli.cjs

@@ -4286,7 +4286,7 @@ function gitignorePath(cwd, filePath) {
 
 // src/version.ts
 var GENERATOR_NAME = "codebase-snapshot";
-var GENERATOR_VERSION = "0.9.0";
+var GENERATOR_VERSION = "4.5.0";
 var LEGACY_GENERATOR_NAMES = ["@ankurhalder/codebase-snapshot"];
 function isOurGeneratorName(name) {
   if (typeof name !== "string") return false;
@@ -8107,7 +8107,7 @@ function buildAgentContract() {
       bins: ["codebase-snapshot", "snap"],
       notes: [
         `The bare package name also works: npx ${PACKAGE_NAME} <command>.`,
-        "Pin an exact version \u2014 for example `codebase-snapshot@0.9.0` \u2014 when you need the same build on every machine. A major range is not enough before 1.0: npm's caret on a 0.x version pins the minor, and 0.x minors are breaking by convention.",
+        "Pin @latest (or @4) when you need the exact same version on every machine.",
         "Both bin names point at the same file. npm resolves a package by its bin entries, so they must stay aliases of one executable.",
         "Human progress goes to stderr. With --format json the payload on stdout is pure JSON.",
         "A failing run also writes pure JSON to stdout: { error: { message, exitCode } }. The exit code and the stderr line are unchanged."
@@ -8122,7 +8122,7 @@ function buildAgentContract() {
         // floating tag may print 4.0.7 today and 4.0.9 next week, and an agent
         // must not conclude that a working tool is broken because of a patch.
         expect: `prints v${MAJOR_VERSION} or newer on stdout and exits 0 (this build is v${GENERATOR_VERSION}: compare the major version, not the patch)`,
-        notes: `If it prints an older major than this contract's, the @latest tag is behind the release: pin the exact version with \`npx ${PACKAGE_NAME}@${GENERATOR_VERSION} --version\` instead of retrying @latest. If it prints nothing, clear the npm cache and retry, or use \`npx -p <pkg> codebase-snapshot\`.`
+        notes: `If it prints an older major than this contract's, the @latest tag is behind the release: pin the major with \`npx ${PACKAGE_NAME}@${MAJOR_VERSION} --version\` instead of retrying @latest. If it prints nothing, clear the npm cache and retry, or use \`npx -p <pkg> codebase-snapshot\`.`
       },
       {
         step: 2,
@@ -8518,7 +8518,7 @@ another model, and reading files one by one would not fit in context.
 This tool is a Node CLI. It needs **Node.js 18 or newer**. You do not need to install it
 globally, and you do not need to clone anything.
 
-**Pin a version** \u2014 \`npx ${PACKAGE_NAME2}@${GENERATOR_VERSION} <command>\` \u2014 when you
+**Pin a version** \u2014 \`npx ${PACKAGE_NAME2}@${MAJOR_VERSION2} <command>\` (or an exact release) \u2014 when you
 need the same version on every machine. The bare package name works too: this package ships
 one executable file, published under two names (\`codebase-snapshot\` and \`snap\`), which is what
 lets npm pick it. If a command exits 0 printing nothing,
@@ -8529,8 +8529,8 @@ is broken.
 
 1. **Verify the tool.** Run \`npx ${PACKAGE_NAME2}@latest --version\`. Expect \`v${MAJOR_VERSION2}\` or
    newer on stdout \u2014 compare the major version, not the patch, because the
-   \`@latest\` tag can lag this release. If what it prints is older, pin the exact
-   release (\`@${GENERATOR_VERSION}\`) instead of retrying. Empty output means you hit the
+   \`@latest\` tag can lag this release. If the printed major is older, pin the
+   major (\`@${MAJOR_VERSION2}\`) instead of retrying. Empty output means you hit the
    bare-spec problem above.
 
 2. **Read the contract, not the prose.** Run

package/dist/cli.js

@@ -1,4 +1,4 @@
-import { GENERATOR_VERSION, loadConfigFileDetailed, resolveConfig, validateSnapshot, describeManifestShapeProblem, explainPath, compareManifests, loadManifest, renderDiffText, generateSnapshot, formatNumber, isDiscoveryMode, ARTIFACT_NAMES, getPreset, unknownPresetMessage, GENERATOR_NAME, runInit, PromptCancelled, MIN_MAX_PART_BYTES, SCHEMA_VERSION, PRESETS, parseByteSize, gitignorePath, appendGitignoreEntries, escapeControls, renderExplainText } from './chunk-FJ4RQYY2.js';
+import { GENERATOR_VERSION, loadConfigFileDetailed, resolveConfig, validateSnapshot, describeManifestShapeProblem, explainPath, compareManifests, loadManifest, renderDiffText, generateSnapshot, formatNumber, isDiscoveryMode, ARTIFACT_NAMES, getPreset, unknownPresetMessage, GENERATOR_NAME, runInit, PromptCancelled, MIN_MAX_PART_BYTES, SCHEMA_VERSION, PRESETS, parseByteSize, gitignorePath, appendGitignoreEntries, escapeControls, renderExplainText } from './chunk-SSCFLILW.js';
 import { spawnSync } from 'child_process';
 import * as fs from 'fs';
 import * as path2 from 'path';
@@ -228,7 +228,7 @@ function buildAgentContract() {
       bins: ["codebase-snapshot", "snap"],
       notes: [
         `The bare package name also works: npx ${PACKAGE_NAME} <command>.`,
-        "Pin an exact version \u2014 for example `codebase-snapshot@0.9.0` \u2014 when you need the same build on every machine. A major range is not enough before 1.0: npm's caret on a 0.x version pins the minor, and 0.x minors are breaking by convention.",
+        "Pin @latest (or @4) when you need the exact same version on every machine.",
         "Both bin names point at the same file. npm resolves a package by its bin entries, so they must stay aliases of one executable.",
         "Human progress goes to stderr. With --format json the payload on stdout is pure JSON.",
         "A failing run also writes pure JSON to stdout: { error: { message, exitCode } }. The exit code and the stderr line are unchanged."
@@ -243,7 +243,7 @@ function buildAgentContract() {
         // floating tag may print 4.0.7 today and 4.0.9 next week, and an agent
         // must not conclude that a working tool is broken because of a patch.
         expect: `prints v${MAJOR_VERSION} or newer on stdout and exits 0 (this build is v${GENERATOR_VERSION}: compare the major version, not the patch)`,
-        notes: `If it prints an older major than this contract's, the @latest tag is behind the release: pin the exact version with \`npx ${PACKAGE_NAME}@${GENERATOR_VERSION} --version\` instead of retrying @latest. If it prints nothing, clear the npm cache and retry, or use \`npx -p <pkg> codebase-snapshot\`.`
+        notes: `If it prints an older major than this contract's, the @latest tag is behind the release: pin the major with \`npx ${PACKAGE_NAME}@${MAJOR_VERSION} --version\` instead of retrying @latest. If it prints nothing, clear the npm cache and retry, or use \`npx -p <pkg> codebase-snapshot\`.`
       },
       {
         step: 2,
@@ -639,7 +639,7 @@ another model, and reading files one by one would not fit in context.
 This tool is a Node CLI. It needs **Node.js 18 or newer**. You do not need to install it
 globally, and you do not need to clone anything.
 
-**Pin a version** \u2014 \`npx ${PACKAGE_NAME2}@${GENERATOR_VERSION} <command>\` \u2014 when you
+**Pin a version** \u2014 \`npx ${PACKAGE_NAME2}@${MAJOR_VERSION2} <command>\` (or an exact release) \u2014 when you
 need the same version on every machine. The bare package name works too: this package ships
 one executable file, published under two names (\`codebase-snapshot\` and \`snap\`), which is what
 lets npm pick it. If a command exits 0 printing nothing,
@@ -650,8 +650,8 @@ is broken.
 
 1. **Verify the tool.** Run \`npx ${PACKAGE_NAME2}@latest --version\`. Expect \`v${MAJOR_VERSION2}\` or
    newer on stdout \u2014 compare the major version, not the patch, because the
-   \`@latest\` tag can lag this release. If what it prints is older, pin the exact
-   release (\`@${GENERATOR_VERSION}\`) instead of retrying. Empty output means you hit the
+   \`@latest\` tag can lag this release. If the printed major is older, pin the
+   major (\`@${MAJOR_VERSION2}\`) instead of retrying. Empty output means you hit the
    bare-spec problem above.
 
 2. **Read the contract, not the prose.** Run

package/dist/index.cjs

@@ -5450,7 +5450,7 @@ function validateSnapshot(configInput) {
 
 // src/version.ts
 var GENERATOR_NAME = "codebase-snapshot";
-var GENERATOR_VERSION = "0.9.0";
+var GENERATOR_VERSION = "4.5.0";
 var LEGACY_GENERATOR_NAMES = ["@ankurhalder/codebase-snapshot"];
 function isOurGeneratorName(name) {
   if (typeof name !== "string") return false;

package/dist/index.d.cts

@@ -398,7 +398,7 @@ declare function validateSnapshot(configInput: ResolvedSnapshotConfig | Snapshot
  * `package.json` carries the same version; `npm run verify` compares the two.
  */
 declare const GENERATOR_NAME = "codebase-snapshot";
-declare const GENERATOR_VERSION = "0.9.0";
+declare const GENERATOR_VERSION = "4.5.0";
 
 declare const DEFAULT_SECRET_PATTERNS: SecretRule[];
 

package/dist/index.d.ts

@@ -398,7 +398,7 @@ declare function validateSnapshot(configInput: ResolvedSnapshotConfig | Snapshot
  * `package.json` carries the same version; `npm run verify` compares the two.
  */
 declare const GENERATOR_NAME = "codebase-snapshot";
-declare const GENERATOR_VERSION = "0.9.0";
+declare const GENERATOR_VERSION = "4.5.0";
 
 declare const DEFAULT_SECRET_PATTERNS: SecretRule[];
 

package/dist/index.js

@@ -1,3 +1,3 @@
-export { ARTIFACT_NAMES, DEFAULT_ANSWERS, DEFAULT_SECRET_PATTERNS, GENERATOR_NAME, GENERATOR_VERSION, LANGUAGE_PROFILES, MIN_MAX_PART_BYTES, PRESETS, PromptCancelled, SCHEMA_VERSION, anchorForPath, assertReplaceable, assertUsableConfigInput, collectFiles, compareManifests, countInvalidUtf8Bytes, countLines, decodeText, defineConfig, detectLanguage, detectPreset, explainPath, fenceForContent, fenceForText, generateProjectTree, generateSnapshot, generateSnapshotAsync, getPreset, globToRegExp, isBinaryBuffer, isBinaryExtension, isBinaryFile, isInteractive, isResolvedConfig, isSensitivePath, listPresetNames, loadConfigFile, loadConfigFileDetailed, loadManifest, markResolvedConfig, matchRule, matchesExclude, normalizeResolvedConfig, parseByteSize, partitionFiles, profileForPath, renderConfig, renderDiffText, renderExplainText, renumberParts, resolveConfig, resolveSafeOutputDirs, runInit, scanAndRedactSecrets, stripJsonComments, summarizeJson, summarizeMarkdown, summarizeTypeScriptSource, summarizeWithProfile, supportsTypeScriptImports, truncatePreview, truncateToBytes, validateSnapshot } from './chunk-FJ4RQYY2.js';
+export { ARTIFACT_NAMES, DEFAULT_ANSWERS, DEFAULT_SECRET_PATTERNS, GENERATOR_NAME, GENERATOR_VERSION, LANGUAGE_PROFILES, MIN_MAX_PART_BYTES, PRESETS, PromptCancelled, SCHEMA_VERSION, anchorForPath, assertReplaceable, assertUsableConfigInput, collectFiles, compareManifests, countInvalidUtf8Bytes, countLines, decodeText, defineConfig, detectLanguage, detectPreset, explainPath, fenceForContent, fenceForText, generateProjectTree, generateSnapshot, generateSnapshotAsync, getPreset, globToRegExp, isBinaryBuffer, isBinaryExtension, isBinaryFile, isInteractive, isResolvedConfig, isSensitivePath, listPresetNames, loadConfigFile, loadConfigFileDetailed, loadManifest, markResolvedConfig, matchRule, matchesExclude, normalizeResolvedConfig, parseByteSize, partitionFiles, profileForPath, renderConfig, renderDiffText, renderExplainText, renumberParts, resolveConfig, resolveSafeOutputDirs, runInit, scanAndRedactSecrets, stripJsonComments, summarizeJson, summarizeMarkdown, summarizeTypeScriptSource, summarizeWithProfile, supportsTypeScriptImports, truncatePreview, truncateToBytes, validateSnapshot } from './chunk-SSCFLILW.js';
 //# sourceMappingURL=index.js.map
 //# sourceMappingURL=index.js.map

package/docs/agent.md

@@ -19,7 +19,7 @@ npx codebase-snapshot generate
 npx codebase-snapshot validate
 ```
 
-The bare package name works; pin an exact version (`npx codebase-snapshot --version` prints the current one) when the same version must run on every
+The bare package name works; pin `@latest` or `@4` when the same version must run on every
 machine.
 
 ## The contract

package/docs/install.md

@@ -28,7 +28,7 @@ Pin the version when you need the same build on every machine:
 
 ```bash
 npx codebase-snapshot@latest generate
-npx codebase-snapshot@0.9.0 generate
+npx codebase-snapshot@4 generate
 ```
 
 **Why the bare name works.** npm resolves which binary to run from the package's `bin`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codebase-snapshot",
-  "version": "0.9.0",
+  "version": "4.5.0",
   "description": "Turn a codebase into token-efficient, size-budgeted Markdown parts for an LLM: an AST partitioner, snapshot generator, secret auditor and drift validator for ChatGPT, Claude and Cursor.",
   "keywords": [
     "codebase",