aelix-agent-core 0.1.0b2__tar.gz

aelix_agent_core-0.1.0b2/.gitignore

@@ -0,0 +1,150 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+build/
+dist/
+.coverage
+.pytest_cache/
+
+# Virtual environments
+.venv/
+venv/
+
+# Local environment
+.env
+.env.local
+# Plaintext key dumps carried between machines. `.env` above covers the file the
+# code reads; these cover the shapes it arrives in. Neither is in the pyproject
+# `exclude` lists, so this file is their only guard — see the `.claude` block
+# below for why that distinction matters.
+env.txt
+
+# Container-escape exports (RESTORE.md). Root-level and large, and the sdist's
+# default file set is the whole repo root, so an unignored one ships.
+/aelix-export-*.tar.gz
+
+# Editor / OS
+.DS_Store
+.idea/
+.vscode/
+
+# Agent / OMC developer state — never publish (#111 B-7).
+#
+# The previous rules were `.omc/state/` + `.omc/sessions/`. A gitignore pattern
+# with a slash in the middle is ANCHORED to the directory holding the .gitignore,
+# so those two matched ONLY `/.omc/state/` at the repo root. A nested
+# `packages/aelix-coding-agent/src/aelix_coding_agent/.omc/state/` escaped them
+# entirely, stayed untracked-but-present on a maintainer's disk, and hatchling
+# (which honours these ignore rules when selecting build files) swept maintainer
+# session transcripts straight into the published wheel and sdist.
+#
+# A NESTED `.omc` is always developer state and is ignored at any depth, which is
+# what closes the leak. The REPO-ROOT `.omc/` is different: `.omc/specs/` is the
+# committed sprint-plan record, not scratch — 50 files are tracked there and every
+# recent sprint (P2, P3, W1-A, #114, #118) commits its plan alongside the code it
+# describes. Requiring `git add -f` for those is friction pointed at the wrong
+# thing: P1's plan was written, left unstaged, and lost exactly that way.
+#
+# So: ignore everything directly under the root `.omc/` EXCEPT `specs/`. Git
+# cannot re-include a path whose parent directory is excluded, which is why this
+# is `/.omc/*` (contents) rather than `/.omc/` (the directory itself).
+#
+# Publishing is NOT what this rule protects — the wheel and sdist are guarded
+# independently by the `exclude` blocks in each pyproject, proven by
+# `tests/packaging/test_build_hygiene.py`: strip `.omc` from those excludes and
+# planted state leaks into the wheel even with this file untouched.
+/.omc/*
+!/.omc/specs/
+**/*/.omc/
+.ruff_cache/
+
+# Agent instruction files — local to a maintainer's checkout, not product.
+CLAUDE.md
+AGENTS.md
+
+# Exported TUI session transcripts (`/export`) land in the CWD.
+aelix-session-*.html
+
+# Claude Code per-checkout state (#143).
+#
+# This used to be just `.claude/settings.local.json`, with the rest of `.claude/`
+# covered by `.git/info/exclude`. That file is PER-CLONE and does not travel, so
+# the protection existed only on the machines that had already set it up — and
+# hatchling, which selects build files by honouring VCS ignore rules, had nothing
+# to go on here. A maintainer's local `uv build --sdist` at ee1623c swept
+# `.claude/worktrees/` into the tarball — complete internal working copies of this
+# repo, one directory per agent session, uncommitted work included — ready to be
+# attached to a public GitHub Release.
+#
+# HOW BIG IS A MOVING TARGET, so do not read the figures as a size. Three builds
+# of that SAME commit, same machine, measured 1,994 entries under
+# `.claude/worktrees/` in a 20,039,596-byte tarball; then 4,112 six minutes
+# later; then 7,233 in a 48,004,955-byte tarball later the same day. The commit
+# never changed — agents kept creating worktrees. Each number is a floor observed
+# at a moment, and it rises for as long as this repo is worked on by agents.
+#
+# `.claude/` is developer state, and the repo root's copy is ignored wholesale
+# (all but one file — see the exception below). Publishing is guarded
+# independently by the `exclude` blocks in every pyproject (most of
+# tests/packaging/test_build_hygiene.py deletes this file before building,
+# precisely so the excludes are what gets measured) — this rule is the belt.
+#
+# The live agent worktrees under `.claude/worktrees/` are registered in
+# `.git/worktrees/`, not by being tracked, so ignoring the directory does not
+# disturb them: `git worktree list` is unaffected.
+#
+# ONE EXCEPTION, `.claude/settings.json`: Claude Code's documented CHECKED-IN
+# team configuration (`settings.local.json` is the personal sibling and stays
+# ignored). Nothing tracks it today — `git ls-files .claude/` is empty — so this
+# breaks nothing now; it exists so that a maintainer who adds team settings
+# tomorrow does not watch git silently swallow them.
+#
+# THE FOUR LINES ARE NOT INTERCHANGEABLE. Git cannot re-include a path whose
+# parent directory is excluded, so the obvious `.claude/` + `!/.claude/settings.json`
+# does NOT work — measured, the file stays ignored by `.claude/`. The root
+# directory has to be re-admitted (`!/.claude/`), its contents re-excluded
+# (`/.claude/*`, which keeps git from descending into `worktrees/`), and only then
+# can the one file be named.
+#
+# AND EVERY ONE OF THEM IS ANCHORED, WHICH IS THE OPPOSITE OF THE `.omc` RULE
+# ABOVE — deliberately, and it cost a build to learn. The agent worktrees this
+# repo is developed in LIVE under `.claude/worktrees/`, so a build run from one
+# has `.claude` sitting in its own root path. An UNANCHORED rule naming that
+# directory therefore matches the build root itself, and hatchling responds by
+# discarding this entire file for that build: measured twice, first with
+# `.claude/` and again with `**/*/.claude/`, and both times a planted `.env.local`
+# — a file only this rule excludes, in a repo whose real `.env` holds provider
+# keys and a PyPI token — shipped into the sdist. Anchoring to `/.claude/` fixed
+# it in the same tree, same command. The cost is real and accepted: a nested
+# `packages/**/.claude/` is no longer ignored by git. It still reaches no
+# artifact, because the pyproject `exclude` lists name `.claude` unanchored and
+# those are read as build config rather than as VCS rules, so they do not trip
+# this. `.omc` can use the `**/*/` form for the same job only because nothing
+# ever builds from inside a `.omc/` directory.
+#
+# AND THE NEGATION CHANGES WHAT THE BUILD SHIPS, which is not obvious and was not
+# free. hatchling reads THIS FILE and concatenates its lines with the pyproject
+# `exclude` patterns into one gitignore spec, and in that spec a pattern matching
+# the FILE outranks a pattern matching its parent DIRECTORY no matter which came
+# later — so `!/.claude/settings.json` here beat `.claude` there, and a real
+# `uv build --sdist` shipped `.claude/settings.json` into the tarball. Every
+# pyproject `exclude` list therefore names that exact path as well. Keep the two
+# in step: a negation added here needs its counterpart there, or this file
+# quietly re-opens #143 one path at a time.
+#
+# With both in place the halves are independent again, as intended: git MAY track
+# that one file, and it still reaches no artifact.
+# tests/packaging/test_build_hygiene.py proves the second half by building with
+# this file present — the older fixtures there delete it on purpose and so cannot
+# see this interaction at all.
+/.claude/
+!/.claude/
+/.claude/*
+!/.claude/settings.json
+
+# Name-reservation build output (scripts/reserve_*_names.py) — regenerable
+/dist-reservation/
+/npm-reservation/
+/.reservation-build/

aelix_agent_core-0.1.0b2/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.

aelix_agent_core-0.1.0b2/NOTICE

@@ -0,0 +1,15 @@
+Aelix
+Copyright 2026 Aelix Contributors
+
+This product includes software derived from pi
+(https://github.com/earendil-works/pi), Copyright (c) 2025 Mario Zechner,
+licensed under the MIT License. Substantial portions of Aelix are a
+TypeScript-to-Python port of pi (reference commit earendil-works/pi@734e08e).
+The full MIT license text and copyright notice are reproduced in
+THIRD-PARTY-NOTICES.md, which accompanies this file in all source and
+binary distributions of Aelix.
+
+The bundled model catalog (aelix_ai/models_generated.json) is derived from
+pi's generated catalog, which is in turn generated from data published by
+models.dev (https://github.com/sst/models.dev), Copyright (c) 2025
+models.dev, licensed under the MIT License.

aelix_agent_core-0.1.0b2/PKG-INFO

@@ -0,0 +1,55 @@
+Metadata-Version: 2.5
+Name: aelix-agent-core
+Version: 0.1.0b2
+Summary: Aelix agent loop + harness + hook bus. Pi-agent-core parity.
+Project-URL: Homepage, https://github.com/handochan/aelix-ai
+Project-URL: Repository, https://github.com/handochan/aelix-ai
+Project-URL: Issues, https://github.com/handochan/aelix-ai/issues
+Author: Aelix Contributors
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+License-File: THIRD-PARTY-NOTICES.md
+Keywords: agent,agent-loop,ai,harness,hooks,llm
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Requires-Python: >=3.11
+Requires-Dist: aelix-ai==0.1.0b2
+Requires-Dist: pathspec>=0.12
+Requires-Dist: pydantic<3,>=2.7
+Requires-Dist: pyyaml>=6.0
+Description-Content-Type: text/markdown
+
+# aelix-agent-core
+
+The low-level agent runtime for [Aelix](https://github.com/handochan/aelix-ai):
+the stateful `Agent`, the hook-aware `AgentHarness`, the typed `HookBus`, and the
+async agent loop. Core runtime with no extension dependencies. Pi-agent-core
+parity.
+
+This package is part of the Aelix distribution set. For the full runtime, install
+the umbrella package:
+
+```bash
+pip install aelix
+```
+
+> **Below `0.1.0b2` that command installs a placeholder, not Aelix.** The PyPI
+> names were reserved by a metadata-only `0.0.0a0` pre-release, and with nothing
+> but pre-releases on the index pip takes the newest — so it reported success and
+> left you with no `aelix` command. From `0.1.0b2` on a pre-release tag publishes
+> the real distribution (ADR-0240) and the command above resolves it. The
+> checksum-verified installer described in the project README is still the
+> recommended path: it is the only one that verifies the wheels it installs.
+
+See the [project README](https://github.com/handochan/aelix-ai#readme) for
+architecture, usage, and the CLI/TUI.
+
+Licensed under Apache-2.0.

aelix_agent_core-0.1.0b2/README.md

@@ -0,0 +1,26 @@
+# aelix-agent-core
+
+The low-level agent runtime for [Aelix](https://github.com/handochan/aelix-ai):
+the stateful `Agent`, the hook-aware `AgentHarness`, the typed `HookBus`, and the
+async agent loop. Core runtime with no extension dependencies. Pi-agent-core
+parity.
+
+This package is part of the Aelix distribution set. For the full runtime, install
+the umbrella package:
+
+```bash
+pip install aelix
+```
+
+> **Below `0.1.0b2` that command installs a placeholder, not Aelix.** The PyPI
+> names were reserved by a metadata-only `0.0.0a0` pre-release, and with nothing
+> but pre-releases on the index pip takes the newest — so it reported success and
+> left you with no `aelix` command. From `0.1.0b2` on a pre-release tag publishes
+> the real distribution (ADR-0240) and the command above resolves it. The
+> checksum-verified installer described in the project README is still the
+> recommended path: it is the only one that verifies the wheels it installs.
+
+See the [project README](https://github.com/handochan/aelix-ai#readme) for
+architecture, usage, and the CLI/TUI.
+
+Licensed under Apache-2.0.

aelix_agent_core-0.1.0b2/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,84 @@
+# Third-Party Notices
+
+Aelix is licensed under the Apache License 2.0 (see [LICENSE](LICENSE)). This
+file reproduces the license texts and copyright notices of third-party software
+that Aelix is derived from, as required by those licenses. It accompanies the
+`LICENSE` and `NOTICE` files in all source and binary distributions of Aelix.
+
+## pi (earendil-works/pi)
+
+Substantial portions of Aelix are a TypeScript-to-Python port of **pi**
+(<https://github.com/earendil-works/pi>, reference commit `734e08e`): the agent
+loop and harness, session and compaction machinery, provider adapters, built-in
+tools, model registry and generated model catalog, CLI modes, and HTML export
+are derived from the corresponding pi modules. Per-module provenance markers
+(`Pi parity: <file>.ts (SHA 734e08e)`) are preserved in source docstrings.
+
+```
+MIT License
+
+Copyright (c) 2025 Mario Zechner
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## models.dev (model catalog data)
+
+The generated model catalog
+(`packages/aelix-ai/src/aelix_ai/models_generated.json`) is derived from pi's
+`models.generated.ts`, which pi generates from data published by **models.dev**
+(<https://github.com/sst/models.dev> / <https://models.dev>).
+
+```
+MIT License
+
+Copyright (c) 2025 models.dev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## Python package dependencies
+
+Aelix's wheels and sdists do not vendor or bundle third-party Python packages;
+dependencies are declared as installation requirements and are installed
+separately by pip/uv under their own licenses. The full dependency inventory
+with licenses is recorded in the CycloneDX SBOM under [`sbom/`](sbom/).
+
+If you redistribute Aelix *together with* its resolved dependencies (for
+example a frozen binary, a container image, or vendored `site-packages`), you
+must additionally comply with those packages' licenses. In the current locked
+set this notably includes `certifi`, `pathspec`, and parts of `tqdm` (Mozilla
+Public License 2.0 — file-level copyleft: include their license texts and keep
+their source availability).

aelix_agent_core-0.1.0b2/pyproject.toml

@@ -0,0 +1,86 @@
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[project]
+name = "aelix-agent-core"
+version = "0.1.0b2"
+description = "Aelix agent loop + harness + hook bus. Pi-agent-core parity."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE", "THIRD-PARTY-NOTICES.md"]
+authors = [{ name = "Aelix Contributors" }]
+keywords = ["ai", "agent", "llm", "agent-loop", "harness", "hooks"]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "Operating System :: MacOS",
+  "Operating System :: POSIX :: Linux",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Software Development :: Libraries :: Application Frameworks",
+  "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+dependencies = [
+  # Pinned to the shared release version; the workspace source below is
+  # dev-only and stripped from the built metadata.
+  "aelix-ai==0.1.0b2",
+  # Sprint 6h₁ (ADR-0069, P-216/P-217): prompt-templates frontmatter
+  # parsing + skills .gitignore-style ignore matching.
+  "PyYAML>=6.0",
+  "pathspec>=0.12",
+  # Sprint 6h₉a (ADR-0094/0095/0096): contracts Pydantic models for the
+  # 4-tier extension architecture (descriptor envelope, manifest, primitives).
+  "pydantic>=2.7,<3",
+]
+
+[project.urls]
+Homepage = "https://github.com/handochan/aelix-ai"
+Repository = "https://github.com/handochan/aelix-ai"
+Issues = "https://github.com/handochan/aelix-ai/issues"
+
+[tool.uv.sources]
+aelix-ai = { workspace = true }
+
+# #111 B-7 — developer-state exclusions on both targets. See the root
+# pyproject.toml for the rationale. NARROW ON PURPOSE: exact directory names,
+# exact file names and one scoped glob only. Never widen to an extension glob —
+# the distributions carry content files, not only .py sources.
+[tool.hatch.build.targets.wheel]
+packages = ["src/aelix_agent_core"]
+exclude = [
+  ".claude",
+  ".claude/settings.json",
+  ".uv-cache",
+  ".omc",
+  "__pycache__",
+  "*.pyc",
+  "*.pyo",
+  ".ruff_cache",
+  ".pytest_cache",
+  "CLAUDE.md",
+  "AGENTS.md",
+  "aelix-session-*.html",
+  ".env",
+  ".env.local",
+]
+
+[tool.hatch.build.targets.sdist]
+exclude = [
+  ".claude",
+  ".claude/settings.json",
+  ".uv-cache",
+  ".omc",
+  "__pycache__",
+  "*.pyc",
+  "*.pyo",
+  ".ruff_cache",
+  ".pytest_cache",
+  "CLAUDE.md",
+  "AGENTS.md",
+  "aelix-session-*.html",
+  ".env",
+  ".env.local",
+]