lkml-blastradius 0.1.0__tar.gz

lkml_blastradius-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --python ${{ matrix.python }}
+      - run: uv run ruff check src tests
+      - run: uv run ruff format --check src tests
+      - run: uv run mypy
+      - run: uv run pytest
+      - run: uv run lkblast demo

lkml_blastradius-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,63 @@
+# Release: push a tag like v0.2.0.
+#  1. build sdist + wheel from a clean checkout and smoke-test the wheel (offline demo);
+#  2. create a GitHub Release with the artifacts;
+#  3. publish to PyPI with trusted publishing (no API tokens) — only when the repository variable
+#     PYPI_PUBLISH is "true", i.e. after the PyPI trusted publisher has been configured.
+name: release
+on:
+  push:
+    tags: ["v*"]
+permissions:
+  contents: read
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - name: Check tag matches package version
+        run: |
+          v=$(grep -m1 '^version' pyproject.toml | cut -d'"' -f2)
+          [ "v$v" = "${GITHUB_REF_NAME}" ] || { echo "::error::tag ${GITHUB_REF_NAME} != version $v"; exit 1; }
+      - run: uv build
+      - name: Smoke-test the wheel in a clean environment
+        run: |
+          uv venv /tmp/smoke --python 3.12
+          uv pip install --python /tmp/smoke/bin/python dist/*.whl
+          cd /tmp && /tmp/smoke/bin/lkblast demo -o /tmp/lkblast-demo && /tmp/smoke/bin/lkblast init /tmp/init-check
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  github-release:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Create GitHub Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh release create "$GITHUB_REF_NAME" dist/* --title "$GITHUB_REF_NAME" \
+            --notes "See [CHANGELOG.md](https://github.com/${{ github.repository }}/blob/$GITHUB_REF_NAME/CHANGELOG.md)."
+
+  pypi:
+    needs: build
+    if: vars.PYPI_PUBLISH == 'true'
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write   # trusted publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

lkml_blastradius-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.egg-info/
+.venv/
+dist/
+.lkblast/
+reports/
+lkblast-demo/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/

lkml_blastradius-0.1.0/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+## 0.1.0 (2026-10-03)
+
+First release.
+
+- `lkblast run`: daily snapshot of Looker metadata through the API (explores and fields, dashboard
+  tiles and filters, Looks, merged queries, Looker CA agents, content validator, Looker version,
+  deployed LookML commits, Google release notes), compared with the previous run.
+- Impact per content item: breaking, numbers may change, AI agents may answer differently, cosmetic;
+  each change attributed to a LookML deploy or a Looker upgrade.
+- Reports: `blastradius.md`, `blastradius.html`, `blastradius.json`, and a Slack summary.
+- `lkblast init`: `blastradius.yaml` and a daily GitHub Actions workflow.
+- `lkblast compare` for any two snapshots; `lkblast demo` offline.
+- Optional Conversational Analytics API data agents.

lkml_blastradius-0.1.0/LICENSE

@@ -0,0 +1,177 @@
+
+                                 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

lkml_blastradius-0.1.0/PKG-INFO

@@ -0,0 +1,146 @@
+Metadata-Version: 2.5
+Name: lkml-blastradius
+Version: 0.1.0
+Summary: The blast radius of every Looker change: which dashboards, Looks, explores and Conversational Analytics agents a LookML deploy or Google release affects, reported daily.
+Author: Venkata Sangaraju
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Database
+Requires-Python: >=3.11
+Requires-Dist: httpx>=0.27
+Requires-Dist: pyyaml>=6.0
+Description-Content-Type: text/markdown
+
+# lkml-blastradius
+
+**The blast radius of every Looker change.** Every morning: what changed (LookML deploys, Looker
+upgrades, Google releases), and which dashboards, Looks, explores and Conversational Analytics
+agents it hits.
+
+```bash
+pip install lkml-blastradius
+lkblast init    # writes blastradius.yaml + a daily GitHub Actions workflow
+lkblast run     # snapshot Looker, compare with yesterday, write the report
+```
+
+Each run takes a metadata snapshot through the Looker API and compares it with the previous one:
+
+| It tracks | From |
+|---|---|
+| Every explore and field: SQL, type, label, description, synonyms, joins, `sql_table_name`, always filters | `lookml_models`, `lookml_model_explore` |
+| Every dashboard tile and filter, Look, and merged query, with each field it uses (including filters, sorts, pivots, custom fields) | `dashboards`, `looks`, `queries`, `merge_queries` |
+| Conversational Analytics agents in Looker: explores, golden queries, fields named in instructions | `agents` (beta API) |
+| CA API data agents (optional) | `geminidataanalytics.googleapis.com` `dataAgents` |
+| Broken content, whatever the cause | Looker content validator |
+| Looker version and the deployed LookML commit of every project, including imported ones | `versions`, `projects/{id}/git_branch` |
+| What Google shipped | Looker release-notes feed, CA API release notes |
+
+Then it reports **what changed, old → new, which content it touches, how badly, and why**:
+
+| Severity | Meaning |
+|---|---|
+| **Breaking** | A field, join or explore that the content uses was removed, or the content validator found a new error |
+| **Numbers may change** | SQL, type, measure filters, joins, table or always-filters changed for a field the content uses |
+| **AI agents may answer differently** | Descriptions, labels, synonyms, hidden flags or new fields changed in an explore an agent can use. Dashboards ignore these changes, but agents read them. |
+| **Cosmetic** | Labels or formats on dashboards and Looks |
+
+Every change is attributed to one of three causes: **a LookML deploy** in a named project (old → new commit),
+**a Looker upgrade** (old → new version) with no deploy, or neither. Changes from Google come from
+the upgrade line, the matching release notes, and the content validator.
+
+## Try it offline
+
+```bash
+lkblast demo    # two days on a fake Looker (fictional Harborline Supply Co.)
+open lkblast-demo/reports/blastradius.html
+```
+
+```
+  2 breaking, 3 numbers may change, 1 cosmetic
+  2 new content error(s), 2 open
+  Looker upgraded 26.14.2 → 26.16.1
+  LookML deployed in core_project, finance_project
+  3 new Google release note(s), 2 need attention
+```
+
+| Content | Severity | Why | Cause |
+|---|---|---|---|
+| Executive revenue / Revenue by region (tile) | Breaking | `customers.region` removed | LookML deploy in finance_project |
+| Executive revenue / Region (filter) | Breaking | `customers.region` removed | LookML deploy in finance_project |
+| Executive revenue / Net revenue by month | Numbers may change | `orders.net_revenue` SQL now also subtracts discounts | LookML deploy in core_project (imported) |
+| Collections / Amount due vs net revenue (merged query) | Numbers may change | same | same |
+| Finance assistant (Looker CA agent) | Numbers may change | its golden query uses `orders.net_revenue` | same |
+| Executive revenue / Order volume | Cosmetic | `orders.order_count` label | same |
+
+The *Refund watch* Look and the *Logistics helper* agent are not listed because nothing they use changed.
+
+## Run it daily (GitHub Actions + Slack)
+
+1. `lkblast init` in any repo (it can be an otherwise empty repo).
+2. Add repository secrets: `LOOKER_BASE_URL`, `LOOKER_CLIENT_ID`, `LOOKER_CLIENT_SECRET`, and
+   optionally `SLACK_WEBHOOK_URL`.
+3. Push. The workflow runs at 06:00 UTC daily (change the cron in `.github/workflows/lkml-blastradius.yml`)
+   or on demand from the Actions tab.
+
+Every run writes `reports/blastradius.{md,html,json}`. The Markdown goes to the job summary, the reports are
+uploaded as an artifact, and a short summary with a link to the run is posted to Slack. Snapshot history
+lives in the Actions cache. Each run refreshes it, so it doesn't expire while the job runs daily.
+
+The first run saves a baseline. Impact is reported from the second run on.
+
+**API user.** Use API credentials of a user that can see all content (an admin, or a role with
+`see_lookml`, `see_user_dashboards`, `see_looks`, `access_data` on all models). Content the user
+can't see is not analyzed. Reading deployed commits needs `see_lookml`/`develop`; without it, the
+report still works but can't tell a LookML deploy from a Looker upgrade.
+
+## Options
+
+`blastradius.yaml` (written by `lkblast init`; every key is optional):
+
+```yaml
+looker:   {models: [], workers: 8, timeout_seconds: 120}
+content:  {dashboards: true, looks: true, looker_agents: true, content_validator: true}
+ca_api:   {enabled: false, locations: [global]}   # + GOOGLE_CLOUD_PROJECT, GOOGLE_OAUTH_ACCESS_TOKEN
+releases: {enabled: true, lookback_days: 7}
+storage:  {dir: .lkblast, keep: 30}
+report:   {dir: reports}
+```
+
+```bash
+lkblast run --fail-on breaking          # exit 1 when something breaks (for alerting)
+lkblast compare OLD.json.gz NEW.json.gz # report between any two saved snapshots
+```
+
+To include **CA API data agents**, set `ca_api.enabled: true` and provide `GOOGLE_CLOUD_PROJECT`
+and an access token in `GOOGLE_OAUTH_ACCESS_TOKEN`. In Actions, get one with
+`google-github-actions/auth` (`token_format: access_token`). Agents that point at another Looker
+instance are ignored.
+
+## What it does not do
+
+- It reports changes **after** they reach production (daily). It doesn't check a LookML branch
+  before merge.
+- It never runs queries and stores no row data. It can't see a number change that comes from the
+  warehouse data itself.
+- It can't see a Google change that alters behavior but not metadata, such as how an agent picks
+  fields. That shows up only as an upgrade line and release notes. Agent answer regression testing
+  is what [lookml-agentops](https://github.com/sangaraju1988/lookml-agentops) does.
+
+## API sources
+
+Every Looker endpoint and attribute used is checked against Looker's OpenAPI spec
+(`looker-open-source/sdk-codegen`, `spec/Looker.4.0.oas.json`, 4.0.26.12). The list is in the
+docstring of [`looker.py`](src/lkml_blastradius/looker.py). `/agents` is marked **beta** by Looker.
+CA API fields come from the v1 REST reference. Release-note formats were checked on 2026-10-03
+(see [`releases.py`](src/lkml_blastradius/releases.py)). If Google changes the page layout, the run
+records a warning and continues.
+
+## Development
+
+```bash
+uv sync && uv run pytest && uv run ruff check src tests && uv run mypy
+```
+
+Apache-2.0. Not affiliated with or endorsed by Google. Looker is a trademark of Google LLC.

lkml_blastradius-0.1.0/README.md

@@ -0,0 +1,131 @@
+# lkml-blastradius
+
+**The blast radius of every Looker change.** Every morning: what changed (LookML deploys, Looker
+upgrades, Google releases), and which dashboards, Looks, explores and Conversational Analytics
+agents it hits.
+
+```bash
+pip install lkml-blastradius
+lkblast init    # writes blastradius.yaml + a daily GitHub Actions workflow
+lkblast run     # snapshot Looker, compare with yesterday, write the report
+```
+
+Each run takes a metadata snapshot through the Looker API and compares it with the previous one:
+
+| It tracks | From |
+|---|---|
+| Every explore and field: SQL, type, label, description, synonyms, joins, `sql_table_name`, always filters | `lookml_models`, `lookml_model_explore` |
+| Every dashboard tile and filter, Look, and merged query, with each field it uses (including filters, sorts, pivots, custom fields) | `dashboards`, `looks`, `queries`, `merge_queries` |
+| Conversational Analytics agents in Looker: explores, golden queries, fields named in instructions | `agents` (beta API) |
+| CA API data agents (optional) | `geminidataanalytics.googleapis.com` `dataAgents` |
+| Broken content, whatever the cause | Looker content validator |
+| Looker version and the deployed LookML commit of every project, including imported ones | `versions`, `projects/{id}/git_branch` |
+| What Google shipped | Looker release-notes feed, CA API release notes |
+
+Then it reports **what changed, old → new, which content it touches, how badly, and why**:
+
+| Severity | Meaning |
+|---|---|
+| **Breaking** | A field, join or explore that the content uses was removed, or the content validator found a new error |
+| **Numbers may change** | SQL, type, measure filters, joins, table or always-filters changed for a field the content uses |
+| **AI agents may answer differently** | Descriptions, labels, synonyms, hidden flags or new fields changed in an explore an agent can use. Dashboards ignore these changes, but agents read them. |
+| **Cosmetic** | Labels or formats on dashboards and Looks |
+
+Every change is attributed to one of three causes: **a LookML deploy** in a named project (old → new commit),
+**a Looker upgrade** (old → new version) with no deploy, or neither. Changes from Google come from
+the upgrade line, the matching release notes, and the content validator.
+
+## Try it offline
+
+```bash
+lkblast demo    # two days on a fake Looker (fictional Harborline Supply Co.)
+open lkblast-demo/reports/blastradius.html
+```
+
+```
+  2 breaking, 3 numbers may change, 1 cosmetic
+  2 new content error(s), 2 open
+  Looker upgraded 26.14.2 → 26.16.1
+  LookML deployed in core_project, finance_project
+  3 new Google release note(s), 2 need attention
+```
+
+| Content | Severity | Why | Cause |
+|---|---|---|---|
+| Executive revenue / Revenue by region (tile) | Breaking | `customers.region` removed | LookML deploy in finance_project |
+| Executive revenue / Region (filter) | Breaking | `customers.region` removed | LookML deploy in finance_project |
+| Executive revenue / Net revenue by month | Numbers may change | `orders.net_revenue` SQL now also subtracts discounts | LookML deploy in core_project (imported) |
+| Collections / Amount due vs net revenue (merged query) | Numbers may change | same | same |
+| Finance assistant (Looker CA agent) | Numbers may change | its golden query uses `orders.net_revenue` | same |
+| Executive revenue / Order volume | Cosmetic | `orders.order_count` label | same |
+
+The *Refund watch* Look and the *Logistics helper* agent are not listed because nothing they use changed.
+
+## Run it daily (GitHub Actions + Slack)
+
+1. `lkblast init` in any repo (it can be an otherwise empty repo).
+2. Add repository secrets: `LOOKER_BASE_URL`, `LOOKER_CLIENT_ID`, `LOOKER_CLIENT_SECRET`, and
+   optionally `SLACK_WEBHOOK_URL`.
+3. Push. The workflow runs at 06:00 UTC daily (change the cron in `.github/workflows/lkml-blastradius.yml`)
+   or on demand from the Actions tab.
+
+Every run writes `reports/blastradius.{md,html,json}`. The Markdown goes to the job summary, the reports are
+uploaded as an artifact, and a short summary with a link to the run is posted to Slack. Snapshot history
+lives in the Actions cache. Each run refreshes it, so it doesn't expire while the job runs daily.
+
+The first run saves a baseline. Impact is reported from the second run on.
+
+**API user.** Use API credentials of a user that can see all content (an admin, or a role with
+`see_lookml`, `see_user_dashboards`, `see_looks`, `access_data` on all models). Content the user
+can't see is not analyzed. Reading deployed commits needs `see_lookml`/`develop`; without it, the
+report still works but can't tell a LookML deploy from a Looker upgrade.
+
+## Options
+
+`blastradius.yaml` (written by `lkblast init`; every key is optional):
+
+```yaml
+looker:   {models: [], workers: 8, timeout_seconds: 120}
+content:  {dashboards: true, looks: true, looker_agents: true, content_validator: true}
+ca_api:   {enabled: false, locations: [global]}   # + GOOGLE_CLOUD_PROJECT, GOOGLE_OAUTH_ACCESS_TOKEN
+releases: {enabled: true, lookback_days: 7}
+storage:  {dir: .lkblast, keep: 30}
+report:   {dir: reports}
+```
+
+```bash
+lkblast run --fail-on breaking          # exit 1 when something breaks (for alerting)
+lkblast compare OLD.json.gz NEW.json.gz # report between any two saved snapshots
+```
+
+To include **CA API data agents**, set `ca_api.enabled: true` and provide `GOOGLE_CLOUD_PROJECT`
+and an access token in `GOOGLE_OAUTH_ACCESS_TOKEN`. In Actions, get one with
+`google-github-actions/auth` (`token_format: access_token`). Agents that point at another Looker
+instance are ignored.
+
+## What it does not do
+
+- It reports changes **after** they reach production (daily). It doesn't check a LookML branch
+  before merge.
+- It never runs queries and stores no row data. It can't see a number change that comes from the
+  warehouse data itself.
+- It can't see a Google change that alters behavior but not metadata, such as how an agent picks
+  fields. That shows up only as an upgrade line and release notes. Agent answer regression testing
+  is what [lookml-agentops](https://github.com/sangaraju1988/lookml-agentops) does.
+
+## API sources
+
+Every Looker endpoint and attribute used is checked against Looker's OpenAPI spec
+(`looker-open-source/sdk-codegen`, `spec/Looker.4.0.oas.json`, 4.0.26.12). The list is in the
+docstring of [`looker.py`](src/lkml_blastradius/looker.py). `/agents` is marked **beta** by Looker.
+CA API fields come from the v1 REST reference. Release-note formats were checked on 2026-10-03
+(see [`releases.py`](src/lkml_blastradius/releases.py)). If Google changes the page layout, the run
+records a warning and continues.
+
+## Development
+
+```bash
+uv sync && uv run pytest && uv run ruff check src tests && uv run mypy
+```
+
+Apache-2.0. Not affiliated with or endorsed by Google. Looker is a trademark of Google LLC.

lkml_blastradius-0.1.0/pyproject.toml

@@ -0,0 +1,44 @@
+[project]
+name = "lkml-blastradius"
+version = "0.1.0"
+description = "The blast radius of every Looker change: which dashboards, Looks, explores and Conversational Analytics agents a LookML deploy or Google release affects, reported daily."
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.11"
+authors = [{ name = "Venkata Sangaraju" }]
+classifiers = [
+  "Programming Language :: Python :: 3",
+  "License :: OSI Approved :: Apache Software License",
+  "Topic :: Database",
+]
+dependencies = ["httpx>=0.27", "pyyaml>=6.0"]
+
+[project.scripts]
+lkblast = "lkml_blastradius.cli:main"
+
+[dependency-groups]
+dev = ["pytest>=8", "ruff>=0.5", "mypy>=1.10", "types-PyYAML>=6.0"]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/lkml_blastradius"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+select = ["E", "F", "W", "I", "B", "UP", "SIM", "RUF"]
+ignore = ["E501"]
+
+[tool.mypy]
+strict = true
+files = ["src/lkml_blastradius"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"

lkml_blastradius-0.1.0/src/lkml_blastradius/__init__.py

@@ -0,0 +1,3 @@
+"""lkml-blastradius: the blast radius of every Looker change on dashboards, Looks and agents."""
+
+__version__ = "0.1.0"