context-loader 1.3.1__tar.gz → 1.3.3__tar.gz

{context_loader-1.3.1 → context_loader-1.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: context-loader
-Version: 1.3.1
+Version: 1.3.3
 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.1**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
+Current stable release: **1.3.3**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
 
 ```bash
-uv tool install 'context-loader==1.3.1'
+uv tool install 'context-loader==1.3.3'
 ```
 
 ```bash
-pip install 'context-loader==1.3.1'
+pip install 'context-loader==1.3.3'
 ```
 
 ```bash
@@ -239,21 +239,21 @@ project-context --repo /path/to/repo --format json
 
 ## Install
 
-Source version: `1.3.1`. Install its matching published release or an exact source commit.
+Source version: `1.3.3`. Install its matching published release or an exact source commit.
 
 Install via `uv`:
 
 ```bash
-uv tool install 'context-loader==1.3.1'
+uv tool install 'context-loader==1.3.3'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.1'
+pip install 'context-loader==1.3.3'
 ```
 
-For development or source-based installs tracking current repository (`1.3.1`):
+For development or source-based installs tracking current repository (`1.3.3`):
 
 ```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
 
@@ -348,7 +350,7 @@ set differs, as described under “Compact model consumption”. The declared co
   "schema_version": 3,
   "tool": {
     "name": "context-loader",
-    "version": "1.3.1"
+    "version": "1.3.3"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -395,12 +397,19 @@ 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 skipped or absent sources, truncated sources, unreadable tree entries,
+directories whose listing exceeds its retention cap, globally omitted sections, and truncated
+working-tree, command, tree or nested-`AGENTS.md` listings. A skipped or absent source reports
+the observed condition (`not_present`, `skipped_symlink`, `skipped_not_regular`,
+`skipped_encoding`, `skipped_unreadable`); its sentence in `context` comes from that same
+condition. Each entry has stable `code`, `subject_kind`, and `subject` fields. The two
+`nested_agents_*` codes mirror the `nested_context` truncation booleans; the complete object
+remains a separate field. 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
@@ -414,8 +423,9 @@ budget metered on the emitted array itself — each path's escaped, JSON-seriali
 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, or a directory
-or entry could not be read, so absence of a path is not proof of absence of the file. Nested paths
+`scan_truncated` means the depth (4) or directory-count (2,000) budget was reached, a directory
+held more entries than one listing retains (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
@@ -423,6 +433,16 @@ see “Limits” for the root paths that are emitted verbatim. The corresponding
 Presence is not instruction: whether a nested file applies, and its text, remain the caller's
 judgment; Markdown output is unchanged.
 
+Escaped names remain reversible and distinct: a literal backslash becomes `\\`, a backtick
+becomes `\x60`, ASCII controls and undecodable filesystem bytes become `\xNN`, and other
+non-printable Unicode characters become `\uNNNN` or `\UNNNNNNNN`. Printable Unicode stays
+unchanged. After JSON decoding, recover POSIX path bytes by reading escapes from left to right:
+`\\` yields one backslash byte, `\xNN` yields that byte, and Unicode escapes and ordinary
+characters yield their UTF-8 bytes. Thus a backtick, a literal `\x60`, an undecodable byte
+`0x80`, and Unicode `U+0080` all have different representations. This applies to nested paths
+and displayed tree/change/status names; the verbatim root/source paths retain their existing
+semantics.
+
 ### Compact model consumption (`--format json-compact`)
 
 `--format json-compact` emits a `schema_version` 4 document: exactly the version-3 document with
@@ -447,10 +467,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.1`. Version 1
+for `--format json` and `4` for `--format json-compact`, while `tool.version` is `1.3.3`. 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.
@@ -524,11 +544,51 @@ bullet is a per-component, read or capture bound, as each one states:
   16 KiB, including a 4-KiB maximum small head
 - `README.md`: 16 KiB
 - Each entry file: 8 KiB
-- All entry-file bodies: 24 KiB
+- All entry-file bodies: 24 KiB, including truncation markers. Room is reserved for markers
+  on later text sources, so exhausting the budget never hides that their bodies were cut.
 - Declared commands: 8 KiB
-- Directory tree: 12 KiB, 300 entries, and depth 2
-- Nested `AGENTS.md` presence scan: depth 4, 2,000 directories, at most 32 reported paths and
-  a 4 KiB budget metered on the emitted array; file contents are never read
+- Directory tree: 12 KiB of listing body, 300 entries, and depth 2. Each directory is
+  retains and classifies 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
+  retention limit decides which names a directory offers at all; above it only an alphabetical
+  prefix is classified. All names must still be scanned to find that prefix, subject to the
+  separate hard name-scan bound below; the retention cap bounds memory and classification work.
+  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 retained and classified
+  per directory. Names are scanned to select that prefix, subject to the separate hard
+  name-scan bound below; file contents are never read
+- Directory name scans stop on the first entry beyond 65,536 names per directory. An
+  over-limit directory's entire partial prefix is discarded to keep results independent of
+  operating system order. The tree emits `Skipped: directory name scan limit reached.` and
+  a `directory_scan_limit_exceeded` status; the nested presence scan sets `scan_truncated`.
+  This bounds name iteration, not elapsed time on a blocked filesystem call.
 - 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
@@ -536,6 +596,7 @@ bullet is a per-component, read or capture bound, as each one states:
   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)
+- Git status preflight: at most 128 repositories, including initialized nested submodules
 - Candidate file validation: 16 MiB hard read bound
 
 Truncation occurs only at complete UTF-8 and line boundaries and is marked explicitly.
@@ -559,6 +620,13 @@ the remote.
   this is normal after cloning an empty remote.
 - `Ahead / behind: not available` means the commit relationship cannot currently be computed.
   Counts are reported only when the configured upstream commit is available locally.
+- Executable Git clean/process filters can run during `status`, even with optional locks
+  disabled. Before reading status, the loader checks effective repository configuration,
+  including includes, worktree configuration and initialized nested submodules. A non-empty
+  clean/process command causes a safe error with no stdout, even if no current attribute uses
+  it. Disabling a driver silently would change cleanliness semantics. Filter-dependent repositories
+  (including locally configured Git LFS drivers) therefore need ordinary Git inspection outside
+  this loader. Git protocols are also disabled to prevent lazy object retrieval.
 
 ## Exit Codes
 
@@ -571,7 +639,7 @@ or candidate-file content.
 
 ## Not Included
 
-Version 1.3.1 does not provide AI summaries, project-type detection, loading or transport of
+Version 1.3.3 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.
@@ -584,6 +652,17 @@ Run the complete local check:
 just check
 ```
 
+The lockfile uses public PyPI artifact URLs; no organization mirror or local Renovate preset
+is needed. Renovate keeps scheduled, rate-limited updates and manual merges using a public
+recommended preset plus the repository's explicit settings. Python 3.12 remains the tested
+runtime; widening that range requires testing those interpreters first.
+
+Git test fixtures discard inherited `GIT_*` routing/configuration before creating repositories.
+Permission-sensitive tests must run as a non-root user. Gitea uses `just ci-check`: non-root
+runners execute directly; root containers use `runuser` with an existing account named by
+`CONTEXT_LOADER_CI_USER` (default `ubuntu`). That account must be able to execute the installed
+`uv`, Python and `just`. No `sudo` dependency is required for this CI step.
+
 ## Version maintenance
 
 The versions in `pyproject.toml` and `context_loader/__init__.py`, the `tool_version` in
@@ -604,11 +683,17 @@ only verifies the public release, mirrors its exact formal tag object if missing
 the Gitea Release record. It builds no package and has no PyPI publishing credentials.
 No private endpoint or credential is needed on GitHub.
 
+For environments that permit direct public reads but share an exhausted proxy quota,
+set the Gitea Actions repository variable `RELEASE_PUBLIC_API_DIRECT=true`. The record
+step appends only public GitHub API/PyPI hosts to the existing proxy bypass lists. Without
+this explicit option, the workflow uses its inherited proxy settings.
+
 Release checks use Python 3.12, Git, and the runner's existing OpenSSL CLI. They compare downloaded
 PyPI file bytes, metadata and SHA-256, plus the publisher/tag/commit claims in PyPI's HTTPS-served
 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.1 → context_loader-1.3.3}/README.md

@@ -8,14 +8,14 @@ Python standard library.
 
 ## Open-source quick start
 
-Current stable release: **1.3.1**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
+Current stable release: **1.3.3**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
 
 ```bash
-uv tool install 'context-loader==1.3.1'
+uv tool install 'context-loader==1.3.3'
 ```
 
 ```bash
-pip install 'context-loader==1.3.1'
+pip install 'context-loader==1.3.3'
 ```
 
 ```bash
@@ -28,21 +28,21 @@ project-context --repo /path/to/repo --format json
 
 ## Install
 
-Source version: `1.3.1`. Install its matching published release or an exact source commit.
+Source version: `1.3.3`. Install its matching published release or an exact source commit.
 
 Install via `uv`:
 
 ```bash
-uv tool install 'context-loader==1.3.1'
+uv tool install 'context-loader==1.3.3'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.1'
+pip install 'context-loader==1.3.3'
 ```
 
-For development or source-based installs tracking current repository (`1.3.1`):
+For development or source-based installs tracking current repository (`1.3.3`):
 
 ```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
 
@@ -137,7 +139,7 @@ set differs, as described under “Compact model consumption”. The declared co
   "schema_version": 3,
   "tool": {
     "name": "context-loader",
-    "version": "1.3.1"
+    "version": "1.3.3"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -184,12 +186,19 @@ 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 skipped or absent sources, truncated sources, unreadable tree entries,
+directories whose listing exceeds its retention cap, globally omitted sections, and truncated
+working-tree, command, tree or nested-`AGENTS.md` listings. A skipped or absent source reports
+the observed condition (`not_present`, `skipped_symlink`, `skipped_not_regular`,
+`skipped_encoding`, `skipped_unreadable`); its sentence in `context` comes from that same
+condition. Each entry has stable `code`, `subject_kind`, and `subject` fields. The two
+`nested_agents_*` codes mirror the `nested_context` truncation booleans; the complete object
+remains a separate field. 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
@@ -203,8 +212,9 @@ budget metered on the emitted array itself — each path's escaped, JSON-seriali
 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, or a directory
-or entry could not be read, so absence of a path is not proof of absence of the file. Nested paths
+`scan_truncated` means the depth (4) or directory-count (2,000) budget was reached, a directory
+held more entries than one listing retains (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
@@ -212,6 +222,16 @@ see “Limits” for the root paths that are emitted verbatim. The corresponding
 Presence is not instruction: whether a nested file applies, and its text, remain the caller's
 judgment; Markdown output is unchanged.
 
+Escaped names remain reversible and distinct: a literal backslash becomes `\\`, a backtick
+becomes `\x60`, ASCII controls and undecodable filesystem bytes become `\xNN`, and other
+non-printable Unicode characters become `\uNNNN` or `\UNNNNNNNN`. Printable Unicode stays
+unchanged. After JSON decoding, recover POSIX path bytes by reading escapes from left to right:
+`\\` yields one backslash byte, `\xNN` yields that byte, and Unicode escapes and ordinary
+characters yield their UTF-8 bytes. Thus a backtick, a literal `\x60`, an undecodable byte
+`0x80`, and Unicode `U+0080` all have different representations. This applies to nested paths
+and displayed tree/change/status names; the verbatim root/source paths retain their existing
+semantics.
+
 ### Compact model consumption (`--format json-compact`)
 
 `--format json-compact` emits a `schema_version` 4 document: exactly the version-3 document with
@@ -236,10 +256,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.1`. Version 1
+for `--format json` and `4` for `--format json-compact`, while `tool.version` is `1.3.3`. 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.
@@ -313,11 +333,51 @@ bullet is a per-component, read or capture bound, as each one states:
   16 KiB, including a 4-KiB maximum small head
 - `README.md`: 16 KiB
 - Each entry file: 8 KiB
-- All entry-file bodies: 24 KiB
+- All entry-file bodies: 24 KiB, including truncation markers. Room is reserved for markers
+  on later text sources, so exhausting the budget never hides that their bodies were cut.
 - Declared commands: 8 KiB
-- Directory tree: 12 KiB, 300 entries, and depth 2
-- Nested `AGENTS.md` presence scan: depth 4, 2,000 directories, at most 32 reported paths and
-  a 4 KiB budget metered on the emitted array; file contents are never read
+- Directory tree: 12 KiB of listing body, 300 entries, and depth 2. Each directory is
+  retains and classifies 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
+  retention limit decides which names a directory offers at all; above it only an alphabetical
+  prefix is classified. All names must still be scanned to find that prefix, subject to the
+  separate hard name-scan bound below; the retention cap bounds memory and classification work.
+  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 retained and classified
+  per directory. Names are scanned to select that prefix, subject to the separate hard
+  name-scan bound below; file contents are never read
+- Directory name scans stop on the first entry beyond 65,536 names per directory. An
+  over-limit directory's entire partial prefix is discarded to keep results independent of
+  operating system order. The tree emits `Skipped: directory name scan limit reached.` and
+  a `directory_scan_limit_exceeded` status; the nested presence scan sets `scan_truncated`.
+  This bounds name iteration, not elapsed time on a blocked filesystem call.
 - 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
@@ -325,6 +385,7 @@ bullet is a per-component, read or capture bound, as each one states:
   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)
+- Git status preflight: at most 128 repositories, including initialized nested submodules
 - Candidate file validation: 16 MiB hard read bound
 
 Truncation occurs only at complete UTF-8 and line boundaries and is marked explicitly.
@@ -348,6 +409,13 @@ the remote.
   this is normal after cloning an empty remote.
 - `Ahead / behind: not available` means the commit relationship cannot currently be computed.
   Counts are reported only when the configured upstream commit is available locally.
+- Executable Git clean/process filters can run during `status`, even with optional locks
+  disabled. Before reading status, the loader checks effective repository configuration,
+  including includes, worktree configuration and initialized nested submodules. A non-empty
+  clean/process command causes a safe error with no stdout, even if no current attribute uses
+  it. Disabling a driver silently would change cleanliness semantics. Filter-dependent repositories
+  (including locally configured Git LFS drivers) therefore need ordinary Git inspection outside
+  this loader. Git protocols are also disabled to prevent lazy object retrieval.
 
 ## Exit Codes
 
@@ -360,7 +428,7 @@ or candidate-file content.
 
 ## Not Included
 
-Version 1.3.1 does not provide AI summaries, project-type detection, loading or transport of
+Version 1.3.3 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.
@@ -373,6 +441,17 @@ Run the complete local check:
 just check
 ```
 
+The lockfile uses public PyPI artifact URLs; no organization mirror or local Renovate preset
+is needed. Renovate keeps scheduled, rate-limited updates and manual merges using a public
+recommended preset plus the repository's explicit settings. Python 3.12 remains the tested
+runtime; widening that range requires testing those interpreters first.
+
+Git test fixtures discard inherited `GIT_*` routing/configuration before creating repositories.
+Permission-sensitive tests must run as a non-root user. Gitea uses `just ci-check`: non-root
+runners execute directly; root containers use `runuser` with an existing account named by
+`CONTEXT_LOADER_CI_USER` (default `ubuntu`). That account must be able to execute the installed
+`uv`, Python and `just`. No `sudo` dependency is required for this CI step.
+
 ## Version maintenance
 
 The versions in `pyproject.toml` and `context_loader/__init__.py`, the `tool_version` in
@@ -393,11 +472,17 @@ only verifies the public release, mirrors its exact formal tag object if missing
 the Gitea Release record. It builds no package and has no PyPI publishing credentials.
 No private endpoint or credential is needed on GitHub.
 
+For environments that permit direct public reads but share an exhausted proxy quota,
+set the Gitea Actions repository variable `RELEASE_PUBLIC_API_DIRECT=true`. The record
+step appends only public GitHub API/PyPI hosts to the existing proxy bypass lists. Without
+this explicit option, the workflow uses its inherited proxy settings.
+
 Release checks use Python 3.12, Git, and the runner's existing OpenSSL CLI. They compare downloaded
 PyPI file bytes, metadata and SHA-256, plus the publisher/tag/commit claims in PyPI's HTTPS-served
 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.1 → context_loader-1.3.3}/context_loader/__init__.py

@@ -1,3 +1,3 @@
 """Project Context Loader."""
 
-__version__ = "1.3.1"
+__version__ = "1.3.3"