lighthouse-cli 0.16.0__tar.gz

lighthouse_cli-0.16.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 [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

lighthouse_cli-0.16.0/NOTICE

@@ -0,0 +1,2 @@
+LightHouse CLI
+Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.

lighthouse_cli-0.16.0/PKG-INFO

@@ -0,0 +1,23 @@
+Metadata-Version: 2.4
+Name: lighthouse-cli
+Version: 0.16.0
+Summary: The LightHouse command line: sign in, connect your estate, deploy agents, watch runs
+License-Expression: Apache-2.0
+Classifier: Programming Language :: Python :: 3
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: httpx==0.28.1
+Requires-Dist: keyring==25.7.0
+Requires-Dist: cryptography==50.0.2
+Provides-Extra: dev
+Requires-Dist: pytest==9.1.1; extra == "dev"
+Requires-Dist: pytest-cov==7.1.0; extra == "dev"
+Requires-Dist: ruff==0.16.10; extra == "dev"
+Requires-Dist: mypy==2.4.0; extra == "dev"
+Requires-Dist: bandit[toml]==1.9.4; extra == "dev"
+Requires-Dist: jsonschema==4.25.1; extra == "dev"
+Provides-Extra: build
+Requires-Dist: pyinstaller==6.22.3; extra == "build"
+Dynamic: license-file

lighthouse_cli-0.16.0/README.md

@@ -0,0 +1,258 @@
+# The `lighthouse` command line for LightHouse™
+
+LightHouse from a terminal: sign in through the browser, see what is connected,
+read spend and limits, scaffold an agent, follow the runs. In the manner of the
+Stripe CLI — one command to install, one to sign in, and everything else
+scriptable.
+
+```sh
+brew install atlantic-agentic-labs/tap/lighthouse     # or npm, pip, curl (below)
+lighthouse login --host t7m2kqx9vbn.atlanticagenticlabs.com
+lighthouse whoami
+lighthouse spend --by model --json | jq '.rows[0]'
+```
+
+## Why Python
+
+The requirement is one binary installable four ways. Go would give that most
+directly, and the Stripe CLI is written in Go. We chose Python, on this
+evidence:
+
+| | Weight |
+|---|---|
+| **The control plane is Python.** The service, its OpenAPI generator and its MCP server are all `aal_control`. The CLI's integration tests therefore run **in process against the very application that is deployed** (`service/tests/test_cli_integration.py`) — the real routes, the real OAuth, the real row-level security, no stack to boot and no stub to drift. No other choice gets us that. | decisive |
+| **No new toolchain in any pipeline.** Every job already runs `python:3.13-slim`; a Go CLI would add a compiler, a cross-build matrix and a second dependency-audit path to all 21 repositories. | heavy |
+| **`keyring` gives the OS keychain on all three platforms** — macOS Keychain, Secret Service, Windows Credential Locker — with no native code to sign or notarise. | heavy |
+| Against: `npm` and `curl` want a runtime-free binary. | the cost |
+
+That last line is the real cost, and it is paid rather than hidden: `pip` and
+`brew` install from source, while the **npm package and the curl script serve a
+single-file build** made with PyInstaller (`installers/`), which embeds the
+interpreter. A person installing by `curl | sh` needs no Python; a person
+installing by `pip` has one already.
+
+If the npm and curl routes ever become the main way people install this, the
+decision is worth revisiting — the commands, their output and their tests are
+the valuable part and none of it is language-specific.
+
+## Install
+
+| Route | Command | What it installs |
+|---|---|---|
+| Homebrew | `brew install atlantic-agentic-labs/tap/lighthouse` | from source, into its own virtualenv (`installers/lighthouse.rb`) |
+| pip | `pip install lighthouse-cli` | from source, as a normal console script |
+| curl | `curl -fsSL https://get.atlanticagenticlabs.com/lighthouse \| sh` | the single-file build (`installers/install.sh`) |
+
+**Nothing is published yet.** From a clone:
+
+```sh
+cd cli && pip install -e ".[dev]"
+```
+
+What has to exist before any of the three routes work is in
+`installers/README.md`: a Homebrew tap, a PyPI project and one DNS name. No
+registry credential is stored for any of them.
+
+## Signing in
+
+```
+$ lighthouse login --host t7m2kqx9vbn.atlanticagenticlabs.com
+
+Your pairing code is: WXKM-7T4P
+Approve it at https://t7m2kqx9vbn.atlanticagenticlabs.com/device
+Press Enter to open the browser, or Ctrl-C to stop…
+Signed in to Example Air as ops@example.test (client_admin).
+```
+
+A device code, exactly as `stripe login` does it. The person approves in their
+own portal, behind their own identity provider and their own second factor;
+nothing is typed into the terminal and no token is copied by hand.
+
+**The credential goes in the operating system keychain, never a file.** Not in
+the repository, not in a dotfile, not in an environment file. One entry per
+host, so you can be signed in to several tenants at once:
+
+```sh
+lighthouse whoami --profiles
+lighthouse logout --all          # revokes at the service, then forgets
+```
+
+**What the credential can do** is in
+`docs/adr/0012-delegated-credentials.md`: it reads as you, it never
+administers, approves or pays, and the access grant behind it is re-read on
+every request — so a withdrawn grant stops it at once.
+
+## In CI
+
+There is no keychain on a runner and no browser to open, so a pipeline uses a
+**machine key** and the tenant's **Cloudflare Access service token**, both in
+masked variables:
+
+| Variable | What it is |
+|---|---|
+| `LIGHTHOUSE_HOST` | the tenant, `<tenant id>.atlanticagenticlabs.com` |
+| `LIGHTHOUSE_TOKEN` | a machine key (`aalcp-...`), created on the portal's **Keys** page |
+| `LIGHTHOUSE_ACCESS_CLIENT_ID` | the tenant's Access service token id |
+| `LIGHTHOUSE_ACCESS_CLIENT_SECRET` | its secret |
+
+```yaml
+spend-report:
+  image: python:3.13-slim
+  variables:
+    LIGHTHOUSE_HOST: t7m2kqx9vbn.atlanticagenticlabs.com
+    # LIGHTHOUSE_TOKEN, LIGHTHOUSE_ACCESS_CLIENT_ID and
+    # LIGHTHOUSE_ACCESS_CLIENT_SECRET are masked CI/CD variables.
+  script:
+    - pip install -q lighthouse-cli
+    - lighthouse whoami --json
+    - lighthouse evals list --fail-below 0.8 --json
+    - lighthouse spend --json > spend.json
+```
+
+**Why two credentials.** Every tenant host sits behind Cloudflare Access except
+the sign-in endpoints, so every other request carries the Access service token
+(`CF-Access-Client-Id` and `CF-Access-Client-Secret`) *and* the key
+(`Authorization: Bearer ...`). If Access answers instead of LightHouse (a
+redirect to `*.cloudflareaccess.com`, or a login page) the CLI says the Access
+service token is missing or wrong and names the two variables.
+
+**Machine key or delegated token.** `LIGHTHOUSE_TOKEN` also accepts a delegated
+token (`lhat-...`), but that expires after **eight hours** and is not refreshed
+under the variable: there would be nowhere to put the new one. A machine key
+does not expire by time and has no refresh; revoke it on the Keys page. A
+machine key has no person behind it, so `lighthouse tokens` says so rather than
+failing, and `whoami` shows the key's kind.
+
+When `LIGHTHOUSE_TOKEN` is set, the CLI reads and writes **no** credential
+store at all.
+
+**On a workstation** behind Access, `login` can keep the service token in the
+keychain with the delegated token:
+
+```sh
+printf '%s\n' "$ACCESS_SECRET" | lighthouse login --access-client-id "$ACCESS_ID" \
+    --access-client-secret-stdin
+```
+
+The secret comes from standard input or `LIGHTHOUSE_ACCESS_CLIENT_SECRET`, never
+from a command-line argument, where `ps` and shell history would keep it.
+
+`--timeout N` is the number of seconds for one request (connect, read and write
+each). `--no-input` makes any question an exit 7 instead of a hang, which is
+what you want in a job. Colour is off automatically when standard output is not
+a terminal, and when `CI`, `NO_COLOR` or `TERM=dumb` is set.
+
+## The commands
+
+| Command | |
+|---|---|
+| `login`, `logout`, `tokens` | sign in, sign out, see and revoke your delegated tokens |
+| `whoami` | which tenant, which person, which role, which scopes, where the credential came from |
+| `connect [provider]` | what is connected; open a provider's own approval; with `--credential-stdin`, connect an existing token as yourself (read from standard input, `--access read_write` by choice; needs `cloudflared access login https://<host>`); with `--reuse-local`, offer the `gh`, `glab` or `DD_*` sign-in already on this machine, sent the same way only after you type `yes` at a terminal (never under `--yes` or `--no-input`) |
+| `connections`, `connections schedule <id> --mode ...`, `connections sync <id>` | each connection's sync schedule, last and next sync; set a schedule (`off`, `every_15m`, `hourly`, `working_hours --tz ...`, `daily --at HH:MM --tz ...`) or sync now, as yourself (a client administrator; needs `cloudflared access login https://<host>`; checked by the service exactly as on the card) |
+| `collectors`, `collectors request --vendor ... --product ... --reads ... --cloud ...` | your tenant's collector requests and their stage in Atlantic's backlog; ask for another (handler or client administrator; `--kind`, `--access read_write`, `--urgency`, `--docs-url` optional; at a terminal it asks for what is missing). The request becomes a public issue that never names your organisation |
+| `models` | the model library and its evidence scores |
+| `kb`, `kb show`, `kb ingest <index> --source <connection or connector> [--wait]` | knowledge bases and their freshness; sync a connection into one now (`connections sync` by another name, as yourself), and with `--wait` until the deployment reports the sync finished |
+| `agents`, `agents show`, `agents init`, `agents logs` | the agents, and scaffold one |
+| `agents deploy <pack:card> --version V [--wait]`, `agents rollback <pack:card> [--to V]` | make a released version current (the `deploy` scope): live at once when the version passed its evaluation gate and your policy allows it, otherwise a request a person approves in LightHouse; `--wait` follows it to the end |
+| `evals list`, `evals list --fail-below N` | evaluation results, as a release gate on one named metric (`--metric`, default `f1`); fails closed when a row has no such number |
+| `evals run <pack:card> --cap N [--set S] [--wait] [--fail-below N]` | run the agent's scheduled evaluation once under a spend cap (the `deploy` scope, or a person); with `--wait`, gate on the new results |
+| `runs`, `runs show`, `runs tail` | what ran, and what is running now |
+| `spend` | spend by day, model, pack, agent or connection; the forecast; the estimated savings |
+| `limits` | the limits in force, and whether the engines applied them |
+| `terms` | the commercial terms in force |
+
+### A release gate in CI
+
+`evals run --wait --fail-below` exits 1 when a new evaluation row did not
+pass, or its metric is below the threshold or missing (it fails closed), so
+a pipeline can evaluate, then deploy only what passed. Deploying and running
+an evaluation need a person's delegated token with the `deploy` scope
+(`lighthouse login --scope "telemetry:read agents:read deploy"`, eight hours,
+in `LIGHTHOUSE_TOKEN`); a machine key reads but never deploys or spends.
+
+```yaml
+release:
+  image: python:3.13-slim
+  script:
+    - pip install -q lighthouse-cli
+    - lighthouse evals run research:summary --cap 5 --wait --fail-below 0.8 --json
+    - lighthouse agents deploy research:summary --version "$CI_COMMIT_TAG" --wait --json
+```
+
+`agents deploy --wait` exits 0 when the version is current, 1 when the
+deployment refused it or a person rejected the request, and 5 when it is
+still waiting at `--wait-timeout` (default 900 seconds; 1,800 for `evals run`).
+A rate limit (`429`) is waited out and retried by the CLI itself.
+
+## Output and exit codes
+
+**Language.** `--lang <tag>` (or `LIGHTHOUSE_LANG`) picks the language of help,
+prompts, errors and table headers for one run: `en` (British English, the
+default and the source), `fr`, `de`, `es`, `it`, `pt`, `nl`, `ga`, `ja`, `zh-Hans`, `zh-Hant` or `ar`. Without
+either, the CLI uses the language you set in the portal (kept by `lighthouse
+whoami` and `lighthouse language`), then `LANG`. `--json` is never translated: its
+keys, values and the `error` code are the same in every language. The translations
+are machine-drafted, pending native review; the command-specific notes not yet in a
+catalogue are shown in English.
+
+`--json` on every command: one JSON document on standard output and **nothing
+else** — prose, prompts and progress go to standard error, so
+`lighthouse spend --json | jq` works while the command is still talking to you.
+`runs tail --json` writes JSON Lines, one object per change.
+
+| Code | Meaning | What a pipeline should do |
+|---|---|---|
+| 0 | it worked | carry on |
+| 1 | the command failed | stop; the message says why |
+| 2 | the command line was wrong | stop; fix the invocation |
+| 3 | not signed in, or the credential expired | `lighthouse login` |
+| 4 | signed in, but the role or scope does not reach this | ask an administrator |
+| 5 | refused for now: a rate limit, or a retryable 5xx | retry later |
+| 7 | it needed a person and none is there | stop |
+
+`--json` is the API's own document: the keys the service sent, unchanged, with
+`ok` added. Every `--json` output is frozen in `tests/golden/`, built from
+fixtures that are themselves generated from the service's OpenAPI document
+(`tests/api_fixtures.py`, checked by `tests/test_fixtures.py`), so a key cannot
+be renamed or dropped, and the CLI cannot drift from the API, without a reviewer
+seeing it in the diff.
+
+## Develop
+
+```sh
+pip install -e ".[dev]"
+pytest                                  # no network, no keychain
+python -m tests.api_fixtures            # regenerate the fixtures from docs/api/openapi.json
+LIGHTHOUSE_GOLDEN=update pytest         # re-record the golden files, then read the diff
+ruff check . && mypy && bandit -q -c pyproject.toml -r lighthouse
+```
+
+The integration test lives with the service (`service/tests/test_cli_integration.py`),
+because that is where the fixtures that build a working tenant are. It runs the
+real CLI against the real application in process: the device flow, connect,
+tail, spend, and the refusals.
+
+```sh
+cd ../service && pip install -e ".[dev]" -e ../cli
+AAL_TEST_PG_DSN=... pytest tests/test_cli_integration.py
+```
+
+Three things are stood in for and no more: the keychain (a dictionary), the
+browser (a recorder), and `sleep`. The device code is approved by calling the
+portal's own route as the person would have after clicking, so the grant, the
+token and every check on it are real.
+
+**The gap, named.** That test runs the CLI against the application *in
+process*, through Starlette's own test transport. So the routes, the database,
+the row-level security, the OAuth flow and the refusals are all real, and
+everything between the CLI's `httpx` call and the service is not: TLS, a
+redirect, chunked transfer, a `Retry-After` from Cloudflare. The retry and
+back-off code is covered against a stubbed transport in `tests/test_plumbing.py`
+and the back-off arithmetic is a pure function, so what is unproved is the
+socket, not the logic. The honest next step is a scenario in `e2e/`, where the
+stack is already stood up behind its Cloudflare stand-in; it is not in this
+change, and `--target live` against a deployed hostname is the other half of
+it.
+
+© 2026 Atlantic Agentic Labs.

lighthouse_cli-0.16.0/lighthouse/__init__.py

@@ -0,0 +1,6 @@
+# Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+"""The `lighthouse` command line for LightHouse."""
+from __future__ import annotations
+
+__version__ = "0.16.0"

lighthouse_cli-0.16.0/lighthouse/__main__.py

@@ -0,0 +1,9 @@
+# Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+"""`python -m lighthouse`, the same as the `lighthouse` script."""
+from __future__ import annotations
+
+from lighthouse.main import run
+
+if __name__ == "__main__":
+    run()