hypergumbo 9.0.0__tar.gz → 9.2.0__tar.gz

{hypergumbo-9.0.0 → hypergumbo-9.2.0}/.gitignore

@@ -15,6 +15,7 @@ build/
 
 # hypergumbo
 .hypergumbo/
+.hypergumbo-examples/
 hypergumbo_capsule/
 hypergumbo.results.json
 hypergumbo.results.*.json

{hypergumbo-9.0.0 → hypergumbo-9.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hypergumbo
-Version: 9.0.0
+Version: 9.2.0
 Summary: Local-first repo behavior map generator
 Author: Hypergumbo contributors
 License: AGPL-3.0-or-later
@@ -10,10 +10,10 @@ Classifier: License :: OSI Approved :: GNU Affero General Public License v3 or l
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3 :: Only
 Requires-Python: >=3.10
-Requires-Dist: hypergumbo-core==9.0.0
-Requires-Dist: hypergumbo-lang-common==9.0.0
-Requires-Dist: hypergumbo-lang-extended1==9.0.0
-Requires-Dist: hypergumbo-lang-mainstream==9.0.0
+Requires-Dist: hypergumbo-core==9.2.0
+Requires-Dist: hypergumbo-lang-common==9.2.0
+Requires-Dist: hypergumbo-lang-extended1==9.2.0
+Requires-Dist: hypergumbo-lang-mainstream==9.2.0
 Provides-Extra: dev
 Requires-Dist: bandit~=1.9.3; extra == 'dev'
 Requires-Dist: check-jsonschema~=0.36.1; extra == 'dev'
@@ -27,9 +27,9 @@ Requires-Dist: yamllint~=1.38.0; extra == 'dev'
 Provides-Extra: embeddings
 Requires-Dist: sentence-transformers~=5.7; extra == 'embeddings'
 Provides-Extra: rust-analyzer
-Requires-Dist: hypergumbo-lang-rust-analyzer==9.0.0; extra == 'rust-analyzer'
+Requires-Dist: hypergumbo-lang-rust-analyzer==9.2.0; extra == 'rust-analyzer'
 Provides-Extra: scip-python
-Requires-Dist: hypergumbo-lang-scip-python==9.0.0; extra == 'scip-python'
+Requires-Dist: hypergumbo-lang-scip-python==9.2.0; extra == 'scip-python'
 Description-Content-Type: text/markdown
 
 <!-- SPDX-License-Identifier: AGPL-3.0-or-later -->
@@ -153,7 +153,7 @@ Read this before installing hypergumbo on a machine you care about. Each stateme
 **What a default run does** (`hypergumbo .`, the same as `hypergumbo sketch .`):
 
 - Reads the files of the repository you point it at.
-- Writes its results under `~/.cache/hypergumbo/` (`$XDG_CACHE_HOME/hypergumbo/` if set), plus short-lived files in the system temp directory. It does not write into the repository it analyses ([ADR-0047](https://github.com/iterabloom/hypergumbo/blob/dev/docs/adr/0047-catalogue-scope-and-user-visible-homes.md) ruling 9). The exceptions are an `-o` path you choose inside it, and the case in the last bullet of this list.
+- Writes its results under `~/.cache/hypergumbo/` (`$XDG_CACHE_HOME/hypergumbo/` if set), plus short-lived files in the system temp directory. It does not write into the repository it analyses ([ADR-0047](https://github.com/iterabloom/hypergumbo/blob/dev/docs/adr/0047-catalogue-scope-and-user-visible-homes.md) ruling 9). The exceptions are an `-o` path you choose inside it, and the case in the last bullet of this list. One command writes more than the file you name: `survey --out X.json` also writes `X.4k.json`, `X.16k.json` and `X.64k.json` (the same map compacted to those token budgets) and a directory `X.slices/` holding one slice per detected route handler, all beside `X.json`. `--no-sketch-fan-out --no-handler-slices` suppresses them, so exactly one file is written.
 - Runs `git` read-only (`rev-parse HEAD`, `rev-list --max-parents=0 HEAD`, `config --get remote.origin.url`). If they are installed, it also runs `gitleaks` to scan for secrets and `rust-analyzer --version`; the version check does not index anything.
 - Makes no network connection, unless you installed embeddings support (`install-embeddings`, `add-extras`, or `pip install 'hypergumbo[embeddings]'`). In that case the first sketch downloads two models (`microsoft/unixcoder-base` and `nomic-ai/modernbert-embed-base`) from huggingface.co into `~/.cache/huggingface/` (or `$HF_HOME`). Once both models are cached, later runs work offline. To stop the download, set `HF_HUB_OFFLINE=1`; the sketch then runs without embeddings. SECURITY.md's network claim still says downloads happen only through `install-embeddings`. That claim is wrong, and INV-gujus tracks it.
 - If a directory `~/hypergumbo` exists (for example, a clone of this repository), an interactive run asks once whether to write example config files into `~/hypergumbo/.hypergumbo-examples/`. It records your answer in `~/.local/state/hypergumbo/offers.json`. If you answer yes while analysing `~/hypergumbo` itself, that is a write into the analysed repository (INV-kuroj).
@@ -182,6 +182,7 @@ Read this before installing hypergumbo on a machine you care about. Each stateme
 
 1. **Self-claims.** [SECURITY.md](https://github.com/iterabloom/hypergumbo/blob/dev/SECURITY.md) lists 18 claims about what each group of commands may touch, and hypergumbo checks them by analysing its own source (`scripts/check-self-claims`). All 18 currently read `confirmed_with_caveats`. That means the analysis found no contradiction where it could see, and it names what it could not see: programs it launches, statements the repository made about itself, and the 70.6% of method calls whose receiver type it could not work out. In auditing terms this is a qualified opinion, not proof ([ADR-0016](https://github.com/iterabloom/hypergumbo/blob/dev/docs/adr/0016-io-boundary-analysis.md)). It covers the `hypergumbo` command only.
 2. **I/O allowlist.** `scripts/check-io-allowlist` is a separate scan that uses only the standard library. It finds every place in `packages/*/src`, tracker included, that writes or deletes a file, starts a process, opens a connection or a server, or loads a model. Each one must be listed with its purpose in [`docs/hypergumbo.io-allowlist.yaml`](https://github.com/iterabloom/hypergumbo/blob/dev/docs/hypergumbo.io-allowlist.yaml), and an unlisted one fails CI. The gate proves that every such place was reviewed. It does not prove that any of them is safe.
+3. **Observed I/O manifest.** At every release, `scripts/io-manifest` runs the installed `hypergumbo` over six pinned open-source repositories under `strace` and records every file write, delete and rename, every program started and every connection attempted, reduced to fifteen lines ([`docs/io-manifest/expected.txt`](https://github.com/iterabloom/hypergumbo/blob/dev/docs/io-manifest/expected.txt)). A line not seen at the previous release fails the build, and a write into the analysed repository or a network connection fails it regardless. This is the only one of the three checks that sees what dependencies and compiled extensions do, because it watches the process rather than reading the Python. It covers a default run with no extras installed, on those six repositories: the "every scenario we exercised" statement, not "every scenario".
 
 The allowlist gate currently records these open findings:
 
@@ -239,6 +240,7 @@ Useful flags:
 hypergumbo . -x                                # exclude test files (cleaner output)
 hypergumbo . --no-source                       # omit source code (included by default)
 hypergumbo . --no-progress                     # hide progress indicator (sketch/run only; on by default)
+HG_HEARTBEAT=10 hypergumbo .                   # stack heartbeat every 10s (default 30; 0 disables)
 hypergumbo io-boundaries --show-external-potential   # opt into the (large) external-potential bucket (text output)
 hypergumbo --help --all                        # comprehensive help for all commands
 ```

{hypergumbo-9.0.0 → hypergumbo-9.2.0}/README.md

@@ -119,7 +119,7 @@ Read this before installing hypergumbo on a machine you care about. Each stateme
 **What a default run does** (`hypergumbo .`, the same as `hypergumbo sketch .`):
 
 - Reads the files of the repository you point it at.
-- Writes its results under `~/.cache/hypergumbo/` (`$XDG_CACHE_HOME/hypergumbo/` if set), plus short-lived files in the system temp directory. It does not write into the repository it analyses ([ADR-0047](https://github.com/iterabloom/hypergumbo/blob/dev/docs/adr/0047-catalogue-scope-and-user-visible-homes.md) ruling 9). The exceptions are an `-o` path you choose inside it, and the case in the last bullet of this list.
+- Writes its results under `~/.cache/hypergumbo/` (`$XDG_CACHE_HOME/hypergumbo/` if set), plus short-lived files in the system temp directory. It does not write into the repository it analyses ([ADR-0047](https://github.com/iterabloom/hypergumbo/blob/dev/docs/adr/0047-catalogue-scope-and-user-visible-homes.md) ruling 9). The exceptions are an `-o` path you choose inside it, and the case in the last bullet of this list. One command writes more than the file you name: `survey --out X.json` also writes `X.4k.json`, `X.16k.json` and `X.64k.json` (the same map compacted to those token budgets) and a directory `X.slices/` holding one slice per detected route handler, all beside `X.json`. `--no-sketch-fan-out --no-handler-slices` suppresses them, so exactly one file is written.
 - Runs `git` read-only (`rev-parse HEAD`, `rev-list --max-parents=0 HEAD`, `config --get remote.origin.url`). If they are installed, it also runs `gitleaks` to scan for secrets and `rust-analyzer --version`; the version check does not index anything.
 - Makes no network connection, unless you installed embeddings support (`install-embeddings`, `add-extras`, or `pip install 'hypergumbo[embeddings]'`). In that case the first sketch downloads two models (`microsoft/unixcoder-base` and `nomic-ai/modernbert-embed-base`) from huggingface.co into `~/.cache/huggingface/` (or `$HF_HOME`). Once both models are cached, later runs work offline. To stop the download, set `HF_HUB_OFFLINE=1`; the sketch then runs without embeddings. SECURITY.md's network claim still says downloads happen only through `install-embeddings`. That claim is wrong, and INV-gujus tracks it.
 - If a directory `~/hypergumbo` exists (for example, a clone of this repository), an interactive run asks once whether to write example config files into `~/hypergumbo/.hypergumbo-examples/`. It records your answer in `~/.local/state/hypergumbo/offers.json`. If you answer yes while analysing `~/hypergumbo` itself, that is a write into the analysed repository (INV-kuroj).
@@ -148,6 +148,7 @@ Read this before installing hypergumbo on a machine you care about. Each stateme
 
 1. **Self-claims.** [SECURITY.md](https://github.com/iterabloom/hypergumbo/blob/dev/SECURITY.md) lists 18 claims about what each group of commands may touch, and hypergumbo checks them by analysing its own source (`scripts/check-self-claims`). All 18 currently read `confirmed_with_caveats`. That means the analysis found no contradiction where it could see, and it names what it could not see: programs it launches, statements the repository made about itself, and the 70.6% of method calls whose receiver type it could not work out. In auditing terms this is a qualified opinion, not proof ([ADR-0016](https://github.com/iterabloom/hypergumbo/blob/dev/docs/adr/0016-io-boundary-analysis.md)). It covers the `hypergumbo` command only.
 2. **I/O allowlist.** `scripts/check-io-allowlist` is a separate scan that uses only the standard library. It finds every place in `packages/*/src`, tracker included, that writes or deletes a file, starts a process, opens a connection or a server, or loads a model. Each one must be listed with its purpose in [`docs/hypergumbo.io-allowlist.yaml`](https://github.com/iterabloom/hypergumbo/blob/dev/docs/hypergumbo.io-allowlist.yaml), and an unlisted one fails CI. The gate proves that every such place was reviewed. It does not prove that any of them is safe.
+3. **Observed I/O manifest.** At every release, `scripts/io-manifest` runs the installed `hypergumbo` over six pinned open-source repositories under `strace` and records every file write, delete and rename, every program started and every connection attempted, reduced to fifteen lines ([`docs/io-manifest/expected.txt`](https://github.com/iterabloom/hypergumbo/blob/dev/docs/io-manifest/expected.txt)). A line not seen at the previous release fails the build, and a write into the analysed repository or a network connection fails it regardless. This is the only one of the three checks that sees what dependencies and compiled extensions do, because it watches the process rather than reading the Python. It covers a default run with no extras installed, on those six repositories: the "every scenario we exercised" statement, not "every scenario".
 
 The allowlist gate currently records these open findings:
 
@@ -205,6 +206,7 @@ Useful flags:
 hypergumbo . -x                                # exclude test files (cleaner output)
 hypergumbo . --no-source                       # omit source code (included by default)
 hypergumbo . --no-progress                     # hide progress indicator (sketch/run only; on by default)
+HG_HEARTBEAT=10 hypergumbo .                   # stack heartbeat every 10s (default 30; 0 disables)
 hypergumbo io-boundaries --show-external-potential   # opt into the (large) external-potential bucket (text output)
 hypergumbo --help --all                        # comprehensive help for all commands
 ```

{hypergumbo-9.0.0 → hypergumbo-9.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "hypergumbo"
-version = "9.0.0"
+version = "9.2.0"
 description = "Local-first repo behavior map generator"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -19,10 +19,10 @@ classifiers = [
 ]
 dependencies = [
   # Meta-package that pulls in all hypergumbo components
-  "hypergumbo-core==9.0.0",
-  "hypergumbo-lang-mainstream==9.0.0",
-  "hypergumbo-lang-common==9.0.0",
-  "hypergumbo-lang-extended1==9.0.0",
+  "hypergumbo-core==9.2.0",
+  "hypergumbo-lang-mainstream==9.2.0",
+  "hypergumbo-lang-common==9.2.0",
+  "hypergumbo-lang-extended1==9.2.0",
 ]
 
 [project.optional-dependencies]
@@ -47,13 +47,13 @@ embeddings = [
 # Without this extra, --backend rust-analyzer hits the BUG-06 runtime gate.
 # Install with: pipx install 'hypergumbo[rust-analyzer]'
 rust-analyzer = [
-  "hypergumbo-lang-rust-analyzer==9.0.0",
+  "hypergumbo-lang-rust-analyzer==9.2.0",
 ]
 # SCIP-backed Python analysis via scip-python / pyright (WI-nanom). Executes
 # nothing from the analysed repository; the producer itself is an npm package:
 #   npm install -g @sourcegraph/scip-python@0.6.6
 scip-python = [
-  "hypergumbo-lang-scip-python==9.0.0",
+  "hypergumbo-lang-scip-python==9.2.0",
 ]
 
 [project.scripts]