context-loader 1.3.0__tar.gz → 1.3.2__tar.gz

{context_loader-1.3.0 → context_loader-1.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: context-loader
-Version: 1.3.0
+Version: 1.3.2
 Summary: Render deterministic local Git context for any executor
 License:                                  Apache License
                                     Version 2.0, January 2004
@@ -219,14 +219,14 @@ Python standard library.
 
 ## Open-source quick start
 
-Current stable release: **1.3.0**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
+Current stable release: **1.3.2**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
 
 ```bash
-uv tool install 'context-loader==1.3.0'
+uv tool install 'context-loader==1.3.2'
 ```
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.2'
 ```
 
 ```bash
@@ -239,21 +239,21 @@ project-context --repo /path/to/repo --format json
 
 ## Install
 
-Source version: `1.3.0`. Install its matching published release or an exact source commit.
+Source version: `1.3.2`. Install its matching published release or an exact source commit.
 
 Install via `uv`:
 
 ```bash
-uv tool install 'context-loader==1.3.0'
+uv tool install 'context-loader==1.3.2'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.2'
 ```
 
-For development or source-based installs tracking current repository (`1.3.0`):
+For development or source-based installs tracking current repository (`1.3.2`):
 
 ```bash
 uv tool install git+https://github.com/xuanheng-tech/context-loader.git
@@ -319,6 +319,8 @@ and bare repositories are rejected in every mode.
 `--focus` and `--path` are optional, bounded selection signals for the root `AGENTS.md`. `--path`
 must be repository-relative. The collector does not retain either input in output or audit data.
 Calls that omit both options remain valid and use the conservative fallback described below.
+Each value option (`--repo`, `--focus`, `--path`, `--format`) may be supplied once;
+duplicates are rejected before collection rather than silently overriding an earlier value.
 
 ## Markdown Output
 
@@ -338,16 +340,17 @@ The output has no generated timestamp, AI summary, architecture inference, or di
 ## JSON Output
 
 `--format json` writes exactly one separator-compact UTF-8 JSON document plus one trailing newline
-to stdout. Keys are serialized in sorted order with `ensure_ascii=False`. `--format json-compact`
-uses the identical serialization; only the field set differs, as described under “Compact model
-consumption”. The declared contract for `--format json` is:
+to stdout, within the JSON document bound under “Limits”. Keys are serialized in sorted order
+with `ensure_ascii=False`. `--format json-compact` uses the identical serialization; only the field
+set differs, as described under “Compact model consumption”. The declared contract for
+`--format json` is:
 
 ```json
 {
   "schema_version": 3,
   "tool": {
     "name": "context-loader",
-    "version": "1.3.0"
+    "version": "1.3.2"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -394,12 +397,12 @@ context, in assembly order, after the existing newline normalization and truncat
 distinguishes `repository` from `global`; version 1.0.0's fixed root-file selection currently emits
 only `repository` sources and does not add any global-file discovery.
 
-`statuses` lists machine-readable collection and render conditions that previously appeared only inside `context` Markdown — plus the nested-context truncation flags, which exist only in machine form: skipped or absent sources, truncated sources, unreadable directory-tree entries, sections omitted under the global output budget, truncated working-tree or declared-command listings, and truncated nested-`AGENTS.md` presence reports. Each entry has stable `code`, `subject_kind`, and `subject` fields. The two `nested_agents_*` codes mirror the `nested_context` truncation booleans for consumers that branch only on `statuses`; the full `nested_context` object remains a first-class field, never folded into `statuses`. Callers can ignore `statuses` safely.
+`statuses` lists machine-readable collection and render conditions that previously appeared only inside `context` Markdown — plus the nested-context truncation flags, which exist only in machine form: skipped or absent sources, truncated sources, unreadable directory-tree entries, directory-tree entries whose directory holds more entries than one enumeration examines, sections omitted under the global output budget, truncated working-tree, declared-command or directory-tree listings, and truncated nested-`AGENTS.md` presence reports. A skipped or absent source reports the code of the condition the collector observed (`not_present`, `skipped_symlink`, `skipped_not_regular`, `skipped_encoding`, `skipped_unreadable`); the sentence in `context` is rendered from that same condition, so wording and code cannot drift apart. Each entry has stable `code`, `subject_kind`, and `subject` fields. The two `nested_agents_*` codes mirror the `nested_context` truncation booleans for consumers that branch only on `statuses`; the full `nested_context` object remains a first-class field, never folded into `statuses`. Callers can ignore `statuses` safely.
 
 The optional `selection` object is present only on a rendered `AGENTS.md` source. Its section entries
 contain heading, heading level, and fixed selection reasons; it never contains the original focus or
 target path. Existing per-source fields remain unchanged; the document's exact key
-set (now including `nested_context`) is named by its `schema_version`, described below.
+set (which includes `nested_context`) is named by its `schema_version`, described below.
 
 `nested_context` is always present and existence-only: `files` lists repository-relative paths of
 non-directory `AGENTS.md` entries under subdirectories, found by a bounded scan that enumerates
@@ -408,11 +411,17 @@ no sizes, no mtimes and no contents. A symlinked (even dangling) `AGENTS.md` is
 existence comes from the directory entry itself; the scan never resolves what it points at. Any
 `.git`, `.venv`, `venv`, `node_modules` or `site-packages` directory is skipped at every depth:
 package-manager and interpreter-managed trees are not authored repository instructions.
-`list_truncated` means more matching entries exist beyond the report caps (32 paths and 4 KiB of
-path bytes); `scan_truncated` means the depth (4) or directory-count (2,000) budget was reached, or
-a directory or entry could not be read, so absence of a path is not proof of absence of the file.
-Paths are sanitized with the same escaping the Markdown uses for repository-derived text, so the
-document is always valid UTF-8. The corresponding
+`list_truncated` means more matching entries exist beyond the report caps: 32 paths, and a 4 KiB
+budget metered on the emitted array itself — each path's escaped, JSON-serialized string plus its
+separator, with the array's brackets charged to the first entry — so the emitted array never costs
+more than the budget it declares. Because quoting is counted, an array already near the cap can
+report one path fewer than an older release did, and then says so through `list_truncated`.
+`scan_truncated` means the depth (4) or directory-count (2,000) budget was reached, a directory
+held more entries than one enumeration examines (1,024), or a directory or entry could not be
+read, so absence of a path is not proof of absence of the file. Nested paths
+are sanitized with the same escaping the Markdown uses for repository-derived text, so a nested name
+the filesystem could not decode never breaks the document;
+see “Limits” for the root paths that are emitted verbatim. The corresponding
 `nested_agents_list_truncated` and `nested_agents_scan_truncated` status entries mirror both flags.
 Presence is not instruction: whether a nested file applies, and its text, remain the caller's
 judgment; Markdown output is unchanged.
@@ -441,10 +450,10 @@ not otherwise change default Markdown bytes, exit codes or determinism.
 
 One historical exception is acknowledged: releases 1.0.0 and 1.1.0 both emitted `schema_version` 1
 although 1.1.0 added the top-level `statuses` key. From release 1.2.0 onward each emitted number
-names exactly one key set, and the `nested_context` renumber below enforces that rule going forward.
+names exactly one key set, and a new number is issued whenever a key set would otherwise be reused.
 
 The JSON schema version and package version are independent: this build emits `schema_version` `3`
-for `--format json` and `4` for `--format json-compact`, while `tool.version` is `1.3.0`. Version 1
+for `--format json` and `4` for `--format json-compact`, while `tool.version` is `1.3.2`. Version 1
 and 2 are the exact shapes already published in release 1.2.0 and are never reused: because
 `nested_context` changes the default document's key set, version 3 names the current full-document
 key set and version 4 names the compact projection.
@@ -497,18 +506,69 @@ scan that ends before EOF still reports the characters it could not select.
 
 ## Limits
 
-- Final stdout: 98,304 bytes
+Final output bounds differ per format. The two stdout bounds below are enforced on the bytes written
+to stdout and the nested report cap on the bytes the document emits for that array; every other
+bullet is a per-component, read or capture bound, as each one states:
+
+- Markdown stdout: 98,304 bytes. A section that cannot fit is replaced by an omission notice, and so
+  is every later section, so the limit holds without cutting a section mid-body.
+- JSON and JSON-compact stdout: 8,388,608 bytes (8 MiB) for the serialized document, including its
+  trailing newline. This bound is fail-closed: if a repository's evidence cannot fit, the tool exits
+  1, writes nothing to stdout and prints `error: JSON output exceeded the 8388608 byte document
+  limit`. It never emits a truncated document. The component budgets below keep legitimate
+  documents far inside it — the largest escape-dense repository audited for this release emitted
+  263 KiB, of which 248 KiB was escaped `statuses` subjects — so it is a final backstop rather
+  than an expected truncation point.
+- Component budgets below are metered on the Markdown `context` content, and that same string is the
+  JSON `context` value; because JSON escaping expands quotes, backslashes and control characters,
+  the serialized bytes can be several times larger. The JSON document also repeats the source
+  bodies, so no single component figure bounds JSON stdout.
 - `AGENTS.md`: 256-KiB bounded source scan; selected source plus selection audit remains at most
   16 KiB, including a 4-KiB maximum small head
 - `README.md`: 16 KiB
 - Each entry file: 8 KiB
 - All entry-file bodies: 24 KiB
 - Declared commands: 8 KiB
-- Directory tree: 12 KiB, 300 entries, and depth 2
-- Nested `AGENTS.md` presence scan: depth 4, 2,000 directories, and at most 32 reported paths;
+- Directory tree: 12 KiB of listing body, 300 entries, and depth 2. Each directory is
+  enumerated up to 512 entries, keeping the alphabetically first names so the listing never
+  depends on operating system order. A directory that holds more is reported by a single
+  `Listing incomplete:` line stating the total, the limit and up to three names, and by at most
+  eight `directory_listing_incomplete` status entries naming individual directories plus one
+  aggregate entry giving the totals when more directories were capped than are named: beyond the
+  retained examples a capped directory is counted but not individually named, and no listing
+  claims completeness it does not have. That total covers the capped directories the listing
+  reached: a directory is reached only when its parent offered it inside the parent's own
+  alphabetical prefix and the entry budget kept it, so capped siblings displaced by the budget are
+  disclosed as their parent's truncation rather than as separate numbers.
+  Three limits act in sequence and a name survives only if all three leave room. The 512-entry
+  enumeration limit decides which names a directory offers at all; above it only an alphabetical
+  prefix is ever seen. The 300-entry item budget is then shared between a directory's
+  subdirectories and its non-directories: each may take up to half of what remains before the other
+  claims the surplus, which stops alphabetically-earlier directories from evicting every file, but
+  it is a share rather than a floor -- with a single slot left the non-directories take it. The 12
+  KiB listing budget then decides which kept names are rendered. Descent
+  happens after a directory's own entries, so deep content cannot displace top-level names, but
+  the tool promises no specific file: a root `README.md` is listed only when all three limits leave
+  room for it -- the enumeration offered it, the entry budget still has a slot, and the byte budget
+  still has room -- and each of those three can fail on its own. Being offered is not the same as
+  an uncapped root: the 512-entry cut drops only the names that sort after its retained prefix, so
+  an early-sorting `README.md` is still listed from a capped root while a late-sorting one never
+  reaches the listing. Whenever one of the three bites, the listing says so through the
+  note, the marker, or a `truncated` status instead of presenting itself as complete.
+  The `Listing incomplete:` line is charged to the 12 KiB listing budget before the body is cut,
+  so the claim can never inflate the section; its cost is paid in listing bytes, so a long note
+  removes that many bytes of entries, and the `truncated` status plus the marker inside the
+  fence say so. The heading and the code-fence lines are not metered, so the whole Markdown
+  section can exceed 12 KiB by that fixed few dozen bytes.
+- Nested `AGENTS.md` presence scan: depth 4, 2,000 directories, at most 32 reported paths, a
+  4 KiB budget metered on the emitted array, and at most 1,024 entries examined per directory;
   file contents are never read
 - Working-tree changes: 100 paths and 4 KiB
 - Recent commits: 8
+- JSON-only listings have no byte budget of their own: `statuses` subjects are escaped names bounded
+  by the entry counts above, while `repository` and `sources[*].path` are emitted verbatim, so a
+  repository root the filesystem could not decode makes the machine formats exit 1 where Markdown
+  still renders
 - Git subprocess output: 16 MiB (bounded while reading)
 - Candidate file validation: 16 MiB hard read bound
 
@@ -545,7 +605,7 @@ or candidate-file content.
 
 ## Not Included
 
-Version 1.3.0 does not provide AI summaries, project-type detection, loading or transport of
+Version 1.3.2 does not provide AI summaries, project-type detection, loading or transport of
 nested `AGENTS.md` contents (the JSON `nested_context` field reports bounded existence only),
 Memory retrieval, semantic ranking, ignore-rule parsing, plugins, profiles, caches, databases,
 network services, MCP, daemons, GUIs, CI/CD, telemetry, or automatic updates.
@@ -583,6 +643,7 @@ PyPI file bytes, metadata and SHA-256, plus the publisher/tag/commit claims in P
 provenance. This is an identity check, not an independent cryptographic Sigstore verifier.
 
 - Tag/version or expected-commit mismatch and `just check` failure stop before build/upload.
+- Annotated tag headers must match the exact tag name and commit, without extra or duplicate headers.
 - The build refuses to run unless `dist/` is empty, and refuses any produced file set other than
   the current version's wheel and sdist. A leftover artifact can carry a release filename while
   holding different bytes, so it is never treated as the current release.

{context_loader-1.3.0 → context_loader-1.3.2}/README.md

@@ -8,14 +8,14 @@ Python standard library.
 
 ## Open-source quick start
 
-Current stable release: **1.3.0**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
+Current stable release: **1.3.2**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
 
 ```bash
-uv tool install 'context-loader==1.3.0'
+uv tool install 'context-loader==1.3.2'
 ```
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.2'
 ```
 
 ```bash
@@ -28,21 +28,21 @@ project-context --repo /path/to/repo --format json
 
 ## Install
 
-Source version: `1.3.0`. Install its matching published release or an exact source commit.
+Source version: `1.3.2`. Install its matching published release or an exact source commit.
 
 Install via `uv`:
 
 ```bash
-uv tool install 'context-loader==1.3.0'
+uv tool install 'context-loader==1.3.2'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.2'
 ```
 
-For development or source-based installs tracking current repository (`1.3.0`):
+For development or source-based installs tracking current repository (`1.3.2`):
 
 ```bash
 uv tool install git+https://github.com/xuanheng-tech/context-loader.git
@@ -108,6 +108,8 @@ and bare repositories are rejected in every mode.
 `--focus` and `--path` are optional, bounded selection signals for the root `AGENTS.md`. `--path`
 must be repository-relative. The collector does not retain either input in output or audit data.
 Calls that omit both options remain valid and use the conservative fallback described below.
+Each value option (`--repo`, `--focus`, `--path`, `--format`) may be supplied once;
+duplicates are rejected before collection rather than silently overriding an earlier value.
 
 ## Markdown Output
 
@@ -127,16 +129,17 @@ The output has no generated timestamp, AI summary, architecture inference, or di
 ## JSON Output
 
 `--format json` writes exactly one separator-compact UTF-8 JSON document plus one trailing newline
-to stdout. Keys are serialized in sorted order with `ensure_ascii=False`. `--format json-compact`
-uses the identical serialization; only the field set differs, as described under “Compact model
-consumption”. The declared contract for `--format json` is:
+to stdout, within the JSON document bound under “Limits”. Keys are serialized in sorted order
+with `ensure_ascii=False`. `--format json-compact` uses the identical serialization; only the field
+set differs, as described under “Compact model consumption”. The declared contract for
+`--format json` is:
 
 ```json
 {
   "schema_version": 3,
   "tool": {
     "name": "context-loader",
-    "version": "1.3.0"
+    "version": "1.3.2"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -183,12 +186,12 @@ context, in assembly order, after the existing newline normalization and truncat
 distinguishes `repository` from `global`; version 1.0.0's fixed root-file selection currently emits
 only `repository` sources and does not add any global-file discovery.
 
-`statuses` lists machine-readable collection and render conditions that previously appeared only inside `context` Markdown — plus the nested-context truncation flags, which exist only in machine form: skipped or absent sources, truncated sources, unreadable directory-tree entries, sections omitted under the global output budget, truncated working-tree or declared-command listings, and truncated nested-`AGENTS.md` presence reports. Each entry has stable `code`, `subject_kind`, and `subject` fields. The two `nested_agents_*` codes mirror the `nested_context` truncation booleans for consumers that branch only on `statuses`; the full `nested_context` object remains a first-class field, never folded into `statuses`. Callers can ignore `statuses` safely.
+`statuses` lists machine-readable collection and render conditions that previously appeared only inside `context` Markdown — plus the nested-context truncation flags, which exist only in machine form: skipped or absent sources, truncated sources, unreadable directory-tree entries, directory-tree entries whose directory holds more entries than one enumeration examines, sections omitted under the global output budget, truncated working-tree, declared-command or directory-tree listings, and truncated nested-`AGENTS.md` presence reports. A skipped or absent source reports the code of the condition the collector observed (`not_present`, `skipped_symlink`, `skipped_not_regular`, `skipped_encoding`, `skipped_unreadable`); the sentence in `context` is rendered from that same condition, so wording and code cannot drift apart. Each entry has stable `code`, `subject_kind`, and `subject` fields. The two `nested_agents_*` codes mirror the `nested_context` truncation booleans for consumers that branch only on `statuses`; the full `nested_context` object remains a first-class field, never folded into `statuses`. Callers can ignore `statuses` safely.
 
 The optional `selection` object is present only on a rendered `AGENTS.md` source. Its section entries
 contain heading, heading level, and fixed selection reasons; it never contains the original focus or
 target path. Existing per-source fields remain unchanged; the document's exact key
-set (now including `nested_context`) is named by its `schema_version`, described below.
+set (which includes `nested_context`) is named by its `schema_version`, described below.
 
 `nested_context` is always present and existence-only: `files` lists repository-relative paths of
 non-directory `AGENTS.md` entries under subdirectories, found by a bounded scan that enumerates
@@ -197,11 +200,17 @@ no sizes, no mtimes and no contents. A symlinked (even dangling) `AGENTS.md` is
 existence comes from the directory entry itself; the scan never resolves what it points at. Any
 `.git`, `.venv`, `venv`, `node_modules` or `site-packages` directory is skipped at every depth:
 package-manager and interpreter-managed trees are not authored repository instructions.
-`list_truncated` means more matching entries exist beyond the report caps (32 paths and 4 KiB of
-path bytes); `scan_truncated` means the depth (4) or directory-count (2,000) budget was reached, or
-a directory or entry could not be read, so absence of a path is not proof of absence of the file.
-Paths are sanitized with the same escaping the Markdown uses for repository-derived text, so the
-document is always valid UTF-8. The corresponding
+`list_truncated` means more matching entries exist beyond the report caps: 32 paths, and a 4 KiB
+budget metered on the emitted array itself — each path's escaped, JSON-serialized string plus its
+separator, with the array's brackets charged to the first entry — so the emitted array never costs
+more than the budget it declares. Because quoting is counted, an array already near the cap can
+report one path fewer than an older release did, and then says so through `list_truncated`.
+`scan_truncated` means the depth (4) or directory-count (2,000) budget was reached, a directory
+held more entries than one enumeration examines (1,024), or a directory or entry could not be
+read, so absence of a path is not proof of absence of the file. Nested paths
+are sanitized with the same escaping the Markdown uses for repository-derived text, so a nested name
+the filesystem could not decode never breaks the document;
+see “Limits” for the root paths that are emitted verbatim. The corresponding
 `nested_agents_list_truncated` and `nested_agents_scan_truncated` status entries mirror both flags.
 Presence is not instruction: whether a nested file applies, and its text, remain the caller's
 judgment; Markdown output is unchanged.
@@ -230,10 +239,10 @@ not otherwise change default Markdown bytes, exit codes or determinism.
 
 One historical exception is acknowledged: releases 1.0.0 and 1.1.0 both emitted `schema_version` 1
 although 1.1.0 added the top-level `statuses` key. From release 1.2.0 onward each emitted number
-names exactly one key set, and the `nested_context` renumber below enforces that rule going forward.
+names exactly one key set, and a new number is issued whenever a key set would otherwise be reused.
 
 The JSON schema version and package version are independent: this build emits `schema_version` `3`
-for `--format json` and `4` for `--format json-compact`, while `tool.version` is `1.3.0`. Version 1
+for `--format json` and `4` for `--format json-compact`, while `tool.version` is `1.3.2`. Version 1
 and 2 are the exact shapes already published in release 1.2.0 and are never reused: because
 `nested_context` changes the default document's key set, version 3 names the current full-document
 key set and version 4 names the compact projection.
@@ -286,18 +295,69 @@ scan that ends before EOF still reports the characters it could not select.
 
 ## Limits
 
-- Final stdout: 98,304 bytes
+Final output bounds differ per format. The two stdout bounds below are enforced on the bytes written
+to stdout and the nested report cap on the bytes the document emits for that array; every other
+bullet is a per-component, read or capture bound, as each one states:
+
+- Markdown stdout: 98,304 bytes. A section that cannot fit is replaced by an omission notice, and so
+  is every later section, so the limit holds without cutting a section mid-body.
+- JSON and JSON-compact stdout: 8,388,608 bytes (8 MiB) for the serialized document, including its
+  trailing newline. This bound is fail-closed: if a repository's evidence cannot fit, the tool exits
+  1, writes nothing to stdout and prints `error: JSON output exceeded the 8388608 byte document
+  limit`. It never emits a truncated document. The component budgets below keep legitimate
+  documents far inside it — the largest escape-dense repository audited for this release emitted
+  263 KiB, of which 248 KiB was escaped `statuses` subjects — so it is a final backstop rather
+  than an expected truncation point.
+- Component budgets below are metered on the Markdown `context` content, and that same string is the
+  JSON `context` value; because JSON escaping expands quotes, backslashes and control characters,
+  the serialized bytes can be several times larger. The JSON document also repeats the source
+  bodies, so no single component figure bounds JSON stdout.
 - `AGENTS.md`: 256-KiB bounded source scan; selected source plus selection audit remains at most
   16 KiB, including a 4-KiB maximum small head
 - `README.md`: 16 KiB
 - Each entry file: 8 KiB
 - All entry-file bodies: 24 KiB
 - Declared commands: 8 KiB
-- Directory tree: 12 KiB, 300 entries, and depth 2
-- Nested `AGENTS.md` presence scan: depth 4, 2,000 directories, and at most 32 reported paths;
+- Directory tree: 12 KiB of listing body, 300 entries, and depth 2. Each directory is
+  enumerated up to 512 entries, keeping the alphabetically first names so the listing never
+  depends on operating system order. A directory that holds more is reported by a single
+  `Listing incomplete:` line stating the total, the limit and up to three names, and by at most
+  eight `directory_listing_incomplete` status entries naming individual directories plus one
+  aggregate entry giving the totals when more directories were capped than are named: beyond the
+  retained examples a capped directory is counted but not individually named, and no listing
+  claims completeness it does not have. That total covers the capped directories the listing
+  reached: a directory is reached only when its parent offered it inside the parent's own
+  alphabetical prefix and the entry budget kept it, so capped siblings displaced by the budget are
+  disclosed as their parent's truncation rather than as separate numbers.
+  Three limits act in sequence and a name survives only if all three leave room. The 512-entry
+  enumeration limit decides which names a directory offers at all; above it only an alphabetical
+  prefix is ever seen. The 300-entry item budget is then shared between a directory's
+  subdirectories and its non-directories: each may take up to half of what remains before the other
+  claims the surplus, which stops alphabetically-earlier directories from evicting every file, but
+  it is a share rather than a floor -- with a single slot left the non-directories take it. The 12
+  KiB listing budget then decides which kept names are rendered. Descent
+  happens after a directory's own entries, so deep content cannot displace top-level names, but
+  the tool promises no specific file: a root `README.md` is listed only when all three limits leave
+  room for it -- the enumeration offered it, the entry budget still has a slot, and the byte budget
+  still has room -- and each of those three can fail on its own. Being offered is not the same as
+  an uncapped root: the 512-entry cut drops only the names that sort after its retained prefix, so
+  an early-sorting `README.md` is still listed from a capped root while a late-sorting one never
+  reaches the listing. Whenever one of the three bites, the listing says so through the
+  note, the marker, or a `truncated` status instead of presenting itself as complete.
+  The `Listing incomplete:` line is charged to the 12 KiB listing budget before the body is cut,
+  so the claim can never inflate the section; its cost is paid in listing bytes, so a long note
+  removes that many bytes of entries, and the `truncated` status plus the marker inside the
+  fence say so. The heading and the code-fence lines are not metered, so the whole Markdown
+  section can exceed 12 KiB by that fixed few dozen bytes.
+- Nested `AGENTS.md` presence scan: depth 4, 2,000 directories, at most 32 reported paths, a
+  4 KiB budget metered on the emitted array, and at most 1,024 entries examined per directory;
   file contents are never read
 - Working-tree changes: 100 paths and 4 KiB
 - Recent commits: 8
+- JSON-only listings have no byte budget of their own: `statuses` subjects are escaped names bounded
+  by the entry counts above, while `repository` and `sources[*].path` are emitted verbatim, so a
+  repository root the filesystem could not decode makes the machine formats exit 1 where Markdown
+  still renders
 - Git subprocess output: 16 MiB (bounded while reading)
 - Candidate file validation: 16 MiB hard read bound
 
@@ -334,7 +394,7 @@ or candidate-file content.
 
 ## Not Included
 
-Version 1.3.0 does not provide AI summaries, project-type detection, loading or transport of
+Version 1.3.2 does not provide AI summaries, project-type detection, loading or transport of
 nested `AGENTS.md` contents (the JSON `nested_context` field reports bounded existence only),
 Memory retrieval, semantic ranking, ignore-rule parsing, plugins, profiles, caches, databases,
 network services, MCP, daemons, GUIs, CI/CD, telemetry, or automatic updates.
@@ -372,6 +432,7 @@ PyPI file bytes, metadata and SHA-256, plus the publisher/tag/commit claims in P
 provenance. This is an identity check, not an independent cryptographic Sigstore verifier.
 
 - Tag/version or expected-commit mismatch and `just check` failure stop before build/upload.
+- Annotated tag headers must match the exact tag name and commit, without extra or duplicate headers.
 - The build refuses to run unless `dist/` is empty, and refuses any produced file set other than
   the current version's wheel and sdist. A leftover artifact can carry a release filename while
   holding different bytes, so it is never treated as the current release.

{context_loader-1.3.0 → context_loader-1.3.2}/context_loader/__init__.py

@@ -1,3 +1,3 @@
 """Project Context Loader."""
 
-__version__ = "1.3.0"
+__version__ = "1.3.2"