toolframe-auth 0.2.0__tar.gz

toolframe_auth-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,79 @@
+name: Python CI
+
+on:
+  pull_request:
+  push:
+  workflow_dispatch:
+  workflow_call:
+    inputs:
+      release-ref:
+        description: Require this ref to match the package version before validation
+        type: string
+        default: ""
+    secrets:
+      TOOLFRAME_READ_TOKEN:
+        description: Optional read-only token for private sibling repositories
+        required: false
+      TOOLFRAME_DEPENDENCIES_TOKEN:
+        description: Optional read-only token for private sibling repositories
+        required: false
+
+permissions:
+  contents: read
+
+jobs:
+  validate:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 20
+    steps:
+      - name: Check out the revision being validated
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ github.sha }}
+          path: toolframe-auth
+          persist-credentials: false
+
+      - name: Check out the pinned SDK
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          repository: ${{ vars.TOOLFRAME_REPOSITORY_OWNER || github.repository_owner }}/toolframe-sdk
+          ref: ef91b609137a5fe7bae8e0c893e74b096ff06ffe
+          path: toolframe-sdk
+          token: ${{ secrets.TOOLFRAME_READ_TOKEN || secrets.TOOLFRAME_DEPENDENCIES_TOKEN || github.token }}
+          persist-credentials: false
+
+      - name: Check out the pinned SQLite provider
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          repository: ${{ vars.TOOLFRAME_REPOSITORY_OWNER || github.repository_owner }}/toolframe-storage-sqlite
+          ref: 67c3b0ac4365db81c6c866083330c6405f299dfd
+          path: toolframe-storage-sqlite
+          token: ${{ secrets.TOOLFRAME_READ_TOKEN || secrets.TOOLFRAME_DEPENDENCIES_TOKEN || github.token }}
+          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: Lint, test, build and install the distributions
+        working-directory: toolframe-auth
+        env:
+          RELEASE_REF: ${{ inputs.release-ref || '' }}
+        run: python scripts/ci.py --release-ref "$RELEASE_REF" --output "$RUNNER_TEMP/auth-dist"
+
+      - name: Save validated distributions
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: toolframe-auth-dist
+          path: |
+            ${{ runner.temp }}/auth-dist/*.whl
+            ${{ runner.temp }}/auth-dist/*.tar.gz
+          if-no-files-found: error
+          retention-days: 7

toolframe_auth-0.2.0/.github/workflows/publish.yml

@@ -0,0 +1,55 @@
+name: Publish Python package
+
+on:
+  workflow_dispatch:
+    inputs:
+      repository:
+        description: Package index (run this workflow on a v<project.version> tag)
+        type: choice
+        options:
+          - testpypi
+          - pypi
+        default: testpypi
+        required: true
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-${{ github.repository }}-${{ github.ref }}-${{ inputs.repository }}
+  cancel-in-progress: false
+
+jobs:
+  validate:
+    uses: ./.github/workflows/ci.yml
+    secrets: inherit
+    with:
+      release-ref: ${{ github.ref }}
+
+  publish:
+    needs: validate
+    runs-on: ubuntu-24.04
+    timeout-minutes: 10
+    environment:
+      name: ${{ inputs.repository }}
+    permissions:
+      id-token: write
+    steps:
+      - name: Download the distributions from this run
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: toolframe-auth-dist
+          path: dist
+
+      - name: Publish to TestPyPI
+        if: inputs.repository == 'testpypi'
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          packages-dir: dist/
+
+      - name: Publish to PyPI
+        if: inputs.repository == 'pypi'
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          packages-dir: dist/

toolframe_auth-0.2.0/.gitignore

@@ -0,0 +1,13 @@
+.venv/
+__pycache__/
+.pytest_cache/
+.ruff_cache/
+dist/
+/build/
+/.coverage
+/htmlcov/
+
+# Local working documents, issue state, and development worktrees.
+/.local/
+/.issues/
+/.worktrees/

toolframe_auth-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

toolframe_auth-0.2.0/NOTICE

@@ -0,0 +1,2 @@
+toolframe-auth
+Copyright 2026 byfb

toolframe_auth-0.2.0/PKG-INFO

@@ -0,0 +1,129 @@
+Metadata-Version: 2.5
+Name: toolframe-auth
+Version: 0.2.0
+Summary: Managed access passwords and sessions for Toolframe
+Project-URL: Homepage, https://github.com/toolframe/toolframe-auth
+Project-URL: Repository, https://github.com/toolframe/toolframe-auth
+Project-URL: Documentation, https://github.com/toolframe/toolframe-auth#readme
+Project-URL: Issues, https://github.com/toolframe/toolframe-auth/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: toolframe-sdk==0.3.0
+Description-Content-Type: text/markdown
+
+# Toolframe Auth
+
+Authentication and grant decisions for access passwords, federated users and
+revocable agent delegation. This provider owns `auth`'s managed SQL store; it never opens
+database files itself. It requires SDK 0.3.0 and `toolframe.storage.sql`.
+
+## Install
+
+With a running Toolframe application and an active SQL storage provider:
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-auth==0.2.0 --enable
+```
+
+The [Entry Register template](https://github.com/toolframe/toolframe-core#readme)
+includes Auth and Dashboard Auth. The host resolves the SDK and the plugin's
+isolated environment automatically.
+
+Core supplies the private `password-lookup` key separately from configuration.
+Credential records store a keyed HMAC-SHA256 lookup plus a per-record salted
+scrypt verifier (`N=131072`, `r=8`, `p=1`, 32-byte output). At most two hashes run
+concurrently. Core also limits login attempts. Sessions use random opaque tokens;
+only SHA-256 digests of those high-entropy tokens are persisted. Metadata/list
+responses exclude lookup values, salts and verifiers.
+
+The internal `toolframe.auth` service implements login, resolve/touch, logout,
+create/list/update/revoke. Core admits administrators and passes their trusted
+principal/catalog. These methods are not directly published business APIs.
+`toolframe-dashboard-auth` supplies presentation through core's protected API.
+
+New passwords accept 8–32 characters; omitted passwords generate a random
+32-character secret. Existing longer passwords issued by 0.1.0 can still log in.
+The password-length policy preserves existing password records and sessions.
+
+## Federated users and agent grants
+
+Enable `toolframe-oidc-auth` for OIDC login. Auth remains the local identity and
+permission authority; it does not implement provider discovery or OAuth endpoints.
+Configure the trusted plugin ID with `identity_provider` (default `oidc-auth`) and
+initial admission with exact `federated_identities` entries:
+
+```toml
+[plugins.auth.config]
+identity_provider = "oidc-auth"
+federated_identities = [
+  { issuer = "https://accounts.google.com", subject = "VERIFIED_SUB", label = "Alice", scopes = ["notes.read"] },
+]
+```
+
+The trusted plugin must supply verified issuer/subject claims. No email matching
+or automatic account merging occurs. The admission entry creates a local user
+once; later permission/disablement changes use the protected user-management API.
+Changing admission configuration does not overwrite existing users. Every user
+gets `system.auth.self`; `system.auth.users` permits bounded administration.
+
+The internal service additionally implements `federated_login`, `users`,
+`user_update`, `grant_create`, `grant_check`, `grants` and `revoke_grant`.
+Core verifies administrative/self-service callers; only the configured identity
+provider may admit external identities or issue/check delegated grants.
+Agent grants include user, issuer, client, resource, explicit business scopes and
+expiry. Grant checks intersect current user permissions. Revocation does not end
+the browser session; disabling a user invalidates sessions and revokes all their
+agent grants. Password and MCP-key credentials retain their independent behavior.
+
+This feature introduces additive **store revision v2**. Existing v1 stores require
+Core's explicit `migrate plan auth` / `migrate apply auth --plan-id ...` workflow
+after staging a compatible Auth build. Back up the store and retained secrets
+first. The migration leaves existing password/session tables intact.
+
+Active secret uniqueness is transactional. Expired/revoked secrets can be reused
+in a new record with a new grant; old sessions remain tied to the old record.
+Revoked records cannot be restored. Editing a grant invalidates its sessions.
+Delegation is limited by the administrator's own scopes, dynamic-business selector
+and expiry. Issued grants do not inherit a revocation dependency on their creator.
+
+Configuration: `session_max_seconds` defaults to 604800; `session_idle_seconds`
+defaults to 86400. Password expiry caps both. Successful logins and authorized
+functional activity update usage; polling and denied attempts do not.
+
+Back up the consistent auth SQLite store and retained private key together. A
+missing key with an existing store is a recovery error, not a reason to regenerate
+the key. Removing/reloading the plugin retains both. Runtime validation uses
+temporary storage and secrets.
+
+```sh
+uv sync
+uv run pytest -q
+uv run ruff check src tests
+uv build --wheel
+```
+
+For the same isolated lint, tests, distribution and wheel-install checks used by
+GitHub Actions, run `python3.14 scripts/ci.py`. See [CI and publishing](docs/ci.md)
+for pinned sibling sources, local requirements and TestPyPI/PyPI setup.
+
+Core owns access policy. Its compatible OIDC integration supports
+`access.failure_mode = "closed"` for protected deployments; the default preserves
+legacy public business fallback. MCP, llms and explicitly public business APIs
+have independent policies.
+
+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).
+
+## PostgreSQL storage
+
+Version 0.2 requires SDK 0.3 and declares PostgreSQL migration SQL alongside the
+unchanged SQLite history. Provision this plugin’s stable store owner with the
+PostgreSQL provider before enabling it. The application still runs one Core;
+retain its private keys and configuration with the application home. Existing
+SQLite records are not imported automatically.

toolframe_auth-0.2.0/README.md

@@ -0,0 +1,113 @@
+# Toolframe Auth
+
+Authentication and grant decisions for access passwords, federated users and
+revocable agent delegation. This provider owns `auth`'s managed SQL store; it never opens
+database files itself. It requires SDK 0.3.0 and `toolframe.storage.sql`.
+
+## Install
+
+With a running Toolframe application and an active SQL storage provider:
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-auth==0.2.0 --enable
+```
+
+The [Entry Register template](https://github.com/toolframe/toolframe-core#readme)
+includes Auth and Dashboard Auth. The host resolves the SDK and the plugin's
+isolated environment automatically.
+
+Core supplies the private `password-lookup` key separately from configuration.
+Credential records store a keyed HMAC-SHA256 lookup plus a per-record salted
+scrypt verifier (`N=131072`, `r=8`, `p=1`, 32-byte output). At most two hashes run
+concurrently. Core also limits login attempts. Sessions use random opaque tokens;
+only SHA-256 digests of those high-entropy tokens are persisted. Metadata/list
+responses exclude lookup values, salts and verifiers.
+
+The internal `toolframe.auth` service implements login, resolve/touch, logout,
+create/list/update/revoke. Core admits administrators and passes their trusted
+principal/catalog. These methods are not directly published business APIs.
+`toolframe-dashboard-auth` supplies presentation through core's protected API.
+
+New passwords accept 8–32 characters; omitted passwords generate a random
+32-character secret. Existing longer passwords issued by 0.1.0 can still log in.
+The password-length policy preserves existing password records and sessions.
+
+## Federated users and agent grants
+
+Enable `toolframe-oidc-auth` for OIDC login. Auth remains the local identity and
+permission authority; it does not implement provider discovery or OAuth endpoints.
+Configure the trusted plugin ID with `identity_provider` (default `oidc-auth`) and
+initial admission with exact `federated_identities` entries:
+
+```toml
+[plugins.auth.config]
+identity_provider = "oidc-auth"
+federated_identities = [
+  { issuer = "https://accounts.google.com", subject = "VERIFIED_SUB", label = "Alice", scopes = ["notes.read"] },
+]
+```
+
+The trusted plugin must supply verified issuer/subject claims. No email matching
+or automatic account merging occurs. The admission entry creates a local user
+once; later permission/disablement changes use the protected user-management API.
+Changing admission configuration does not overwrite existing users. Every user
+gets `system.auth.self`; `system.auth.users` permits bounded administration.
+
+The internal service additionally implements `federated_login`, `users`,
+`user_update`, `grant_create`, `grant_check`, `grants` and `revoke_grant`.
+Core verifies administrative/self-service callers; only the configured identity
+provider may admit external identities or issue/check delegated grants.
+Agent grants include user, issuer, client, resource, explicit business scopes and
+expiry. Grant checks intersect current user permissions. Revocation does not end
+the browser session; disabling a user invalidates sessions and revokes all their
+agent grants. Password and MCP-key credentials retain their independent behavior.
+
+This feature introduces additive **store revision v2**. Existing v1 stores require
+Core's explicit `migrate plan auth` / `migrate apply auth --plan-id ...` workflow
+after staging a compatible Auth build. Back up the store and retained secrets
+first. The migration leaves existing password/session tables intact.
+
+Active secret uniqueness is transactional. Expired/revoked secrets can be reused
+in a new record with a new grant; old sessions remain tied to the old record.
+Revoked records cannot be restored. Editing a grant invalidates its sessions.
+Delegation is limited by the administrator's own scopes, dynamic-business selector
+and expiry. Issued grants do not inherit a revocation dependency on their creator.
+
+Configuration: `session_max_seconds` defaults to 604800; `session_idle_seconds`
+defaults to 86400. Password expiry caps both. Successful logins and authorized
+functional activity update usage; polling and denied attempts do not.
+
+Back up the consistent auth SQLite store and retained private key together. A
+missing key with an existing store is a recovery error, not a reason to regenerate
+the key. Removing/reloading the plugin retains both. Runtime validation uses
+temporary storage and secrets.
+
+```sh
+uv sync
+uv run pytest -q
+uv run ruff check src tests
+uv build --wheel
+```
+
+For the same isolated lint, tests, distribution and wheel-install checks used by
+GitHub Actions, run `python3.14 scripts/ci.py`. See [CI and publishing](docs/ci.md)
+for pinned sibling sources, local requirements and TestPyPI/PyPI setup.
+
+Core owns access policy. Its compatible OIDC integration supports
+`access.failure_mode = "closed"` for protected deployments; the default preserves
+legacy public business fallback. MCP, llms and explicitly public business APIs
+have independent policies.
+
+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).
+
+## PostgreSQL storage
+
+Version 0.2 requires SDK 0.3 and declares PostgreSQL migration SQL alongside the
+unchanged SQLite history. Provision this plugin’s stable store owner with the
+PostgreSQL provider before enabling it. The application still runs one Core;
+retain its private keys and configuration with the application home. Existing
+SQLite records are not imported automatically.