evo-agents-core-plugins 1.0.0__tar.gz

evo_agents_core_plugins-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

evo_agents_core_plugins-1.0.0/PKG-INFO

@@ -0,0 +1,119 @@
+Metadata-Version: 2.4
+Name: evo-agents-core-plugins
+Version: 1.0.0
+Summary: The first-party core plugins of the evo-agents hub: Telegram and the chat history in the knowledge graph
+Author: maycuatroi
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/maycuatroi1/evo-agents-core-plugins
+Keywords: agents,evo-agents,hub,plugins,telegram
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# evo-agents-core-plugins
+
+The first-party core plugins of the [evo-agents](https://github.com/maycuatroi1/evo-agents) hub, out of evo-agents
+and built on its API of core plugins alone (`evo_agents.hub.server.core_plugin_api`):
+
+| Plugin | Package | What it does |
+|---|---|---|
+| `telegram` | `evo_core_plugins.telegram` | The hub's Telegram channel: a member links a private chat from the web, gets decisions, proposals and notices there, and answers them with buttons or replies |
+| `chats` | `evo_core_plugins.chats` | The messages of the hub's group chats in each project's knowledge graph, for who is in each chat |
+
+Both left evo-ak unchanged for their users: the same id, publisher (`evo-agents`) and entry point name, the same
+routes, webhook path and variables (`EVO_HUB_TELEGRAM_*`), the same item ids (`plugin.chats:...`). Their manifests
+moved to version 1.1.0, so the hub's store records a new version of the image's plugins.
+
+## How the hub installs it
+
+One distribution, `evo-agents-core-plugins`, with one entry point per plugin in group `evo_agents.plugins`. The hub's
+image installs it from PyPI with `--no-deps --require-hashes`, from the line `deploy/hub/core-plugins.txt` of
+evo-agents pins:
+
+```
+evo-agents-core-plugins==1.0.0 --hash=sha256:<the hash the release prints>
+```
+
+The wheel declares no dependency: the plugins use only what the image of the hub already holds (evo-ak with its
+`hub-server` extra: FastAPI, pydantic, httpx). Declaring evo-ak would let a resolver pull evo-ak from PyPI over the
+one the image builds from evo-agents' main. `plugin_tests/test_packaging.py` keeps both.
+
+## The API of core plugins
+
+A plugin imports `evo_agents.hub.server.core_plugin_api` and nothing else of evo_agents, imports no SQLAlchemy, and
+reaches its own modules with relative imports (`plugin_tests/test_api_imports.py`, a copy of evo-agents'
+`tests/plugins/test_core_plugin_imports.py`). No plugin imports another (`lint-imports`, contract
+`plugins-own-package`). Neither the plugins nor their tests hold raw SQL (`plugin_tests/test_no_raw_sql.py`).
+
+Each plugin's entry point names `manifest()`, which calls `hub.require(*API)` with the version of the API the plugin
+is written for. A hub serves exactly one `major.minor`: a hub that serves another leaves the plugin out with the reason
+(`core plugin not loaded`), and the `check` its Dockerfile runs fails the build. Every plugin of one release asks for
+the same version, which `python -m evo_core_plugins api` prints; `python -m evo_agents.hub.server.core_plugin_api
+version` prints the one a checkout of evo-agents serves. `docs/plugins.md` of evo-agents has the rules and the table of
+versions.
+
+| This distribution | API it asks for | evo-agents commit that serves it |
+|---|---|---|
+| 1.0.0 | 1.1 | `ad12d3ccbee695a6915b22f4512f11794f7944fb` (pull request #106) |
+
+### A change of the API
+
+1. A pull request of evo-agents changes the API and its version. Its CI fails where the pinned release asks for the
+   old one.
+2. A pull request here moves `API` of every plugin to the new version, uses what changed, and sets `evo-agents.lock` to
+   the head commit of that evo-agents pull request, so CI runs against it. evo-agents merges with merge commits, so the
+   commit stays in main's history.
+3. Merge, bump `evo_core_plugins.__version__`, tag `v<version>`: the release publishes it.
+4. The evo-agents pull request pins the new release with its hash; its CI turns green.
+
+The nightly `compat` job tells early when main serves a version these plugins do not ask for.
+
+## Development
+
+You need `uv`, git and, for the tests that start a hub, Postgres.
+
+```sh
+make setup   # evo-agents at the commit of evo-agents.lock in .evo-agents, a venv in .venv with both, editable
+make check   # ruff, import-linter, the import, raw SQL and packaging checks
+make test    # every test; the hub's need EVO_HUB_TEST_DSN, such as postgresql://postgres:test@localhost:5432/postgres
+```
+
+`make setup EVO_AGENTS_URL=~/github/evo-agents` fetches from a local clone instead of GitHub, `EVO_AGENTS_REF=main`
+checks out main instead of the lock, and `make lock` says whether `.evo-agents` is at the lock.
+
+## Tests
+
+`plugin_tests/test_telegram.py`, `test_telegram_model.py`, `fake_telegram.py` and `test_chats_kg_source.py` are the
+tests these plugins had in evo-agents. They use evo-agents' test helpers from the checkout at the lock: `tests.hub.pg`,
+`tests.hub.live`, the fixtures of `tests/hub/conftest.py` and functions of its test modules (`conftest.py` puts the
+checkout on `sys.path` and loads them). **These helpers are not part of the API of core plugins.** No wheel holds them
+and no version covers them: evo-agents may change one without changing the API's version, and the tests here then
+break at the next move of the lock or in the compat job, never on a hub.
+
+The directory is `plugin_tests`, not `tests`, so that evo-agents' `tests` package stays importable. Until evo-agents
+drops its own copies of `telegram` and `chats`, the evo-ak the tests install declares entry points of the same names;
+`plugin_tests/conftest.py` leaves those out, so the hub the tests start loads this checkout's plugins, and
+`plugin_tests/test_installed.py` checks that it does.
+
+## CI and releases
+
+- `ci.yml`, on pull requests and main: `make check`, and `make test` against a Postgres service, with evo-agents at the
+  lock.
+- `compat.yml`, every night and by hand: the same tests against evo-agents' main, after comparing the API main serves
+  with the one the plugins ask for. A failure opens an issue labelled `compat`, or comments on the open one.
+- `release.yml`, on a tag `v<version>` that matches `evo_core_plugins.__version__`: `ci.yml`, then the wheel and sdist,
+  published to PyPI by trusted publishing in the environment `pypi` (a reviewer approves it). The run's summary holds
+  the line to pin in evo-agents, with the wheel's sha256.
+
+## Names
+
+This repository is public, like evo-agents: tests, fixtures, docs and commit messages use made-up names only (such as
+northwind and lumen), never a customer's.
+
+## License
+
+Apache-2.0, as evo-agents.

evo_agents_core_plugins-1.0.0/README.md

@@ -0,0 +1,103 @@
+# evo-agents-core-plugins
+
+The first-party core plugins of the [evo-agents](https://github.com/maycuatroi1/evo-agents) hub, out of evo-agents
+and built on its API of core plugins alone (`evo_agents.hub.server.core_plugin_api`):
+
+| Plugin | Package | What it does |
+|---|---|---|
+| `telegram` | `evo_core_plugins.telegram` | The hub's Telegram channel: a member links a private chat from the web, gets decisions, proposals and notices there, and answers them with buttons or replies |
+| `chats` | `evo_core_plugins.chats` | The messages of the hub's group chats in each project's knowledge graph, for who is in each chat |
+
+Both left evo-ak unchanged for their users: the same id, publisher (`evo-agents`) and entry point name, the same
+routes, webhook path and variables (`EVO_HUB_TELEGRAM_*`), the same item ids (`plugin.chats:...`). Their manifests
+moved to version 1.1.0, so the hub's store records a new version of the image's plugins.
+
+## How the hub installs it
+
+One distribution, `evo-agents-core-plugins`, with one entry point per plugin in group `evo_agents.plugins`. The hub's
+image installs it from PyPI with `--no-deps --require-hashes`, from the line `deploy/hub/core-plugins.txt` of
+evo-agents pins:
+
+```
+evo-agents-core-plugins==1.0.0 --hash=sha256:<the hash the release prints>
+```
+
+The wheel declares no dependency: the plugins use only what the image of the hub already holds (evo-ak with its
+`hub-server` extra: FastAPI, pydantic, httpx). Declaring evo-ak would let a resolver pull evo-ak from PyPI over the
+one the image builds from evo-agents' main. `plugin_tests/test_packaging.py` keeps both.
+
+## The API of core plugins
+
+A plugin imports `evo_agents.hub.server.core_plugin_api` and nothing else of evo_agents, imports no SQLAlchemy, and
+reaches its own modules with relative imports (`plugin_tests/test_api_imports.py`, a copy of evo-agents'
+`tests/plugins/test_core_plugin_imports.py`). No plugin imports another (`lint-imports`, contract
+`plugins-own-package`). Neither the plugins nor their tests hold raw SQL (`plugin_tests/test_no_raw_sql.py`).
+
+Each plugin's entry point names `manifest()`, which calls `hub.require(*API)` with the version of the API the plugin
+is written for. A hub serves exactly one `major.minor`: a hub that serves another leaves the plugin out with the reason
+(`core plugin not loaded`), and the `check` its Dockerfile runs fails the build. Every plugin of one release asks for
+the same version, which `python -m evo_core_plugins api` prints; `python -m evo_agents.hub.server.core_plugin_api
+version` prints the one a checkout of evo-agents serves. `docs/plugins.md` of evo-agents has the rules and the table of
+versions.
+
+| This distribution | API it asks for | evo-agents commit that serves it |
+|---|---|---|
+| 1.0.0 | 1.1 | `ad12d3ccbee695a6915b22f4512f11794f7944fb` (pull request #106) |
+
+### A change of the API
+
+1. A pull request of evo-agents changes the API and its version. Its CI fails where the pinned release asks for the
+   old one.
+2. A pull request here moves `API` of every plugin to the new version, uses what changed, and sets `evo-agents.lock` to
+   the head commit of that evo-agents pull request, so CI runs against it. evo-agents merges with merge commits, so the
+   commit stays in main's history.
+3. Merge, bump `evo_core_plugins.__version__`, tag `v<version>`: the release publishes it.
+4. The evo-agents pull request pins the new release with its hash; its CI turns green.
+
+The nightly `compat` job tells early when main serves a version these plugins do not ask for.
+
+## Development
+
+You need `uv`, git and, for the tests that start a hub, Postgres.
+
+```sh
+make setup   # evo-agents at the commit of evo-agents.lock in .evo-agents, a venv in .venv with both, editable
+make check   # ruff, import-linter, the import, raw SQL and packaging checks
+make test    # every test; the hub's need EVO_HUB_TEST_DSN, such as postgresql://postgres:test@localhost:5432/postgres
+```
+
+`make setup EVO_AGENTS_URL=~/github/evo-agents` fetches from a local clone instead of GitHub, `EVO_AGENTS_REF=main`
+checks out main instead of the lock, and `make lock` says whether `.evo-agents` is at the lock.
+
+## Tests
+
+`plugin_tests/test_telegram.py`, `test_telegram_model.py`, `fake_telegram.py` and `test_chats_kg_source.py` are the
+tests these plugins had in evo-agents. They use evo-agents' test helpers from the checkout at the lock: `tests.hub.pg`,
+`tests.hub.live`, the fixtures of `tests/hub/conftest.py` and functions of its test modules (`conftest.py` puts the
+checkout on `sys.path` and loads them). **These helpers are not part of the API of core plugins.** No wheel holds them
+and no version covers them: evo-agents may change one without changing the API's version, and the tests here then
+break at the next move of the lock or in the compat job, never on a hub.
+
+The directory is `plugin_tests`, not `tests`, so that evo-agents' `tests` package stays importable. Until evo-agents
+drops its own copies of `telegram` and `chats`, the evo-ak the tests install declares entry points of the same names;
+`plugin_tests/conftest.py` leaves those out, so the hub the tests start loads this checkout's plugins, and
+`plugin_tests/test_installed.py` checks that it does.
+
+## CI and releases
+
+- `ci.yml`, on pull requests and main: `make check`, and `make test` against a Postgres service, with evo-agents at the
+  lock.
+- `compat.yml`, every night and by hand: the same tests against evo-agents' main, after comparing the API main serves
+  with the one the plugins ask for. A failure opens an issue labelled `compat`, or comments on the open one.
+- `release.yml`, on a tag `v<version>` that matches `evo_core_plugins.__version__`: `ci.yml`, then the wheel and sdist,
+  published to PyPI by trusted publishing in the environment `pypi` (a reviewer approves it). The run's summary holds
+  the line to pin in evo-agents, with the wheel's sha256.
+
+## Names
+
+This repository is public, like evo-agents: tests, fixtures, docs and commit messages use made-up names only (such as
+northwind and lumen), never a customer's.
+
+## License
+
+Apache-2.0, as evo-agents.

evo_agents_core_plugins-1.0.0/evo_agents_core_plugins.egg-info/PKG-INFO

@@ -0,0 +1,119 @@
+Metadata-Version: 2.4
+Name: evo-agents-core-plugins
+Version: 1.0.0
+Summary: The first-party core plugins of the evo-agents hub: Telegram and the chat history in the knowledge graph
+Author: maycuatroi
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/maycuatroi1/evo-agents-core-plugins
+Keywords: agents,evo-agents,hub,plugins,telegram
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# evo-agents-core-plugins
+
+The first-party core plugins of the [evo-agents](https://github.com/maycuatroi1/evo-agents) hub, out of evo-agents
+and built on its API of core plugins alone (`evo_agents.hub.server.core_plugin_api`):
+
+| Plugin | Package | What it does |
+|---|---|---|
+| `telegram` | `evo_core_plugins.telegram` | The hub's Telegram channel: a member links a private chat from the web, gets decisions, proposals and notices there, and answers them with buttons or replies |
+| `chats` | `evo_core_plugins.chats` | The messages of the hub's group chats in each project's knowledge graph, for who is in each chat |
+
+Both left evo-ak unchanged for their users: the same id, publisher (`evo-agents`) and entry point name, the same
+routes, webhook path and variables (`EVO_HUB_TELEGRAM_*`), the same item ids (`plugin.chats:...`). Their manifests
+moved to version 1.1.0, so the hub's store records a new version of the image's plugins.
+
+## How the hub installs it
+
+One distribution, `evo-agents-core-plugins`, with one entry point per plugin in group `evo_agents.plugins`. The hub's
+image installs it from PyPI with `--no-deps --require-hashes`, from the line `deploy/hub/core-plugins.txt` of
+evo-agents pins:
+
+```
+evo-agents-core-plugins==1.0.0 --hash=sha256:<the hash the release prints>
+```
+
+The wheel declares no dependency: the plugins use only what the image of the hub already holds (evo-ak with its
+`hub-server` extra: FastAPI, pydantic, httpx). Declaring evo-ak would let a resolver pull evo-ak from PyPI over the
+one the image builds from evo-agents' main. `plugin_tests/test_packaging.py` keeps both.
+
+## The API of core plugins
+
+A plugin imports `evo_agents.hub.server.core_plugin_api` and nothing else of evo_agents, imports no SQLAlchemy, and
+reaches its own modules with relative imports (`plugin_tests/test_api_imports.py`, a copy of evo-agents'
+`tests/plugins/test_core_plugin_imports.py`). No plugin imports another (`lint-imports`, contract
+`plugins-own-package`). Neither the plugins nor their tests hold raw SQL (`plugin_tests/test_no_raw_sql.py`).
+
+Each plugin's entry point names `manifest()`, which calls `hub.require(*API)` with the version of the API the plugin
+is written for. A hub serves exactly one `major.minor`: a hub that serves another leaves the plugin out with the reason
+(`core plugin not loaded`), and the `check` its Dockerfile runs fails the build. Every plugin of one release asks for
+the same version, which `python -m evo_core_plugins api` prints; `python -m evo_agents.hub.server.core_plugin_api
+version` prints the one a checkout of evo-agents serves. `docs/plugins.md` of evo-agents has the rules and the table of
+versions.
+
+| This distribution | API it asks for | evo-agents commit that serves it |
+|---|---|---|
+| 1.0.0 | 1.1 | `ad12d3ccbee695a6915b22f4512f11794f7944fb` (pull request #106) |
+
+### A change of the API
+
+1. A pull request of evo-agents changes the API and its version. Its CI fails where the pinned release asks for the
+   old one.
+2. A pull request here moves `API` of every plugin to the new version, uses what changed, and sets `evo-agents.lock` to
+   the head commit of that evo-agents pull request, so CI runs against it. evo-agents merges with merge commits, so the
+   commit stays in main's history.
+3. Merge, bump `evo_core_plugins.__version__`, tag `v<version>`: the release publishes it.
+4. The evo-agents pull request pins the new release with its hash; its CI turns green.
+
+The nightly `compat` job tells early when main serves a version these plugins do not ask for.
+
+## Development
+
+You need `uv`, git and, for the tests that start a hub, Postgres.
+
+```sh
+make setup   # evo-agents at the commit of evo-agents.lock in .evo-agents, a venv in .venv with both, editable
+make check   # ruff, import-linter, the import, raw SQL and packaging checks
+make test    # every test; the hub's need EVO_HUB_TEST_DSN, such as postgresql://postgres:test@localhost:5432/postgres
+```
+
+`make setup EVO_AGENTS_URL=~/github/evo-agents` fetches from a local clone instead of GitHub, `EVO_AGENTS_REF=main`
+checks out main instead of the lock, and `make lock` says whether `.evo-agents` is at the lock.
+
+## Tests
+
+`plugin_tests/test_telegram.py`, `test_telegram_model.py`, `fake_telegram.py` and `test_chats_kg_source.py` are the
+tests these plugins had in evo-agents. They use evo-agents' test helpers from the checkout at the lock: `tests.hub.pg`,
+`tests.hub.live`, the fixtures of `tests/hub/conftest.py` and functions of its test modules (`conftest.py` puts the
+checkout on `sys.path` and loads them). **These helpers are not part of the API of core plugins.** No wheel holds them
+and no version covers them: evo-agents may change one without changing the API's version, and the tests here then
+break at the next move of the lock or in the compat job, never on a hub.
+
+The directory is `plugin_tests`, not `tests`, so that evo-agents' `tests` package stays importable. Until evo-agents
+drops its own copies of `telegram` and `chats`, the evo-ak the tests install declares entry points of the same names;
+`plugin_tests/conftest.py` leaves those out, so the hub the tests start loads this checkout's plugins, and
+`plugin_tests/test_installed.py` checks that it does.
+
+## CI and releases
+
+- `ci.yml`, on pull requests and main: `make check`, and `make test` against a Postgres service, with evo-agents at the
+  lock.
+- `compat.yml`, every night and by hand: the same tests against evo-agents' main, after comparing the API main serves
+  with the one the plugins ask for. A failure opens an issue labelled `compat`, or comments on the open one.
+- `release.yml`, on a tag `v<version>` that matches `evo_core_plugins.__version__`: `ci.yml`, then the wheel and sdist,
+  published to PyPI by trusted publishing in the environment `pypi` (a reviewer approves it). The run's summary holds
+  the line to pin in evo-agents, with the wheel's sha256.
+
+## Names
+
+This repository is public, like evo-agents: tests, fixtures, docs and commit messages use made-up names only (such as
+northwind and lumen), never a customer's.
+
+## License
+
+Apache-2.0, as evo-agents.

evo_agents_core_plugins-1.0.0/evo_agents_core_plugins.egg-info/SOURCES.txt

@@ -0,0 +1,15 @@
+LICENSE
+README.md
+pyproject.toml
+evo_agents_core_plugins.egg-info/PKG-INFO
+evo_agents_core_plugins.egg-info/SOURCES.txt
+evo_agents_core_plugins.egg-info/dependency_links.txt
+evo_agents_core_plugins.egg-info/entry_points.txt
+evo_agents_core_plugins.egg-info/top_level.txt
+evo_core_plugins/__init__.py
+evo_core_plugins/__main__.py
+evo_core_plugins/chats/__init__.py
+evo_core_plugins/chats/kg.py
+evo_core_plugins/telegram/__init__.py
+evo_core_plugins/telegram/model.py
+evo_core_plugins/telegram/server.py

evo_agents_core_plugins-1.0.0/evo_agents_core_plugins.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

evo_agents_core_plugins-1.0.0/evo_agents_core_plugins.egg-info/entry_points.txt

@@ -0,0 +1,3 @@
+[evo_agents.plugins]
+chats = evo_core_plugins.chats:manifest
+telegram = evo_core_plugins.telegram:manifest

evo_agents_core_plugins-1.0.0/evo_agents_core_plugins.egg-info/top_level.txt

@@ -0,0 +1 @@
+evo_core_plugins

evo_agents_core_plugins-1.0.0/evo_core_plugins/__init__.py

@@ -0,0 +1,17 @@
+"""evo-agents-core-plugins: the first-party core plugins of the evo-agents hub, each a package of its own here
+(``telegram``, ``chats``) and an entry point of group ``evo_agents.plugins``, built on the API of core plugins alone
+(``evo_agents.hub.server.core_plugin_api``).
+
+The hub's image installs this distribution with ``--no-deps`` from the line ``deploy/hub/core-plugins.txt`` of
+evo-agents pins: it declares no dependency and uses only what the image of the hub already holds. Each plugin asks for
+the version of the API it is written for in its ``manifest``; ``python -m evo_core_plugins api`` prints that version,
+which every plugin of one release shares.
+
+Nothing here imports another plugin's package: ``PLUGINS`` names them for the checks and the command alone.
+"""
+
+__version__ = "1.0.0"
+
+PLUGINS = ("telegram", "chats")  # the packages of the plugins, each named as its entry point
+
+__all__ = ["PLUGINS", "__version__"]

evo_agents_core_plugins-1.0.0/evo_core_plugins/__main__.py

@@ -0,0 +1,54 @@
+"""``python -m evo_core_plugins api`` prints the version of the API of core plugins the plugins of this release are
+written for, ``major.minor``, as ``python -m evo_agents.hub.server.core_plugin_api version`` prints the version a
+checkout of evo-agents serves; the compat job of CI compares the two. It exits 1 when two plugins ask for different
+versions, which one release must not do.
+
+The version is read from each plugin's source (the assignment ``API = (major, minor)`` of its ``__init__``), without
+importing it, so the command runs where evo-agents is not installed.
+"""
+
+from __future__ import annotations
+
+import ast
+import sys
+from pathlib import Path
+
+from evo_core_plugins import PLUGINS
+
+USAGE = "usage: python -m evo_core_plugins api"
+HERE = Path(__file__).resolve().parent
+
+
+def required(plugin: str, root: Path = HERE) -> tuple[int, int]:
+    """The version of the API plugin ``plugin`` asks for, read from ``API = (major, minor)`` in its ``__init__``."""
+    init = root / plugin / "__init__.py"
+    for node in ast.parse(init.read_text(encoding="utf-8"), filename=str(init)).body:
+        if isinstance(node, ast.Assign) and any(getattr(target, "id", None) == "API" for target in node.targets):
+            value = ast.literal_eval(node.value)
+            if isinstance(value, tuple) and len(value) == 2 and all(type(part) is int for part in value):
+                return value
+            raise ValueError(f"{init}: API is {value!r}, not (major, minor)")
+    raise ValueError(f"{init} assigns no API = (major, minor)")
+
+
+def versions(root: Path = HERE) -> dict[str, tuple[int, int]]:
+    """plugin -> the version of the API it asks for, for every plugin of PLUGINS."""
+    return {plugin: required(plugin, root) for plugin in PLUGINS}
+
+
+def main(argv: list[str], root: Path | None = None) -> int:
+    if argv != ["api"]:
+        sys.stderr.write(USAGE + "\n")
+        return 2
+    found = versions(HERE if root is None else root)
+    if len(set(found.values())) != 1:
+        listed = ", ".join(f"{plugin} {major}.{minor}" for plugin, (major, minor) in found.items())
+        sys.stderr.write(f"the plugins of one release ask for different versions of the API: {listed}\n")
+        return 1
+    major, minor = next(iter(found.values()))
+    sys.stdout.write(f"{major}.{minor}\n")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv[1:]))