foretop-telltale 0.1.0__tar.gz

foretop_telltale-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_telltale-0.1.0/PKG-INFO

@@ -0,0 +1,354 @@
+Metadata-Version: 2.4
+Name: foretop-telltale
+Version: 0.1.0
+Summary: Compares an OpenAPI contract with the telemetry a service actually emits, and produces a route-by-route gap list before an incident finds it for you.
+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: pyyaml>=6.0
+Requires-Dist: pydantic>=2.9
+Requires-Dist: httpx>=0.28
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+
+# telltale
+
+> Compares an OpenAPI contract with the telemetry a service actually emits, and produces a
+> route-by-route gap list before an incident finds it for you.
+
+An OpenAPI spec says a route exists. Somewhere a Prometheus alert, an OTel Collector pipeline,
+or a Grafana dashboard is supposed to be watching it — or isn't, and nobody notices until the
+incident. `telltale` compares the two and tells you which routes (and which of their
+documented 4xx/5xx failures specifically) have no telemetry at all.
+
+## Install and run
+
+```
+uvx foretop-telltale check .
+```
+
+No config, no account, no network call beyond installing the package — autodetects an OpenAPI
+document at the repo root and walks the repo for Prometheus alert rules, an OTel Collector
+config, and Grafana dashboards, entirely local. Add `--base origin/main` to fail only when
+coverage that existed at the merge base is gone now (never an absolute threshold — see DEC-04
+below), or `--format markdown`/`--format annotations` for the same output a PR comment or
+GitHub annotation would use. `telltale check --help` lists everything.
+
+## Use it as a GitHub Action
+
+```yaml
+- uses: foretop-dev/telltale@main
+  with:
+    base: ${{ github.event.pull_request.base.sha }} # default; empty string disables the gate
+```
+
+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 9): OpenAPI parser + Prometheus alerting-rule parser + the matcher +
+a terminal coverage matrix, run against one fixture service. No network, no DB.
+
+**Slice 2, part 1** (Session 11): OTel Collector config parser + Grafana dashboard parser,
+extending real coverage to all four signal dimensions (`log`/`metric`/`trace`/`alert`) —
+every column in the matrix now has at least one real extractor behind it, none are
+permanently `ambiguous` by construction anymore (see below for what `ambiguous` still means).
+
+**Slice 3 (Session 12): the error-mode dimension** — DEC-03's own words, "the actual
+differentiator, do not skip it." Every route-level cell now has siblings, one per documented
+4xx/5xx response code (`src/telltale/response_code.py` normalizes both OpenAPI's "5XX"
+wildcard and specific codes like "404" into one comparable space) — the coverage question
+becomes not just "does this route have an alert" but "does *this specific documented
+failure* have one." `telltale check` now renders two tables: route-level, then error-mode
+(only when at least one route documents a 4xx/5xx code).
+
+**Slice 4, part 1 (Session 13): the regression-vs-merge-base gate** — DEC-04: "Fail on
+regression... vs the merge base. Absolute thresholds get disabled on day two of adoption." No
+`--fail-on <threshold>` flag exists here on purpose (unlike ebb's) — that was a deliberate
+choice as far back as Session 9's CLI, not an oversight filled in later.
+
+```
+telltale check <path> --base origin/main
+```
+
+Computes the merge base of the current checkout and `--base` (`git merge-base HEAD <ref>` —
+the commit where they diverged, not `<ref>`'s current tip, which can have moved since a PR
+branched: `src/telltale/git_ref.py`), materializes it into a real temporary `git worktree`
+(so the ordinary gitignore-aware walker sees exactly what a normal checkout would — never a
+bare `git show`/tarball extraction), runs the full pipeline against it, and diffs the two
+matrices (`src/telltale/regression.py`, pure — no I/O, no git). Exit 1 only if something that
+was `present` at the merge base is not `present` now, at either granularity (route-level or a
+specific error mode) — never on an absolute percentage or count. `absent → present` is an
+improvement, not a regression; `ambiguous → absent` (a new extractor started running and found
+nothing) is new information, not a loss; a route added or removed entirely is a spec change,
+not a coverage regression.
+
+Handles being run from a subdirectory of a larger repository correctly — `git worktree add`
+always materializes the *whole* repo, never a subtree, so `run_check_at_merge_base` computes
+the offset between the given path and the repo's actual toplevel once (`git_ref.toplevel()`)
+and re-applies it inside the new worktree. An earlier version of this didn't do that and
+happened to pass every test anyway, because every test so far had pointed `--base` straight at
+a repo's own root — caught by testing the monorepo case explicitly, then confirmed against
+this actual repository (`telltale check apps/telltale/tests/fixtures/fixture_service --base
+HEAD`, run for real, not just in pytest) before it shipped.
+
+**Slice 4, part 2 (Session 14): `--format`, the composite Action, and the PR comment** — the
+same shape as ebb's own Session 8, roughly half the work, because `packages/keel` and the
+`scripts/upsert_pr_comment.sh` pattern already existed to build on.
+
+```
+telltale check <path> --format table|markdown|annotations
+```
+
+Three renderers now sit behind one flag, all built from the same `Matrix` + `Regression`
+tuple computed once per run (`src/telltale/cli.py`'s `_render`) — never three separate scans:
+
+- `table` (default): unchanged from Session 13 — the two Rich tables plus, if `--base` found
+  regressions, the regressions table (`src/telltale/render/terminal.py`).
+- `markdown` (`src/telltale/render/markdown.py`, new): the same two tables as plain Markdown
+  pipe-tables, plus a "Regressions vs merge base" section when `--base` found any — this is
+  the composite Action's PR comment body.
+- `annotations` (`src/telltale/render/annotations.py`, new): GitHub workflow-command syntax
+  (`::error file=...,line=...::message`), **one per regression, never one per coverage cell**.
+  Unlike ebb's Finding (a model-id string at a specific line), a `CoverageCell` has no file:line
+  of its own — the annotation points at the route's OpenAPI definition instead
+  (`Regression.route_source_file`/`route_source_line`, taken from the `after` state, i.e.
+  HEAD — what a PR reviewer actually has open, not the now-deleted merge-base worktree). A gap
+  that already existed at the merge base isn't new information for this PR, so only PRESENT ->
+  not-PRESENT gets annotated, same DEC-04 discipline as the exit-code gate itself — there's
+  deliberately no "annotate every absent cell" mode.
+
+`apps/telltale/action.yml` (composite, not Docker/JS — same reasoning as the repo root's ebb
+action): wraps `uvx foretop-telltale check`, defaults `--base` to the pull request's own base
+SHA, emits `--format annotations` for inline PR annotations (zero extra permissions, same
+mechanism ebb's action already uses) and upserts a `--format markdown` PR comment by HTML
+marker (`apps/telltale/scripts/upsert_pr_comment.sh` — logic duplicated from, not imported
+from, the repo-root copy: docs/adr/0002 requires every app to stay standalone-copyable into
+its own future public mirror, exactly the ebb/`sync-ebb-mirror.sh` precedent, so this app's
+action can't reach outside its own directory for a script it needs). Both copies of the script
+now read their marker from a `COMMENT_MARKER` env var instead of a hardcoded string, so a repo
+running both ebb's and telltale's Actions on the same PR upserts two separate comments instead
+of colliding on one — a small, behavior-preserving generalization made to the shared script,
+not a new one.
+
+Lives at `apps/telltale/`, not the repo root (unlike ebb's `action.yml`): a repo can only have
+one `action.yml` per directory, and the root is already ebb's. This also happens to match
+telltale's real state honestly — it has no public mirror yet, so nothing here can assume a
+`uvx foretop-telltale` invocation resolves to a real PyPI release; that's the same not-yet-done
+caveat Session 8 already flagged for ebb's own action before it was ever actually published.
+
+Verified for real, the same way Session 13's regression gate was: ran `telltale check
+apps/telltale/tests/fixtures/fixture_service --format markdown` (clean output, 29% coverage),
+then emptied the fixture's `prometheus/rules.yaml` to simulate a real regression and re-ran
+with `--base HEAD --format annotations` (5 correctly-anchored `::error file=openapi.yaml,
+line=N::` lines, exit 1) and again with `--format markdown` (the same 5 rows in a rendered
+"Regressions vs merge base" table), then restored the fixture and confirmed a clean `git
+status` — never just trusted the unit tests alone for the git-worktree-dependent path.
+
+**Slice 5 (Session 15): the golden corpus** — `tests/golden/` + `tests/golden_manifest.yaml` +
+`tests/unit/test_golden_corpus.py`, same shape and the same floor as ebb's own (Session 7):
+precision >= 0.95, recall >= 0.85, scored **per extractor** (prometheus/grafana/otel — the
+first path segment under `tests/golden/`, same grouping ebb uses for its own detector dirs),
+never pooled into one aggregate that could hide one broken extractor behind two working ones.
+`make accuracy-telltale` runs just this file, verbosely.
+
+Ground truth is one entry per `Signal` a real extractor should produce for a fixture — `path`
+(relative to `tests/golden/`), `evidence_line`, `route_template`, `method`, `status_code`,
+`signal_type`. `null` fields are real ground truth (the extractor has no basis to claim a
+route/method/status), not missing data — see `prometheus/03_no_route_label`, where an alert
+with no route label still produces one Signal, correctly, with `route_template: null`.
+
+Every extractor group has at least one pure-decoy fixture — content that shares surface
+vocabulary with a real match without being one — enforced by its own test
+(`test_every_fixture_group_has_a_pure_decoy_case`, identical logic to ebb's own): a 0-FP score
+is trivial if a false positive was never actually possible to produce.
+
+**A real bug, found by building this corpus, not just theorized about:** `grafana.py`'s own
+docstring already claimed "a non-Prometheus datasource's query language is out of scope, not
+silently misread as PromQL" — but the code only ever checked for the presence of an `expr`
+field, never the target's actual datasource type. Loki's query field is *also* named `expr`,
+and LogQL's `{label="value"}` stream selector is syntactically close enough to a PromQL
+selector that a Loki panel's own labels (a `route="..."` stream label is entirely realistic)
+would have been misread as real route evidence — confirmed against a real Loki-backed
+dashboard fetched live this session, not assumed. Fixed with `_is_explicitly_non_prometheus`:
+a `datasource.type` naming anything other than `"prometheus"`, on either the panel or the
+target, is skipped. The corpus's own `grafana/04_decoy_loki_panel` fixture is what would have
+caught this, and now guards against it regressing. A narrower gap remains and is left
+documented, not silently patched over: a target with no `datasource` at all, or the legacy
+`"${DS_XXX}"` template-variable shape older exported dashboards use, still reads `expr` as
+PromQL — resolving that would mean cross-referencing the document's own `__inputs`, which is
+more machinery than this parser's "good enough, not semantically perfect" scope calls for.
+
+**Session 16: prepping to publish** — the release workflow and public-mirror sync script,
+mirroring `apps/ebb`'s own Session 8 pattern exactly. Not yet actually published: PyPI project
+creation and trusted-publisher configuration were always the user's job, not this session's
+(same NEXT_STEPS.md Track A split ebb's own `docs/adr/0002-ebb-public-mirror.md` already
+documents), and this session stopped short of creating a real `foretop-dev/telltale` repo.
+
+- `.github/workflows/telltale-release.yml` (this monorepo) and
+  `scripts/mirror-workflows/telltale-{ci,release}.yml` (copied into the mirror as `ci.yml`/
+  `release.yml` by `scripts/sync-telltale-mirror.sh`) — same shape as ebb's own three files,
+  tag-namespaced `telltale-v*` per `docs/adr/0002`'s already-stated plan for the whole suite.
+- Two real bugs found while building this, not just theorized about:
+  - `pyproject.toml`'s `[project.scripts]` only declared `telltale = ...`, not also
+    `foretop-telltale = ...` — `uvx <name>` (no `--from`) resolves the entry point matching the
+    *distribution* name, so `uvx foretop-telltale check .` (what `apps/telltale/action.yml`
+    already promises) would have failed to resolve once published. Caught by actually building
+    the wheel and inspecting `entry_points.txt`, not assumed correct because ebb's own
+    `pyproject.toml` already has the equivalent fix — confirmed fixed the same way afterward.
+  - No `LICENSE` file existed in `apps/telltale/` at all (copied from `apps/ebb/LICENSE`,
+    byte-identical standard Apache-2.0 text — a LICENSE file has no per-project content of its
+    own); `license-files = ["LICENSE"]` added to `pyproject.toml` so the built wheel actually
+    bundles it, verified by inspecting the wheel's own `dist-info/licenses/` after the change.
+- The blocker this section used to describe (`keel.collect.walk`/`keel.git_ref` only resolving
+  inside the monorepo's own workspace) is fixed as of a later session — see
+  `packages/keel/README.md`'s own "Packaging note": `scripts/sync-telltale-mirror.sh` now
+  vendors the exact `keel` submodules telltale imports (`git_ref.py`, `collect/
+  line_tracking.py`, `collect/walk.py`) into the mirror at sync time, and the mirror's own
+  `pyproject.toml` (`scripts/mirror-pyproject/telltale.toml`) no longer depends on
+  `foretop-keel`. Re-verified for real after the fix: `ruff`/`mypy`/`pytest` (156 tests) all
+  green standalone, a real wheel built, and the built wheel cold-installed into a fresh venv
+  with `telltale --help` actually running.
+
+```
+uv run --package foretop-telltale telltale check <path>
+```
+
+Domain model (`src/telltale/models.py`) is the SUITE_ARCHITECTURE-style pure core:
+`RouteSet` (from the OpenAPI parser) × `SignalSet` (from the signal extractors) →
+`match()` (`src/telltale/match.py`, pure, no I/O) → `Matrix`. Every coverage cell is
+**three-state** — `present` / `absent` / `ambiguous` — never just present/absent. `ambiguous`
+is not a synonym for `absent`: a route gets `ambiguous` for a signal type only when no
+extractor for that type exists in telltale's own code at all — as of Session 11 every
+`SignalType` has a real extractor (Prometheus → `alert`; Grafana → `metric`; OTel Collector →
+`log`/`metric`/`trace`), so `ambiguous` no longer appears in ordinary runs. It stays a real,
+reachable state, not a vestige: the moment a *new* signal dimension is added to `SignalType`
+without an extractor yet, every route goes `ambiguous` for it, honestly, rather than a false
+`absent` — see `SignalSet.attempted_types` in `models.py`. `absent` means an extractor
+genuinely ran across the whole repo and found nothing for that route — specs/telltale.md's
+explicit warning: "never claim coverage that does not exist... ambiguous is its own outcome
+and is never counted as covered."
+
+**OpenAPI parser** (`src/telltale/openapi.py`): OpenAPI 3.0/3.1, YAML or JSON. Reads the 8
+Path Item Object method keys (get/put/post/delete/options/head/patch/trace — `spec.openapis.org`
+oas/v3.1.0.html §4.8.7, fetched live this session, not written from memory) and each operation's
+`responses` keys as-is (`"200"`, `"5XX"`, `"default"`) — stored since Session 9, consumed by
+the matcher's error-mode dimension since Session 12. `$ref` resolution is local-document-only
+(`#/components/...` JSON Pointers, walked against the already-parsed document) — external-file
+`$ref`s are out of scope for Slice 1 and produce an `ambiguous`-flavoured skip, never a crash,
+per specs/telltale.md §6's degrade-not-crash rule.
+
+**Prometheus rule parser** (`src/telltale/prometheus.py`): parses `groups[].rules[]`
+(`prometheus.io/docs/prometheus/latest/configuration/alerting_rules/`, fetched live), and only
+entries with an `alert:` key — `record:` entries are recording rules, not alerts, and are
+skipped. Extracts route-identifying label matchers from each rule's `expr` with a lightweight
+selector regex (`metric_name{label="value", ...}` — PromQL's own basic matcher syntax,
+`prometheus.io/docs/prometheus/latest/querying/basics/`, fetched live), not a full PromQL
+parser — same "good enough, not semantically perfect" scope decision ebb's detectors made.
+Which label names count as "this is the route" is a **declarative rules file**
+(`src/telltale/rules/label_names.yaml`), not hardcoded `if` branches — specs/telltale.md §5's
+explicit requirement, so this is a config edit for a user extending it, not a code change.
+
+**Grafana dashboard parser** (`src/telltale/grafana.py`, Session 11): dashboard JSON
+("dashboards as code"). Verified against two real, live-fetched public dashboards — a modern
+flat `panels[]` shape and the legacy `rows[].panels[]` shape both use `targets[].expr` for a
+Prometheus-backed panel's query. Only `expr` targets are read (specs/telltale.md DEC-01 commits
+to OTel + Prometheus for v1; a non-Prometheus datasource's query language is out of scope, not
+silently misread). Reuses the exact same PromQL selector/label-matcher logic as the Prometheus
+parser (`src/telltale/promql.py`, extracted in this session so both parsers share one
+implementation) — a panel visualizing a metric produces `metric`-type evidence, the same "this
+is being watched" signal an alert represents for `alert`, without an alerting threshold.
+
+**OTel Collector config parser** (`src/telltale/otel.py`, Session 11): `receivers`/
+`processors`/`exporters`/`service.pipelines` — verified against opentelemetry.io's own docs
+live. Deliberately narrow, and says so in its own docstring: most collector configs wire
+generic pipelines with no reference to individual routes at all, so this parser only produces
+evidence where a `filter` processor's OTTL condition actually names a route via `http.route`/
+`http.request.method` (OpenTelemetry's current stable semantic convention attribute names,
+`opentelemetry.io/docs/specs/semconv/http/http-spans/`, fetched live — not the code's own
+`route`/`method` shorthand, since these are dotted attribute names from a different
+ecosystem's convention, so they're a separate section of `label_names.yaml`, not folded into
+the Prometheus lists). A processor only counts if it's genuinely wired into a
+`service.pipelines` entry — an unreferenced `processors:` block is dead config that isn't
+affecting the deployed collector, and reading it would be evidence for something not actually
+happening. Which `traces`/`metrics`/`logs` section a condition sits under determines the
+`SignalType` directly, since a filter processor's own structure already says that
+unambiguously — no need to cross-reference the pipeline for that part.
+
+**Evidence, not just data**: every parser needs real line numbers for `evidence_path` /
+`evidence_line` (specs/telltale.md §6: "never assert without evidence"), but plain
+`yaml.safe_load`/`json.loads` discard node positions once a document is built.
+`keel.collect.line_tracking` (originally `src/telltale/yaml_lines.py`, extracted to `keel` in
+Session 15 when charter needed the exact same thing for its own JSON-only config parsers — see
+`packages/keel/README.md`) is a small custom `SafeLoader` that tags every parsed mapping with
+its own starting line — used by every parser here, including the JSON ones (verified directly,
+twice now — first for the OpenAPI parser, then again for a real 12KB Grafana dashboard file —
+that well-formed JSON parses identically through this loader as through `json.loads`, just
+with line tracking available). The one gap: a plain YAML/JSON list of strings (an OTel filter
+condition list) has no per-item position, only the mappings do — `otel.py`'s evidence there
+points at the enclosing `traces:`/`metrics:`/`logs:` block, the finest granularity available,
+not a fabricated per-condition line.
+
+**Route-template matching**: an OpenAPI path template (`/users/{id}`) and a signal's claimed
+route (a Prometheus label value, a Grafana panel's query label, an OTel attribute value) are
+compared after normalizing parameter placeholders (`{id}` and `:id` both collapse to the same
+token) — exact match only, no fuzzy scoring, one shared function
+(`src/telltale/route_template.py`) for every extractor. This is deliberately conservative: a
+false `present` is worse than a false `absent` (specs/telltale.md's explicit priority), so an
+unrecognized placeholder convention or a genuinely different path just doesn't match, rather
+than guessing.
+
+**Method narrowing**: two operations can share a path template (`GET /todos` and `POST
+/todos`). Route-template matching alone would mark both `present` off a single GET-scoped
+alert — a real false `present`, caught by the fixture-service acceptance test, not just
+reasoned about. When an extractor finds a recognized method label/attribute
+(`label_names.yaml`'s `method_label_names` for Prometheus/Grafana, `otel_method_attribute_names`
+for OTel), a match additionally requires that method to agree with the route's. A signal with
+no method information still matches on route template alone — the best information actually
+available, not a reason to withhold a real match. See `.claude/skills/matching-rules.md` for
+the full reasoning.
+
+**The error-mode dimension** (`src/telltale/response_code.py`, Session 12): a route documents
+its response codes as literal codes ("404") or OpenAPI's own wildcard convention ("5XX") —
+`normalize_response_code()` maps both into one comparable space, and `is_error_mode()` restricts
+to 4xx/5xx only (2xx/3xx/1xx are real, normalizable codes but not what DEC-03 tracks). Every
+extractor was extended to also read a status-code label/attribute
+(`label_names.yaml`'s `status_code_label_names` for Prometheus/Grafana,
+`otel_status_code_attribute_names` for OTel) alongside route/method. Matching is **exact string
+equality only, no class-membership reasoning either direction** — a route documenting "5XX" is
+`present` only for a signal also scoped to exactly "5XX", not one scoped to the narrower "503",
+and a route documenting "404" is never satisfied by a signal scoped to the broader "4XX". This
+is a real, deliberate, documented gap (same false-present-is-worse-than-false-absent
+conservatism as method narrowing), not an oversight.
+
+One genuine PromQL idiom is recognized as meaningful, not fuzzy-matched: `code=~"5.."` is the
+standard, widely-used convention for "the 5xx class," equivalent to OpenAPI's own "5XX" — only
+this exact two-dot shape is interpreted, nothing broader. OTTL (OTel's condition language) has
+no equivalent single standard idiom for a status-code *range*, so `otel.py` only reads exact
+`==` conditions for status codes — a range condition like
+`attributes["http.response.status_code"] >= 500` is a known, documented gap, not a silent one.
+`http.response.status_code` is int-typed in OTTL (its own semconv example value is unquoted
+`200`) — `otel.py`'s condition regex reads both quoted strings (`http.route`,
+`http.request.method`) and bare integers, verified against a real OTTL condition shape, not
+assumed to be one or the other.
+
+**Session 10 (the extraction session):** the gitignore-aware file walker
+(`is_binary`/`iter_files`/the gitignore matching) that `src/telltale/walk.py` copied verbatim
+from `apps/ebb/src/ebb/walk.py` in Session 9 (marked `# DUPLICATED-FROM-EBB`) turned out to be
+byte-identical between the two copies, so it moved to `packages/keel` —
+`keel.collect.walk`. `src/telltale/walk.py` now imports it and keeps only
+`iter_readable_text_files`, telltale's own thin layer on top. `packages/keel/README.md` has
+the full identical-vs-similar reasoning.
+
+`src/telltale/brand.py` duplicates ebb's one-line `BRAND` constant rather than importing it,
+per NEXT_STEPS.md's insulation rule — that one stays duplicated; it isn't the kind of thing
+`keel` is for.