lighthouse-cli 0.16.0__tar.gz → 0.17.1__tar.gz

{lighthouse_cli-0.16.0/lighthouse_cli.egg-info → lighthouse_cli-0.17.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lighthouse-cli
-Version: 0.16.0
+Version: 0.17.1
 Summary: The LightHouse command line: sign in, connect your estate, deploy agents, watch runs
 License-Expression: Apache-2.0
 Classifier: Programming Language :: Python :: 3
@@ -18,6 +18,4 @@ 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 → lighthouse_cli-0.17.1}/README.md

@@ -1,4 +1,4 @@
-# The `lighthouse` command line for LightHouse™
+# The `lighthouse-ai` 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
@@ -6,10 +6,10 @@ 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]'
+brew install atlantic-agentic-labs/tap/lighthouse-ai     # or npm, pip, curl (below)
+lighthouse-ai login --host t7m2kqx9vbn.atlanticagenticlabs.com
+lighthouse-ai whoami
+lighthouse-ai spend --by model --json | jq '.rows[0]'
 ```
 
 ## Why Python
@@ -23,25 +23,20 @@ evidence:
 | **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 |
+| Against: 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.
+That last line is the real cost, and it is paid rather than hidden: the CLI
+installs from source as a package, so it needs Python (`pipx` brings its own
+isolated environment; Homebrew brings its own virtualenv). There is no
+stand-alone binary: the stand-alone installer was retired on 11 November 2026
+and the CLI ships as packages only.
 
 ## Install
 
-| Route | Command | What it installs |
+| Route | Command | Platforms |
 |---|---|---|
-| 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`) |
+| pipx or pip | `pipx install lighthouse-cli` (or `pip install lighthouse-cli`) | Linux, macOS, Windows |
+| Homebrew | `brew install atlantic-agentic-labs/tap/lighthouse-ai` | macOS, Linux (`installers/lighthouse-ai.rb`) |
 
 **Nothing is published yet.** From a clone:
 
@@ -49,19 +44,19 @@ the valuable part and none of it is language-specific.
 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.
+What has to exist before either route works is in `installers/README.md`: a
+PyPI project with a trusted publisher and a Homebrew tap. No registry
+credential is stored for PyPI.
 
 ## Signing in
 
 ```
-$ lighthouse login --host t7m2kqx9vbn.atlanticagenticlabs.com
+$ lighthouse-ai 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).
+Signed in to Example Org as ops@example.test (client_admin).
 ```
 
 A device code, exactly as `stripe login` does it. The person approves in their
@@ -73,8 +68,8 @@ 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
+lighthouse-ai whoami --profiles
+lighthouse-ai logout --all          # revokes at the service, then forgets
 ```
 
 **What the credential can do** is in
@@ -104,9 +99,9 @@ spend-report:
     # 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
+    - lighthouse-ai whoami --json
+    - lighthouse-ai evals list --fail-below 0.8 --json
+    - lighthouse-ai spend --json > spend.json
 ```
 
 **Why two credentials.** Every tenant host sits behind Cloudflare Access except
@@ -120,7 +115,7 @@ service token is missing or wrong and names the two variables.
 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
+machine key has no person behind it, so `lighthouse-ai 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
@@ -130,7 +125,7 @@ store at all.
 keychain with the delegated token:
 
 ```sh
-printf '%s\n' "$ACCESS_SECRET" | lighthouse login --access-client-id "$ACCESS_ID" \
+printf '%s\n' "$ACCESS_SECRET" | lighthouse-ai login --access-client-id "$ACCESS_ID" \
     --access-client-secret-stdin
 ```
 
@@ -158,6 +153,10 @@ a terminal, and when `CI`, `NO_COLOR` or `TERM=dumb` is set.
 | `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 |
+| `runs export <run> [--format json\|pdf] [-o file]` | one run's content-free export, as JSON or a branded PDF (contract 1.32); audited |
+| `telemetry import <bundle>`, `telemetry status --deployment D` | upload a telemetry bundle from a deployment with no network path, and see the batches held and missing (contract 1.33; client_admin or the `offline` scope) |
+| `commands export --deployment D --out <file>` | the waiting commands as a signed command file for the deployment's `apply-file` (contract 1.33); audited |
+| `commands import-results <answers.json>` | upload the signed answers the deployment's `apply-file --results` wrote; each is verified and matched to an exported command (contract 1.35); audited |
 | `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 |
@@ -168,7 +167,7 @@ a terminal, and when `CI`, `NO_COLOR` or `TERM=dumb` is set.
 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,
+(`lighthouse-ai login --scope "telemetry:read agents:read deploy"`, eight hours,
 in `LIGHTHOUSE_TOKEN`); a machine key reads but never deploys or spends.
 
 ```yaml
@@ -176,8 +175,8 @@ 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
+    - lighthouse-ai evals run research:summary --cap 5 --wait --fail-below 0.8 --json
+    - lighthouse-ai agents deploy research:summary --version "$CI_COMMIT_TAG" --wait --json
 ```
 
 `agents deploy --wait` exits 0 when the version is current, 1 when the
@@ -190,15 +189,15 @@ A rate limit (`429`) is waited out and retried by the CLI itself.
 **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
+either, the CLI uses the language you set in the portal (kept by `lighthouse-ai
+whoami` and `lighthouse-ai 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.
+`lighthouse-ai 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 |
@@ -206,7 +205,7 @@ else** — prose, prompts and progress go to standard error, so
 | 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` |
+| 3 | not signed in, or the credential expired | `lighthouse-ai 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 |

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/__init__.py

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

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/__main__.py

@@ -1,6 +1,6 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`python -m lighthouse`, the same as the `lighthouse` script."""
+"""`python -m lighthouse`, the same as the `lighthouse-ai` script."""
 from __future__ import annotations
 
 from lighthouse.main import run

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/agents.py

@@ -1,13 +1,13 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse agents`: list, inspect, scaffold, deploy, read logs, roll back.
+"""`lighthouse-ai agents`: list, inspect, scaffold, deploy, read logs, roll back.
 
-    lighthouse agents                              # every agent, with its state
-    lighthouse agents show research:summary
-    lighthouse agents init my-agent                # scaffold agent.toml here
-    lighthouse agents logs research:summary --limit 20
-    lighthouse agents deploy research:summary --version 1.4.0 --wait
-    lighthouse agents rollback research:summary --to 1.3.0
+    lighthouse-ai agents                              # every agent, with its state
+    lighthouse-ai agents show research:summary
+    lighthouse-ai agents init my-agent                # scaffold agent.toml here
+    lighthouse-ai agents logs research:summary --limit 20
+    lighthouse-ai agents deploy research:summary --version 1.4.0 --wait
+    lighthouse-ai agents rollback research:summary --to 1.3.0
 
 **`init` is local and complete.** It writes an `agent.toml` next to you, with
 every field the pipeline will ask for and a comment on each: instructions, the
@@ -20,7 +20,7 @@ with `--trace`, one run's spans, which is what anybody actually wants when an
 agent misbehaves.
 
 **`deploy` and `rollback` make a released version current** (the `deploy`
-scope: sign in with `lighthouse login --scope "telemetry:read agents:read
+scope: sign in with `lighthouse-ai login --scope "telemetry:read agents:read
 deploy"`). Each sends `release.add` for the agent and version; rolling back is
 the same with an earlier version (`--to`, or the last version that passed its
 gate before the current one). The service decides what happens:
@@ -47,7 +47,7 @@ from lighthouse.flags import inherited
 from lighthouse.main import Command, Context
 from lighthouse.out import Out
 
-SCAFFOLD = '''# An agent for LightHouse. `lighthouse agents deploy` reads this file.
+SCAFFOLD = '''# An agent for LightHouse. `lighthouse-ai agents deploy` reads this file.
 #
 # Everything here is checked before an agent runs: the model policy against the
 # model library's evidence scores, the knowledge bases against what this tenant
@@ -63,7 +63,7 @@ instructions = """
 You are …
 """
 
-# Knowledge bases this agent may read, by index name (`lighthouse kb`).
+# Knowledge bases this agent may read, by index name (`lighthouse-ai kb`).
 knowledge_bases = []
 
 # Tools, by name. Write access is a separate, named tool and sits behind an
@@ -142,8 +142,8 @@ def _init(ctx: Context) -> dict[str, Any]:
                        hint="pass --force to overwrite it")
     target.write_text(SCAFFOLD.format(name=ctx.args.name))
     return {"ok": True, "wrote": str(target), "agent": ctx.args.name,
-            "next": ["edit it", "lighthouse evals run <pack:card> --cap 5 --wait",
-                     "lighthouse agents deploy <pack:card> --version <version> --wait"]}
+            "next": ["edit it", "lighthouse-ai evals run <pack:card> --cap 5 --wait",
+                     "lighthouse-ai agents deploy <pack:card> --version <version> --wait"]}
 
 
 def _logs(ctx: Context) -> dict[str, Any]:
@@ -165,10 +165,10 @@ def agents(ctx: Context) -> dict[str, Any]:
         return _logs(ctx)
     if which == "deploy":
         return _release(ctx, str(ctx.args.version), "deploy",
-                        ctx.args.reason or "deployed from the lighthouse CLI")
+                        ctx.args.reason or "deployed from the lighthouse-ai CLI")
     if which == "rollback":
         return _release(ctx, ctx.args.to or _previous(ctx), "rollback",
-                        ctx.args.reason or "rolled back from the lighthouse CLI")
+                        ctx.args.reason or "rolled back from the lighthouse-ai CLI")
     if which == "show":
         agent = ctx.args.agent
         if not agent:

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/builds.py

@@ -1,11 +1,11 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse builds`: agents built with the agent builder, and where each is.
+"""`lighthouse-ai builds`: agents built with the agent builder, and where each is.
 
-    lighthouse builds
-    lighthouse builds --status publish_requested
-    lighthouse builds show 5f0c...e1            # one, with its scores and estimated cost
-    lighthouse builds --json | jq '.proposals[] | select(.status == "evaluated")'
+    lighthouse-ai builds
+    lighthouse-ai builds --status publish_requested
+    lighthouse-ai builds show 5f0c...e1            # one, with its scores and estimated cost
+    lighthouse-ai builds --json | jq '.proposals[] | select(.status == "evaluated")'
 
 Reads `GET /api/v1/builder/proposals` (contract 1.24). Read only, on purpose:
 an agent is drafted, sent to your deployment, evaluated and approved in the

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/collectors.py

@@ -1,9 +1,9 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse collectors`: ask Atlantic for a collector, and follow the request.
+"""`lighthouse-ai collectors`: ask Atlantic for a collector, and follow the request.
 
-    lighthouse collectors requests                  # your tenant's requests and their stage
-    lighthouse collectors request --vendor "Invented CRM" --product "Sales Suite" \\
+    lighthouse-ai collectors requests                  # your tenant's requests and their stage
+    lighthouse-ai collectors request --vendor "Invented CRM" --product "Sales Suite" \\
         --reads "Accounts and opportunities" --cloud aws [--kind crm] [--access read] \\
         [--urgency normal] [--docs-url https://...]
 
@@ -15,7 +15,7 @@ client already asked for the same vendor and product, your request joins
 that issue instead of opening another.
 
 **Asking needs the handler or client_admin role**; reading needs viewer. Both
-use the CLI's own sign-in (`lighthouse login`). At a terminal, a field left
+use the CLI's own sign-in (`lighthouse-ai login`). At a terminal, a field left
 off the command line is asked for; under `--no-input`, or with standard input
 not a terminal, a missing required field is exit 7.
 
@@ -108,10 +108,10 @@ def _ask(ctx: Context) -> dict[str, Any]:
     except Refused as e:
         if e.error in ("invalid", "bad_query", "names_your_organisation"):
             raise CliError(e.message, code=USAGE, error=e.error,
-                           hint="see `lighthouse collectors request --help`") from None
+                           hint="see `lighthouse-ai collectors request --help`") from None
         if e.error == "conflict":
             raise CliError(e.message, code=e.code, error=e.error,
-                           hint="`lighthouse collectors requests` shows it") from None
+                           hint="`lighthouse-ai collectors requests` shows it") from None
         raise
     return {"ok": True, "action": "request", **_row(got), "access": got.get("access"),
             "deployment_cloud": got.get("deployment_cloud"), "urgency": got.get("urgency")}
@@ -140,7 +140,7 @@ def _show(out: Out, body: dict[str, Any]) -> None:
               [[r["id"], f"{r['vendor']} {r['product']}", r["stage"], _issue(r),
                 r["request_count"] if r["request_count"] else "-", r["created_at"] or "-"]
                for r in body["requests"]])
-    out.note("`lighthouse collectors request --vendor ... --product ...` asks for another")
+    out.note("`lighthouse-ai collectors request --vendor ... --product ...` asks for another")
 
 
 COMMANDS = (Command("collectors", "ask Atlantic for a collector, and follow your requests",

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/connect.py

@@ -1,15 +1,15 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse connect <provider>`: open the provider's own approval.
+"""`lighthouse-ai connect <provider>`: open the provider's own approval.
 
-    lighthouse connect                 # what is connected, and what can be
-    lighthouse connect github
-    lighthouse connect aws --no-browser
-    lighthouse connect gitlab --reuse-local     # offers `glab`'s sign-in; asks first
+    lighthouse-ai connect                 # what is connected, and what can be
+    lighthouse-ai connect github
+    lighthouse-ai connect aws --no-browser
+    lighthouse-ai connect gitlab --reuse-local     # offers `glab`'s sign-in; asks first
     security find-generic-password -s gh-ci -w | \
-        lighthouse connect github --credential-stdin --access read_write \
-            --target organisation=example-air       # an existing token, as you
-    ... | lighthouse connect github --credential-stdin \
+        lighthouse-ai connect github --credential-stdin --access read_write \
+            --target organisation=example-org       # an existing token, as you
+    ... | lighthouse-ai connect github --credential-stdin \
             --deployment-key "$(terraform output -raw deployment_public_key)"
 
 **What this command does and does not do.** It opens the portal's Connect page
@@ -302,7 +302,7 @@ def _read_credential(ctx: Context) -> str:
     if len(got.strip()) < 8:
         raise CliError("no credential on standard input", code=USAGE, error="no_credential",
                        hint="pipe it in: security find-generic-password -s <name> -w | "
-                            "lighthouse connect <provider> --credential-stdin")
+                            "lighthouse-ai connect <provider> --credential-stdin")
     return got
 
 
@@ -546,7 +546,7 @@ def _show_listing(out: Out, body: dict[str, Any]) -> None:
                 p["scopes"]] for p in body["providers"]])
     if not body["providers"]:
         out.note("no connector matches; ask for one from Help, or tell your Atlantic contact")
-    out.note("`lighthouse connect <provider>` opens the approval; `--all` lists the coming "
+    out.note("`lighthouse-ai connect <provider>` opens the approval; `--all` lists the coming "
              "ones too; `connect list --family F --kind K --search WORDS` narrows the list")
 
 
@@ -559,7 +559,7 @@ def connect(ctx: Context) -> dict[str, Any]:
     if provider is None:
         raise CliError(f"{name!r} is not a provider LightHouse knows", code=USAGE,
                        error="unknown_provider",
-                       hint="run `lighthouse connect --all` to see every one")
+                       hint="run `lighthouse-ai connect --all` to see every one")
     if getattr(ctx.args, "credential_stdin", False):
         return _connect_token(ctx, provider)
     url = connect_url(ctx.host)

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/connections.py

@@ -1,12 +1,12 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse connections`: what is connected, how often each syncs, and Sync now.
+"""`lighthouse-ai connections`: what is connected, how often each syncs, and Sync now.
 
-    lighthouse connections                         # every connection, its schedule, next sync
-    lighthouse connections schedule cx-abcdef123456 --mode hourly
-    lighthouse connections schedule cx-abcdef123456 --mode daily --at 06:30 --tz Europe/London
-    lighthouse connections schedule cx-abcdef123456 --mode off
-    lighthouse connections sync cx-abcdef123456 --reason "a page was fixed this morning"
+    lighthouse-ai connections                         # every connection, its schedule, next sync
+    lighthouse-ai connections schedule cx-abcdef123456 --mode hourly
+    lighthouse-ai connections schedule cx-abcdef123456 --mode daily --at 06:30 --tz Europe/London
+    lighthouse-ai connections schedule cx-abcdef123456 --mode off
+    lighthouse-ai connections sync cx-abcdef123456 --reason "a page was fixed this morning"
 
 **The listing** reads `GET /api/v1/connectors`, the same connections the
 Connect page shows, with each one's schedule as the deployment reports it
@@ -124,7 +124,7 @@ def _act(ctx: Context, method: str, suffix: str, body: dict[str, Any]) -> dict[s
     except Refused as e:
         if e.error == "invalid":
             raise CliError(e.message, code=USAGE, error="invalid",
-                           hint="see `lighthouse connections schedule --help`") from None
+                           hint="see `lighthouse-ai connections schedule --help`") from None
         if e.error == "commands_disabled":
             raise CliError(e.message, code=e.code, error=e.error,
                            hint=f"a client administrator switches connector.schedule and "
@@ -180,8 +180,8 @@ def _show(out: Out, body: dict[str, Any]) -> None:
             if c.get("check"):
                 out.note(f"{c['id']} ({c['connector']}) is failing: {c['check_words']} "
                          f"({c['check']}).{' ' + c['fix'] if c.get('fix') else ''}")
-        out.note("`lighthouse connections schedule <id> --mode ...` sets one; "
-                 "`lighthouse connections sync <id>` syncs one now")
+        out.note("`lighthouse-ai connections schedule <id> --mode ...` sets one; "
+                 "`lighthouse-ai connections sync <id>` syncs one now")
         return
     if body["action"] == "schedule":
         out.pairs([("connection", body["connection"]), ("schedule", body["schedule"]),

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/evals.py

@@ -1,9 +1,9 @@
-"""`lighthouse evals`: evaluation results, and running a set.
+"""`lighthouse-ai evals`: evaluation results, and running a set.
 
-    lighthouse evals                          # the latest results
-    lighthouse evals list --pack research --json
-    lighthouse evals list --fail-below 0.8    # a release gate on metrics.f1
-    lighthouse evals run research:summary --cap 5 --wait --fail-below 0.8
+    lighthouse-ai evals                          # the latest results
+    lighthouse-ai evals list --pack research --json
+    lighthouse-ai evals list --fail-below 0.8    # a release gate on metrics.f1
+    lighthouse-ai evals run research:summary --cap 5 --wait --fail-below 0.8
 
 `evals` reads `GET /api/v1/evals`, every page of it: each row is one measurement
 of one suite for one agent version, with `passed` (did it meet its own bar) and
@@ -30,8 +30,8 @@ new row did not pass, and, with `--fail-below N`, when a new row's metric is
 below N or missing (the same closed gate as `evals list --fail-below`). In a
 pipeline:
 
-    lighthouse evals run research:summary --cap 5 --wait --fail-below 0.8 \
-        && lighthouse agents deploy research:summary --version "$VERSION" --wait
+    lighthouse-ai evals run research:summary --cap 5 --wait --fail-below 0.8 \
+        && lighthouse-ai agents deploy research:summary --version "$VERSION" --wait
 """
 from __future__ import annotations
 
@@ -100,7 +100,7 @@ def _run(ctx: Context) -> dict[str, Any]:
         raise CliError("--fail-below gates on the results, so it needs --wait", code=USAGE,
                        error="usage")
     body: dict[str, Any] = {"cap_usd": f"{a.cap:.2f}",
-                            "reason": a.reason or "evaluation run from the lighthouse CLI"}
+                            "reason": a.reason or "evaluation run from the lighthouse-ai CLI"}
     if a.eval_set:
         body["set"] = a.eval_set
     if a.deployment:

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/kb.py

@@ -1,12 +1,12 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse kb`: knowledge bases, their freshness, and ingesting into them.
+"""`lighthouse-ai kb`: knowledge bases, their freshness, and ingesting into them.
 
-    lighthouse kb                      # every knowledge base, with its freshness
-    lighthouse kb show <index>
-    lighthouse kb ingest ops --source confluence --wait
-    lighthouse kb ingest ops --source cx-abcdef123456
-    lighthouse kb upload <file> [--deployment NAME]                  (contract 1.21)
+    lighthouse-ai kb                      # every knowledge base, with its freshness
+    lighthouse-ai kb show <index>
+    lighthouse-ai kb ingest ops --source confluence --wait
+    lighthouse-ai kb ingest ops --source cx-abcdef123456
+    lighthouse-ai kb upload <file> [--deployment NAME]                  (contract 1.21)
 
 `kb` and `kb show` read `GET /api/v1/knowledge-bases` and
 `/api/v1/knowledge-bases/{index}` (contract 1.14): the indexes, what is in
@@ -143,7 +143,7 @@ def _resolve(ctx: Context, connections: list[dict[str, Any]]) -> dict[str, Any]:
     if not hit:
         raise CliError(f"no live connection matches {a.source!r}"
                        + (f" and {a.repo!r}" if a.repo else ""), code=USAGE,
-                       error="no_connection", hint="`lighthouse connections` lists them")
+                       error="no_connection", hint="`lighthouse-ai connections` lists them")
     if len(hit) > 1:
         raise CliError(f"{len(hit)} connections match {a.source!r}: name one", code=USAGE,
                        error="ambiguous_connection",
@@ -165,7 +165,7 @@ def _ingest(ctx: Context) -> dict[str, Any]:
     try:
         got = person.post(f"/api/v1/connections/{cid}/sync", {k: v for k, v in {
             "deployment": base.get("deployment"),
-            "reason": a.reason or f"ingest into {a.index} from the lighthouse CLI"}.items()
+            "reason": a.reason or f"ingest into {a.index} from the lighthouse-ai CLI"}.items()
             if v is not None}) or {}
     finally:
         person.close()

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/language.py

@@ -1,10 +1,10 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse language`: the language this CLI, the portal, MCP and the
+"""`lighthouse-ai language`: the language this CLI, the portal, MCP and the
 assistant speak to you (contract 1.29).
 
-    lighthouse language              your setting, your organisation's, and what is in use
-    lighthouse language --list       only the languages on offer
+    lighthouse-ai language              your setting, your organisation's, and what is in use
+    lighthouse-ai language --list       only the languages on offer
 
 Read only. A person sets their own language in the portal under Preferences
 (and a client administrator the organisation's under Settings): a delegated

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/limits.py

@@ -1,9 +1,9 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse limits`: the spend limits in force, and whether they reached the engines.
+"""`lighthouse-ai limits`: the spend limits in force, and whether they reached the engines.
 
-    lighthouse limits
-    lighthouse limits --json
+    lighthouse-ai limits
+    lighthouse-ai limits --json
 
 Reads `GET /api/v1/limits`: each limit's scope (`scope_kind` and `scope`),
 its period, its cap (`cap_usd`), what has been spent against it (`spent_usd`,

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/login.py

@@ -1,11 +1,11 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse login`, `logout` and `tokens`.
+"""`lighthouse-ai login`, `logout` and `tokens`.
 
-    lighthouse login --host t7m2kqx9vbn.atlanticagenticlabs.com
-    lighthouse login --scope "telemetry:read agents:read knowledge:read"
-    lighthouse logout [--all]
-    lighthouse tokens              # every delegated token of mine, and revoke one
+    lighthouse-ai login --host t7m2kqx9vbn.atlanticagenticlabs.com
+    lighthouse-ai login --scope "telemetry:read agents:read knowledge:read"
+    lighthouse-ai logout [--all]
+    lighthouse-ai tokens              # every delegated token of mine, and revoke one
 
 `login` runs the device flow (device.py), stores the token in the OS keychain
 (credentials.py), remembers the host in the profile file (config.py), and then
@@ -47,7 +47,7 @@ def _configure_login(ap: argparse.ArgumentParser) -> None:
                                     "(default: telemetry:read agents:read)")
     ap.add_argument("--no-browser", action="store_true", dest="no_browser",
                     help="print the URL instead of opening a browser")
-    ap.add_argument("--name", default="the lighthouse CLI",
+    ap.add_argument("--name", default="the lighthouse-ai CLI",
                     help="how this sign-in is described in the portal and the audit log")
     ap.add_argument("--access-client-id", dest="access_client_id", metavar="ID",
                     help="the tenant's Cloudflare Access service token id, to keep with "

{lighthouse_cli-0.16.0 → lighthouse_cli-0.17.1}/lighthouse/commands/models.py

@@ -1,10 +1,10 @@
 # Copyright 2026 Atlantic Agentic Labs. All Rights Reserved.
 # SPDX-License-Identifier: Apache-2.0
-"""`lighthouse models`: the model library, with its evidence scores.
+"""`lighthouse-ai models`: the model library, with its evidence scores.
 
-    lighthouse models
-    lighthouse models --provider bedrock
-    lighthouse models --json | jq '.items[] | select(.state == "available") | .model'
+    lighthouse-ai models
+    lighthouse-ai models --provider bedrock
+    lighthouse-ai models --json | jq '.items[] | select(.state == "available") | .model'
 
 Reads `GET /api/v1/models`. Price cards are shown to a client administrator and
 to AAL staff only, and the service decides that, not this command: a viewer's