toolframe-llms-txt 0.2.1__tar.gz

toolframe_llms_txt-0.2.1/.github/workflows/ci.yml

@@ -0,0 +1,59 @@
+name: Python CI
+
+on:
+  push:
+  pull_request:
+  workflow_dispatch:
+  workflow_call:
+
+permissions:
+  contents: read
+
+# This workflow is also called by publish.yml. Do not give it a concurrency
+# group that can cancel its caller.
+jobs:
+  validate:
+    name: Validate Python package
+    runs-on: ubuntu-24.04
+    timeout-minutes: 20
+    steps:
+      - name: Check out this revision
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ github.sha }}
+          path: toolframe-llms-txt
+          persist-credentials: false
+
+      - name: Check out pinned SDK
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          repository: ${{ vars.TOOLFRAME_REPOSITORY_OWNER || github.repository_owner }}/toolframe-sdk
+          token: ${{ secrets.TOOLFRAME_READ_TOKEN || github.token }}
+          ref: ef91b609137a5fe7bae8e0c893e74b096ff06ffe
+          path: toolframe-sdk
+          persist-credentials: false
+
+      - name: Set up Python
+        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: '3.14.7'
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@c18668ad3cf93ea998bef934396af7bb5c839dc7 # v10.2.0
+        with:
+          version: '0.12.8'
+          enable-cache: false
+
+      - name: Run isolated local validation
+        working-directory: toolframe-llms-txt
+        run: bash scripts/ci.sh ../toolframe-sdk "$RUNNER_TEMP/toolframe-llms-txt-dist"
+
+      - name: Save validated distributions
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: python-distributions
+          path: |
+            ${{ runner.temp }}/toolframe-llms-txt-dist/*.whl
+            ${{ runner.temp }}/toolframe-llms-txt-dist/*.tar.gz
+          if-no-files-found: error
+          retention-days: 7

toolframe_llms_txt-0.2.1/.github/workflows/publish.yml

@@ -0,0 +1,73 @@
+name: Publish Python package
+
+on:
+  workflow_dispatch:
+    inputs:
+      repository:
+        description: Package index
+        type: choice
+        required: true
+        default: testpypi
+        options:
+          - testpypi
+          - pypi
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-${{ github.ref }}-${{ inputs.repository }}
+  cancel-in-progress: false
+
+jobs:
+  check-release:
+    name: Require a matching version tag
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    steps:
+      - name: Check out this revision
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ github.sha }}
+          persist-credentials: false
+
+      - name: Set up Python
+        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: '3.14.7'
+
+      - name: Check tag against project version
+        env:
+          PUBLISH_REPOSITORY: ${{ inputs.repository }}
+        run: python scripts/check_release.py "$GITHUB_REF"
+
+  validate:
+    name: Validate the release revision
+    needs: check-release
+    uses: ./.github/workflows/ci.yml
+    secrets: inherit
+    permissions:
+      contents: read
+
+  publish:
+    name: Publish validated distributions
+    needs: validate
+    runs-on: ubuntu-24.04
+    timeout-minutes: 10
+    environment:
+      name: ${{ inputs.repository }}
+      url: ${{ inputs.repository == 'testpypi' && 'https://test.pypi.org/p/toolframe-llms-txt' || 'https://pypi.org/p/toolframe-llms-txt' }}
+    permissions:
+      id-token: write
+    steps:
+      - name: Download distributions from this run
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: python-distributions
+          path: dist
+
+      - name: Publish with Trusted Publishing
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          repository-url: ${{ inputs.repository == 'testpypi' && 'https://test.pypi.org/legacy/' || 'https://upload.pypi.org/legacy/' }}
+          packages-dir: dist/

toolframe_llms_txt-0.2.1/.gitignore

@@ -0,0 +1,17 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+dist/
+*.egg-info/
+.coverage
+.DS_Store
+/build/
+/.coverage
+/htmlcov/
+
+# Local working documents, issue state, and development worktrees.
+/.local/
+/.issues/
+/.worktrees/

toolframe_llms_txt-0.2.1/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.

toolframe_llms_txt-0.2.1/NOTICE

@@ -0,0 +1,2 @@
+toolframe-llms-txt
+Copyright 2026 byfb

toolframe_llms_txt-0.2.1/PKG-INFO

@@ -0,0 +1,74 @@
+Metadata-Version: 2.5
+Name: toolframe-llms-txt
+Version: 0.2.1
+Summary: Standalone llms.txt provider for Toolframe
+Project-URL: Homepage, https://github.com/toolframe/toolframe-llms-txt
+Project-URL: Repository, https://github.com/toolframe/toolframe-llms-txt
+Project-URL: Documentation, https://github.com/toolframe/toolframe-llms-txt#readme
+Project-URL: Issues, https://github.com/toolframe/toolframe-llms-txt/issues
+Author-email: byfb <62798989+byfb@users.noreply.github.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.14
+Requires-Dist: starlette==1.6.0
+Requires-Dist: toolframe-sdk<0.4,>=0.2
+Requires-Dist: uvicorn==0.42.0
+Description-Content-Type: text/markdown
+
+# Toolframe llms.txt provider
+
+`toolframe-llms-txt` is the standalone Toolframe provider for serving the
+selected set of `llms.document` resources. The provider owns the public
+`/llms.txt` index and the linked `/llms/{owner}/{document}.md` documents; it
+serves document text supplied in `OwnedResource.content` and never opens a
+package path or scans a filesystem at request time.
+
+## Install
+
+Install the provider into a running [Toolframe application](https://github.com/toolframe/toolframe-core#readme):
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-llms-txt==0.2.1 --enable
+```
+
+Core resolves dependencies and manages the provider's isolated Python environment.
+The Entry Register template already includes this provider.
+
+Each `prepare` call validates and stages a complete immutable document set for
+its epoch. Staging and aborting leave the current HTTP responses unchanged.
+`commit` atomically selects one staged epoch, replacing the index and its
+documents together. A later epoch can contain fewer or no documents, which
+withdraws entries from the live provider. Other staged epochs remain available
+until they are committed or aborted.
+
+The optional `intro` configuration string is placed before the deterministic,
+owner and document ID sorted link list.
+
+From this directory, install the development environment and run the checks:
+
+```sh
+uv sync --group dev
+uv run pytest -q
+uv run ruff check src tests
+uv run ruff format --check src tests
+uv build --wheel
+```
+
+For the complete, isolated CI check (including sdist/wheel metadata, licenses,
+real dependency installation, and installed-wheel HTTP checks), run:
+
+```sh
+bash scripts/ci.sh
+```
+
+This requires Python 3.14.7, uv 0.12.8, and a sibling `toolframe-sdk` Git
+checkout containing the pinned SDK revision. It leaves the working development
+environment untouched. See [CI and publishing](docs/ci.md) for the dependency
+pin, workflow triggers, release commands, and required external setup.
+
+For release validation and Trusted Publisher setup, see [releasing](docs/releasing.md).
+
+## License
+
+Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

toolframe_llms_txt-0.2.1/README.md

@@ -0,0 +1,56 @@
+# Toolframe llms.txt provider
+
+`toolframe-llms-txt` is the standalone Toolframe provider for serving the
+selected set of `llms.document` resources. The provider owns the public
+`/llms.txt` index and the linked `/llms/{owner}/{document}.md` documents; it
+serves document text supplied in `OwnedResource.content` and never opens a
+package path or scans a filesystem at request time.
+
+## Install
+
+Install the provider into a running [Toolframe application](https://github.com/toolframe/toolframe-core#readme):
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-llms-txt==0.2.1 --enable
+```
+
+Core resolves dependencies and manages the provider's isolated Python environment.
+The Entry Register template already includes this provider.
+
+Each `prepare` call validates and stages a complete immutable document set for
+its epoch. Staging and aborting leave the current HTTP responses unchanged.
+`commit` atomically selects one staged epoch, replacing the index and its
+documents together. A later epoch can contain fewer or no documents, which
+withdraws entries from the live provider. Other staged epochs remain available
+until they are committed or aborted.
+
+The optional `intro` configuration string is placed before the deterministic,
+owner and document ID sorted link list.
+
+From this directory, install the development environment and run the checks:
+
+```sh
+uv sync --group dev
+uv run pytest -q
+uv run ruff check src tests
+uv run ruff format --check src tests
+uv build --wheel
+```
+
+For the complete, isolated CI check (including sdist/wheel metadata, licenses,
+real dependency installation, and installed-wheel HTTP checks), run:
+
+```sh
+bash scripts/ci.sh
+```
+
+This requires Python 3.14.7, uv 0.12.8, and a sibling `toolframe-sdk` Git
+checkout containing the pinned SDK revision. It leaves the working development
+environment untouched. See [CI and publishing](docs/ci.md) for the dependency
+pin, workflow triggers, release commands, and required external setup.
+
+For release validation and Trusted Publisher setup, see [releasing](docs/releasing.md).
+
+## License
+
+Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

toolframe_llms_txt-0.2.1/docs/ci.md

@@ -0,0 +1,93 @@
+# CI and publishing
+
+## Local validation
+
+Install Python 3.14.7 and uv 0.12.8, then run from this repository:
+
+```sh
+bash scripts/ci.sh
+```
+
+The SDK source defaults to `../toolframe-sdk`. It must be a Git checkout that
+contains commit `ef91b609137a5fe7bae8e0c893e74b096ff06ffe`. The script uses
+`git archive` of that exact commit, so concurrent or uncommitted SDK changes do
+not affect this validation. To choose another checkout or retain the validated
+distributions, pass paths explicitly:
+
+```sh
+bash scripts/ci.sh /path/to/toolframe-sdk /tmp/new-llms-txt-distributions
+```
+
+The output directory must not exist. Relative output paths are relative to this
+repository. `CI_KEEP_TEMP=1 bash scripts/ci.sh` retains the temporary workspace
+and prints its path for inspection; otherwise it is removed on exit.
+
+Every run starts with a fresh workspace, uv cache, development environment,
+dependency wheel directory, and runtime environment. It copies the current
+provider sources without `.venv`, `dist`, or caches and exports the SDK pin.
+Neither repository's existing development environment or lockfile is changed.
+The checks are:
+
+1. `uv sync --locked --group dev` with Python 3.14.7.
+2. `ruff check src tests scripts`, `ruff format --check src tests scripts`,
+   `bash -n scripts/ci.sh`, and the existing `pytest -q` provider suite.
+3. `uv build --no-sources` for the sdist and wheel. With no format selection,
+   uv builds the wheel from that sdist.
+4. `twine==7.0.0 check --strict` on both artifacts. Twine 7 supports the
+   Metadata-Version 2.5 emitted by the current build backend; 6.2.0 rejects it.
+5. A new SDK wheel built from the pinned sources with `uv build --no-sources
+   --wheel`, then an empty virtual environment receiving both explicit wheels
+   with normal dependency resolution and `uv pip check`. Starlette, uvicorn,
+   Pydantic, JSON Schema, and their runtime dependencies are actually installed.
+6. `python -I scripts/check_wheel.py` outside the source tree verifies the
+   installed version, plugin entry point, imports from the runtime environment,
+   and exact `LICENSE`/`NOTICE` contents in both distributions. A real localhost
+   HTTP server checks the empty index, staging, commit, document content and
+   MIME types, withdrawal/404 responses, and shutdown using runtime packages
+   plus the standard library only.
+
+The script fails at the first unsuccessful check. It does not use `--no-deps`,
+skip existing tests, or publish anything. Index access is required even if a
+developer already has packages cached. `PYTHON_VERSION` may explicitly override
+the local interpreter request; GitHub uses 3.14.7.
+
+To check workflow and shell syntax locally, install
+[actionlint](https://github.com/rhysd/actionlint) 1.7.12 and run:
+
+```sh
+actionlint .github/workflows/ci.yml .github/workflows/publish.yml
+bash -n scripts/ci.sh
+git diff --check
+```
+
+## GitHub workflows
+
+`ci.yml` runs on pushes, pull requests, manual dispatch, and calls from the
+publish workflow. It uses `ubuntu-24.04`, Python 3.14.7, uv 0.12.8, read-only
+repository permissions, SHA-pinned actions, a 20-minute timeout, and the same
+local script. Only successfully validated provider distributions are uploaded
+as the `python-distributions` artifact, retained for seven days. The SDK wheel
+is a validation dependency and is not part of that upload.
+
+The required sibling checkout is
+`${TOOLFRAME_REPOSITORY_OWNER}/toolframe-sdk`, where the repository variable
+`TOOLFRAME_REPOSITORY_OWNER` defaults to `github.repository_owner`. In a fork PR
+run on the upstream repository, this is the upstream owner, never the PR
+author's owner. The SDK checkout is fixed to the full commit above. There is
+no `pull_request_target` execution or shared reusable-workflow concurrency
+group that could cancel the publish caller.
+
+`publish.yml` runs only on manual dispatch. Its `repository` input selects
+`testpypi` (default) or `pypi`. It first requires `GITHUB_REF` to equal
+`refs/tags/v<project.version>` exactly; branch runs and mismatched tags fail.
+The release guard also rejects any index input other than those two choices.
+It calls CI from the same workflow revision and checks out `github.sha`, then
+downloads the artifacts from that run without rebuilding them. Only the final
+job has `id-token: write`, uses the selected GitHub environment, and invokes
+the PyPA publishing action with the appropriate index URL. Publication runs
+for the same tag and index queue without cancelling one another.
+
+## Publication
+
+See [releasing](releasing.md) for dependency order, private repository access,
+Trusted Publisher bindings, version tags and consumer installation checks.

toolframe_llms_txt-0.2.1/docs/releasing.md

@@ -0,0 +1,59 @@
+# Releasing toolframe-llms-txt
+
+The distribution name is `toolframe-llms-txt`; its current version is `0.2.1`.
+Release tags must exactly match `v<project.version>`. Ordinary CI never uploads
+packages. The manual `publish.yml` workflow reruns validation and publishes only
+artifacts produced by that successful run.
+
+## Validate
+
+Run the repository's existing validation workflow; its local commands and
+integration coverage are described in [CI](ci.md).
+
+Publish `toolframe-sdk==0.3.0` first. The coordinated order and native CLI channels are documented in
+[Toolframe's release guide](https://github.com/toolframe/toolframe-core/blob/main/docs/releasing.md).
+
+## Trusted Publishers
+
+Create GitHub environments named `testpypi` and `pypi`. On each corresponding
+package index, configure a normal or pending Trusted Publisher with these values:
+
+| Field | Value |
+| --- | --- |
+| Project | `toolframe-llms-txt` |
+| GitHub owner | `toolframe` |
+| GitHub repository | `toolframe-llms-txt` |
+| Workflow filename | `publish.yml` |
+| Environment | `testpypi` or `pypi`, matching the index |
+
+If publishing from another owner, use that actual owner in the publisher binding.
+Follow [PyPI's Trusted Publishing guide](https://docs.pypi.org/trusted-publishers/using-a-publisher/).
+Only the publishing job receives `id-token: write`; no PyPI API-token secret is
+needed. Configure environment reviewers and release-tag protections as appropriate.
+
+Jobs that fetch sibling repositories support the optional read-only
+`TOOLFRAME_READ_TOKEN` GitHub secret. It must be able to read those repositories
+while they are private. Public siblings require no extra token; secrets are not
+available to untrusted fork PRs. `TOOLFRAME_REPOSITORY_OWNER` overrides the trusted
+sibling owner where the workflow exposes that variable.
+
+## Publish and verify
+
+After the release commit and matching tag are available remotely, manually run
+`publish.yml` at `v0.2.1`, selecting `testpypi` first and then `pypi`.
+A branch or mismatched tag is rejected. Downloaded files are the artifacts from
+that run; the publishing job does not rebuild them. Published files cannot be
+replaced under the same version.
+
+After PyPI publication, verify a clean installation:
+
+```sh
+uv venv --python 3.14.7 build/consumer
+uv pip install --python build/consumer/bin/python 'toolframe-llms-txt==0.2.1'
+uv pip check --python build/consumer/bin/python
+```
+
+TestPyPI does not mirror dependencies. Test the specific artifact against an
+explicit dependency source; a local or TestPyPI check alone does not demonstrate
+that production PyPI resolution works. Keep logs, hashes and exact revisions in
+CI artifacts or ignored local evidence directories.