elan-agentkit-contracts 0.1.0__tar.gz

elan_agentkit_contracts-0.1.0/.gitignore

@@ -0,0 +1,45 @@
+__pycache__/
+*.py[cod]
+.venv/
+.env
+.env.docker
+.uvcache/
+dist/
+build/
+*.egg-info/
+node_modules/
+.next/
+# TypeScript incremental build cache: rewritten by every portal build, so
+# tracking it dirties the tree on each one and now on every CI run.
+*.tsbuildinfo
+.terraform/
+.terraform.lock.hcl
+tfplan
+*.tfstate*
+.pytest_cache/
+.ruff_cache/
+catalog.json
+.ref/
+
+.local/
+# Per environment (ADR-0179): one shared file meant building for a second
+# environment overwrote the first's recorded digests.
+.platform-digests.*
+
+# Terraform plan files. Build artefacts, and a plan can carry values read
+# from state — including ones marked sensitive. `tfplan` alone did not match
+# `np.tfplan`, which is how one came to be committed.
+*.tfplan
+
+# Per-developer Claude Code settings. `.claude/settings.json` is the shared,
+# checked-in one; this is the personal override beside it, and it routinely
+# holds machine-specific permission grants — a `kubectl exec` allowance for
+# somebody's own cluster has no business in a repo that is also the starter
+# template for new projects.
+.claude/settings.local.json
+
+# GENERATED AT BUILD from the prerendered documentation, by
+# ui/console/scripts/gen-llms.mjs. A build artifact like `.next` and the SDK's
+# `dist`: committing it would mean a second copy of every documentation page
+# in the history, going stale between builds.
+ui/console/public/llms-full.txt

elan_agentkit_contracts-0.1.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.

elan_agentkit_contracts-0.1.0/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.5
+Name: elan-agentkit-contracts
+Version: 0.1.0
+Summary: The wire models, manifest schema and deploy spec the Elan SDK and CLI share with the platform
+Project-URL: Homepage, https://openelan.ai
+Project-URL: Documentation, https://openelan.ai/app/docs
+Author-email: Elan <support@openelan.ai>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: adk,agent-platform,agents,contracts,llm
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: pydantic>=2.9
+Requires-Dist: pyyaml>=6.0
+Description-Content-Type: text/markdown
+
+# elan-agentkit-contracts
+
+The models the Elan platform and its clients both read: the event envelopes, the
+agent manifest, the `elan.yaml` deploy spec, the artifact scope vocabulary and
+the naming rules every derived identifier follows.
+
+You almost certainly do not need to install this directly. `elan-sdk` and
+`elan-cli` depend on it, and installing either brings it along.
+
+```bash
+uv add elan-agentkit-contracts
+```
+
+Requires Python 3.12 or newer. Its only dependencies are `pydantic` and
+`pyyaml`.
+
+## Why it is a separate package
+
+The SDK validates an artifact filename before asking for an upload ticket, and
+the CLI's `elan validate` answers the same question the deploy service will.
+Both are only worth anything while there is **one** copy of each rule — a client
+that reimplements a predicate passes its own tests against its own copy, and
+nothing compares the copies.
+
+So these modules are shared rather than mirrored. What is *not* shared is
+everything that verifies, mints or connects: the token verifiers, the ticket
+minter, the database layer, the broker and the push transports stay in the
+platform's own package. A client has no business holding a verifier, and your
+application image has no business carrying a Pub/Sub SDK.
+
+## What is in it
+
+| Module | What it holds |
+|---|---|
+| `envelopes` | `AgentEventEnvelope`, `InvocationEnvelope`, `ResumeEnvelope`, `EventKind` |
+| `manifest` | `AgentManifest`, `WorkflowManifest`, `ActionPolicy`, `Rule`, `Billing`, `Limits` |
+| `deploy_spec` | `DeploySpec`, `spec_from_yaml`, `cross_check`, `Problem` |
+| `identity` | slug rules and every name derived from `(tenant, project, agent)` |
+| `artifacts` | the four artifact scopes, and what a filename may say |
+| `pricing` | the price grammar and tier arithmetic |
+| `tickets` | `TICKET_ISSUER`, `TICKET_QUERY_PARAM`, `stream_url` |
+| `subjects` | `END_USER_PREFIX`, `TENANT_SCOPE`, `end_user_of` |
+| `oauth` | `token_scope` — the one non-standard part of an OAuth request here |
+| `templates` | what `elan new agent` scaffolds |
+
+## Stability
+
+Pre-1.0 and versioned with the rest of the platform's client packages. These are
+wire contracts, so a field is added far more often than one changes meaning;
+when one does, it goes in the changelog with the version that introduced it.
+
+## Documentation
+
+<https://openelan.ai/app/docs>
+
+## Licence
+
+Apache-2.0. See `LICENSE`.

elan_agentkit_contracts-0.1.0/README.md

@@ -0,0 +1,58 @@
+# elan-agentkit-contracts
+
+The models the Elan platform and its clients both read: the event envelopes, the
+agent manifest, the `elan.yaml` deploy spec, the artifact scope vocabulary and
+the naming rules every derived identifier follows.
+
+You almost certainly do not need to install this directly. `elan-sdk` and
+`elan-cli` depend on it, and installing either brings it along.
+
+```bash
+uv add elan-agentkit-contracts
+```
+
+Requires Python 3.12 or newer. Its only dependencies are `pydantic` and
+`pyyaml`.
+
+## Why it is a separate package
+
+The SDK validates an artifact filename before asking for an upload ticket, and
+the CLI's `elan validate` answers the same question the deploy service will.
+Both are only worth anything while there is **one** copy of each rule — a client
+that reimplements a predicate passes its own tests against its own copy, and
+nothing compares the copies.
+
+So these modules are shared rather than mirrored. What is *not* shared is
+everything that verifies, mints or connects: the token verifiers, the ticket
+minter, the database layer, the broker and the push transports stay in the
+platform's own package. A client has no business holding a verifier, and your
+application image has no business carrying a Pub/Sub SDK.
+
+## What is in it
+
+| Module | What it holds |
+|---|---|
+| `envelopes` | `AgentEventEnvelope`, `InvocationEnvelope`, `ResumeEnvelope`, `EventKind` |
+| `manifest` | `AgentManifest`, `WorkflowManifest`, `ActionPolicy`, `Rule`, `Billing`, `Limits` |
+| `deploy_spec` | `DeploySpec`, `spec_from_yaml`, `cross_check`, `Problem` |
+| `identity` | slug rules and every name derived from `(tenant, project, agent)` |
+| `artifacts` | the four artifact scopes, and what a filename may say |
+| `pricing` | the price grammar and tier arithmetic |
+| `tickets` | `TICKET_ISSUER`, `TICKET_QUERY_PARAM`, `stream_url` |
+| `subjects` | `END_USER_PREFIX`, `TENANT_SCOPE`, `end_user_of` |
+| `oauth` | `token_scope` — the one non-standard part of an OAuth request here |
+| `templates` | what `elan new agent` scaffolds |
+
+## Stability
+
+Pre-1.0 and versioned with the rest of the platform's client packages. These are
+wire contracts, so a field is added far more often than one changes meaning;
+when one does, it goes in the changelog with the version that introduced it.
+
+## Documentation
+
+<https://openelan.ai/app/docs>
+
+## Licence
+
+Apache-2.0. See `LICENSE`.

elan_agentkit_contracts-0.1.0/pyproject.toml

@@ -0,0 +1,72 @@
+[project]
+name = "elan-agentkit-contracts"
+version = "0.1.0"
+description = "The wire models, manifest schema and deploy spec the Elan SDK and CLI share with the platform"
+readme = "README.md"
+requires-python = ">=3.12"
+
+# SPDX, NOT A CLASSIFIER (PEP 639). The two spellings are mutually exclusive —
+# a distribution carrying both a `License-Expression` and a
+# `License :: OSI Approved :: …` classifier is refused by a current build
+# backend, so the classifier list below deliberately has no `License ::` line.
+license = "Apache-2.0"
+# A REAL FILE, NOT A SYMLINK TO THE ROOT. A symlinked `LICENSE` builds a wheel
+# fine and then fails the SDIST — `uv build` refuses with "symlink destination
+# for ../../LICENSE is outside of the target directory". Byte-identity with the
+# root copy is asserted by
+# `tests/test_packaging.py::test_every_published_package_ships_the_licence`.
+license-files = ["LICENSE"]
+
+authors = [{ name = "Elan", email = "support@openelan.ai" }]
+keywords = ["agents", "llm", "adk", "contracts", "agent-platform"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Typing :: Typed",
+]
+
+# TWO DEPENDENCIES, AND THAT IS THE POINT OF THE PACKAGE (ADR-0197).
+#
+# `elan-sdk` and `elan-cli` needed the manifest schema, the wire envelopes, the
+# artifact scope vocabulary and the deploy spec. Getting them from
+# `agentkit-core` would have put the token verifiers, the ticket minter, the
+# database layer, the broker, the push transports and optional extras on
+# google-cloud-pubsub, pyjwt[crypto], sqlalchemy and google-adk into a
+# developer's application image. None of that is a contract.
+#
+# NO OPTIONAL EXTRAS AT ALL, deliberately. An extra is a backend a deployment
+# may select; there is nothing here to select. If a module in this package ever
+# wants one, that is the signal it belongs on the other side of the split.
+dependencies = [
+    "pydantic>=2.9",
+    # `spec_from_yaml` IS THE ONLY PARSER FOR elan.yaml AND IT LIVES HERE, so
+    # this is not optional the way an extra would be — it is the deploy
+    # contract itself.
+    #
+    # DECLARED BECAUSE IT WAS ALREADY BEING GOT BY LUCK, and that history
+    # travelled with the module out of `agentkit-core`. Nothing listed it: the
+    # deploy service had it because `uvicorn[standard]` pulls it in, and
+    # agentkit-runtime happened to name it. Both worked. `elan-cli` installs
+    # neither, so `uv tool install` produced a CLI that could not read the one
+    # file every command of it is about — `elan validate` answered "No module
+    # named 'yaml'", which names a package the developer never asked for and
+    # points at nothing they can fix.
+    "pyyaml>=6.0",
+]
+
+# NO `Repository` OR `Issues` URL while the source repository is private: both
+# would be a 404 on a public project page, which is worse than an absent link.
+[project.urls]
+Homepage = "https://openelan.ai"
+Documentation = "https://openelan.ai/app/docs"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/elan_agentkit_contracts"]

elan_agentkit_contracts-0.1.0/src/elan_agentkit_contracts/__init__.py

@@ -0,0 +1,148 @@
+"""The contracts a client and this platform have to agree on.
+
+WHAT THIS PACKAGE IS FOR. `elan-sdk` and `elan-cli` are published to PyPI, and
+both needed the wire models, the manifest schema, the artifact scope vocabulary
+and the deploy spec. Before ADR-0197 they got them from `agentkit-core`, which
+is a workspace path dependency — uv-local metadata that is NOT written into a
+wheel, so a published wheel declared a bare `Requires-Dist: agentkit-core` that
+pip would resolve from an index that has never seen it.
+
+PUBLISHING `agentkit-core` INSTEAD WAS THE OBVIOUS FIX AND THE WRONG ONE. It
+carries the token verifiers, the ticket minter, the database layer, the broker,
+the push transports and the email and comms clients, with optional extras on
+google-cloud-pubsub, pyjwt[crypto], sqlalchemy and google-adk. None of that
+belongs in a developer's application image, and a client package containing a
+verifier implies the client verifies something.
+
+SO THIS IS THE SUBSET A CLIENT GENUINELY NEEDS, with pydantic and pyyaml as its
+only dependencies. It is a LEAF: it imports neither `agentkit_core` nor
+`agentkit_deploy`, and it never will — that is what keeps it installable beside
+somebody else's code.
+
+MOVED, NEVER COPIED. ADR-0116 is about exactly this: `elan_cli/stream.py` once
+kept its own copy of the terminal-event predicate and hung for ever on every
+paused run, and `ui/portal/lib/types.ts` hand-mirrored `AgentEventEnvelope` and
+silently lost three fields. Two copies that agree today pass every behavioural
+test and diverge the day one is edited. So `agentkit_core.identity`,
+`.manifest`, `.envelopes`, `.artifacts`, `.pricing`, `.deploy_spec` and
+`.templates` are now SHIMS that re-export from here, and `agentkit_core.auth`
+and `.tickets` import their vocabulary back from `subjects`, `oauth` and
+`tickets`.
+
+THE NAME SAYS `elan` ON BOTH SIDES, DELIBERATELY. Everything under `agentkit_*`
+in this repo is brand-free so a derived project renames nothing; a published
+distribution is the opposite kind of name — a developer types it. A neutral
+import name inside a branded distribution would be a distinction every reader
+had to be told about, so `tests/test_template.py`'s brand scan widens by one
+narrow allowance instead.
+"""
+
+from elan_agentkit_contracts.artifacts import (
+    ARTIFACT_SCOPE_PREFIXES,
+    MAX_ARTIFACT_BYTES,
+    SHARED_SCOPES,
+    ArtifactNameRefused,
+    ArtifactScope,
+    qualify,
+    scope_of,
+    validate_artifact_filename,
+)
+from elan_agentkit_contracts.deploy_spec import (
+    DeploySpec,
+    Problem,
+    cross_check,
+    spec_from_yaml,
+)
+from elan_agentkit_contracts.envelopes import (
+    AgentEventEnvelope,
+    EventKind,
+    InvocationEnvelope,
+    MessagePart,
+    ResumeEnvelope,
+    new_id,
+)
+from elan_agentkit_contracts.identity import (
+    AgentRef,
+    AgentSlug,
+    ProjectSlug,
+    TenantSlug,
+)
+from elan_agentkit_contracts.manifest import (
+    SLUG_PATTERN,
+    ActionPolicy,
+    AgentManifest,
+    BaseTargetManifest,
+    Billing,
+    Limits,
+    NodeOverrides,
+    Rule,
+    TargetManifest,
+    Tier,
+    ToolBinding,
+    ToolPhrasing,
+    WorkflowManifest,
+)
+from elan_agentkit_contracts.oauth import token_scope
+from elan_agentkit_contracts.subjects import (
+    END_USER_PREFIX,
+    TENANT_SCOPE,
+    end_user_of,
+)
+from elan_agentkit_contracts.tickets import (
+    TICKET_ISSUER,
+    TICKET_QUERY_PARAM,
+    stream_url,
+)
+
+#: THE HEADLINE NAMES ONLY, not every one of the 163 a submodule exports.
+#:
+#: A FRONT DOOR IS NOT AN INDEX. `agentkit_core.__init__` makes the same choice
+#: and for the same reason: a flat re-export of everything turns every rename
+#: inside a submodule into a change here, and it hides WHICH contract a name
+#: belongs to at the call site. `from elan_agentkit_contracts.identity import
+#: artifact_bucket_of` says what it is about; `from elan_agentkit_contracts
+#: import artifact_bucket_of` does not.
+__all__ = [
+    "ARTIFACT_SCOPE_PREFIXES",
+    "END_USER_PREFIX",
+    "MAX_ARTIFACT_BYTES",
+    "SHARED_SCOPES",
+    "SLUG_PATTERN",
+    "TENANT_SCOPE",
+    "TICKET_ISSUER",
+    "TICKET_QUERY_PARAM",
+    "ActionPolicy",
+    "AgentEventEnvelope",
+    "AgentManifest",
+    "AgentRef",
+    "AgentSlug",
+    "ArtifactNameRefused",
+    "ArtifactScope",
+    "BaseTargetManifest",
+    "Billing",
+    "DeploySpec",
+    "EventKind",
+    "InvocationEnvelope",
+    "Limits",
+    "MessagePart",
+    "NodeOverrides",
+    "Problem",
+    "ProjectSlug",
+    "ResumeEnvelope",
+    "Rule",
+    "TargetManifest",
+    "TenantSlug",
+    "Tier",
+    "ToolBinding",
+    "ToolPhrasing",
+    "WorkflowManifest",
+    "cross_check",
+    "end_user_of",
+    "new_id",
+    "qualify",
+    "scope_of",
+    "spec_from_yaml",
+    "stream_url",
+    "token_scope",
+    "validate_artifact_filename",
+]