refactor: make tangle-api leaf via runtime model composition

[Volv-G]

Summary

Make tangle-api a leaf package while keeping public tangle-cli installs fully capable by default.

Key changes:

• Add default tangle-cli -> tangle-api==0.0.1a3, so pip install tangle-cli includes checked-in static API bindings.
• Keep tangle-cli[native] as a compatibility/no-op install alias for older instructions.
• Remove the tangle-api -> tangle-cli dependency; tangle-api remains a leaf generated/static API package.
• Regenerate tangle_api.generated.* from the checked-in OpenAPI snapshot as base generated models.
• Move CLI model extension composition into tangle_cli.models.
• Add an overridable generated-operations model lookup hook so TangleApiClient can use CLI-composed models while tangle-api remains independent.
• Keep dynamic discovery/runtime and codegen in tangle-cli.

Design

tangle_api.generated.models now provides base generated API model classes only. It does not import tangle_cli and no longer bakes CLI-specific mixins into generated code.

tangle_cli.models composes the CLI public model namespace at import time using the existing MODEL_EXTENSIONS mapping. This preserves imports such as:

from tangle_cli.models import ComponentSpec

while keeping generated imports such as:

from tangle_api.generated.models import ComponentSpec

as the unextended base generated model.

Generated operation methods now resolve return model classes through an overridable hook. The default lookup uses base tangle_api.generated.models; TangleApiClient overrides it to use tangle_cli.models where CLI extension behavior is expected.

Packaging and custom API/codegen path

The default public install is now the fully capable path:

pip install tangle-cli

That install includes the matching official tangle-api package. The native extra remains available as a compatibility alias, but it does not add another dependency because tangle-api is already part of the default install.

Custom API/codegen users can still run codegen from the fully capable install; generation itself does not require removing official tangle-api.

Supported non-first-class custom paths:

• For project-local generated APIs, generate into a local source tree such as src/tangle_api/generated and run from that project so local src/tangle_api shadows site-packages.
• For packaged custom APIs, provide a distribution named tangle-api with a compatible version for this release, e.g. 0.0.1a3+yourorg for the tangle-api==0.0.1a3 dependency, via private index, --find-links, or uv source configuration.
• As an expert escape hatch, --no-deps installs only tangle-cli and skips all dependencies; that environment must manually provide every required runtime dependency plus its generated/custom tangle_api package.

Codegen

Regenerated with:

uv run python -m tangle_cli.openapi.codegen --from-snapshot

This reads:

packages/tangle-api/src/tangle_api/schema/openapi.json

and writes:

packages/tangle-api/src/tangle_api/generated/__init__.py
packages/tangle-api/src/tangle_api/generated/runtime.py
packages/tangle-api/src/tangle_api/generated/models.py
packages/tangle-api/src/tangle_api/generated/operations.py

Assisted-By: devx/9c4ad24f-24d3-4eb9-8747-dbf53e3221df

[Volv-G]

• refactor: make tangle-api leaf via runtime model composition #10 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.