hurdle-gate 0.3.1__tar.gz

hurdle_gate-0.3.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

hurdle_gate-0.3.1/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: hurdle-gate
+Version: 0.3.1
+Summary: Static-analysis gate for source↔test file existence mapping
+License-Expression: Apache-2.0
+Keywords: testing,test-coverage,static-analysis,ci,quality-gate
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Development Status :: 4 - Beta
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Dynamic: license-file
+
+# hurdle
+
+A source ↔ test **existence mapping** tool. A single-file executable that finds
+source files added without tests (Python 3 standard library only, zero external
+dependencies).
+
+**What it does** — decides from filename/path conventions alone whether each
+source file has a corresponding test, and reports the gaps (untested sources).
+Text is the default output; `--json` produces a machine-readable report.
+
+**What it does not do**
+- Does not **run** tests — existence only; whether tests pass is out of scope.
+- Does not measure **coverage** — this is a different (and far cheaper) signal
+  than line/branch coverage: "does this file have any test at all?"
+- Does not judge code **quality** — a test file that exists but is thin will
+  not be caught.
+
+## Installation
+
+```bash
+# Recommended: isolated install via pipx
+pipx install .
+
+# Development: venv + editable install (includes dev extras)
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e .[dev]
+
+# Environments where pip is unavailable (PEP 668 etc.): runs without installing
+PYTHONPATH=src python3 -m hurdle scan .
+```
+
+## Quick start
+
+```bash
+# 1) Full scan — gap report for the whole repository (use this to create a baseline)
+hurdle scan ~/study/kopia --json kopia.json
+
+# 2) diff mode — evaluate only sources new/changed vs. a base point (core of the local/CI gate)
+hurdle scan . --diff origin/main
+
+# 3) strict mode — fail (non-zero exit code) if any evaluated file has a gap
+hurdle scan . --diff origin/main --strict --config .hurdle.json
+```
+
+Reading the output: the report shows a per-file status (`matched` / `gap` /
+`unmapped` — files with unknown extensions are counted only as `unmapped` and
+excluded from language totals), each file's matching test and confidence
+(`exact`/`heuristic`), and per-language totals. Exit codes under `--strict`:
+no gaps = 0, gaps present = failure, runtime error (e.g. `--diff` outside a
+git repository) = 2. CI decides pass/fail from the strict-mode exit code.
+
+## Verdict rules (per language)
+
+| Language | Test-existence verdict | confidence |
+|---|---|---|
+| **go** | Package-level: an exact `{stem}_test.go` match wins first; otherwise covered if any `*_test.go` exists in the same package (directory) | exact |
+| **py** | Probes 4 pytest-convention candidate paths — beside the file / in a `tests/` directory × `test_{stem}.py` / `{stem}_test.py` combinations — plus variant names `tests/test_{stem}_*.py` and `tests/test_*_{stem}.py` (v0.2.0). `__init__.py` counts as a package marker and non-test files under `test_dirs` (default `tests`, `test`) count as test-support — both excluded rather than gapped (config: `strict_init`, `test_dirs`) | exact |
+| **ts/js** | Naming conventions: the `*.test.ts(x)` / `*.spec.ts(x)` families | exact |
+| **c / shell** | File-to-file mapping is impossible in trees like lustre (centralized `lustre/tests/` + `kunit/`), so coverage is aggregated per module/directory (heuristic). Listing module→test keywords in `module_map` improves accuracy | heuristic |
+
+## Configuration (.hurdle.json)
+
+Passed via `--config`. See `.hurdle.example.json` in this repository for a
+minimal example and `baselines/*.hurdle.json` for real-world ones.
+
+```jsonc
+{
+  "exclude": ["vendor/", "**/*_pb.go"],        // kept out of the scan
+  "allowlist": { "cmd/legacy/main.go": "thin wrapper; covered in pkg/" },
+  "module_map": { "lustre/osd-zfs": ["osd", "conf-sanity"] }
+}
+```
+
+| Key | Format | Description |
+|---|---|---|
+| `exclude` | array of strings | Directories are excluded wholesale with a trailing `/` in the name (`vendor/`). Everything else is an fnmatch pattern matched against full paths/filenames (`**/*_pb.go`) |
+| `allowlist` | relpath → reason string | Do not count this file as a gap (escape hatch). Checked **before exclude**, so a file with an explicit reason survives even broad exclude patterns. The reason stays on record in commit history |
+| `module_map` | module relpath → keyword array | Feeds the C/shell heuristic. List the test-suite keywords that cover a module (e.g. `["sanity", "conf-sanity"]`) and module coverage is looked up in the centralized tests/ directory |
+
+## Baseline → gate workflow
+
+The core design is a **ratchet**: existing gaps are frozen, and only new gaps
+are blocked.
+
+1. **Capture a baseline** — run a full scan, commit the resulting JSON gap
+   report (covering all existing code) to the repository. This becomes a
+   de-facto allowlist. The actual results of doing this for the kopia/lustre/
+   longhorn-manager/velero repositories are in [BASELINES.md](BASELINES.md)
+   and `baselines/*.json`.
+2. **Classify with config** — filter generated code (`*_pb.go` etc.), vendor,
+   and test-support code (`internal/testutil` etc.) via `exclude`/`allowlist`
+   so that only files with genuinely no corresponding test remain in the
+   baseline.
+3. **diff + strict gate** — in CI, `--diff origin/<base> --strict` judges only
+   the files changed now. Legacy gaps never show up in the diff and are
+   ignored; only new/modified files are forced to carry tests. The gap count
+   decreases monotonically.
+
+## CI integration
+
+Copy `ci/test-exist-gate.yml` to `.github/workflows/test-exist-gate.yml` in the
+target repository and follow the 4 steps in the comment block at the top of
+the file (swap the URL, commit the config, mark the check as required). The
+flow: `fetch-depth: 0` checkout → install hurdle → run
+`scan . --diff origin/base --strict --config .hurdle.json --json` → upload the
+report artifact even on failure (`if: always()`).
+
+## pre-commit local hook
+
+Copy `ci/pre-commit-hook.sh` to `.git/hooks/pre-commit`, or use this minimal
+3-line form:
+
+```bash
+#!/bin/sh
+[ -n "$(git diff --name-only --diff-filter=ACMR HEAD)" ] || exit 0
+exec hurdle scan . --diff HEAD --strict
+```
+
+## Limitations (honestly)
+
+- **It only checks file existence.** It never sees whether tests run, pass, or
+  assert anything meaningful. It is a minimal gate against "source added with
+  no test" — not a coverage replacement.
+- **Heuristic module verdicts can over- and under-count.** The module-aggregated
+  C/shell verdict depends on `module_map` keywords: keywords that are too
+  broad over-report coverage; a missing per-module suite under-reports it.
+  Treat the report's confidence markers as the trust boundary.
+- **The only escape hatch is the allowlist.** When a rule misjudges a file,
+  allowlisting it with a reason is the sole exception path — hiding it with
+  exclude removes it from the scan entirely and breaks gap tracking.
+
+## License
+
+Apache-2.0 — see the [LICENSE](LICENSE) file for the full text.
+
+## Universe coverage (`hurdle universe`)
+
+Beyond per-file test existence, hurdle can enforce coverage of a
+**defined universe** — a complete set of items every one of which must be
+either used, wildcard-covered, or explicitly allowlisted. The motivating
+case: CDP protocol commands/events (`protocol.json` defines the complete
+universe, so "missing something" is well-defined).
+
+```jsonc
+// .hurdle.json
+"universes": {
+  "cdp-commands": {
+    "items_file": "universes/cdp-commands.json",   // bare array or {"items":[], "meta":{}}
+    "include": ["src/**/*.py"],
+    "literal_shape": "^[A-Z][A-Za-z0-9]*\\.[a-zA-Z][A-Za-z0-9]+$",
+    "wildcard_patterns": ["\\.subscribe\\(\\s*\"({domain})\\.\\*\""],
+    "extra_usage": ["Page.javascriptDialogOpening"],
+    "allowlist": {"Tracing.*": "out of scope — low-level tracing"}
+  }
+}
+```
+
+```bash
+hurdle universe cdp-commands . --strict --json report.json
+```
+
+- Usage extraction collects shape-matched string literals (module
+  constants are picked up at their definition site) and intersects them
+  with the universe — universe membership itself disambiguates commands
+  vs events that share the `Domain.name` shape.
+- Statuses: `covered` / `wildcard` (a `Domain.*` subscription) /
+  `allowed` (fnmatch on item names, reason recorded) / `gap`.
+- `--strict` exits 1 on any gap that is not allowlisted — newly added
+  universe items cannot appear silently.

hurdle_gate-0.3.1/README.md

@@ -0,0 +1,169 @@
+# hurdle
+
+A source ↔ test **existence mapping** tool. A single-file executable that finds
+source files added without tests (Python 3 standard library only, zero external
+dependencies).
+
+**What it does** — decides from filename/path conventions alone whether each
+source file has a corresponding test, and reports the gaps (untested sources).
+Text is the default output; `--json` produces a machine-readable report.
+
+**What it does not do**
+- Does not **run** tests — existence only; whether tests pass is out of scope.
+- Does not measure **coverage** — this is a different (and far cheaper) signal
+  than line/branch coverage: "does this file have any test at all?"
+- Does not judge code **quality** — a test file that exists but is thin will
+  not be caught.
+
+## Installation
+
+```bash
+# Recommended: isolated install via pipx
+pipx install .
+
+# Development: venv + editable install (includes dev extras)
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e .[dev]
+
+# Environments where pip is unavailable (PEP 668 etc.): runs without installing
+PYTHONPATH=src python3 -m hurdle scan .
+```
+
+## Quick start
+
+```bash
+# 1) Full scan — gap report for the whole repository (use this to create a baseline)
+hurdle scan ~/study/kopia --json kopia.json
+
+# 2) diff mode — evaluate only sources new/changed vs. a base point (core of the local/CI gate)
+hurdle scan . --diff origin/main
+
+# 3) strict mode — fail (non-zero exit code) if any evaluated file has a gap
+hurdle scan . --diff origin/main --strict --config .hurdle.json
+```
+
+Reading the output: the report shows a per-file status (`matched` / `gap` /
+`unmapped` — files with unknown extensions are counted only as `unmapped` and
+excluded from language totals), each file's matching test and confidence
+(`exact`/`heuristic`), and per-language totals. Exit codes under `--strict`:
+no gaps = 0, gaps present = failure, runtime error (e.g. `--diff` outside a
+git repository) = 2. CI decides pass/fail from the strict-mode exit code.
+
+## Verdict rules (per language)
+
+| Language | Test-existence verdict | confidence |
+|---|---|---|
+| **go** | Package-level: an exact `{stem}_test.go` match wins first; otherwise covered if any `*_test.go` exists in the same package (directory) | exact |
+| **py** | Probes 4 pytest-convention candidate paths — beside the file / in a `tests/` directory × `test_{stem}.py` / `{stem}_test.py` combinations — plus variant names `tests/test_{stem}_*.py` and `tests/test_*_{stem}.py` (v0.2.0). `__init__.py` counts as a package marker and non-test files under `test_dirs` (default `tests`, `test`) count as test-support — both excluded rather than gapped (config: `strict_init`, `test_dirs`) | exact |
+| **ts/js** | Naming conventions: the `*.test.ts(x)` / `*.spec.ts(x)` families | exact |
+| **c / shell** | File-to-file mapping is impossible in trees like lustre (centralized `lustre/tests/` + `kunit/`), so coverage is aggregated per module/directory (heuristic). Listing module→test keywords in `module_map` improves accuracy | heuristic |
+
+## Configuration (.hurdle.json)
+
+Passed via `--config`. See `.hurdle.example.json` in this repository for a
+minimal example and `baselines/*.hurdle.json` for real-world ones.
+
+```jsonc
+{
+  "exclude": ["vendor/", "**/*_pb.go"],        // kept out of the scan
+  "allowlist": { "cmd/legacy/main.go": "thin wrapper; covered in pkg/" },
+  "module_map": { "lustre/osd-zfs": ["osd", "conf-sanity"] }
+}
+```
+
+| Key | Format | Description |
+|---|---|---|
+| `exclude` | array of strings | Directories are excluded wholesale with a trailing `/` in the name (`vendor/`). Everything else is an fnmatch pattern matched against full paths/filenames (`**/*_pb.go`) |
+| `allowlist` | relpath → reason string | Do not count this file as a gap (escape hatch). Checked **before exclude**, so a file with an explicit reason survives even broad exclude patterns. The reason stays on record in commit history |
+| `module_map` | module relpath → keyword array | Feeds the C/shell heuristic. List the test-suite keywords that cover a module (e.g. `["sanity", "conf-sanity"]`) and module coverage is looked up in the centralized tests/ directory |
+
+## Baseline → gate workflow
+
+The core design is a **ratchet**: existing gaps are frozen, and only new gaps
+are blocked.
+
+1. **Capture a baseline** — run a full scan, commit the resulting JSON gap
+   report (covering all existing code) to the repository. This becomes a
+   de-facto allowlist. The actual results of doing this for the kopia/lustre/
+   longhorn-manager/velero repositories are in [BASELINES.md](BASELINES.md)
+   and `baselines/*.json`.
+2. **Classify with config** — filter generated code (`*_pb.go` etc.), vendor,
+   and test-support code (`internal/testutil` etc.) via `exclude`/`allowlist`
+   so that only files with genuinely no corresponding test remain in the
+   baseline.
+3. **diff + strict gate** — in CI, `--diff origin/<base> --strict` judges only
+   the files changed now. Legacy gaps never show up in the diff and are
+   ignored; only new/modified files are forced to carry tests. The gap count
+   decreases monotonically.
+
+## CI integration
+
+Copy `ci/test-exist-gate.yml` to `.github/workflows/test-exist-gate.yml` in the
+target repository and follow the 4 steps in the comment block at the top of
+the file (swap the URL, commit the config, mark the check as required). The
+flow: `fetch-depth: 0` checkout → install hurdle → run
+`scan . --diff origin/base --strict --config .hurdle.json --json` → upload the
+report artifact even on failure (`if: always()`).
+
+## pre-commit local hook
+
+Copy `ci/pre-commit-hook.sh` to `.git/hooks/pre-commit`, or use this minimal
+3-line form:
+
+```bash
+#!/bin/sh
+[ -n "$(git diff --name-only --diff-filter=ACMR HEAD)" ] || exit 0
+exec hurdle scan . --diff HEAD --strict
+```
+
+## Limitations (honestly)
+
+- **It only checks file existence.** It never sees whether tests run, pass, or
+  assert anything meaningful. It is a minimal gate against "source added with
+  no test" — not a coverage replacement.
+- **Heuristic module verdicts can over- and under-count.** The module-aggregated
+  C/shell verdict depends on `module_map` keywords: keywords that are too
+  broad over-report coverage; a missing per-module suite under-reports it.
+  Treat the report's confidence markers as the trust boundary.
+- **The only escape hatch is the allowlist.** When a rule misjudges a file,
+  allowlisting it with a reason is the sole exception path — hiding it with
+  exclude removes it from the scan entirely and breaks gap tracking.
+
+## License
+
+Apache-2.0 — see the [LICENSE](LICENSE) file for the full text.
+
+## Universe coverage (`hurdle universe`)
+
+Beyond per-file test existence, hurdle can enforce coverage of a
+**defined universe** — a complete set of items every one of which must be
+either used, wildcard-covered, or explicitly allowlisted. The motivating
+case: CDP protocol commands/events (`protocol.json` defines the complete
+universe, so "missing something" is well-defined).
+
+```jsonc
+// .hurdle.json
+"universes": {
+  "cdp-commands": {
+    "items_file": "universes/cdp-commands.json",   // bare array or {"items":[], "meta":{}}
+    "include": ["src/**/*.py"],
+    "literal_shape": "^[A-Z][A-Za-z0-9]*\\.[a-zA-Z][A-Za-z0-9]+$",
+    "wildcard_patterns": ["\\.subscribe\\(\\s*\"({domain})\\.\\*\""],
+    "extra_usage": ["Page.javascriptDialogOpening"],
+    "allowlist": {"Tracing.*": "out of scope — low-level tracing"}
+  }
+}
+```
+
+```bash
+hurdle universe cdp-commands . --strict --json report.json
+```
+
+- Usage extraction collects shape-matched string literals (module
+  constants are picked up at their definition site) and intersects them
+  with the universe — universe membership itself disambiguates commands
+  vs events that share the `Domain.name` shape.
+- Statuses: `covered` / `wildcard` (a `Domain.*` subscription) /
+  `allowed` (fnmatch on item names, reason recorded) / `gap`.
+- `--strict` exits 1 on any gap that is not allowlisted — newly added
+  universe items cannot appear silently.

hurdle_gate-0.3.1/pyproject.toml

@@ -0,0 +1,32 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "hurdle-gate"
+version = "0.3.1"
+description = "Static-analysis gate for source↔test file existence mapping"
+readme = "README.md"
+requires-python = ">=3.9"
+license = "Apache-2.0"
+keywords = ["testing", "test-coverage", "static-analysis", "ci", "quality-gate"]
+classifiers = [
+    "Programming Language :: Python :: 3",
+    "Topic :: Software Development :: Quality Assurance",
+    "Development Status :: 4 - Beta",
+]
+
+[project.optional-dependencies]
+dev = ["pytest>=7"]
+
+[project.scripts]
+hurdle = "hurdle.cli:main"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+packages = ["hurdle"]
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]
+testpaths = ["tests"]
+addopts = "--ignore=tests/fixtures --ignore=tests/fixtures02 --ignore=tests/fixtures03"

hurdle_gate-0.3.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

hurdle_gate-0.3.1/src/hurdle/__init__.py

@@ -0,0 +1,3 @@
+"""hurdle — static-analysis gate for source↔test file existence mapping."""
+
+__version__ = "0.3.1"

hurdle_gate-0.3.1/src/hurdle/__main__.py

@@ -0,0 +1,5 @@
+import sys
+
+from hurdle.cli import main
+
+sys.exit(main())