fix: address OSS packaging review findings

Assisted-By: devx/f5505a8e-b863-4860-8951-135c4c748c11

Author: Volv-G

.github/CODEOWNERS

@@ -1,2 +1,2 @@
-# Require Alexey Volkov and Volv Grebennikov to review changes in this lab repo.
+# Require Alexey Volkov and Volv Grebennikov to review changes in this repository.
 * @Ark-kun @Volv-G

.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Check lockfile
+        run: uv lock --check
+
+      - name: Check whitespace
+        run: git diff --check
+
+      - name: Run tests
+        run: uv run pytest

README.md

@@ -1,8 +1,8 @@
 # tangle-cli
 
-[WIP] Private experimental/lab CLI for Tangle, the open-source ML pipeline orchestration platform.
+CLI for Tangle, the open-source ML pipeline orchestration platform.
 
-This lab repo is used to iterate on the next CLI shape before promoting changes to the public OSS package. The CLI is built with [Cyclopts](https://cyclopts.readthedocs.io/) and is intentionally split into two command families:
+This repository contains the public Tangle CLI package. The CLI is built with [Cyclopts](https://cyclopts.readthedocs.io/) and is intentionally split into two command families:
 
 - `tangle api ...` — pure OpenAPI wrappers around Tangle backend endpoints.
 - `tangle sdk ...` — hand-written SDK, local, and compound commands that may call the API or may run entirely locally.
@@ -263,7 +263,7 @@ configs:
     name: Second component
 ```
 
-Batch `publish-all`, Slack notification flags, dbt generation, from-container generation, and backend-specific search-v2 workflows remain out of this OSS lab CLI slice.
+Batch `publish-all`, notification integrations, dbt generation, from-container generation, and backend-specific advanced search workflows remain out of this OSS CLI package.
 
 ### Pipelines and pipeline runs
 
@@ -360,7 +360,7 @@ At runtime, more `tangle api ...` commands become available in two ways:
 
 ## Generated model extension pattern
 
-Generated models use a private generated base plus a stable public subclass. For example, codegen emits this shape for a model with a handwritten extension:
+Generated models use a generated implementation base plus a stable public subclass. For example, codegen emits this shape for a model with a handwritten extension:
 
 ```python
 class _ComponentSpecGenerated(TangleGeneratedModel):

packages/tangle-cli/src/tangle_cli/artifacts.py

@@ -85,7 +85,7 @@ class ArtifactManager(TangleCliHandler):
     """Read-only artifact metadata manager.
 
     Downstream packages can inject an already-authenticated client or a lazy
-    ``client_factory`` (for example, one that applies Shopify auth). The manager
+    ``client_factory`` (for example, one that applies provider auth). The manager
     keeps the same read-only constraints as the module-level helpers: it never
     downloads artifact contents, signs URLs, writes files, or mutates artifacts.
     """

packages/tangle-cli/src/tangle_cli/component_from_func.py

@@ -1616,8 +1616,7 @@ def build_component_dict(
     command = pip_install + ["sh", "-ec", shell_bootstrap, python_source]
 
     # Tangle's schema rejects ``description: null``, so fall back to a generic
-    # placeholder when the function has no docstring.  See
-    # https://github.com/Shopify/discovery/issues/28703.  Users can override by
+    # placeholder when the function has no docstring. Users can override by
     # adding a docstring to the function (its first paragraph becomes the
     # description — see ``extract_function_spec``).
     description = spec.description or f"{spec.component_name} component"
@@ -1848,7 +1847,7 @@ def _path_annotation(path: Path) -> str:
         # TaskEnv authoring-violation (§3.5): fail LOUD with the actionable
         # guidance instead of swallowing it into a warning + False. A silent
         # False would only resurface later as a confusing missing/broken
-        # component at hydrate or the real-Oasis run, defeating the
+        # component at hydrate or backend run time, defeating the
         # "fail fast with a clear generator error" intent. Every OTHER failure
         # keeps the conservative warn + return False behaviour below.
         raise

packages/tangle-cli/src/tangle_cli/component_publisher.py

@@ -2,7 +2,7 @@
 
 This module intentionally mirrors the generic publisher behavior from
 ``tangle-deploy`` while depending only on OSS ``tangle_cli`` primitives and the
-checked-in/generated static API client. Shopify-specific auth wrappers, Slack
+checked-in/generated static API client. Provider-specific auth wrappers,
 notification plumbing, and a separate ``publish-all`` CLI are kept downstream.
 """
 
@@ -89,8 +89,8 @@ class ComponentPublishHook(Protocol):
     """Extension hook for downstream publishers.
 
     Downstream packages can implement one or more methods to observe publish
-    batches (for example, to send Slack summaries) without OSS importing or
-    knowing about those systems. Implementations that need richer metadata may
+    batches (for example, to send notification summaries) without OSS importing
+    or knowing about those systems. Implementations that need richer metadata may
     add ``context: ComponentPublishContext | None = None`` as a keyword
     parameter; hooks without that parameter continue to work.
     """
@@ -143,10 +143,10 @@ def __init__(
         """Initialize the ComponentPublisher.
 
         Args mirror the generic ``tangle-deploy`` publisher shape, with
-        Shopify/Slack-specific fields intentionally omitted. ``client_factory``
-        is a downstream seam for lazily constructing a custom authenticated
-        client; subclasses may also override :meth:`_get_client` for more
-        control.
+        provider-specific notification/auth fields intentionally omitted.
+        ``client_factory`` is a downstream seam for lazily constructing a custom
+        authenticated client; subclasses may also override :meth:`_get_client`
+        for more control.
         """
 
         super().__init__(

packages/tangle-cli/src/tangle_cli/models.py

@@ -1,5 +1,5 @@
 """
-API-contract dataclasses for the Tangle (Oasis) Cloud Pipelines API.
+API-contract dataclasses for the Tangle Cloud Pipelines API.
 
 These dataclasses model the shapes of HTTP request/response bodies on the
 Tangle API — ``PipelineRun``, ``ComponentSpec``, container state, artifacts,

packages/tangle-cli/src/tangle_cli/pipeline_hydrator.py

@@ -3,7 +3,7 @@
 This module is intentionally a close OSS port of
 ``tangle_deploy.pipeline_hydrator``.  The generic reference-resolution code and
 method names are preserved where possible so future upstream diffs are easy to
-compare.  Shopify/Oasis-only infrastructure integrations are omitted, and
+compare. Provider-specific infrastructure integrations are omitted, and
 Docker/from-container materialization paths raise explicit unsupported errors.
 """
 

packages/tangle-cli/src/tangle_cli/pipeline_run_details.py

@@ -1,8 +1,8 @@
 """Pipeline-run details and graph-state serialization helpers.
 
 These helpers are native-free and keep provider-specific log enrichment out of
-OSS.  Downstreams can call them with their authenticated API client and layer
-Observe/GCP/Slack output through ``PipelineRunHooks.fetch_logs`` or wrappers.
+OSS. Downstreams can call them with their authenticated API client and layer
+provider-specific log output through ``PipelineRunHooks.fetch_logs`` or wrappers.
 """
 
 from __future__ import annotations

packages/tangle-cli/src/tangle_cli/pipeline_run_manager.py

@@ -2,9 +2,9 @@
 
 This module ports the OSS-safe parts of tangle-deploy's runner/run details
 commands while keeping downstream-specific behavior behind hooks.  The default
-implementation uses only the public Tangle API and local files; Shopify/GCP,
-Slack, scheduler, mutex, run-as annotation defaults, and alternate log backends
-are intentionally extension points rather than OSS behavior.
+implementation uses only the public Tangle API and local files; cloud storage,
+notifications, scheduler, mutex, run-as annotation defaults, and alternate log
+backends are intentionally extension points rather than OSS behavior.
 """
 
 from __future__ import annotations
@@ -299,10 +299,10 @@ class PipelineWaitPoll:
 class PipelineRunHooks:
     """Overridable seams for downstream tangle-deploy behavior.
 
-    Subclasses can override these methods to add Shopify auth wrappers, gs://
-    loading, JOB_CONFIG time input, run-as annotations, mutex/schedule behavior,
-    graceful shutdown, Slack notifications, Observe/GCP logs, or from-container
-    runtime defaults without forking the generic pipeline-run manager.
+    Subclasses can override these methods to add provider-specific auth wrappers,
+    cloud-object loading, JOB_CONFIG time input, run-as annotations,
+    mutex/schedule behavior, graceful shutdown, notifications, hosted logs, or
+    from-container runtime defaults without forking the generic pipeline-run manager.
     """
 
     logger: Logger = field(default_factory=get_default_logger)