foretop-ebb 0.1.0__tar.gz

foretop_ebb-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 2026 the foretop authors
+
+   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.

foretop_ebb-0.1.0/PKG-INFO

@@ -0,0 +1,175 @@
+Metadata-Version: 2.4
+Name: foretop-ebb
+Version: 0.1.0
+Summary: Tells an engineering team which repos, jobs, prompts and owners break when an AI provider retires a model — before the deadline becomes an outage.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Dist: typer>=0.15
+Requires-Dist: rich>=13.9
+Requires-Dist: pathspec>=0.12
+Requires-Dist: pydantic>=2.9
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: httpx>=0.28
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+
+# ebb
+
+> Tells an engineering team which repos, jobs, prompts and owners break when an AI provider
+> retires a model — before the deadline becomes an outage.
+
+A provider announces a retirement date. Somewhere in your repos, Airflow DAGs, Terraform
+variables and prompt templates there's a hardcoded model string nobody remembers. `ebb` finds
+every one of them, joins it to the provider's real retirement date, and tells you who owns it.
+
+## Install and run
+
+```
+uvx foretop-ebb scan .
+```
+
+No config, no account, no network call beyond installing the package — detection is entirely
+local and deterministic, matched against a versioned registry bundled in the package. Add
+`--format sarif` for GitHub Code Scanning, `--format markdown` for a PR comment, or
+`--fail-on critical` to make CI fail when something's actually urgent (see below for exit
+codes). `ebb scan --help` lists everything.
+
+## Use it as a GitHub Action
+
+```yaml
+- uses: foretop-dev/ebb@main
+  with:
+    fail-on: critical # info | low | medium | high | critical; empty string = report-only
+```
+
+Annotates the pull request inline and upserts one summary comment (finds its own previous
+comment by an HTML marker and edits it — never posts a second one on repeat pushes). Needs
+`permissions: pull-requests: write` in the calling workflow.
+
+## License
+
+Apache-2.0. This file tracks build status below; the source-of-truth product spec lives in the
+private monorepo this is mirrored from (see `scripts/sync-mirror.sh` there).
+
+## Status
+
+**Slice 1** (Session 3): a Typer CLI that walks a repository and detects model-identifier-shaped
+strings in Python, TypeScript, YAML, TOML, JSON, Terraform, Dockerfiles and Jupyter notebooks.
+Deterministic pattern matching only.
+
+```
+uv run --package foretop-ebb ebb scan <path>
+```
+
+Detectors are pure functions `(path, content) -> list[RawMatch]`, registered in a table in
+`src/ebb/detect/registry.py`. Adding a language means one new detector file plus one new fixture
+under `tests/fixtures/` — nothing else changes.
+
+**Registry (Session 4):** `src/ebb/registry/` loads `src/ebb/registries/retirements/*.yaml` —
+real retirement data for OpenAI, Anthropic and Google, sourced from each provider's live
+deprecations
+page, never invented. `RegistryEntry` requires `source_url` and `verified_at`; a record missing
+either fails the whole load (`RegistryLoadError`) rather than silently dropping it. Loading warns
+(`StaleRegistryEntryWarning`) on any entry verified more than 90 days ago. `resolve(raw_text,
+registry)` is an exact-match lookup against `canonical_id` and curated `aliases` only — no
+prefix or fuzzy matching, so an uncurated floating alias (`claude-3-opus-latest`) resolves to
+`Unknown`, never to whatever entry happens to share a prefix. `registry.version` is a
+content-derived hash, stamped onto every `Finding.rule_version` (Session 6).
+
+**Canonicalisation (Session 5):** `src/ebb/canonicalize.py` — pure, isolated, no registry lookup,
+no I/O. Collapses AWS Bedrock cross-Region inference profile IDs and vendor-prefixed model IDs
+(`us.anthropic.claude-3-haiku-20240307-v1:0` — the literal example from AWS's own docs) and GCP
+Vertex AI publisher-model resource paths (`publishers/{vendor}/models/{id}`, optionally
+`projects/.../locations/...`-prefixed) plus their respective `-v{N}:{M}` / `@{N}` version
+suffixes, down to the bare dated-snapshot id a provider's own API would use directly. Property-
+tested with Hypothesis for idempotency and round-tripping, per the plan's explicit requirement.
+Deliberately does **not** strip `-latest` / `-preview` suffixes — some of those are curated as
+their own whole registry entries (`chatgpt-4o-latest`), and stripping would silently break their
+resolution; an uncurated floating alias stays exactly as unresolvable after canonicalisation as
+before, which is correct (see Session 4's `resolve()` tests).
+
+**Owner attribution (Session 5):** `src/ebb/owner.py` — CODEOWNERS first (reusing `pathspec`'s
+gitignore matching, since GitHub documents CODEOWNERS pattern syntax as the same rules; last
+matching rule in the file wins, per GitHub's own precedence), `git blame` on the specific line as
+fallback. Returns `None` rather than raising when neither source has an answer — a file with no
+declared owner and no git history is a legitimate, common outcome.
+
+**Findings, verdicts and renderers (Session 6):** the whole pipeline is wired together for the
+first time — `src/ebb/build_findings.py` runs walk → detect → `canonicalize()` → `resolve()` →
+`find_owner()` → verdict/severity/confidence (`src/ebb/verdict.py`) → a `Finding`
+(`src/ebb/finding.py`, the SUITE_ARCHITECTURE.md §3 model: `evidence` can never be empty,
+enforced by a Pydantic validator, and `unknown` is a first-class `Verdict`, not a fallback).
+Identity is `sha256(canonical_id | file_path | symbol)[:16]` — deliberately excludes the line
+number; `symbol` is a lightweight, language-agnostic "nearest assignment target" heuristic
+(`detect/scan_text.nearest_symbol`), not full per-language AST scoping, which was out of scope
+for this session.
+
+Verdict logic: `unknown` for anything `resolve()` couldn't verify; for a verified entry, no
+shutdown date on record is `clear`, a shutdown date already passed is `break` (critical severity
+— it's failing now, not eventually), a future one is `drift` (severity scales with days
+remaining: ≤30d high, ≤90d medium, else low).
+
+```
+uv run --package foretop-ebb ebb scan <path> [--format table|markdown|json|sarif] [--fail-on SEVERITY]
+```
+
+Four renderers (`src/ebb/render/`): terminal (Rich, colour-capable — `--format table`, the
+default), Markdown (for PR comments), JSON, and SARIF 2.1.0. The SARIF renderer is validated in
+tests against the real schema fetched from OASIS's own repo (committed at
+`tests/fixtures/sarif-schema-2.1.0.json`), not written from memory. `--fail-on SEVERITY` makes
+exit code 1 when any finding meets or exceeds that severity; exit codes are an API (specs/ebb.md
+§6) — 0 clean, 1 threshold met, 2 internal error (bad `--format`/`--fail-on`, registry failed to
+load) — and these are never conflated.
+
+`--registry-dir` overrides where registry YAML is loaded from; the default is the copy bundled
+inside the `foretop-ebb` distribution itself (`src/ebb/registries/retirements/`, resolved via
+`importlib.resources` — see Session 8 below), so it works identically whether ebb is running
+from an editable monorepo checkout or a `pip`/`uvx`-installed wheel.
+
+Known gap (detection is not the issue — Session 7's golden corpus scores every detector at
+1.000 precision/recall): `canonicalize()` only strips AWS Bedrock and GCP Vertex AI wrapper
+syntax, not a generic OpenAI-style dated-snapshot suffix. `gpt-4-turbo-2024-04-09` is detected
+correctly as a whole match, but `canonicalize()` passes it through unchanged, and the registry
+has no `gpt-4-turbo-2024-04-09` entry or alias — only bare `gpt-4-turbo` — so it resolves
+`unknown` instead of joining to the real tracked entry. Not fixed here deliberately: generic
+snapshot-suffix stripping has the same failure mode `canonicalize()` already refuses for
+`-latest`/`-preview` (some dated suffixes are themselves curated as distinct whole entries,
+and blind-stripping would break their resolution) — it needs the same care as that decision,
+not a quick patch bolted onto Session 8's actual scope.
+
+**Session 10 (the extraction session):** `packages/keel` now exists. `src/ebb/walk.py`'s
+gitignore-aware file walker (`is_binary`/`iter_files`/the gitignore matching) turned out to be
+byte-identical to the copy telltale had made of it in Session 9, so it moved to
+`keel.collect.walk` — the first and, for now, only thing in `keel`. `src/ebb/walk.py` now
+imports it and keeps only `scan_repo`, ebb's own detector-dispatch logic. This is deliberately
+the *only* extraction so far (SUITE_ARCHITECTURE.md §8's "premature platformisation" warning);
+`packages/keel/README.md` has the full identical-vs-similar reasoning, including a real
+packaging gap it left behind: `apps/ebb`'s public mirror (Session 8, `foretop-dev/ebb`) isn't
+yet updated to vendor or depend on `keel`, so it must not be re-synced and republished until
+that's resolved.
+
+**The accuracy floor (Session 7):** `tests/golden/` holds 30 hand-labelled repository fixtures,
+3–5 per detector, covering all 8 detectors (`python`, `typescript`, `yaml`, `json`, `toml`,
+`terraform`, `dockerfile`, `notebook`). Ground truth lives in `tests/golden_manifest.yaml` — kept
+*outside* `tests/golden/` on purpose: a ground-truth file with model-id strings in it living
+*inside* the scanned tree would itself get scanned and picked up as a spurious match. Labels
+reflect real, current OpenAI/Anthropic/Google model-id shapes, not what the detector already
+happened to catch — the entire point is that a gap between the two is a real bug, not a fixture
+mistake.
+
+`tests/unit/test_golden_corpus.py` (`make accuracy` to run it directly) scores every detector
+**independently** — precision and recall are never pooled into one aggregate, because an average
+across 8 detectors can hide one that's badly broken. The floor is precision ≥ 0.95 and recall ≥
+0.85 per detector; a second test asserts every detector has at least one pure-decoy fixture (zero
+expected matches), so a detector that's simply never tempted can't pass on a technicality.
+
+First run against the corpus failed 6 of 8 detectors on real gaps: `patterns.py` had no o3/o4
+family at all (only `o1`), no `gpt-5` family, and `gpt-4.1` silently matched as the shorter,
+wrong `gpt-4` (alternation tries branches in order — with bare `4` before `4\.\d+`, "gpt-4.1"
+matched only "gpt-4" and quietly dropped the `.1` that makes it a different model). Fixed in
+`patterns.py` by adding the missing families and reordering the OpenAI alternation so the
+longer, more specific branch is tried first — not by loosening the 0.95/0.85 floor, which never
+moved. Also extended the OpenAI and Gemini date/qualifier suffixes to cover the bare-4-digit
+snapshot convention (`gpt-4-0125-preview`) and `-preview`/`-exp` qualifiers
+(`gemini-3-pro-preview`), both real, both previously truncating to a shorter, wrong match rather
+than the full one. All 8 detectors now score 1.000 precision / 1.000 recall against the corpus.

foretop_ebb-0.1.0/README.md

@@ -0,0 +1,160 @@
+# ebb
+
+> Tells an engineering team which repos, jobs, prompts and owners break when an AI provider
+> retires a model — before the deadline becomes an outage.
+
+A provider announces a retirement date. Somewhere in your repos, Airflow DAGs, Terraform
+variables and prompt templates there's a hardcoded model string nobody remembers. `ebb` finds
+every one of them, joins it to the provider's real retirement date, and tells you who owns it.
+
+## Install and run
+
+```
+uvx foretop-ebb scan .
+```
+
+No config, no account, no network call beyond installing the package — detection is entirely
+local and deterministic, matched against a versioned registry bundled in the package. Add
+`--format sarif` for GitHub Code Scanning, `--format markdown` for a PR comment, or
+`--fail-on critical` to make CI fail when something's actually urgent (see below for exit
+codes). `ebb scan --help` lists everything.
+
+## Use it as a GitHub Action
+
+```yaml
+- uses: foretop-dev/ebb@main
+  with:
+    fail-on: critical # info | low | medium | high | critical; empty string = report-only
+```
+
+Annotates the pull request inline and upserts one summary comment (finds its own previous
+comment by an HTML marker and edits it — never posts a second one on repeat pushes). Needs
+`permissions: pull-requests: write` in the calling workflow.
+
+## License
+
+Apache-2.0. This file tracks build status below; the source-of-truth product spec lives in the
+private monorepo this is mirrored from (see `scripts/sync-mirror.sh` there).
+
+## Status
+
+**Slice 1** (Session 3): a Typer CLI that walks a repository and detects model-identifier-shaped
+strings in Python, TypeScript, YAML, TOML, JSON, Terraform, Dockerfiles and Jupyter notebooks.
+Deterministic pattern matching only.
+
+```
+uv run --package foretop-ebb ebb scan <path>
+```
+
+Detectors are pure functions `(path, content) -> list[RawMatch]`, registered in a table in
+`src/ebb/detect/registry.py`. Adding a language means one new detector file plus one new fixture
+under `tests/fixtures/` — nothing else changes.
+
+**Registry (Session 4):** `src/ebb/registry/` loads `src/ebb/registries/retirements/*.yaml` —
+real retirement data for OpenAI, Anthropic and Google, sourced from each provider's live
+deprecations
+page, never invented. `RegistryEntry` requires `source_url` and `verified_at`; a record missing
+either fails the whole load (`RegistryLoadError`) rather than silently dropping it. Loading warns
+(`StaleRegistryEntryWarning`) on any entry verified more than 90 days ago. `resolve(raw_text,
+registry)` is an exact-match lookup against `canonical_id` and curated `aliases` only — no
+prefix or fuzzy matching, so an uncurated floating alias (`claude-3-opus-latest`) resolves to
+`Unknown`, never to whatever entry happens to share a prefix. `registry.version` is a
+content-derived hash, stamped onto every `Finding.rule_version` (Session 6).
+
+**Canonicalisation (Session 5):** `src/ebb/canonicalize.py` — pure, isolated, no registry lookup,
+no I/O. Collapses AWS Bedrock cross-Region inference profile IDs and vendor-prefixed model IDs
+(`us.anthropic.claude-3-haiku-20240307-v1:0` — the literal example from AWS's own docs) and GCP
+Vertex AI publisher-model resource paths (`publishers/{vendor}/models/{id}`, optionally
+`projects/.../locations/...`-prefixed) plus their respective `-v{N}:{M}` / `@{N}` version
+suffixes, down to the bare dated-snapshot id a provider's own API would use directly. Property-
+tested with Hypothesis for idempotency and round-tripping, per the plan's explicit requirement.
+Deliberately does **not** strip `-latest` / `-preview` suffixes — some of those are curated as
+their own whole registry entries (`chatgpt-4o-latest`), and stripping would silently break their
+resolution; an uncurated floating alias stays exactly as unresolvable after canonicalisation as
+before, which is correct (see Session 4's `resolve()` tests).
+
+**Owner attribution (Session 5):** `src/ebb/owner.py` — CODEOWNERS first (reusing `pathspec`'s
+gitignore matching, since GitHub documents CODEOWNERS pattern syntax as the same rules; last
+matching rule in the file wins, per GitHub's own precedence), `git blame` on the specific line as
+fallback. Returns `None` rather than raising when neither source has an answer — a file with no
+declared owner and no git history is a legitimate, common outcome.
+
+**Findings, verdicts and renderers (Session 6):** the whole pipeline is wired together for the
+first time — `src/ebb/build_findings.py` runs walk → detect → `canonicalize()` → `resolve()` →
+`find_owner()` → verdict/severity/confidence (`src/ebb/verdict.py`) → a `Finding`
+(`src/ebb/finding.py`, the SUITE_ARCHITECTURE.md §3 model: `evidence` can never be empty,
+enforced by a Pydantic validator, and `unknown` is a first-class `Verdict`, not a fallback).
+Identity is `sha256(canonical_id | file_path | symbol)[:16]` — deliberately excludes the line
+number; `symbol` is a lightweight, language-agnostic "nearest assignment target" heuristic
+(`detect/scan_text.nearest_symbol`), not full per-language AST scoping, which was out of scope
+for this session.
+
+Verdict logic: `unknown` for anything `resolve()` couldn't verify; for a verified entry, no
+shutdown date on record is `clear`, a shutdown date already passed is `break` (critical severity
+— it's failing now, not eventually), a future one is `drift` (severity scales with days
+remaining: ≤30d high, ≤90d medium, else low).
+
+```
+uv run --package foretop-ebb ebb scan <path> [--format table|markdown|json|sarif] [--fail-on SEVERITY]
+```
+
+Four renderers (`src/ebb/render/`): terminal (Rich, colour-capable — `--format table`, the
+default), Markdown (for PR comments), JSON, and SARIF 2.1.0. The SARIF renderer is validated in
+tests against the real schema fetched from OASIS's own repo (committed at
+`tests/fixtures/sarif-schema-2.1.0.json`), not written from memory. `--fail-on SEVERITY` makes
+exit code 1 when any finding meets or exceeds that severity; exit codes are an API (specs/ebb.md
+§6) — 0 clean, 1 threshold met, 2 internal error (bad `--format`/`--fail-on`, registry failed to
+load) — and these are never conflated.
+
+`--registry-dir` overrides where registry YAML is loaded from; the default is the copy bundled
+inside the `foretop-ebb` distribution itself (`src/ebb/registries/retirements/`, resolved via
+`importlib.resources` — see Session 8 below), so it works identically whether ebb is running
+from an editable monorepo checkout or a `pip`/`uvx`-installed wheel.
+
+Known gap (detection is not the issue — Session 7's golden corpus scores every detector at
+1.000 precision/recall): `canonicalize()` only strips AWS Bedrock and GCP Vertex AI wrapper
+syntax, not a generic OpenAI-style dated-snapshot suffix. `gpt-4-turbo-2024-04-09` is detected
+correctly as a whole match, but `canonicalize()` passes it through unchanged, and the registry
+has no `gpt-4-turbo-2024-04-09` entry or alias — only bare `gpt-4-turbo` — so it resolves
+`unknown` instead of joining to the real tracked entry. Not fixed here deliberately: generic
+snapshot-suffix stripping has the same failure mode `canonicalize()` already refuses for
+`-latest`/`-preview` (some dated suffixes are themselves curated as distinct whole entries,
+and blind-stripping would break their resolution) — it needs the same care as that decision,
+not a quick patch bolted onto Session 8's actual scope.
+
+**Session 10 (the extraction session):** `packages/keel` now exists. `src/ebb/walk.py`'s
+gitignore-aware file walker (`is_binary`/`iter_files`/the gitignore matching) turned out to be
+byte-identical to the copy telltale had made of it in Session 9, so it moved to
+`keel.collect.walk` — the first and, for now, only thing in `keel`. `src/ebb/walk.py` now
+imports it and keeps only `scan_repo`, ebb's own detector-dispatch logic. This is deliberately
+the *only* extraction so far (SUITE_ARCHITECTURE.md §8's "premature platformisation" warning);
+`packages/keel/README.md` has the full identical-vs-similar reasoning, including a real
+packaging gap it left behind: `apps/ebb`'s public mirror (Session 8, `foretop-dev/ebb`) isn't
+yet updated to vendor or depend on `keel`, so it must not be re-synced and republished until
+that's resolved.
+
+**The accuracy floor (Session 7):** `tests/golden/` holds 30 hand-labelled repository fixtures,
+3–5 per detector, covering all 8 detectors (`python`, `typescript`, `yaml`, `json`, `toml`,
+`terraform`, `dockerfile`, `notebook`). Ground truth lives in `tests/golden_manifest.yaml` — kept
+*outside* `tests/golden/` on purpose: a ground-truth file with model-id strings in it living
+*inside* the scanned tree would itself get scanned and picked up as a spurious match. Labels
+reflect real, current OpenAI/Anthropic/Google model-id shapes, not what the detector already
+happened to catch — the entire point is that a gap between the two is a real bug, not a fixture
+mistake.
+
+`tests/unit/test_golden_corpus.py` (`make accuracy` to run it directly) scores every detector
+**independently** — precision and recall are never pooled into one aggregate, because an average
+across 8 detectors can hide one that's badly broken. The floor is precision ≥ 0.95 and recall ≥
+0.85 per detector; a second test asserts every detector has at least one pure-decoy fixture (zero
+expected matches), so a detector that's simply never tempted can't pass on a technicality.
+
+First run against the corpus failed 6 of 8 detectors on real gaps: `patterns.py` had no o3/o4
+family at all (only `o1`), no `gpt-5` family, and `gpt-4.1` silently matched as the shorter,
+wrong `gpt-4` (alternation tries branches in order — with bare `4` before `4\.\d+`, "gpt-4.1"
+matched only "gpt-4" and quietly dropped the `.1` that makes it a different model). Fixed in
+`patterns.py` by adding the missing families and reordering the OpenAI alternation so the
+longer, more specific branch is tried first — not by loosening the 0.95/0.85 floor, which never
+moved. Also extended the OpenAI and Gemini date/qualifier suffixes to cover the bare-4-digit
+snapshot convention (`gpt-4-0125-preview`) and `-preview`/`-exp` qualifiers
+(`gemini-3-pro-preview`), both real, both previously truncating to a shorter, wrong match rather
+than the full one. All 8 detectors now score 1.000 precision / 1.000 recall against the corpus.

foretop_ebb-0.1.0/pyproject.toml

@@ -0,0 +1,74 @@
+[project]
+name = "foretop-ebb"
+version = "0.1.0"
+description = "Tells an engineering team which repos, jobs, prompts and owners break when an AI provider retires a model — before the deadline becomes an outage."
+readme = "README.md"
+requires-python = ">=3.12"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+dependencies = [
+    "typer>=0.15",
+    "rich>=13.9",
+    "pathspec>=0.12",
+    "pydantic>=2.9",
+    "pyyaml>=6.0",
+    "httpx>=0.28",
+]
+
+[project.scripts]
+ebb = "ebb.__main__:app"
+foretop-ebb = "ebb.__main__:app"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.3",
+    "types-pyyaml>=6.0",
+    "hypothesis>=6.115",
+    "jsonschema>=4.23",
+    "mypy>=2.3.0",
+    "ruff>=0.16.2",
+]
+
+[tool.uv.build-backend]
+module-name = [
+    "ebb",
+    "keel",
+]
+
+[tool.ruff]
+line-length = 100
+target-version = "py312"
+extend-exclude = [
+    "tests/fixtures",
+    "tests/golden",
+]
+
+[tool.ruff.lint]
+select = [
+    "E",
+    "F",
+    "I",
+    "N",
+    "UP",
+    "B",
+    "A",
+    "C4",
+    "SIM",
+    "TCH",
+    "RUF",
+]
+
+[tool.ruff.lint.isort]
+known-first-party = ["ebb"]
+known-third-party = ["keel"]
+
+[tool.mypy]
+strict = true
+python_version = "3.12"
+
+[tool.pytest.ini_options]
+addopts = "-ra"
+
+[build-system]
+requires = ["uv_build>=0.11.32,<0.12.0"]
+build-backend = "uv_build"