apodex-agent-core 0.3.0__tar.gz

apodex_agent_core-0.3.0/.github/workflows/ci.yml

@@ -0,0 +1,40 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+    types: [opened, synchronize, reopened, labeled, unlabeled]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+        with:
+          python-version: "3.12"
+      - run: uv sync --frozen --extra dev
+      - run: uv run ruff check agent_core tests scripts
+      - run: uv run pyright agent_core
+      - run: uv run pytest -q
+      - run: uv build
+
+  # Two products pin an AgentCore revision. If published code changes without a
+  # version bump, both end up reporting the same version for different code and
+  # the installed dist-info stops identifying what is running. Enforce the bump
+  # at the pull request, where it is cheap to fix.
+  version-bump:
+    if: >-
+      github.event_name == 'pull_request' &&
+      !contains(github.event.pull_request.labels.*.name, 'skip-version-bump')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          # The check needs the merge base, which a shallow clone does not have.
+          fetch-depth: 0
+      - run: python3 scripts/check_version_bump.py --base "$BASE_SHA"
+        env:
+          BASE_SHA: ${{ github.event.pull_request.base.sha }}

apodex_agent_core-0.3.0/.github/workflows/release.yml

@@ -0,0 +1,121 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+        with:
+          python-version: "3.12"
+
+      # Fail before building anything if the tag names a version the tree does
+      # not declare, or if the release has no changelog entry to publish.
+      - name: Verify tag matches declared version
+        run: python3 scripts/version.py --check-tag "$TAG"
+        env:
+          TAG: ${{ github.ref_name }}
+
+      - name: Extract release notes
+        run: |
+          set -euo pipefail
+          version="$(python3 scripts/version.py)"
+          python3 scripts/changelog_section.py "$version" > release-notes.md
+
+      # The tagged tree is re-verified rather than trusting main's CI run: a tag
+      # can point at a commit that never went through a pull request.
+      - run: uv sync --frozen --extra dev
+      - run: uv run ruff check agent_core tests scripts
+      - run: uv run pyright agent_core
+      - run: uv run pytest -q
+      - run: uv build
+
+      # A PyPI version number can never be reused, not even after deleting the
+      # release. Reject malformed metadata here rather than burning the version.
+      - name: Validate package metadata
+        run: uv run --with twine twine check dist/*
+
+      # The release contract requires the artifact to install and import in a
+      # clean environment. Checking it here matters more than usual because a
+      # PyPI version number cannot be reclaimed: a wheel that fails to import
+      # would burn the version rather than fail the release.
+      - name: Install and import the built wheel in a clean environment
+        run: |
+          set -euo pipefail
+          uv venv /tmp/wheel-smoke
+          uv pip install --python /tmp/wheel-smoke/bin/python dist/*.whl
+          /tmp/wheel-smoke/bin/python - <<'SMOKE'
+          import agent_core
+          from agent_core import user_msg
+
+          assert user_msg("hi") == {"role": "user", "content": "hi"}
+          print("imported", agent_core.__name__, "with", len(agent_core.__all__), "exports")
+          SMOKE
+
+      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: release-artifacts
+          path: |
+            dist/
+            release-notes.md
+          if-no-files-found: error
+
+  # Separate job so `id-token: write` — which mints the OIDC identity PyPI
+  # trusts — is scoped to publishing alone and never exposed to the build or to
+  # any third-party action running beside it.
+  publish-pypi:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: release-artifacts
+          path: release-artifacts/
+      # Trusted Publishing: no API token, no secret. PyPI verifies the OIDC
+      # claim naming this repository, this workflow file, and the environment
+      # above, then issues a short-lived upload token itself.
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          packages-dir: release-artifacts/dist/
+
+  # Publish the GitHub Release last. A failed PyPI upload therefore cannot leave
+  # a GitHub Release claiming that a version was published when it was not.
+  publish-github:
+    needs: publish-pypi
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: release-artifacts
+          path: release-artifacts/
+      # `gh release create` is not retry-safe after a partial API failure. Use
+      # an upsert so rerunning this job always converges on the same release.
+      - name: Publish GitHub Release
+        run: |
+          set -euo pipefail
+          if gh release view "$TAG" >/dev/null 2>&1; then
+            gh release edit "$TAG" \
+              --title "AgentCore ${TAG#v}" \
+              --notes-file release-artifacts/release-notes.md
+            gh release upload "$TAG" --clobber \
+              release-artifacts/dist/*.whl release-artifacts/dist/*.tar.gz
+          else
+            gh release create "$TAG" \
+              --title "AgentCore ${TAG#v}" \
+              --notes-file release-artifacts/release-notes.md \
+              release-artifacts/dist/*.whl release-artifacts/dist/*.tar.gz
+          fi
+        env:
+          TAG: ${{ github.ref_name }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

apodex_agent_core-0.3.0/.gitignore

@@ -0,0 +1,10 @@
+/.venv/
+/dist/
+/build/
+/.pytest_cache/
+/.ruff_cache/
+/.mypy_cache/
+/.pyright/
+__pycache__/
+*.py[cod]
+*.egg-info/

apodex_agent_core-0.3.0/CHANGELOG.md

@@ -0,0 +1,132 @@
+# Changelog
+
+Notable changes to `apodex-agent-core`, newest first. This file is the contract
+between AgentCore and its consumers: every release entry must say what a product
+has to know before upgrading. The release workflow reads the matching section as
+the GitHub Release body, so a release with no entry here fails.
+
+Versioning follows [docs/versioning.md](docs/versioning.md).
+
+## [0.3.0] - 2026-09-03
+
+First published release. AgentCore is now open source under Apache-2.0 and
+distributed on PyPI as [`apodex-agent-core`](https://pypi.org/project/apodex-agent-core/).
+
+### Consumer action
+
+Replace the Git dependency with the published package:
+
+```toml
+dependencies = [
+  "apodex-agent-core==0.3.0",   # was: apodex-agent-core @ git+ssh://…@<rev>
+]
+```
+
+Then delete the credential plumbing this required — the AgentCore deploy key,
+`AGENT_CORE_REPO_TOKEN`, and any `insteadOf` rewriting. Installing needs no
+credential now, `docker build` included.
+
+### Changed
+
+- **Distribution.** Releases publish to PyPI from the tagged tree using Trusted
+  Publishing (OIDC): no API token is stored anywhere, and `id-token: write` is
+  scoped to the publishing job alone. GitHub Releases still carry the wheel,
+  sdist, and changelog section.
+- **Downstream bumps are Dependabot's job.** The `repository_dispatch` +
+  repin-script mechanism is deleted along with `.github/downstream/`. It existed
+  only because a private Git dependency could not be resolved without a
+  credential; a public PyPI package needs none, and Dependabot's `uv` ecosystem
+  updates `pyproject.toml` and `uv.lock` and opens a pull request that the
+  product's own CI validates. This also removes the need for an organization-level
+  GitHub App or a cross-repository PAT.
+- Package metadata: SPDX `license = "Apache-2.0"` with `license-files` (PEP 639),
+  trove classifiers, and project URLs.
+- `docs/versioning.md` records why publishing to PyPI reversed the earlier
+  decision to stay on Git pins — going public removed that trade's entire cost
+  side.
+
+### Added
+
+- The release now runs `twine check` and installs the built wheel in a clean
+  environment to `import agent_core` before publishing. A PyPI version number
+  can never be reused, so a broken artifact must fail the release rather than
+  consume the number.
+- `docs/downstream-bump.md`: PyPI publisher registration, the `pypi` environment,
+  the Dependabot config, and the one real limitation — a Dependabot pull request
+  runs CI as if from a fork, so `secrets.*` resolves against Dependabot secrets
+  rather than Actions secrets.
+
+### Fixed
+
+- The version gate accepted a *decreasing* version: it compared for inequality
+  rather than an increase, so a pull request could move `0.2.0` back to `0.1.9`
+  and pass.
+- The `skip-version-bump` label was inert. The default `pull_request` event types
+  exclude `labeled`, so applying the label did not re-run the check and the pull
+  request stayed red forever.
+
+## [0.2.0] - 2026-09-03
+
+**Never published.** No tag was pushed and no artifact was distributed; the
+version exists only in `main`'s history. Consumers went from Git revisions
+straight to `0.3.0` on PyPI. The entry below is kept because it records when
+version discipline was introduced.
+
+First versioned release. Functionally this is the runtime that products have
+already been consuming by commit SHA; what changes is that the revision now has
+a name.
+
+Why 0.2.0 and not 0.1.1: `0.1.0` was the bootstrap constant and was never
+released or moved. Every commit from the initial foundation through the
+cooldown-fallback observability work declared that same version, so `0.1.0`
+identifies no particular code and is retired rather than reused.
+
+### Published surface
+
+The importable surface is `agent_core.*` as scoped in the README, with per-area
+contracts in `docs/*-boundary.md`: messages and token estimation, context
+management and spill storage, LLM runtime (binding, streaming, retry
+classification, runaway recovery), the agent loop and its typed product hooks,
+durable run journals, MiniDAG and registries, middleware and observers, agent-bus
+coordination, skills, and scheduling.
+
+### Consumer action
+
+Repin from a commit SHA to the tag:
+
+```toml
+dependencies = [
+  "apodex-agent-core @ git+ssh://git@github.com/ApodexAI/AgentCore.git@v0.2.0",
+]
+```
+
+No source changes are required: the code at `v0.2.0` is `main` as of this
+release. Installed metadata now reports `0.2.0`, so `pip list` and the
+`dist-info` in a product image finally identify which AgentCore is running.
+
+Note that as of this release neither product declares AgentCore on its `main`
+branch — the pin exists only on each product's in-progress migration branch
+(`fix/ci-bwrap-soft-probe`, `refactor/agent-core`). The repin above applies
+wherever the declaration currently lives.
+
+### Added
+
+- `docs/versioning.md`: version policy, what counts as a breaking change while
+  the public surface is still wider than `agent_core.__all__`, and the release
+  procedure.
+- `CHANGELOG.md` (this file).
+- CI now fails a pull request that changes published code without bumping
+  `[project].version`, which is what let 80 commits ship as `0.1.0`.
+- `Release` workflow: pushing a `v*` tag re-runs the full check suite, verifies
+  the tag matches `[project].version`, builds the wheel and sdist, and publishes
+  them on a GitHub Release with these notes attached.
+- Automated downstream bump PRs: a release dispatches to ApodexHarness and
+  FrontierAgentInternal, which repin and open a pull request for their own CI to
+  validate. Templates live in `.github/downstream/`; setup is
+  [docs/downstream-bump.md](docs/downstream-bump.md). The workflows mint
+  least-privilege, short-lived GitHub App tokens per run, strictly validate the
+  dispatched version before exposing it to shell, and do not persist write
+  credentials in the checkout.
+- Corrected the documented pin scheme to `git+ssh://git@github.com/`, which is
+  what both products actually declare. The credential note previously rewrote
+  `https://github.com/`, a no-op against an `ssh://` dependency URL.

apodex_agent_core-0.3.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 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 Support. 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 support.
+
+   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.