tripl 0.2.2__tar.gz → 0.3.0__tar.gz

{tripl-0.2.2 → tripl-0.3.0}/PKG-INFO

@@ -1,11 +1,11 @@
 Metadata-Version: 2.5
 Name: tripl
-Version: 0.2.2
+Version: 0.3.0
 Summary: Operator CLI for a tripl tracking-plan instance: diagnostics, health and live monitoring
-Project-URL: Homepage, https://vladenisov.github.io/tripl/
-Project-URL: Documentation, https://vladenisov.github.io/tripl/run/cli
-Project-URL: Repository, https://github.com/vladenisov/tripl
-Project-URL: Issues, https://github.com/vladenisov/tripl/issues
+Project-URL: Homepage, https://docs.tripl.io/
+Project-URL: Documentation, https://docs.tripl.io/run/cli
+Project-URL: Repository, https://github.com/tripl-io/tripl
+Project-URL: Issues, https://github.com/tripl-io/tripl/issues
 Author: Vladislav Denisov
 License-Expression: Apache-2.0
 License-File: LICENSE
@@ -38,7 +38,7 @@ import package is **`tripl_cli`**. The last one is deliberate: the service's own
 source package is `backend/src/tripl/`, so a distribution that installed an
 importable `tripl` would shadow it in any environment holding both — a
 contributor's backend venv, for one. The service is packaged as the separate
-`tripl-server` distribution (tripl-ey6j.6), so `tripl` names this CLI alone.
+`tripl-server` distribution, so `tripl` names this CLI alone.
 
 This package also owns the **shared async REST client** (`tripl_cli.client`) and
 the **shared request layer** above it (`tripl_cli.api`): every REST path, query
@@ -72,7 +72,7 @@ From git without a checkout — how you get a revision that is not released yet.
 It resolves, but it is not exercised by CI:
 
 ```bash
-uvx --from "git+https://github.com/vladenisov/tripl.git#subdirectory=cli" tripl --version
+uvx --from "git+https://github.com/tripl-io/tripl.git#subdirectory=cli" tripl --version
 ```
 
 ## Commands
@@ -386,7 +386,7 @@ release. `title`, `summary` and `message` are prose. **Assert on `code` and
 Full reference — every check, every finding code with its `evidence` keys, every
 `watch` event token and the JSON Lines envelope, and what an operator should
 actually do about each one:
-<https://vladenisov.github.io/tripl/run/cli> (source:
+<https://docs.tripl.io/run/cli> (source:
 [`website/docs/run/cli.md`](../website/docs/run/cli.md)).
 
 ## Configuration

{tripl-0.2.2 → tripl-0.3.0}/README.md

@@ -10,7 +10,7 @@ import package is **`tripl_cli`**. The last one is deliberate: the service's own
 source package is `backend/src/tripl/`, so a distribution that installed an
 importable `tripl` would shadow it in any environment holding both — a
 contributor's backend venv, for one. The service is packaged as the separate
-`tripl-server` distribution (tripl-ey6j.6), so `tripl` names this CLI alone.
+`tripl-server` distribution, so `tripl` names this CLI alone.
 
 This package also owns the **shared async REST client** (`tripl_cli.client`) and
 the **shared request layer** above it (`tripl_cli.api`): every REST path, query
@@ -44,7 +44,7 @@ From git without a checkout — how you get a revision that is not released yet.
 It resolves, but it is not exercised by CI:
 
 ```bash
-uvx --from "git+https://github.com/vladenisov/tripl.git#subdirectory=cli" tripl --version
+uvx --from "git+https://github.com/tripl-io/tripl.git#subdirectory=cli" tripl --version
 ```
 
 ## Commands
@@ -358,7 +358,7 @@ release. `title`, `summary` and `message` are prose. **Assert on `code` and
 Full reference — every check, every finding code with its `evidence` keys, every
 `watch` event token and the JSON Lines envelope, and what an operator should
 actually do about each one:
-<https://vladenisov.github.io/tripl/run/cli> (source:
+<https://docs.tripl.io/run/cli> (source:
 [`website/docs/run/cli.md`](../website/docs/run/cli.md)).
 
 ## Configuration

{tripl-0.2.2 → tripl-0.3.0}/pyproject.toml

@@ -1,9 +1,9 @@
 [project]
 name = "tripl"
-# 0.2.2: `tripl_cli.api` gained the `docs` module and typed-property reads
-# that tripl-mcp 0.2.2 imports, so this has to reach the index FIRST (tag
-# `cli-v0.2.2`), then tripl-mcp 0.2.2. Versioned with the service release.
-version = "0.2.2"
+# 0.2.3: the installer's compose file runs RabbitMQ's healthcheck as the
+# rabbitmq user (gosu), so a first `tripl install` no longer races the Erlang
+# cookie. Versioned with the service release; tripl-mcp is unchanged.
+version = "0.3.0"
 description = "Operator CLI for a tripl tracking-plan instance: diagnostics, health and live monitoring"
 readme = "README.md"
 requires-python = ">=3.12"
@@ -37,7 +37,7 @@ classifiers = [
 ]
 dependencies = [
     # httpx alone, and that is a BUDGET rather than a starting point: tripl-mcp
-    # imports its HTTP client from this distribution (tripl-ey6j.1), so every
+    # imports its HTTP client from this distribution, so every
     # dependency added here is forced onto every MCP-server install too. Config
     # parsing uses stdlib tomllib and argument parsing stdlib argparse for
     # exactly that reason — no click, no rich, no tomli.
@@ -48,14 +48,14 @@ dependencies = [
 ]
 
 [project.urls]
-Homepage = "https://vladenisov.github.io/tripl/"
+Homepage = "https://docs.tripl.io/"
 # The docs site sets `routeBasePath: '/'` under baseUrl `/tripl/`, so a page at
 # website/docs/run/cli.md is served at /tripl/run/cli — there is no /docs/
 # segment. mcp-server/pyproject.toml carried the /docs/ form and 404ed; both are
 # corrected now, so check this shape when adding a third package.
-Documentation = "https://vladenisov.github.io/tripl/run/cli"
-Repository = "https://github.com/vladenisov/tripl"
-Issues = "https://github.com/vladenisov/tripl/issues"
+Documentation = "https://docs.tripl.io/run/cli"
+Repository = "https://github.com/tripl-io/tripl"
+Issues = "https://github.com/tripl-io/tripl/issues"
 
 [project.scripts]
 # `main` returns an int rather than calling sys.exit itself: the generated
@@ -83,12 +83,12 @@ build-backend = "hatchling.build"
 # The import package is tripl_cli, NOT tripl: the service's own source package
 # is backend/src/tripl/, and a distribution installing an importable `tripl`
 # would shadow it in any environment holding both — a contributor's backend
-# venv, for one (tripl-ey6j).
+# venv, for one.
 #
 # No `artifacts` entry is needed for src/tripl_cli/install/files/*: hatchling
 # copies a listed package wholesale, so compose.yaml and rabbitmq.conf ship as
 # package data already. Verified against a built wheel rather than assumed —
-# `uv build --wheel` then unzip, and both files are there (tripl-ey6j.3). They
+# `uv build --wheel` then unzip, and both files are there. They
 # are read through importlib.resources, which is why this matters at all.
 # The same holds for src/tripl_cli/codegen/templates/*.mustache, the built-in
 # `tripl codegen` templates (#262): package data by the same rule, read the same way.
@@ -100,7 +100,7 @@ testpaths = ["tests"]
 # An un-awaited coroutine is a RuntimeWarning printed at garbage-collection time,
 # which in a fan-out test reads as unrelated noise long after the bug. doctor
 # builds its fan-outs from comprehensions over targets precisely so a coroutine
-# is never reused or dropped; this makes the failure mode loud (tripl-ey6j.2).
+# is never reused or dropped; this makes the failure mode loud.
 filterwarnings = ["error::RuntimeWarning"]
 
 [tool.ruff]

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/__init__.py

@@ -2,7 +2,7 @@
 
 Two consumers, one implementation: the ``tripl`` console script defined here and
 the separate ``tripl-mcp`` distribution, which depends on this one and imports
-``tripl_cli.client`` rather than carrying its own copy (tripl-ey6j.1). This repo
+``tripl_cli.client`` rather than carrying its own copy. This repo
 has grown the same defect four times over — query keys drifted four ways, the
 event-name regex three, plus security headers and the signal significance gate —
 so a second HTTP client was not on the table.
@@ -15,7 +15,7 @@ from importlib.metadata import PackageNotFoundError, version
 # The DISTRIBUTION name, not the import package name: this is `tripl`, while the
 # module you are reading is `tripl_cli`. version(__name__) would raise
 # PackageNotFoundError forever — nothing publishes a distribution called
-# tripl_cli (tripl-ey6j).
+# tripl_cli.
 DISTRIBUTION_NAME = "tripl"
 
 try:

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/__init__.py

@@ -1,4 +1,4 @@
-"""The one home for REST request construction (tripl-ey6j.5).
+"""The one home for REST request construction.
 
 Shared by the ``tripl`` CLI commands and by ``tripl-mcp``'s tools. A path
 template appears here and nowhere else; ``ApiRequest`` is constructed here and
@@ -27,13 +27,13 @@ half-follow.
 The one import out of this package is ``tripl_cli.model``, for its untyped-JSON
 helpers and ``JOBS_WINDOW``. Those are facts about the wire rather than about
 doctor's verdict machinery, which is why that module now sits at the package
-root instead of under ``diagnostics`` (tripl-azhh) — this import used to read as
+root instead of under ``diagnostics`` — this import used to read as
 the request layer depending on the doctor.
 
 ``page_items``/``page_total`` are RE-EXPORTED from there, not redefined: the
 ``{items, total}`` envelope is an envelope shape, so it is part of what this
 package is about, and ``tripl_cli.api`` is the whole import surface ``tripl_mcp``
-has. Before tripl-i1dt that unwrapping was written out by hand at four call
+has. Previously that unwrapping was written out by hand at four call
 sites — three tool bodies plus the CLI's own watch loop — and they had already
 diverged from the definition: the shared reader drops a non-dict row where the
 tools passed it through, reading the same routes. ``cli/tests/test_contract.py``

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/auth.py

@@ -16,7 +16,7 @@ ME = "/auth/me"
 # the instance it just started instead of a static blurb — "create the first
 # account, it becomes the owner" versus "this instance already has accounts"
 # versus "registration is closed, ask an owner for an invitation". The auth
-# screen reads it for the same reason (tripl-ey6j.3).
+# screen reads it for the same reason.
 STATUS = "/auth/status"
 
 ENDPOINTS: tuple[tuple[str, str], ...] = (("get", ME), ("get", STATUS))

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/branches.py

@@ -60,7 +60,7 @@ def get_diff(slug: str, branch_id: str) -> ApiRequest:
 
     ``tripl plan`` does not expose it: that payload is not a list, so it does
     not fit the one document shape the seven read verbs share, and
-    ``behind_base`` is too load-bearing to smuggle into an ``items`` array
-    (tripl-3ixs). ``tripl-mcp``'s ``get_branch_diff`` calls this.
+    ``behind_base`` is too load-bearing to smuggle into an ``items`` array.
+    ``tripl-mcp``'s ``get_branch_diff`` calls this.
     """
     return ApiRequest("GET", DIFF.format(slug=slug, branch_id=branch_id))

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/event_types.py

@@ -45,7 +45,7 @@ DISMISS_ACTIONS: tuple[str, ...] = ("false_positive", "snooze")
 
 # `tripl drifts reopen`, a verb of its own rather than a flag on `dismiss`:
 # dismissing and reopening move a drift in opposite directions, and
-# `dismiss --reopen` would name the wrong one (tripl-k8j9).
+# `dismiss --reopen` would name the wrong one.
 REOPEN_ACTION = "reopen"
 
 # Everything the CLI can put on the wire. `accept` is the one exclusion, and it
@@ -150,7 +150,7 @@ def field_count(event_type: JsonDict) -> int:
     replace the array it strips. It lives here, beside ``scans.is_dispatchable``
     and for the same reason: a derived operational fact must not be computed
     twice. Both call sites read it now — the MCP's ``_event_type_summary`` spelled
-    it inline until tripl-i1dt, which meant two places had to remember that
+    it inline until recently, which meant two places had to remember that
     ``field_definitions`` is nullable on the wire.
     """
     return len(event_type.get("field_definitions") or [])
@@ -201,7 +201,7 @@ def plan_drift_targets(
     The per-project counts are what let the caller record what each project
     actually got. A split budget lands unevenly by construction, and one
     instance-wide ratio names no project: "we did not look there" is only useful
-    when it says where (tripl-ey6j.9).
+    when it says where.
     """
     totals: dict[str, int] = {}
     per_project: list[list[tuple[str, str]]] = []

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/events.py

@@ -5,7 +5,7 @@ No projection for ``EventListItemResponse``. Its ``field_values`` and
 rather than into a model's context window — so ``tripl events list --json``
 carries a row verbatim, exactly as ``scans.list_jobs`` does. The MCP's
 ``EVENT_LIST_FIELDS`` is a statement about an AGENT's context budget and stays
-where its one consumer is (tripl-i1dt revisits that).
+where its one consumer is.
 """
 
 from __future__ import annotations
@@ -73,7 +73,7 @@ def list_events(
     # (`EventFieldValue.value ILIKE %...%`) - the same shape `meta_value` has,
     # on the other half of an event's content. It shipped with the route in
     # PR #78 and was never mirrored here, so no shell and no agent could ask
-    # "which events carry this value" (tripl-nhj0).
+    # "which events carry this value".
     field_value: str | None = None,
     meta_value: str | None = None,
     event_type_id: str | None = None,
@@ -81,7 +81,7 @@ def list_events(
     # Tri-state, exactly as the route declares it: True and False isolate the
     # two halves and OMITTING it means either. Not a spelling of `status` - an
     # event can be marked reviewed and still sit at status=in_review, which is
-    # why the route grew an axis of its own (tripl-invv).
+    # why the route grew an axis of its own.
     reviewed: bool | None = None,
     # Tri-state like `reviewed`, and for the same reason: True keeps only events
     # whose discussion still has an unanswered thread, False only those with

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/scans.py

@@ -81,7 +81,7 @@ def replay_metrics(slug: str, scan_id: str, body: JsonDict) -> ApiRequest:
     ``scans.py`` guards this route with ``deps.get_owner_user``, which rejects
     ANY request carrying ``request.state.api_key_scope`` — and every valid API
     key sets it, read or write. So a Bearer-token client cannot reach it at all
-    and a ``tripl scans replay`` would 403 every time (tripl-ey6j.5). The builder
+    and a ``tripl scans replay`` would 403 every time. The builder
     exists so the contract test still watches the route; see the follow-up bead
     on whether an owner-role ``tk_w_`` key should be allowed through.
     """
@@ -138,7 +138,7 @@ def config_names(scans: JsonList) -> dict[str, str]:
     AND a time column because doctor asks "is the scheduler working", and a
     config with no interval has no dispatch history worth reading. Watch — and
     ``tripl scans run`` — ask "what is running right now", and a manual replay on
-    an unscheduled config is exactly what tripl-ey6j.4 was filed for.
+    an unscheduled config is exactly what the watch command was built for.
 
     Kept as a name of its own because that exclusion is the fact worth writing
     down; the extraction itself is ``model.names_by_id``, which the event-type

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/api/search.py

@@ -30,7 +30,7 @@ ENTITY_TYPES: tuple[str, ...] = (
 
 # The route's own bounds: `q` is Query(min_length=1, max_length=500) and `limit`
 # is Query(ge=1, le=100) with a server default of 20. Checked locally so a
-# too-long phrase fails at parse time rather than as a 422 (tripl-3ixs).
+# too-long phrase fails at parse time rather than as a 422.
 QUERY_MAX_LENGTH = 500
 LIMIT_DEFAULT = 20
 LIMIT_MAX = 100
@@ -64,7 +64,7 @@ def semantic_used(payload: Any) -> bool:
     something different, so a consumer that cannot tell the two regimes apart
     misreads every score. ``tripl plan search`` publishes it in the document's
     ``meta`` and ``tripl-mcp``'s ``search_plan`` in its envelope — one route, one
-    reader, rather than a ``.get`` per surface (tripl-i1dt).
+    reader, rather than a ``.get`` per surface.
 
     Absent reads as False rather than as unknown: the backend declares
     ``SearchResponse.semantic_used: bool = False``, so a body without the key IS
@@ -84,7 +84,7 @@ def reported_truncated(payload: Any) -> bool | None:
 
     The second envelope fact this route adds, and the one ``total`` cannot give:
     ``total`` is ``len(items)`` after the trim, so on a full page it equals
-    ``limit`` whether or not anything was dropped (tripl-wkwv.3). ``/search``
+    ``limit`` whether or not anything was dropped. ``/search``
     takes no ``offset``, so the answer to a True is a bigger ``limit``.
 
     Absent is ``None`` rather than False HERE because the two surfaces want two

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/check/render.py

@@ -34,7 +34,7 @@ from tripl_cli.render import plural
 SARIF_VERSION = "2.1.0"
 SARIF_SCHEMA = "https://json.schemastore.org/sarif-2.1.0.json"
 SARIF_ROOT_BASE = "%SRCROOT%"
-INFORMATION_URI = "https://vladenisov.github.io/tripl/run/cli"
+INFORMATION_URI = "https://docs.tripl.io/run/cli"
 
 # What each finding code means, for SARIF's rule table and the human legend.
 # A code the validator returns that is not listed here still renders; it just
@@ -49,6 +49,7 @@ RULE_TEXT: dict[str, str] = {
     "dynamic_value": "The value is only known at runtime, so it could not be checked.",
     "too_dynamic": "The name has too many runtime parts to look up in the plan.",
     "wrong_type": "A property's value is not of the type the plan gives it.",
+    "policy_violation": "The call breaks a plan rule the server adds (an organization policy).",
     "oversize_value": "A value exceeded the validator's size limits and was sent as null.",
     "no_verdict": "The validator returned no verdict for this item.",
 }

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/cli.py

@@ -128,7 +128,7 @@ def main(argv: Sequence[str] | None = None) -> int:
     except KeyboardInterrupt:
         # Reached without a real SIGINT by `tripl watch`, whose loop catches the
         # interrupt only long enough to print its footer and then RE-RAISES so
-        # this stays the only place 130 is decided (tripl-ey6j.4).
+        # this stays the only place 130 is decided.
         print(file=sys.stderr)
         return EXIT_INTERRUPTED
 

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/client.py

@@ -4,7 +4,7 @@ Maps tripl's auth/validation failures to typed exceptions the caller can render
 however it needs. Pure pass-through otherwise — no re-modeling of API responses.
 
 Shared by two distributions: the ``tripl`` CLI it ships in, and ``tripl-mcp``,
-which imports it from here rather than carrying a copy (tripl-ey6j.1). Nothing
+which imports it from here rather than carrying a copy. Nothing
 consumer-specific belongs in this module — no MCP vocabulary, no CLI flag names,
 no ``print``. Errors carry structure (``status_code``, ``base_url``) and each
 consumer words its own guidance around them.
@@ -25,7 +25,7 @@ DEFAULT_TIMEOUT_SECONDS = 30.0
 # What this distribution calls itself on the wire. The backend does not read
 # User-Agent, but it is the only thing an operator reading access logs has to
 # tell CLI traffic from agent traffic — so it is a PARAMETER, not a constant,
-# and tripl-mcp passes its own (tripl-ey6j.1).
+# and tripl-mcp passes its own.
 DEFAULT_USER_AGENT = f"tripl/{__version__}"
 
 

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/__init__.py

@@ -9,7 +9,7 @@ than in a module of their own because they exist for one purpose only: a bad
 ``--days``, ``--timeout``, ``--until`` or ``--to`` fails at parse time with
 ``EXIT_USAGE``, before a socket is opened or a container is pulled.
 
-...and, since tripl-3ixs, the three flags that are the same flag on every
+...and, since they were shared, the three flags that are the same flag on every
 command that carries them. ``--json``, ``--timeout`` and ``--project`` were
 spelled out at each ``add_parser`` call, which by the sixth verb was five copies
 of the timeout default and two private ``_add_timeout`` helpers in two command
@@ -82,7 +82,7 @@ def register_all(
     # word; a command acting on a CLASS OF OBJECTS is `<plural-noun> <verb>`.
     scans.register(subparsers, parent)
     drifts.register(subparsers, parent)
-    # The read groups (tripl-3ixs). `events` obeys the grammar above exactly.
+    # The read groups. `events` obeys the grammar above exactly.
     # `plan` bends it — its verbs name KINDS (`plan types`, `plan variables`)
     # rather than actions — and that is deliberate: the alternative was
     # `event-types list`, `variables list`, `branches list` and `search`, four
@@ -92,7 +92,7 @@ def register_all(
     events.register(subparsers, parent)
     plan.register(subparsers, parent)
     # One word each, by the same rule: they act on an instance as a whole — one
-    # that does not exist yet, or one being moved to a new tag (tripl-ey6j.3).
+    # that does not exist yet, or one being moved to a new tag.
     install.register(subparsers, parent)
     upgrade.register(subparsers, parent)
     # One word as well: it records one fact about the project ("we deployed") from
@@ -184,7 +184,7 @@ def require_single_project(args: argparse.Namespace) -> str:
     infer from a drift id, and every ``events``/``plan`` route is per project
     with no instance-wide form at all. Lives beside the other argparse rules
     rather than in ``_write.py``, where it started: four READ verbs now need it,
-    and "exactly one project" was never a write-safety rule (tripl-3ixs).
+    and "exactly one project" was never a write-safety rule.
     """
     slugs: tuple[str, ...] = tuple(getattr(args, "project", None) or ())
     if len(slugs) == 1:

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/_plan.py

@@ -4,7 +4,7 @@ Seven verbs read seven resources and print seven tables. Everything AROUND that
 — resolving ``--branch``, opening a counting reader, stamping the run, choosing
 which stream the human lines go to, and writing at most one JSON document — is
 the same seven times, and was already spelled six times across ``scans.py`` and
-``drifts.py`` before these landed. It is spelled once here (tripl-3ixs).
+``drifts.py`` before these landed. It is spelled once here.
 
 The ``--branch`` rule is the load-bearing part. Every plan read is answered from
 ONE revision, and which one is decided by a query parameter that

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/_resolve.py

@@ -11,7 +11,7 @@ two config names share a prefix is worse than one that refuses to start, and a
 ``--branch`` that silently guessed would answer plan questions about the wrong
 revision — which is the same class of wrong answer, on a read, and quieter. So
 a selector matching nothing lists the candidates and exits 2, and a selector
-matching two names them both and exits 2 (tripl-3ixs).
+matching two names them both and exits 2.
 """
 
 from __future__ import annotations

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/_write.py

@@ -3,7 +3,7 @@
 ``doctor``, ``status`` and ``watch`` are all read-only and a ``tk_r_`` key
 suffices for every one of them. ``scans run``, ``scans cancel``,
 ``drifts dismiss`` and ``drifts reopen`` change the instance, which is a new
-category and needs rules rather than habits (tripl-ey6j.5):
+category and needs rules rather than habits:
 
 * THE SERVER IS THE AUTHORITY ON SCOPE. The ``tk_r_``/``tk_w_`` prefix is derived
   in ``api_key_service.py`` from the scope's first letter and says NOTHING about
@@ -32,7 +32,7 @@ from tripl_cli.errors import TriplConfigError, TriplError
 from tripl_cli.model import JsonDict
 
 # ``require_single_project`` used to live here. It moved to ``commands`` in
-# tripl-3ixs: four read verbs need it now, and "this command acts on one
+# four read verbs need it now, and "this command acts on one
 # project" is an argument rule rather than a write-safety one — leaving it here
 # would have had `tripl plan fields` importing the write-safety module.
 

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/doctor.py

@@ -4,7 +4,7 @@ The command the 2026-07-28..31 incident needed: a scan config failing for days
 behind a generic error, events frozen with no indication why, a stale ACCEPTED
 schema drift that had silently deleted a field, and a retry backoff that looked
 like a hang. All four are visible through read-only REST calls, and this is the
-one invocation that surfaces them (tripl-ey6j.2).
+one invocation that surfaces them.
 """
 
 from __future__ import annotations

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/drifts.py

@@ -11,13 +11,13 @@ Two facts shape this whole module:
   ``schema_drift_service._apply_acceptance_to_plan``, which DELETES the
   FieldDefinition — the exact damage ``doctor``'s ``schema_field_deleted_by_accept``
   finding exists to report. The tool that reports it must not be the easiest way
-  to cause it. Accepting stays in the tripl UI (tripl-ey6j.5).
+  to cause it. Accepting stays in the tripl UI.
 
 ``reopen`` is a VERB, not a flag on ``dismiss``. The two move a drift in
 opposite directions, so ``dismiss --reopen`` would read as its own opposite. It
 prompts for a reason ``dismiss``'s prompt does not share: reopening DISCARDS the
 resolution note and the resolver, so the record of who triaged this drift and
-why is gone, and nothing in the API restores it (tripl-k8j9).
+why is gone, and nothing in the API restores it.
 """
 
 from __future__ import annotations
@@ -310,7 +310,7 @@ def run_list(args: argparse.Namespace, config: Config) -> int:
         types_by_slug = dict(zip(found, type_reads, strict=True))
         # The SAME plan doctor uses, from the same function: two implementations
         # of a budgeted fan-out is how "we did not look there" starts printing as
-        # "nothing there" (tripl-ey6j.5).
+        # "nothing there".
         targets, examined, totals = event_types_api.plan_drift_targets(
             {slug: types_by_slug[slug].value or [] for slug in found}, budget=budget
         )

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/events.py

@@ -8,8 +8,7 @@ edit that lands on main is an edit to the live plan nobody reviewed. Reproducing
 that gate from a shell (resolve a branch, refuse main, prompt, then read the
 server's canonical-name warnings back and tell the operator their proposed name
 was ignored) is a command surface of its own, and shipping the easy half first
-would leave the CLI with a write easier to get wrong than the agent's
-(tripl-3ixs).
+would leave the CLI with a write easier to get wrong than the agent's.
 
 Both verbs take exactly one ``--project``: every route here is per project and
 there is no instance-wide form, so a repeated ``--project`` would be a fan-out
@@ -110,7 +109,7 @@ def _register_list(
         metavar="TEXT",
         # "substring", not "exact": the route compares with ILIKE '%value%', so
         # `--meta-value TRIPL-4` also keeps TRIPL-412. This line claimed "exact
-        # match" until tripl-nhj0 put the sibling --field-value next to it and
+        # match" until the sibling --field-value next to it and
         # the two would have described one ILIKE two different ways.
         help="substring match on any meta value, e.g. a ticket key (case-insensitive)",
     )

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/install.py

@@ -7,7 +7,7 @@ files that already match are left alone, files that differ are reported and
 kept, and the two compose commands run anyway, because "make the running stack
 match what is on disk" is the useful meaning of a re-run.
 
-WHAT IT DELIBERATELY DOES NOT DO (tripl-ey6j.3):
+WHAT IT DELIBERATELY DOES NOT DO:
 
 * It does not create the owner account, connect a data source or run the first
   scan. Two of those three are unreachable with an API key at all and the third
@@ -115,6 +115,30 @@ def register(
             "tag in production so a re-run cannot move you"
         ),
     )
+    parser.add_argument(
+        "--edition",
+        dest="edition",
+        choices=sorted(files.EDITION_IMAGES),
+        # None rather than "community", for the same provenance reason as
+        # --version: only a typed edition is reported back when .env keeps
+        # another image.
+        default=None,
+        help=(
+            "which image .env pins as TRIPL_IMAGE (default: community). The enterprise "
+            "image is private: run `docker login ghcr.io` with your subscription's "
+            "credentials first"
+        ),
+    )
+    parser.add_argument(
+        "--telemetry",
+        dest="telemetry",
+        action="store_true",
+        help=(
+            "share anonymous usage telemetry: one small ping a day, no names, emails, hosts "
+            "or data (TELEMETRY_ENABLED in the new .env; default: off). Asked once, here: an "
+            "existing .env is never rewritten"
+        ),
+    )
     add_wait_flag(parser)
     parser.add_argument(
         "--no-start",
@@ -247,7 +271,7 @@ def refuse_loose_append(appending: FileWrite | None) -> None:
     secret is disclosed the moment it lands, and no later ``chmod`` un-discloses
     it. Refusing rather than tightening the mode ourselves keeps rule 2 of
     ``install/files.py`` intact - the file is the operator's - and costs them one
-    ``chmod`` they can see (tripl-jfm3).
+    ``chmod`` they can see.
     """
     if appending is None or not appending.secret:
         return
@@ -338,16 +362,20 @@ def run_install(args: argparse.Namespace, config: Config) -> int:
     refuse_source_checkout(directory, "install")
     requested_url = normalize_base_url(str(args.app_url), FLAG_APP_URL)
     requested_version = files.DEFAULT_VERSION if args.version is None else str(args.version)
+    requested_image = (
+        files.DEFAULT_IMAGE if args.edition is None else files.EDITION_IMAGES[str(args.edition)]
+    )
 
     values = secrets.generate(secrets.default_rng())
     writes = files.plan_writes(
         directory,
         app_base_url=requested_url,
-        image=files.DEFAULT_IMAGE,
+        image=requested_image,
         version=requested_version,
         generated_at=generated_at,
         values=values,
         force=bool(args.force),
+        telemetry=bool(args.telemetry),
     )
     # What will be TRUE when this finishes, which on a re-run is the existing
     # .env's values - that file is never overwritten. Everything downstream (the
@@ -356,11 +384,15 @@ def run_install(args: argparse.Namespace, config: Config) -> int:
     settings = files.plan_settings(
         directory,
         app_base_url=requested_url,
-        image=files.DEFAULT_IMAGE,
+        image=requested_image,
         version=requested_version,
-        # --app-url is required, so it is always a real request. --version is
-        # one only when it was typed; TRIPL_IMAGE has no flag at all.
-        explicit=("APP_BASE_URL", *((files.VERSION_KEY,) if args.version is not None else ())),
+        # --app-url is required, so it is always a real request. --version and
+        # --edition (TRIPL_IMAGE) are one only when they were typed.
+        explicit=(
+            "APP_BASE_URL",
+            *((files.VERSION_KEY,) if args.version is not None else ()),
+            *(("TRIPL_IMAGE",) if args.edition is not None else ()),
+        ),
     )
     effective = {setting.name: setting.effective for setting in settings}
     app_base_url = effective["APP_BASE_URL"].rstrip("/")
@@ -398,6 +430,14 @@ def run_install(args: argparse.Namespace, config: Config) -> int:
             "onto an image you have not read the notes for.",
             file=sys.stderr,
         )
+    if plan.image == files.ENTERPRISE_IMAGE:
+        # Not checked here: the CLI holds no registry credentials, and a pull
+        # without them fails in `docker compose pull` with Docker's own words.
+        print(
+            f"tripl: note: {files.ENTERPRISE_IMAGE} is private. Run `docker login ghcr.io` "
+            "with the credentials that came with your subscription before the pull.",
+            file=sys.stderr,
+        )
     if plan.insecure_scheme:
         # Loud, and not a refusal: an operator terminating TLS elsewhere or
         # evaluating on a laptop has a legitimate http:// origin.
@@ -467,7 +507,7 @@ def run_install(args: argparse.Namespace, config: Config) -> int:
                 # brought up in front of :8000 - so reading /auth/status here
                 # bought a ten-second stall against a URL the operator has just
                 # told us not to try, and then printed a "could not be read"
-                # line about an attempt nobody asked for (tripl-jfm3).
+                # line about an attempt nobody asked for.
                 print(file=human)
                 print(render_next_steps(None, app_base_url, probed=False), file=human)
             elif health.ok:

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/plan.py

@@ -13,8 +13,7 @@ an action. The alternative was one top-level group per REST collection —
 is four more entries in ``tripl --help`` for four reads, and that is the same
 objection that rejected ``list-scans``. An operator does not arrive with "I want
 to query the event-types collection"; they arrive with "what does this plan look
-like", and this is one group per QUESTION rather than one per collection
-(tripl-3ixs).
+like", and this is one group per QUESTION rather than one per collection.
 
 ``plan diff`` is deliberately ABSENT even though ``api.branches.get_diff``
 exists and the MCP exposes it. The diff route answers
@@ -431,7 +430,7 @@ def run_search(args: argparse.Namespace, config: Config) -> int:
             meta={"semantic_used": search_api.semantic_used(payload)},
         )
         # The route's OWN truncation flag, which `PlanRead.truncated` prefers to
-        # its page-fullness guess (tripl-wkwv.3). That guess reads True whenever
+        # its page-fullness guess. That guess reads True whenever
         # the matches land exactly on --limit, so this command was printing "more
         # may have matched" on the same HTTP body that said nothing was dropped —
         # and answering the opposite of `tripl-mcp`'s `search_plan`, which reads

{tripl-0.2.2 → tripl-0.3.0}/src/tripl_cli/commands/scans.py

@@ -11,7 +11,7 @@ more top-level entries, and no answer for the sixth.
 ``request.state.api_key_scope`` is set — and that is every valid API key, read or
 write. A Bearer-token client cannot reach it, so the command would 403 every
 time. ``scans cancel`` ships in its place: editor-gated, the natural pair to
-``run``, and what the 2026-07-28..31 incident actually needed (tripl-ey6j.5).
+``run``, and what the 2026-07-28..31 incident actually needed.
 """
 
 from __future__ import annotations