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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: context-loader
-Version: 1.3.0
+Version: 1.3.1
 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.1**. 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.1'
 ```
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.1'
 ```
 
 ```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.1`. 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.1'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.1'
 ```
 
-For development or source-based installs tracking current repository (`1.3.0`):
+For development or source-based installs tracking current repository (`1.3.1`):
 
 ```bash
 uv tool install git+https://github.com/xuanheng-tech/context-loader.git
@@ -338,16 +338,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.1"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -408,11 +409,16 @@ 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, 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.
@@ -444,7 +450,7 @@ although 1.1.0 added the top-level `statuses` key. From release 1.2.0 onward eac
 names exactly one key set, and the `nested_context` renumber below enforces that rule going forward.
 
 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.1`. 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,7 +503,23 @@ 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
@@ -505,10 +527,14 @@ scan that ends before EOF still reports the characters it could not select.
 - 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;
-  file contents are never read
+- 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
 - 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 +571,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.1 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.

{context_loader-1.3.0 → context_loader-1.3.1}/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.1**. 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.1'
 ```
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.1'
 ```
 
 ```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.1`. 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.1'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install 'context-loader==1.3.0'
+pip install 'context-loader==1.3.1'
 ```
 
-For development or source-based installs tracking current repository (`1.3.0`):
+For development or source-based installs tracking current repository (`1.3.1`):
 
 ```bash
 uv tool install git+https://github.com/xuanheng-tech/context-loader.git
@@ -127,16 +127,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.1"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -197,11 +198,16 @@ 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, 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.
@@ -233,7 +239,7 @@ although 1.1.0 added the top-level `statuses` key. From release 1.2.0 onward eac
 names exactly one key set, and the `nested_context` renumber below enforces that rule going forward.
 
 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.1`. 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,7 +292,23 @@ 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
@@ -294,10 +316,14 @@ scan that ends before EOF still reports the characters it could not select.
 - 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;
-  file contents are never read
+- 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
 - 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 +360,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.1 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.

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

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

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

@@ -23,15 +23,19 @@ from .collect import (
     NestedContextPresence,
     ProjectContext,
     collect_project_context,
+    display_text,
 )
 from .git import ContextLoaderError, collect_repository
-from .render import _display, render_markdown_with_details, rendered_source_contents
+from .render import 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
 # formats moved the default document to 3 and the compact projection to 4.
 JSON_SCHEMA_VERSION = 3
 COMPACT_JSON_SCHEMA_VERSION = 4
+# Both machine formats share this final bound on the serialized document: output is
+# either valid JSON within it or a fail-closed error, never a truncated document.
+JSON_OUTPUT_LIMIT_BYTES = 8 * 1024 * 1024
 TOOL_NAME = "context-loader"
 
 _STATUS_CODE_BY_MESSAGE = {
@@ -190,7 +194,7 @@ def _build_statuses(
     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(subject)))
+            statuses.append(_status("unreadable", "tree_entry", display_text(subject)))
 
     for title in omitted_sections:
         statuses.append(_status("section_omitted", "section", title))
@@ -305,6 +309,9 @@ def render_json(result: ProjectContextResult, *, compact: bool = False) -> bytes
     ``compact`` projects away the duplicated source bodies only at this
     boundary: statuses and context were computed from the full model at load
     time, so both documents agree on everything except ``sources[*].content``.
+
+    The bound is on the final serialized document: a repository whose evidence
+    cannot fit fails closed with no output rather than emitting a partial file.
     """
     document = {
         "schema_version": (COMPACT_JSON_SCHEMA_VERSION if compact else result.schema_version),
@@ -323,7 +330,7 @@ def render_json(result: ProjectContextResult, *, compact: bool = False) -> bytes
         "nested_context": {
             # Filesystem names arrive undecoded (surrogate-escaped); sanitize exactly like
             # tree/change paths so no raw byte can reach the UTF-8 document.
-            "files": [_display(path) for path in result.nested_context.files],
+            "files": [display_text(path) for path in result.nested_context.files],
             "list_truncated": result.nested_context.list_truncated,
             "scan_truncated": result.nested_context.scan_truncated,
         },
@@ -337,4 +344,9 @@ def render_json(result: ProjectContextResult, *, compact: bool = False) -> bytes
         sort_keys=True,
         separators=(",", ":"),
     )
-    return f"{serialized}\n".encode()
+    encoded = f"{serialized}\n".encode()
+    if len(encoded) > JSON_OUTPUT_LIMIT_BYTES:
+        raise ContextLoaderError(
+            f"JSON output exceeded the {JSON_OUTPUT_LIMIT_BYTES} byte document limit"
+        )
+    return encoded

{context_loader-1.3.0 → context_loader-1.3.1}/context_loader/collect.py

@@ -992,6 +992,40 @@ def _collect_directory_tree(root: Path) -> DirectoryTree:
     return DirectoryTree(tuple(collected), truncated)
 
 
+def display_text(value: str) -> str:
+    r"""Render one filesystem or Git string as printable, encodable ASCII-safe text.
+
+    Backticks, lone surrogates produced by ``surrogateescape`` decoding, and every
+    other non-printable codepoint become ``\xNN``/``\uNNNN``/``\UNNNNNNNN`` escapes so
+    the character can cross the JSON and Markdown serialization boundaries intact.
+    """
+    rendered: list[str] = []
+    for character in value:
+        codepoint = ord(character)
+        if character == "`":
+            rendered.append(r"\x60")
+        elif 0xDC80 <= codepoint <= 0xDCFF:
+            rendered.append(f"\\x{codepoint - 0xDC00:02x}")
+        elif character.isprintable():
+            rendered.append(character)
+        elif codepoint <= 0xFF:
+            rendered.append(f"\\x{codepoint:02x}")
+        elif codepoint <= 0xFFFF:
+            rendered.append(f"\\u{codepoint:04x}")
+        else:
+            rendered.append(f"\\U{codepoint:08x}")
+    return "".join(rendered)
+
+
+def serialized_display_length(value: str) -> int:
+    """Return the UTF-8 byte size of ``value`` once escaped and JSON-serialized.
+
+    This is the exact bytes one ``nested_context`` entry costs, quotes included, so the
+    report budget is metered on emitted output rather than on raw path bytes.
+    """
+    return len(json.dumps(display_text(value), ensure_ascii=False).encode("utf-8"))
+
+
 def collect_nested_agents_presence(repository: Path) -> NestedContextPresence:
     """List nested AGENTS.md paths under a bounded, contents-blind directory scan.
 
@@ -1035,8 +1069,9 @@ def collect_nested_agents_presence(repository: Path) -> NestedContextPresence:
             if len(files) >= NESTED_AGENTS_MAX_FILES:
                 state["list_truncated"] = True
                 continue
-            name_bytes = len(path.encode("utf-8", errors="surrogateescape"))
-            name_bytes += 1 if files else 0
+            # Charge the array's two bracket bytes to the first entry, so the budget
+            # covers everything this list makes the document emit.
+            name_bytes = serialized_display_length(path) + (1 if files else 2)
             if reported_bytes + name_bytes > NESTED_AGENTS_MAX_LIST_BYTES:
                 state["list_truncated"] = True
                 continue

{context_loader-1.3.0 → context_loader-1.3.1}/context_loader/render.py

@@ -19,6 +19,7 @@ from .collect import (
     DirectoryTree,
     ProjectContext,
     TreeEntry,
+    display_text,
     render_agents_selection_audit,
 )
 from .git import RecentCommit, RepositoryState
@@ -39,30 +40,11 @@ class MarkdownRender:
     commands_truncated: bool
 
 
-def _display(value: str) -> str:
-    rendered: list[str] = []
-    for character in value:
-        codepoint = ord(character)
-        if character == "`":
-            rendered.append(r"\x60")
-        elif 0xDC80 <= codepoint <= 0xDCFF:
-            rendered.append(f"\\x{codepoint - 0xDC00:02x}")
-        elif character.isprintable():
-            rendered.append(character)
-        elif codepoint <= 0xFF:
-            rendered.append(f"\\x{codepoint:02x}")
-        elif codepoint <= 0xFFFF:
-            rendered.append(f"\\u{codepoint:04x}")
-        else:
-            rendered.append(f"\\U{codepoint:08x}")
-    return "".join(rendered)
-
-
 def _display_limited(value: str, limit: int) -> str | None:
     rendered: list[str] = []
     used = 0
     for character in value:
-        piece = _display(character)
+        piece = display_text(character)
         size = len(piece.encode())
         if used + size > limit:
             return None
@@ -121,7 +103,7 @@ def _change_lines(state: RepositoryState) -> tuple[list[str], bool]:
     for change in state.changes:
         if len(lines) == MAX_CHANGE_ENTRIES:
             return lines, True
-        line = f"- `{change.status} {_display(change.path)}`"
+        line = f"- `{change.status} {display_text(change.path)}`"
         line_bytes = len(f"{line}\n".encode())
         if used_bytes + line_bytes > MAX_CHANGE_MARKDOWN_BYTES:
             return lines, True
@@ -134,10 +116,10 @@ def _render_git_state(state: RepositoryState) -> str:
     lines = [
         "## Git State",
         "",
-        f"- Branch: `{_display(state.branch)}`",
-        f"- HEAD: `{_display(state.head)}`",
-        f"- Upstream: `{_display(state.upstream)}`",
-        f"- Ahead / behind: `{_display(state.ahead_behind)}`",
+        f"- Branch: `{display_text(state.branch)}`",
+        f"- HEAD: `{display_text(state.head)}`",
+        f"- Upstream: `{display_text(state.upstream)}`",
+        f"- Ahead / behind: `{display_text(state.ahead_behind)}`",
         f"- Worktree: `{state.worktree}`",
         "",
         "### Working Tree Changes",
@@ -170,10 +152,10 @@ def _command_line(command: DeclaredCommand) -> str:
     if command.parse_error:
         return f"- `{command.source}`: unable to parse command declarations."
     assert command.invocation is not None
-    invocation = _display(command.invocation)
+    invocation = display_text(command.invocation)
     if command.target is None:
         return f"- `{invocation}`"
-    return f"- `{invocation}` → `{_display(command.target)}`"
+    return f"- `{invocation}` → `{display_text(command.target)}`"
 
 
 def _bounded_lines(
@@ -262,7 +244,7 @@ def _render_recent_commits(commits: tuple[RecentCommit, ...]) -> str | None:
 
 
 def _tree_line(entry: TreeEntry) -> str:
-    path = _display(entry.path)
+    path = display_text(entry.path)
     if entry.kind == "directory":
         return f"{path}/"
     if entry.kind == "symlink":
@@ -295,7 +277,7 @@ def render_markdown_with_details(state: RepositoryState, project: ProjectContext
             "# Project Context",
             "",
             f"- Schema: `{SCHEMA}`",
-            f"- Repository: `{_display(os.fspath(state.repository))}`",
+            f"- Repository: `{display_text(os.fspath(state.repository))}`",
         )
     )
     commands_section, commands_truncated = _render_commands(project.commands)

{context_loader-1.3.0 → context_loader-1.3.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 
 [project]
 name = "context-loader"
-version = "1.3.0"
+version = "1.3.1"
 description = "Render deterministic local Git context for any executor"
 readme = "README.md"
 requires-python = ">=3.12,<3.13"

{context_loader-1.3.0 → context_loader-1.3.1}/pyproject.toml.orig

@@ -4,7 +4,7 @@ build-backend = "uv_build"
 
 [project]
 name = "context-loader"
-version = "1.3.0"
+version = "1.3.1"
 description = "Render deterministic local Git context for any executor"
 license = { file = "LICENSE" }
 readme = "README.md"

{context_loader-1.3.0 → context_loader-1.3.1}/tool_cli_contract.json

@@ -46,5 +46,5 @@
   ],
   "schema_version": 1,
   "tool_name": "context-loader",
-  "tool_version": "1.3.0"
+  "tool_version": "1.3.1"
 }