context-loader 1.1.0__tar.gz → 1.2.0__tar.gz

{context_loader-1.1.0 → context_loader-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: context-loader
-Version: 1.1.0
+Version: 1.2.0
 Summary: Render deterministic local Git context for any executor
 License:                                  Apache License
                                     Version 2.0, January 2004
@@ -219,15 +219,14 @@ Python standard library.
 
 ## Open-source quick start
 
-Context Loader is a local CLI that exports repository context deterministically for coding-agent workflows,
-rendering stable Markdown or JSON output.
+Current stable release: **1.2.0**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
 
 ```bash
-uv tool install context-loader
+uv tool install 'context-loader==1.2.0'
 ```
 
 ```bash
-pip install context-loader
+pip install 'context-loader==1.2.0'
 ```
 
 ```bash
@@ -240,21 +239,21 @@ project-context --repo /path/to/repo --format json
 
 ## Install
 
-Source version: `1.1.0`. Install its matching published release or an exact source commit.
+Source version: `1.2.0`. Install its matching published release or an exact source commit.
 
 Install via `uv`:
 
 ```bash
-uv tool install context-loader
+uv tool install 'context-loader==1.2.0'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install context-loader
+pip install 'context-loader==1.2.0'
 ```
 
-For development or source-based installs tracking current repository (`1.1.0`):
+For development or source-based installs tracking current repository (`1.2.0`):
 
 ```bash
 uv tool install git+https://github.com/xuanheng-tech/context-loader.git
@@ -305,16 +304,17 @@ project-context --version
 project-context --repo /home/user/projects/example
 project-context --repo /home/user/projects/example --format markdown
 project-context --repo /home/user/projects/example --format json
+project-context --repo /home/user/projects/example --format json-compact
 project-context --repo /home/user/projects/example \
   --focus "Authentication and session management" \
   --path auth/session.py
 ```
 
 `--format` defaults to `markdown`. In Markdown mode, `--repo` retains the 0.1.1 contract: it must be
-the absolute, canonical root of a non-bare Git working tree. In JSON mode, an absolute existing
-directory inside the working tree is accepted; symlinks are normalized and the discovered root is
-reported as `canonical_root`. Relative paths, non-Git directories, regular files, and bare
-repositories are rejected in both modes.
+the absolute, canonical root of a non-bare Git working tree. In the `json` and `json-compact` modes,
+an absolute existing directory inside the working tree is accepted; symlinks are normalized and the
+discovered root is reported as `canonical_root`. Relative paths, non-Git directories, regular files,
+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.
@@ -337,15 +337,17 @@ The output has no generated timestamp, AI summary, architecture inference, or di
 
 ## JSON Output
 
-`--format json` writes exactly one compact UTF-8 JSON document plus one trailing newline to stdout.
-Keys are serialized in sorted order with `ensure_ascii=False`. The declared contract is:
+`--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:
 
 ```json
 {
   "schema_version": 1,
   "tool": {
     "name": "context-loader",
-    "version": "1.1.0"
+    "version": "1.2.0"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -380,10 +382,12 @@ Keys are serialized in sorted order with `ensure_ascii=False`. The declared cont
 ```
 
 `context_sha256` hashes the UTF-8 bytes of `context`; each `content_sha256` does the same for that
-source's `content`. `sources` contains only file bodies that actually enter the final context, in
-assembly order, after the existing newline normalization and truncation rules. `scope` 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.
+source's `content` body as rendered (after newline normalization, any `AGENTS.md` section selection
+and any truncation marker) — never for the raw bytes of the file at `path`, which match only for
+unselected, untruncated LF files. `sources` contains only file bodies that actually enter the final
+context, in assembly order, after the existing newline normalization and truncation rules. `scope`
+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: skipped or absent sources, truncated sources, unreadable directory-tree entries, sections omitted under the global output budget, and truncated working-tree or declared-command listings. Each entry has stable `code`, `subject_kind`, and `subject` fields. `sources`, `context`, and `schema_version` remain unchanged; callers can ignore `statuses` safely.
 
@@ -391,8 +395,26 @@ The optional `selection` object is present only on a rendered `AGENTS.md` source
 contain heading, heading level, and fixed selection reasons; it never contains the original focus or
 target path. Existing source fields and schema version 1 remain unchanged.
 
-The JSON schema version and package version are independent: `schema_version` is currently the
-integer `1`, while `tool.version` is `1.1.0`. Callers must depend only on fields declared above.
+### Compact model consumption (`--format json-compact`)
+
+`--format json-compact` emits a `schema_version` 2 document: exactly the version-1 document with
+`sources[*].content` omitted. Every other field — `context`, `context_sha256`, `statuses`,
+`warnings`, `tool`, `repository`, and each source's `ordinal`, `kind`, `scope`, `path`,
+`content_sha256` and optional `selection` — is identical to `--format json` for the same arguments.
+The projection exists because the selected source bodies already occur verbatim inside `context`,
+so carrying them again in `sources` duplicates a large share of the document bytes (measured up to
+~44% on real worktrees, scaling with how much of `context` those bodies occupy) for a model
+consumer without adding information. Nothing is lost: each omitted body remains inside `context`,
+`content_sha256` still fingerprints that rendered body, and `path` plus `canonical_root` locate the
+underlying file for a bounded manual re-read (whose raw bytes may differ from the rendered body as
+defined above). `schema_version` is an exact document selector, not an upgrade marker: version 2 is
+a field-set projection of version 1, so consumers must branch on the value and must not apply
+`>=`-superset reasoning. Default Markdown and `--format json` output bytes, exit codes and
+determinism are unchanged.
+
+The JSON schema version and package version are independent: `--format json` currently emits
+`schema_version` `1` and `--format json-compact` emits `2`, while `tool.version` is `1.2.0`.
+Callers must depend only on fields declared above.
 The document contains no generated time or random identifier, so unchanged input produces identical
 JSON bytes. On failure, stdout remains empty and stderr contains only a short diagnostic.
 
@@ -500,8 +522,11 @@ just check
 ## Version maintenance
 
 The versions in `pyproject.toml` and `context_loader/__init__.py`, the matching `CHANGELOG.md`
-section, and required tests must change in the same release-preparation batch. `CHANGELOG.md` is the
-authoritative version-change record. Merging to `master` is not a release; formal publication
+section, required tests, and the README current-stable declaration plus `context-loader==X.Y.Z`
+install pins must change in the same release-preparation batch. `CHANGELOG.md` is the
+authoritative version-change record. `scripts/release.py` rejects README stable/install
+pins that disagree with the intended package version; historical changelog entries are
+not part of that check. Merging to `master` is not a release; formal publication
 still requires a separately created and pushed tag.
 
 ## Release closure and retries

{context_loader-1.1.0 → context_loader-1.2.0}/README.md

@@ -8,15 +8,14 @@ Python standard library.
 
 ## Open-source quick start
 
-Context Loader is a local CLI that exports repository context deterministically for coding-agent workflows,
-rendering stable Markdown or JSON output.
+Current stable release: **1.2.0**. Local CLI for coding-agent workflows; renders deterministic Markdown or JSON.
 
 ```bash
-uv tool install context-loader
+uv tool install 'context-loader==1.2.0'
 ```
 
 ```bash
-pip install context-loader
+pip install 'context-loader==1.2.0'
 ```
 
 ```bash
@@ -29,21 +28,21 @@ project-context --repo /path/to/repo --format json
 
 ## Install
 
-Source version: `1.1.0`. Install its matching published release or an exact source commit.
+Source version: `1.2.0`. Install its matching published release or an exact source commit.
 
 Install via `uv`:
 
 ```bash
-uv tool install context-loader
+uv tool install 'context-loader==1.2.0'
 ```
 
 Install via `pip`:
 
 ```bash
-pip install context-loader
+pip install 'context-loader==1.2.0'
 ```
 
-For development or source-based installs tracking current repository (`1.1.0`):
+For development or source-based installs tracking current repository (`1.2.0`):
 
 ```bash
 uv tool install git+https://github.com/xuanheng-tech/context-loader.git
@@ -94,16 +93,17 @@ project-context --version
 project-context --repo /home/user/projects/example
 project-context --repo /home/user/projects/example --format markdown
 project-context --repo /home/user/projects/example --format json
+project-context --repo /home/user/projects/example --format json-compact
 project-context --repo /home/user/projects/example \
   --focus "Authentication and session management" \
   --path auth/session.py
 ```
 
 `--format` defaults to `markdown`. In Markdown mode, `--repo` retains the 0.1.1 contract: it must be
-the absolute, canonical root of a non-bare Git working tree. In JSON mode, an absolute existing
-directory inside the working tree is accepted; symlinks are normalized and the discovered root is
-reported as `canonical_root`. Relative paths, non-Git directories, regular files, and bare
-repositories are rejected in both modes.
+the absolute, canonical root of a non-bare Git working tree. In the `json` and `json-compact` modes,
+an absolute existing directory inside the working tree is accepted; symlinks are normalized and the
+discovered root is reported as `canonical_root`. Relative paths, non-Git directories, regular files,
+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.
@@ -126,15 +126,17 @@ The output has no generated timestamp, AI summary, architecture inference, or di
 
 ## JSON Output
 
-`--format json` writes exactly one compact UTF-8 JSON document plus one trailing newline to stdout.
-Keys are serialized in sorted order with `ensure_ascii=False`. The declared contract is:
+`--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:
 
 ```json
 {
   "schema_version": 1,
   "tool": {
     "name": "context-loader",
-    "version": "1.1.0"
+    "version": "1.2.0"
   },
   "repository": {
     "requested_path": "/canonical/requested/path",
@@ -169,10 +171,12 @@ Keys are serialized in sorted order with `ensure_ascii=False`. The declared cont
 ```
 
 `context_sha256` hashes the UTF-8 bytes of `context`; each `content_sha256` does the same for that
-source's `content`. `sources` contains only file bodies that actually enter the final context, in
-assembly order, after the existing newline normalization and truncation rules. `scope` 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.
+source's `content` body as rendered (after newline normalization, any `AGENTS.md` section selection
+and any truncation marker) — never for the raw bytes of the file at `path`, which match only for
+unselected, untruncated LF files. `sources` contains only file bodies that actually enter the final
+context, in assembly order, after the existing newline normalization and truncation rules. `scope`
+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: skipped or absent sources, truncated sources, unreadable directory-tree entries, sections omitted under the global output budget, and truncated working-tree or declared-command listings. Each entry has stable `code`, `subject_kind`, and `subject` fields. `sources`, `context`, and `schema_version` remain unchanged; callers can ignore `statuses` safely.
 
@@ -180,8 +184,26 @@ The optional `selection` object is present only on a rendered `AGENTS.md` source
 contain heading, heading level, and fixed selection reasons; it never contains the original focus or
 target path. Existing source fields and schema version 1 remain unchanged.
 
-The JSON schema version and package version are independent: `schema_version` is currently the
-integer `1`, while `tool.version` is `1.1.0`. Callers must depend only on fields declared above.
+### Compact model consumption (`--format json-compact`)
+
+`--format json-compact` emits a `schema_version` 2 document: exactly the version-1 document with
+`sources[*].content` omitted. Every other field — `context`, `context_sha256`, `statuses`,
+`warnings`, `tool`, `repository`, and each source's `ordinal`, `kind`, `scope`, `path`,
+`content_sha256` and optional `selection` — is identical to `--format json` for the same arguments.
+The projection exists because the selected source bodies already occur verbatim inside `context`,
+so carrying them again in `sources` duplicates a large share of the document bytes (measured up to
+~44% on real worktrees, scaling with how much of `context` those bodies occupy) for a model
+consumer without adding information. Nothing is lost: each omitted body remains inside `context`,
+`content_sha256` still fingerprints that rendered body, and `path` plus `canonical_root` locate the
+underlying file for a bounded manual re-read (whose raw bytes may differ from the rendered body as
+defined above). `schema_version` is an exact document selector, not an upgrade marker: version 2 is
+a field-set projection of version 1, so consumers must branch on the value and must not apply
+`>=`-superset reasoning. Default Markdown and `--format json` output bytes, exit codes and
+determinism are unchanged.
+
+The JSON schema version and package version are independent: `--format json` currently emits
+`schema_version` `1` and `--format json-compact` emits `2`, while `tool.version` is `1.2.0`.
+Callers must depend only on fields declared above.
 The document contains no generated time or random identifier, so unchanged input produces identical
 JSON bytes. On failure, stdout remains empty and stderr contains only a short diagnostic.
 
@@ -289,8 +311,11 @@ just check
 ## Version maintenance
 
 The versions in `pyproject.toml` and `context_loader/__init__.py`, the matching `CHANGELOG.md`
-section, and required tests must change in the same release-preparation batch. `CHANGELOG.md` is the
-authoritative version-change record. Merging to `master` is not a release; formal publication
+section, required tests, and the README current-stable declaration plus `context-loader==X.Y.Z`
+install pins must change in the same release-preparation batch. `CHANGELOG.md` is the
+authoritative version-change record. `scripts/release.py` rejects README stable/install
+pins that disagree with the intended package version; historical changelog entries are
+not part of that check. Merging to `master` is not a release; formal publication
 still requires a separately created and pushed tag.
 
 ## Release closure and retries

{context_loader-1.1.0 → context_loader-1.2.0}/context_loader/__init__.py

@@ -1,3 +1,3 @@
 """Project Context Loader."""
 
-__version__ = "1.1.0"
+__version__ = "1.2.0"

{context_loader-1.1.0 → context_loader-1.2.0}/context_loader/application.py

@@ -27,6 +27,7 @@ from .git import ContextLoaderError, collect_repository
 from .render import render_markdown_with_details, rendered_source_contents
 
 JSON_SCHEMA_VERSION = 1
+COMPACT_JSON_SCHEMA_VERSION = 2
 TOOL_NAME = "context-loader"
 
 _STATUS_CODE_BY_MESSAGE = {
@@ -272,24 +273,30 @@ def _status_document(status: ContextStatus) -> dict[str, object]:
     }
 
 
-def _source_document(source: ProjectContextSource) -> dict[str, object]:
+def _source_document(source: ProjectContextSource, *, include_content: bool) -> dict[str, object]:
     document: dict[str, object] = {
         "ordinal": source.ordinal,
         "kind": source.kind,
         "scope": source.scope,
         "path": os.fspath(source.path),
         "content_sha256": source.content_sha256,
-        "content": source.content,
     }
+    if include_content:
+        document["content"] = source.content
     if source.selection is not None:
         document["selection"] = _selection_document(source.selection)
     return document
 
 
-def render_json(result: ProjectContextResult) -> bytes:
-    """Serialize one result as stable UTF-8 JSON followed by exactly one newline."""
+def render_json(result: ProjectContextResult, *, compact: bool = False) -> bytes:
+    """Serialize one result as stable UTF-8 JSON followed by exactly one newline.
+
+    ``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``.
+    """
     document = {
-        "schema_version": result.schema_version,
+        "schema_version": (COMPACT_JSON_SCHEMA_VERSION if compact else result.schema_version),
         "tool": {
             "name": result.tool.name,
             "version": result.tool.version,
@@ -298,7 +305,9 @@ def render_json(result: ProjectContextResult) -> bytes:
             "requested_path": os.fspath(result.repository.requested_path),
             "canonical_root": os.fspath(result.repository.canonical_root),
         },
-        "sources": [_source_document(source) for source in result.sources],
+        "sources": [
+            _source_document(source, include_content=not compact) for source in result.sources
+        ],
         "statuses": [_status_document(status) for status in result.statuses],
         "context": result.context,
         "context_sha256": result.context_sha256,

{context_loader-1.1.0 → context_loader-1.2.0}/context_loader/cli.py

@@ -36,9 +36,12 @@ def _parser() -> argparse.ArgumentParser:
     )
     parser.add_argument(
         "--format",
-        choices=("markdown", "json"),
+        choices=("markdown", "json", "json-compact"),
         default="markdown",
-        help="output format (default: markdown)",
+        help=(
+            "output format (default: markdown); json-compact emits schema "
+            "version 2 without duplicated source bodies"
+        ),
     )
     return parser
 
@@ -52,11 +55,12 @@ def main(argv: Sequence[str] | None = None) -> int:
             focus=arguments.focus,
             path=arguments.target_path,
         )
-        output = (
-            result.context.encode("utf-8")
-            if arguments.format == "markdown"
-            else render_json(result)
-        )
+        if arguments.format == "markdown":
+            output = result.context.encode("utf-8")
+        elif arguments.format == "json":
+            output = render_json(result)
+        else:
+            output = render_json(result, compact=True)
     except ContextLoaderError as exc:
         print(f"error: {exc}", file=sys.stderr)
         return exc.exit_code

{context_loader-1.1.0 → context_loader-1.2.0}/pyproject.toml

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

{context_loader-1.1.0 → context_loader-1.2.0}/pyproject.toml.orig

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

{context_loader-1.1.0 → context_loader-1.2.0}/tool_cli_contract.json

@@ -15,6 +15,7 @@
         "repo_is_absolute_git_worktree",
         "markdown_requires_canonical_root",
         "json_accepts_path_inside_worktree",
+        "json_compact_accepts_path_inside_worktree",
         "target_path_is_repository_relative"
       ],
       "result_statuses": [
@@ -24,11 +25,12 @@
       ]
     }
   ],
-  "contract_version": 2,
+  "contract_version": 3,
   "flags": {
     "format": [
       "markdown",
-      "json"
+      "json",
+      "json-compact"
     ],
     "output": "stdout",
     "stderr": "bounded_diagnostic_only"
@@ -44,5 +46,5 @@
   ],
   "schema_version": 1,
   "tool_name": "context-loader",
-  "tool_version": "1.1.0"
+  "tool_version": "1.2.0"
 }