toolframe-dashboard-auth 0.1.3__tar.gz

toolframe_dashboard_auth-0.1.3/.github/workflows/ci.yml

@@ -0,0 +1,18 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ci-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  validate:
+    uses: ./.github/workflows/validate.yml
+    secrets: inherit

toolframe_dashboard_auth-0.1.3/.github/workflows/publish.yml

@@ -0,0 +1,64 @@
+name: Publish package
+
+on:
+  workflow_dispatch:
+    inputs:
+      environment:
+        description: Package index (run this workflow on a matching version tag)
+        type: choice
+        required: true
+        default: testpypi
+        options:
+          - testpypi
+          - pypi
+
+permissions:
+  contents: read
+
+concurrency:
+  group: publish-${{ github.ref }}
+  cancel-in-progress: false
+
+jobs:
+  check-tag:
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: '3.14.7'
+      - name: Require a tag matching project.version
+        run: python scripts/check_release_tag.py
+
+  validate:
+    needs: check-tag
+    uses: ./.github/workflows/validate.yml
+    secrets: inherit
+  publish:
+    needs: validate
+    runs-on: ubuntu-24.04
+    timeout-minutes: 10
+    environment:
+      name: ${{ inputs.environment }}
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - name: Download distributions validated in this run
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: dashboard-auth-dist-${{ github.sha }}
+          path: dist
+
+      - name: Publish to TestPyPI
+        if: inputs.environment == 'testpypi'
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+      - name: Publish to PyPI
+        if: inputs.environment == 'pypi'
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2

toolframe_dashboard_auth-0.1.3/.github/workflows/validate.yml

@@ -0,0 +1,62 @@
+name: Validate package
+
+on:
+  workflow_call:
+
+permissions:
+  contents: read
+
+# Concurrency belongs to the caller, so validation cannot cancel a publish run.
+jobs:
+  validate:
+    name: Python 3.14.7 / ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 20
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-24.04, macos-15]
+    steps:
+      - name: Check out this revision
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          path: toolframe-dashboard-auth
+          persist-credentials: false
+
+      - name: Check out the pinned SDK
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          # repository_owner is the base repository owner for fork PRs.
+          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: Validate from fresh environments
+        id: validate
+        working-directory: toolframe-dashboard-auth
+        shell: bash
+        run: bash scripts/ci.sh
+
+      - name: Retain validated distributions
+        if: matrix.os == 'ubuntu-24.04'
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: dashboard-auth-dist-${{ github.sha }}
+          path: |
+            ${{ steps.validate.outputs.dist-dir }}/*.whl
+            ${{ steps.validate.outputs.dist-dir }}/*.tar.gz
+          if-no-files-found: error
+          retention-days: 7

toolframe_dashboard_auth-0.1.3/.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_dashboard_auth-0.1.3/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_dashboard_auth-0.1.3/NOTICE

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

toolframe_dashboard_auth-0.1.3/PKG-INFO

@@ -0,0 +1,106 @@
+Metadata-Version: 2.5
+Name: toolframe-dashboard-auth
+Version: 0.1.3
+Summary: Password login and access management pages for Toolframe
+Project-URL: Homepage, https://github.com/toolframe/toolframe-dashboard-auth
+Project-URL: Repository, https://github.com/toolframe/toolframe-dashboard-auth
+Project-URL: Documentation, https://github.com/toolframe/toolframe-dashboard-auth#readme
+Project-URL: Issues, https://github.com/toolframe/toolframe-dashboard-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.4,>=0.2
+Provides-Extra: ui
+Requires-Dist: streamlit==1.61.0; extra == 'ui'
+Description-Content-Type: text/markdown
+
+# Toolframe Dashboard Auth
+
+The `dashboard-auth` provider supplies password and configured OIDC login choices,
+plus Streamlit access-management pages. It depends on the `toolframe.auth` service
+and SDK 0.2–0.3. Core handles cookies, admission and protected auth API calls; this
+plugin holds no credential database or verifier key.
+
+Install the package in a running application with compatible Auth and Dashboard
+providers, then open **Access passwords** as a local operator:
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-dashboard-auth==0.1.3 --enable
+```
+
+With Core 0.6.1, **Access by entrance** reports Dashboard/service access, independent
+MCP policy, declared public HTTP methods and the current local/operator context.
+The policy form lets settings administrators choose closed or public behavior
+when Dashboard authentication fails. Closed is the default for new applications;
+existing application choices are preserved. Older Core versions keep the existing
+policy controls but do not offer the unsupported failure-policy editor. Public
+HTTP declarations and llms documents remain public, and method scopes do not
+provide per-person row isolation.
+While this page is available, credential-list errors leave its policy controls
+usable by local operators. If Dashboard Auth itself is unavailable, use Core's
+local management API for recovery.
+
+With compatible Core/Auth and `toolframe-oidc-auth` installed, the login page
+loads provider buttons from Core's safe provider catalogue. **Connected agents**
+requires `system.auth.self` and lets a federated user revoke their own connections
+without logging out. **User access** requires `system.auth.users` and manages
+permissions/disablement for identities already admitted by application
+configuration. Disabling a user revokes their browser sessions and agent grants.
+The pages call Core's protected facade; no upstream credentials enter Streamlit.
+
+The optional **MCP keys** page requires `system.auth.mcp_keys` and manages named
+256-bit bearer keys through core's separate MCP auth API. Install/enable
+`toolframe-mcp-auth` to generate keys, select business scopes and expiry, copy each
+secret once and revoke it later. `system.settings.manage` also permits changing
+the independent MCP public/protected policy. The page remains available for policy
+recovery when the MCP auth provider is absent. See the MCP authentication guide
+in the core repository for configuration details.
+
+The management page fills in an editable **Unnamed password** label, adding a
+number for names already in use. The password field accepts 8–32 characters and
+shows a stable random suggestion as its placeholder. Leave the field blank to use
+that exact suggestion; after creation, copy the one-time displayed password.
+Failed submissions preserve the draft; successful creation starts a fresh one.
+
+**Set expiry** immediately reveals a duration and unit side by side, with minutes,
+hours, days, weeks or calendar months and a calculated local expiry preview.
+Preview and record timestamps use the browser's timezone (its UTC offset is a
+fallback, then UTC if neither is available). Durations start when saved; months
+follow that local calendar and clamp to the destination month's last day. Other
+units measure elapsed time, including across daylight-saving changes. No
+date/time entry is needed.
+Turning expiry off hides the controls and saves no expiry. When editing, leave the
+duration blank to preserve the exact existing expiry, or enter a duration to
+replace it. Saving other grant fields never silently extends the expiry.
+
+The page selects scopes, edits grants, revokes records and shows creation,
+last-login and last-use timestamps. Its page
+requires `system.auth.passwords`; access-policy controls additionally require
+`system.settings.manage`. Core/auth enforce the same rules beyond the UI.
+
+Core serves the login page at `/_toolframe/auth/login`. The existing Dashboard
+provider owns the common local/public/protected header so it remains available
+when this integration fails or is disabled. Streamlit is supplied by the shared
+Dashboard execution environment, not the business/auth worker.
+
+```sh
+uv sync
+uv run pytest -q
+uv run ruff check src tests
+uv build --wheel
+```
+
+For the same isolated validation used by GitHub Actions, run `bash scripts/ci.sh`
+with Python 3.14.7, uv 0.12.8 and a sibling `toolframe-sdk` Git checkout available.
+This runs the presentation tests against a newly built wheel, checks both
+distributions, and verifies a separate installation with only runtime dependencies.
+See [CI and publishing](docs/ci.md) for the pinned SDK revision, workflow triggers,
+release prerequisites and local validation limits.
+
+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_dashboard_auth-0.1.3/README.md

@@ -0,0 +1,88 @@
+# Toolframe Dashboard Auth
+
+The `dashboard-auth` provider supplies password and configured OIDC login choices,
+plus Streamlit access-management pages. It depends on the `toolframe.auth` service
+and SDK 0.2–0.3. Core handles cookies, admission and protected auth API calls; this
+plugin holds no credential database or verifier key.
+
+Install the package in a running application with compatible Auth and Dashboard
+providers, then open **Access passwords** as a local operator:
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-dashboard-auth==0.1.3 --enable
+```
+
+With Core 0.6.1, **Access by entrance** reports Dashboard/service access, independent
+MCP policy, declared public HTTP methods and the current local/operator context.
+The policy form lets settings administrators choose closed or public behavior
+when Dashboard authentication fails. Closed is the default for new applications;
+existing application choices are preserved. Older Core versions keep the existing
+policy controls but do not offer the unsupported failure-policy editor. Public
+HTTP declarations and llms documents remain public, and method scopes do not
+provide per-person row isolation.
+While this page is available, credential-list errors leave its policy controls
+usable by local operators. If Dashboard Auth itself is unavailable, use Core's
+local management API for recovery.
+
+With compatible Core/Auth and `toolframe-oidc-auth` installed, the login page
+loads provider buttons from Core's safe provider catalogue. **Connected agents**
+requires `system.auth.self` and lets a federated user revoke their own connections
+without logging out. **User access** requires `system.auth.users` and manages
+permissions/disablement for identities already admitted by application
+configuration. Disabling a user revokes their browser sessions and agent grants.
+The pages call Core's protected facade; no upstream credentials enter Streamlit.
+
+The optional **MCP keys** page requires `system.auth.mcp_keys` and manages named
+256-bit bearer keys through core's separate MCP auth API. Install/enable
+`toolframe-mcp-auth` to generate keys, select business scopes and expiry, copy each
+secret once and revoke it later. `system.settings.manage` also permits changing
+the independent MCP public/protected policy. The page remains available for policy
+recovery when the MCP auth provider is absent. See the MCP authentication guide
+in the core repository for configuration details.
+
+The management page fills in an editable **Unnamed password** label, adding a
+number for names already in use. The password field accepts 8–32 characters and
+shows a stable random suggestion as its placeholder. Leave the field blank to use
+that exact suggestion; after creation, copy the one-time displayed password.
+Failed submissions preserve the draft; successful creation starts a fresh one.
+
+**Set expiry** immediately reveals a duration and unit side by side, with minutes,
+hours, days, weeks or calendar months and a calculated local expiry preview.
+Preview and record timestamps use the browser's timezone (its UTC offset is a
+fallback, then UTC if neither is available). Durations start when saved; months
+follow that local calendar and clamp to the destination month's last day. Other
+units measure elapsed time, including across daylight-saving changes. No
+date/time entry is needed.
+Turning expiry off hides the controls and saves no expiry. When editing, leave the
+duration blank to preserve the exact existing expiry, or enter a duration to
+replace it. Saving other grant fields never silently extends the expiry.
+
+The page selects scopes, edits grants, revokes records and shows creation,
+last-login and last-use timestamps. Its page
+requires `system.auth.passwords`; access-policy controls additionally require
+`system.settings.manage`. Core/auth enforce the same rules beyond the UI.
+
+Core serves the login page at `/_toolframe/auth/login`. The existing Dashboard
+provider owns the common local/public/protected header so it remains available
+when this integration fails or is disabled. Streamlit is supplied by the shared
+Dashboard execution environment, not the business/auth worker.
+
+```sh
+uv sync
+uv run pytest -q
+uv run ruff check src tests
+uv build --wheel
+```
+
+For the same isolated validation used by GitHub Actions, run `bash scripts/ci.sh`
+with Python 3.14.7, uv 0.12.8 and a sibling `toolframe-sdk` Git checkout available.
+This runs the presentation tests against a newly built wheel, checks both
+distributions, and verifies a separate installation with only runtime dependencies.
+See [CI and publishing](docs/ci.md) for the pinned SDK revision, workflow triggers,
+release prerequisites and local validation limits.
+
+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_dashboard_auth-0.1.3/docs/ci.md

@@ -0,0 +1,103 @@
+# CI and publishing
+
+## Run the CI checks locally
+
+Use Git, Bash, Python **3.14.7** and uv **0.12.8**, with network access to PyPI.
+The SDK checkout must contain commit
+`ef91b609137a5fe7bae8e0c893e74b096ff06ffe` (SDK 0.3.0).
+
+```sh
+uv python install 3.14.7
+bash scripts/ci.sh
+```
+
+By default the script reads `../toolframe-sdk`. To use a different checkout:
+
+```sh
+TOOLFRAME_SDK_REPOSITORY=/absolute/path/to/toolframe-sdk bash scripts/ci.sh
+```
+
+Each invocation creates and prints a new temporary workspace. It copies this
+working tree and archives the exact SDK commit there; it does not build from
+the SDK's current working tree. It leaves both original repositories, their
+lockfiles, existing `.venv` directories and existing `dist` directories alone.
+The temporary workspace is retained on success or failure for inspection.
+
+The script performs these checks, stopping on any failure:
+
+1. Export the existing `uv.lock` with `uv export --locked`, retaining the locked
+   development dependency versions, including Streamlit 1.61.0. Exclude the two
+   editable project entries because fresh wheels supply them instead.
+2. Build the SDK wheel and this project's sdist and wheel with `uv build
+   --no-sources`. The project wheel is built from its sdist by uv's default build
+   sequence. All build directories and the uv cache start empty.
+3. Install the new SDK and plugin wheels with the `ui` extra, locked development
+   dependencies and Twine 7.0.0 into a new test environment, compiling dependency
+   bytecode before the existing Streamlit AppTest deadlines start. Run `uv pip check`,
+   `ruff check src tests scripts`, all existing presentation tests via
+   `python -I -m pytest -q -p no:cacheprovider --durations=5 <copied-source>/tests`
+   from an empty working directory, and
+   `twine check --strict` on both distributions.
+4. Install both wheels into another empty environment with their real runtime
+   dependencies. Run `uv pip check` and the wheel smoke check from outside the
+   source tree using Python's isolated mode. Check installed module paths,
+   versions, plugin discovery, scoped management-page metadata, bundled password
+   login HTML, and the unchanged Apache-2.0 `LICENSE` and `NOTICE` files.
+
+The runtime smoke environment contains no Streamlit or development tools; the
+presentation tests exercise Streamlit in the test environment. Neither install
+uses `--no-deps`. Only this project's two distributions are upload artifacts;
+the SDK wheel is a local validation dependency and is never uploaded by this repo.
+Twine is pinned to 7.0.0 for its
+[Metadata 2.5 compatibility fix](https://twine.readthedocs.io/en/stable/changelog.html#twine-7-0-0-2026-07-27).
+
+Workflow and shell syntax checks can also be run from the repository root:
+
+```sh
+actionlint .github/workflows/*.yml
+bash -n scripts/ci.sh
+python3.14 scripts/check_release_tag.py refs/tags/v0.1.3
+```
+
+## GitHub Actions
+
+`ci.yml` handles pull requests, pushes (including tags), and manual runs. It calls
+`validate.yml`, which runs the same local script on `ubuntu-24.04` and `macos-15`,
+with Python 3.14.7 and uv 0.12.8. These labels appear in the
+[official runner list](https://docs.github.com/en/actions/reference/runners/github-hosted-runners).
+Successful Linux validation retains the wheel and sdist for seven days as
+`dashboard-auth-dist-<commit SHA>`. Both matrix jobs must pass for validation to
+succeed. Jobs have bounded timeouts and default to `contents: read`.
+
+All external actions use full commit pins with version comments. Checkouts do not
+persist credentials. CI concurrency cancels superseded runs; the reusable
+workflow has no concurrency group and cannot cancel its caller. There is no
+`pull_request_target` execution or automatic publishing from PRs or tag pushes.
+
+Before remote runs, push this repository and the pinned SDK commit to the chosen
+GitHub owner. The dependency repository must be named `toolframe-sdk`; its owner
+defaults to `github.repository_owner`. Set the repository Actions variable
+`TOOLFRAME_REPOSITORY_OWNER` if the SDK lives under another trusted owner. Fork
+PRs still fetch from this configured/base owner, never the PR author's owner.
+Public siblings need no additional token. For private SDK access, configure the
+read-only `TOOLFRAME_READ_TOKEN` described in [releasing](releasing.md). The
+current repository's `GITHUB_TOKEN` cannot read a different private repository.
+
+## Publication
+
+See [releasing](releasing.md) for dependency order, private repository access,
+Trusted Publisher bindings, version tags and consumer installation checks.
+
+## Validation limits
+
+Local validation runs on the host executing the script. Passing it on an Apple
+Silicon Mac does not claim an executed GitHub Linux/macOS matrix, Windows or
+physical Intel support, full Core/auth integration, browser automation, or an
+actual OIDC upload. Presentation behavior is covered by the existing Streamlit
+AppTest suite; authentication enforcement remains owned by Core/auth. Preparing
+these files does not push commits, create tags remotely, register publishers or
+deploy a release.
+
+The first Streamlit AppTest render has a bounded 60-second timeout to allow
+cold native-library imports. Later interactions retain their shorter timeout;
+assertions remain active and the suite does not retry failures.