sediment-cli 0.6.1__tar.gz → 0.7.0__tar.gz

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sediment-cli
-Version: 0.6.1
+Version: 0.7.0
 Summary: A self-hosted evidence store for coding agents: the sediment CLI and local server
 Project-URL: Source, https://github.com/sediment-ai/sediment
 Project-URL: Documentation, https://docs.sediment.so
@@ -10,10 +10,10 @@ License-Expression: AGPL-3.0-or-later
 License-File: LICENSE
 Requires-Python: >=3.12
 Requires-Dist: httpx>=0.27
-Requires-Dist: sediment-api==0.6.1
-Requires-Dist: sediment-core==0.6.1
-Requires-Dist: sediment-derive==0.6.1
-Requires-Dist: sediment-export==0.6.1
+Requires-Dist: sediment-api==0.7.0
+Requires-Dist: sediment-core==0.7.0
+Requires-Dist: sediment-derive==0.7.0
+Requires-Dist: sediment-export==0.7.0
 Description-Content-Type: text/markdown
 
 # sediment-cli

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/pyproject.toml

@@ -5,7 +5,7 @@
 # Depends on sediment-api deliberately: the operator verbs are DB-local by
 # design (ADR 0001) and `server`/reports/mirror-gc forward into it.
 name = "sediment-cli"
-version = "0.6.1"
+version = "0.7.0"
 description = "A self-hosted evidence store for coding agents: the sediment CLI and local server"
 readme = "README.md"
 requires-python = ">=3.12"
@@ -15,10 +15,10 @@ license-files = ["LICENSE"]
 # so an install never mixes member versions (the release workflow asserts
 # the versions agree before publishing).
 dependencies = [
-    "sediment-core==0.6.1",
-    "sediment-derive==0.6.1",
-    "sediment-export==0.6.1",
-    "sediment-api==0.6.1",
+    "sediment-core==0.7.0",
+    "sediment-derive==0.7.0",
+    "sediment-export==0.7.0",
+    "sediment-api==0.7.0",
     "httpx>=0.27",
 ]
 

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/sediment_cli/_pi/README.md

@@ -195,7 +195,7 @@ delivery changes also trigger this workflow. To exercise the same tests locally,
 set `SEDIMENT_PI_TEST_PYTHON` to the installed environment's Python executable
 and `SEDIMENT_PI_TEST_INSTALLED_BIN` to its `bin` directory before `npm test`.
 
-The lockfile pins pi 1.1.0 (`@earendil-works/pi-coding-agent`) as a development
+The lockfile pins pi 1.5.0 (`@earendil-works/pi-coding-agent`) as a development
 dependency. The native retrieval test exercises its extension registration,
 argument validation, agent loop, and model-visible tool result with a scripted
 model stream. It makes no paid inference request and downloads no package during

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/sediment_cli/_pi/package.json

@@ -13,7 +13,7 @@
     "typecheck": "tsc --noEmit"
   },
   "devDependencies": {
-    "@earendil-works/pi-coding-agent": "1.1.0",
+    "@earendil-works/pi-coding-agent": "1.5.0",
     "@types/node": "^24.19.2",
     "typescript": "^7.0.2"
   }

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/sediment_cli/agent_guide.txt

@@ -85,9 +85,10 @@ Session checks to verify delivery. `commit` requires an operator credential;
 - Preserve the `sediment env` blocks in shell profiles and Sediment's entries
   in Claude Code settings, Codex hooks and profiles, Cursor hooks, and pi
   settings. User-level agent hooks apply across repositories.
-- Read hook output. Sediment commands end in `|| true`; an appended block can
-  also mask a repository check that relies on its last command's exit status.
-  A zero status alone doesn't prove that the repository's checks passed.
+- Read hook output. Sediment commands end in `|| true`, so they never fail a
+  commit or push. The marked block keeps the hook's previous exit status.
+  Commands after the block still run. A zero status alone doesn't prove that
+  capture succeeded.
 
 [What the installer changes](../capture/local-capture.md#what-the-installer-changes)
 describes the hooks. [Roll out managed capture](../capture/managed-capture.md)

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/sediment_cli/attribution.py

@@ -152,7 +152,9 @@ _HOOK_BLOCK_RE = re.compile(
 # disagree about which hooks exist.
 _REPO_HOOKS = (
     ("post-commit", "stamp"),
-    ("prepare-commit-msg", 'union-squash-notes "$1" "$2"'),
+    # A plain `git commit` passes one argument. `${2-}` is empty when git
+    # omits the commit source, so `set -u` doesn't abort before `|| true`.
+    ("prepare-commit-msg", 'union-squash-notes "$1" "${2-}"'),
     ("pre-push", 'push-notes "$1"'),
 )
 # Substrings used to recognise our entries in agent hook configs. The
@@ -2257,8 +2259,24 @@ def _install_hook_block(hook_file: Path, command: str) -> bool:
     Refuses (returns False) when the existing hook is not an sh script —
     appending sh to a python/binary hook would break every commit/push, the
     one thing the stamper must never do.
+
+    The block saves the status it found and restores it after ``command``.
+    ``command`` ends in ``|| true``, so a Sediment failure cannot fail the
+    commit or push. The restore runs in a subshell: later hook commands still
+    run, and ``set -e`` doesn't treat the restored status as a block failure.
     """
-    block = f"{HOOK_BLOCK_BEGIN}\n{command}\n{HOOK_BLOCK_END}\n"
+    # The subshell restores the previous command's status without exiting the
+    # hook or leaking `__sediment_status`. `&& :` keeps that restored status
+    # from tripping `set -e` before later commands.
+    block = (
+        f"{HOOK_BLOCK_BEGIN}\n"
+        "(\n"
+        "    __sediment_status=$?\n"
+        f"    {command}\n"
+        '    exit "$__sediment_status"\n'
+        ") && :\n"
+        f"{HOOK_BLOCK_END}\n"
+    )
     if hook_file.exists():
         try:
             content = hook_file.read_text(encoding="utf-8")

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/sediment_cli/cli.py

@@ -132,6 +132,10 @@ _REPORTS = {
         "sediment_api.reports.merge_retention_report",
         "attributed change retention through pull request merge",
     ),
+    "compute": (
+        "sediment_api.reports.compute_report",
+        "Session completion time by final Compute allocation",
+    ),
     "lifecycle": (
         "sediment_api.reports.lifecycle_report",
         "accepted-work progression, retention, attrition, and rework evidence",

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/tests/testdata/help/quarantine.txt

@@ -1,12 +1,12 @@
 USAGE:
   sediment quarantine [-h] --reason REASON
-                      {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames}
+                      {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames,compute_allocations}
                       fact_id
 
   quarantine one fact by id
 
 ARGUMENTS:
-  {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames}
+  {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames,compute_allocations}
   fact_id
 
 OPTIONS:

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/tests/testdata/help/release.txt

@@ -1,12 +1,12 @@
 USAGE:
   sediment release [-h] --reason REASON
-                   {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames}
+                   {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames,compute_allocations}
                    fact_id
 
   release one quarantined fact by id
 
 ARGUMENTS:
-  {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames}
+  {inference_calls,developer_decisions,ci_outcomes,pushes,pull_request_merges,pull_request_revisions,edit_observations,rejected_edits,retry_linkages,session_commit_observations,repository_renames,compute_allocations}
   fact_id
 
 OPTIONS:

sediment_cli-0.7.0/tests/testdata/help/report-compute.txt

@@ -0,0 +1,14 @@
+USAGE:
+  sediment report compute [-h] [--org ORG] [--json] [--rows-out FILE]
+                          [--database-url DATABASE_URL]
+
+  Compare Session completion time across final Compute allocations.
+
+OPTIONS:
+  -h, --help            show this help message and exit
+  --org ORG             org id (default: $SEDIMENT_ORG_ID)
+  --json                emit JSON instead of a text report
+  --rows-out FILE       write one Session compute timing per line to FILE as
+                        JSONL
+  --database-url DATABASE_URL
+                        PostgreSQL URL (default: $SEDIMENT_DATABASE_URL)

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/tests/testdata/help/report.txt

@@ -12,4 +12,5 @@ REPORTS:
   abandonment            sessions whose accepted edits never reached a commit
   attribution-share      notes-attribution share and decline alert
   merge-retention        attributed change retention through pull request merge
+  compute                Session completion time by final Compute allocation
   lifecycle              accepted-work progression, retention, attrition, and rework evidence

{sediment_cli-0.6.1 → sediment_cli-0.7.0}/tests/testdata/help/sediment.txt

@@ -1,4 +1,4 @@
-sediment v0.6.1 — A self-hosted evidence store for coding agents.
+sediment v0.7.0 — A self-hosted evidence store for coding agents.
 
 USAGE:
   sediment <command> [options]