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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: context-loader
-Version: 1.3.1
+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.1**. 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.1'
+uv tool install 'context-loader==1.3.2'
 ```
 
 ```bash
-pip install 'context-loader==1.3.1'
+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.1`. 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.1'
+uv tool install 'context-loader==1.3.2'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.1'
+pip install 'context-loader==1.3.2'
 ```
 
-For development or source-based installs tracking current repository (`1.3.1`):
+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
 
@@ -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.2"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -395,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
@@ -414,8 +416,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 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
@@ -447,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.1`. 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.
@@ -526,9 +529,40 @@ bullet is a per-component, read or capture bound, as each one states:
 - 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, 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
+  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
@@ -571,7 +605,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.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.
@@ -609,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.1 → context_loader-1.3.2}/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.2**. 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.2'
 ```
 
 ```bash
-pip install 'context-loader==1.3.1'
+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.1`. 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.1'
+uv tool install 'context-loader==1.3.2'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.1'
+pip install 'context-loader==1.3.2'
 ```
 
-For development or source-based installs tracking current repository (`1.3.1`):
+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
 
@@ -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.2"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -184,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
@@ -203,8 +205,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 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
@@ -236,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.1`. 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.
@@ -315,9 +318,40 @@ bullet is a per-component, read or capture bound, as each one states:
 - 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, 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
+  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
@@ -360,7 +394,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.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.
@@ -398,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.1 → context_loader-1.3.2}/context_loader/__init__.py

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

{context_loader-1.3.1 → context_loader-1.3.2}/context_loader/application.py

@@ -5,28 +5,29 @@ from __future__ import annotations
 import hashlib
 import json
 import os
-from dataclasses import dataclass
+from dataclasses import dataclass, field
 from pathlib import Path
 
 from . import __version__
 from .collect import (
-    NOT_PRESENT,
-    SKIPPED_ENCODING,
-    SKIPPED_NOT_REGULAR,
-    SKIPPED_SYMLINK,
-    SKIPPED_UNREADABLE,
-    TRUNCATION_MARKER,
+    AgentsSelectionInputError,
+    collect_project_context,
+)
+from .filesystem import display_text
+from .git import ContextLoaderError, collect_repository
+from .model import (
     AgentsSectionAuditEntry,
     AgentsSelectionAudit,
-    AgentsSelectionInputError,
+    Availability,
     CollectedFile,
     NestedContextPresence,
     ProjectContext,
-    collect_project_context,
-    display_text,
 )
-from .git import ContextLoaderError, collect_repository
-from .render import render_markdown_with_details, rendered_source_contents
+from .render import (
+    RenderedSourceBody,
+    render_markdown_with_details,
+    rendered_source_contents,
+)
 
 # Each value names one exact document shape and is never reused: 1 and 2 are the
 # shapes published in release 1.2.0, so adding the nested_context object to both
@@ -38,14 +39,6 @@ COMPACT_JSON_SCHEMA_VERSION = 4
 JSON_OUTPUT_LIMIT_BYTES = 8 * 1024 * 1024
 TOOL_NAME = "context-loader"
 
-_STATUS_CODE_BY_MESSAGE = {
-    NOT_PRESENT: "not_present",
-    SKIPPED_SYMLINK: "skipped_symlink",
-    SKIPPED_NOT_REGULAR: "skipped_not_regular",
-    SKIPPED_ENCODING: "skipped_encoding",
-    SKIPPED_UNREADABLE: "skipped_unreadable",
-}
-
 
 @dataclass(frozen=True, slots=True)
 class ToolIdentity:
@@ -77,6 +70,10 @@ class ContextStatus:
     code: str
     subject_kind: str
     subject: str
+    # The raw fact behind the displayed subject. Display escaping is not injective, so
+    # deduplication must key on this and never on `subject`, or two different directories
+    # could collapse into one claim. It is not serialized.
+    identity: str = field(default="", compare=False)
 
 
 @dataclass(frozen=True, slots=True)
@@ -115,13 +112,11 @@ def _source_kind(name: str) -> str:
 
 def _sources(
     canonical_root: Path,
-    project: ProjectContext,
-    included_sections: tuple[str, ...],
+    rendered_bodies: tuple[RenderedSourceBody, ...],
 ) -> tuple[ProjectContextSource, ...]:
     sources: list[ProjectContextSource] = []
-    for ordinal, (source, content) in enumerate(
-        rendered_source_contents(project, included_sections)
-    ):
+    for ordinal, rendered_body in enumerate(rendered_bodies):
+        source = rendered_body.source
         path = canonical_root / source.name
         sources.append(
             ProjectContextSource(
@@ -129,22 +124,23 @@ def _sources(
                 kind=_source_kind(source.name),
                 scope=source_scope_for_path(path, canonical_root),
                 path=path,
-                content_sha256=_text_sha256(content),
-                content=content,
+                content_sha256=_text_sha256(rendered_body.body),
+                content=rendered_body.body,
                 selection=source.selection,
             )
         )
     return tuple(sources)
 
 
-def _status(code: str, subject_kind: str, subject: str) -> ContextStatus:
-    return ContextStatus(code=code, subject_kind=subject_kind, subject=subject)
+def _status(code: str, subject_kind: str, subject: str, identity: str = "") -> ContextStatus:
+    return ContextStatus(
+        code=code, subject_kind=subject_kind, subject=subject, identity=identity or subject
+    )
 
 
 def _statuses_for_source(source: CollectedFile) -> list[ContextStatus]:
-    if source.status is not None:
-        code = _STATUS_CODE_BY_MESSAGE.get(source.status, "skipped_unreadable")
-        return [_status(code, "source", source.name)]
+    if source.reason is not Availability.PRESENT:
+        return [_status(source.reason.value, "source", source.name)]
     statuses: list[ContextStatus] = []
     if source.truncated or (source.selection is not None and source.selection.truncated):
         statuses.append(_status("truncated", "source", source.name))
@@ -164,7 +160,8 @@ def _build_statuses(
     omitted_sections: tuple[str, ...],
     changes_truncated: bool,
     commands_truncated: bool,
-    rendered_sources: tuple[ProjectContextSource, ...],
+    tree_truncated: bool,
+    rendered_bodies: tuple[RenderedSourceBody, ...],
 ) -> tuple[ContextStatus, ...]:
     statuses: list[ContextStatus] = []
     for source in (project.instructions, project.overview, *project.entry_files):
@@ -175,10 +172,10 @@ def _build_statuses(
         for status in statuses
         if status.subject_kind == "source" and status.code == "truncated"
     }
-    for source in rendered_sources:
-        if TRUNCATION_MARKER not in source.content:
+    for rendered_body in rendered_bodies:
+        if not rendered_body.truncated:
             continue
-        name = source.path.name
+        name = rendered_body.source.name
         if name in truncated_sources:
             continue
         statuses.append(_status("truncated", "source", name))
@@ -189,13 +186,37 @@ def _build_statuses(
     if changes_truncated:
         statuses.append(_status("truncated", "changes", "Working Tree Changes"))
 
-    if project.directory_tree.truncated:
+    if project.directory_tree.truncated or tree_truncated:
         statuses.append(_status("truncated", "tree", "Directory Tree"))
     for entry in project.directory_tree.entries:
         if entry.kind == "unreadable_directory":
             subject = entry.path if entry.path else "."
             statuses.append(_status("unreadable", "tree_entry", display_text(subject)))
-
+    tree = project.directory_tree
+    named = list(dict.fromkeys(tree.incomplete_directories))
+    for path in named:
+        subject = path if path else "."
+        statuses.append(
+            _status(
+                "directory_listing_incomplete",
+                "tree_entry",
+                display_text(subject),
+                identity=path,
+            )
+        )
+    unnamed = tree.incomplete_count - len(named)
+    if unnamed > 0:
+        stem = "directory" if unnamed == 1 else "directories"
+        statuses.append(
+            _status(
+                "directory_listing_incomplete",
+                "tree",
+                f"{tree.incomplete_count} directories exceeded the "
+                f"{tree.enumeration_limit}-entry per-directory enumeration limit; "
+                f"{unnamed} further {stem} not named individually",
+                identity=f"aggregate:{tree.incomplete_count}:{unnamed}",
+            )
+        )
     for title in omitted_sections:
         statuses.append(_status("section_omitted", "section", title))
 
@@ -207,7 +228,7 @@ def _build_statuses(
     deduped: list[ContextStatus] = []
     seen: set[tuple[str, str, str]] = set()
     for status in statuses:
-        key = (status.code, status.subject_kind, status.subject)
+        key = (status.code, status.subject_kind, status.identity)
         if key in seen:
             continue
         seen.add(key)
@@ -233,13 +254,15 @@ def load_project_context(
         raise ContextLoaderError(str(exc), exit_code=2) from None
     rendered = render_markdown_with_details(state, project)
     context = rendered.output.decode("utf-8")
-    sources = _sources(state.repository, project, rendered.included_sections)
+    rendered_bodies = rendered_source_contents(project, rendered.included_sections)
+    sources = _sources(state.repository, rendered_bodies)
     statuses = _build_statuses(
         project,
         omitted_sections=rendered.omitted_sections,
         changes_truncated=rendered.changes_truncated,
         commands_truncated=rendered.commands_truncated,
-        rendered_sources=sources,
+        tree_truncated=rendered.tree_truncated,
+        rendered_bodies=rendered_bodies,
     )
     return ProjectContextResult(
         schema_version=JSON_SCHEMA_VERSION,

{context_loader-1.3.1 → context_loader-1.3.2}/context_loader/cli.py

@@ -17,6 +17,21 @@ class SafeArgumentParser(argparse.ArgumentParser):
         raise ContextLoaderError("invalid command-line arguments", exit_code=2)
 
 
+class _OnceAction(argparse.Action):
+    def __call__(
+        self,
+        parser: argparse.ArgumentParser,
+        namespace: argparse.Namespace,
+        values: str,
+        option_string: str | None = None,
+    ) -> None:
+        seen = f"_seen_{self.dest}"
+        if getattr(namespace, seen, False):
+            parser.error("option supplied more than once")
+        setattr(namespace, seen, True)
+        setattr(namespace, self.dest, values)
+
+
 def _parser() -> argparse.ArgumentParser:
     parser = SafeArgumentParser(
         prog="project-context",
@@ -24,20 +39,25 @@ def _parser() -> argparse.ArgumentParser:
         allow_abbrev=False,
     )
     parser.add_argument("--version", action="version", version=f"%(prog)s {__version__}")
-    parser.add_argument("--repo", required=True, help="absolute Git worktree path")
+    parser.add_argument(
+        "--repo", required=True, action=_OnceAction, help="absolute Git worktree path"
+    )
     parser.add_argument(
         "--focus",
+        action=_OnceAction,
         help="optional bounded task focus used for deterministic AGENTS section selection",
     )
     parser.add_argument(
         "--path",
         dest="target_path",
+        action=_OnceAction,
         help="optional repository-relative target path used for AGENTS section selection",
     )
     parser.add_argument(
         "--format",
         choices=("markdown", "json", "json-compact"),
         default="markdown",
+        action=_OnceAction,
         help=(
             "output format (default: markdown); json-compact omits the "
             "duplicated source bodies (see README, Compact model consumption)"