toolframe-streamlit-dashboard 0.4.2__tar.gz

toolframe_streamlit_dashboard-0.4.2/.github/workflows/ci.yml

@@ -0,0 +1,71 @@
+name: Python CI
+
+on:
+  pull_request:
+  push:
+  workflow_dispatch:
+  workflow_call:
+
+permissions:
+  contents: read
+
+# No shared concurrency group: this workflow is also called by publish.yml.
+jobs:
+  validate:
+    name: Validate (${{ matrix.os }}, Python 3.14.7)
+    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:
+          ref: ${{ github.sha }}
+          path: dashboard
+          persist-credentials: false
+      - name: Check out the pinned SDK
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          # github.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: dependencies/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 in isolated environments
+        shell: bash
+        run: |
+          python dashboard/scripts/validate.py \
+            --sdk-source "$GITHUB_WORKSPACE/dependencies/toolframe-sdk" \
+            --output-dir "$RUNNER_TEMP/dashboard-artifacts"
+      - name: Save validated distributions
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: dashboard-distributions-${{ matrix.os }}-${{ github.sha }}
+          path: ${{ runner.temp }}/dashboard-artifacts/dist/*
+          if-no-files-found: error
+          retention-days: 14
+      - name: Save validation evidence
+        if: ${{ !cancelled() }}
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: dashboard-validation-${{ matrix.os }}-${{ github.sha }}
+          path: |
+            ${{ runner.temp }}/dashboard-artifacts/pytest.xml
+            ${{ runner.temp }}/dashboard-artifacts/validation.json
+            ${{ runner.temp }}/dashboard-artifacts/installed.txt
+            ${{ runner.temp }}/dashboard-artifacts/dependency-wheels/*.whl
+          if-no-files-found: warn
+          retention-days: 14

toolframe_streamlit_dashboard-0.4.2/.github/workflows/publish.yml

@@ -0,0 +1,68 @@
+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: dashboard-publish-${{ github.ref }}-${{ inputs.repository }}
+  cancel-in-progress: false
+
+jobs:
+  release-ref:
+    name: Require a matching version tag
+    runs-on: ubuntu-24.04
+    timeout-minutes: 5
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ github.sha }}
+          persist-credentials: false
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: '3.14.7'
+      - name: Check tag against project.version
+        shell: bash
+        env:
+          PUBLISH_REPOSITORY: ${{ inputs.repository }}
+        run: python scripts/check_release.py "$GITHUB_REF" --repository "$PUBLISH_REPOSITORY"
+
+  validate:
+    needs: release-ref
+    uses: ./.github/workflows/ci.yml
+    secrets: inherit
+    permissions:
+      contents: read
+
+  publish:
+    name: Upload validated distributions
+    needs: validate
+    runs-on: ubuntu-24.04
+    timeout-minutes: 10
+    environment:
+      name: ${{ inputs.repository }}
+      url: ${{ inputs.repository == 'pypi' && 'https://pypi.org/p/toolframe-streamlit-dashboard' || 'https://test.pypi.org/p/toolframe-streamlit-dashboard' }}
+    permissions:
+      id-token: write
+    steps:
+      - name: Download distributions from this run
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          name: dashboard-distributions-ubuntu-24.04-${{ github.sha }}
+          path: dist
+      - name: Publish with Trusted Publishing
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          packages-dir: dist/
+          repository-url: ${{ inputs.repository == 'testpypi' && 'https://test.pypi.org/legacy/' || 'https://upload.pypi.org/legacy/' }}

toolframe_streamlit_dashboard-0.4.2/.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_streamlit_dashboard-0.4.2/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_streamlit_dashboard-0.4.2/NOTICE

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

toolframe_streamlit_dashboard-0.4.2/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.5
+Name: toolframe-streamlit-dashboard
+Version: 0.4.2
+Summary: Native Streamlit page and management provider for Toolframe
+Project-URL: Homepage, https://github.com/toolframe/toolframe-streamlit-dashboard
+Project-URL: Repository, https://github.com/toolframe/toolframe-streamlit-dashboard
+Project-URL: Documentation, https://github.com/toolframe/toolframe-streamlit-dashboard#readme
+Project-URL: Issues, https://github.com/toolframe/toolframe-streamlit-dashboard/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: streamlit==1.61.0
+Requires-Dist: toolframe-sdk<0.4,>=0.2
+Requires-Dist: uvicorn==0.42.0
+Description-Content-Type: text/markdown
+
+# Toolframe Streamlit Dashboard
+
+This provider runs one native Streamlit process for the shared UI environment.
+Business plugins contribute synchronous `render(context)` pages; navigation and
+plugin management are provided here. Pages use the SDK's synchronous
+`context.services.require(name, version=1).call(method, params)` proxy.
+The Streamlit toolbar uses viewer mode, hiding its Deploy and developer controls.
+Its native running indicator shows a circular spinner instead of cycling sports
+icons. The Running label, Stop button and connection indicators remain available;
+reduced-motion preferences disable the rotation. The narrowly scoped styling
+targets Streamlit 1.61's busy-widget test ID and should be checked on upgrades.
+Plugin lifecycle operations remain available on the Toolframe management page.
+
+## Install
+
+Install the provider into a running [Toolframe application](https://github.com/toolframe/toolframe-core#readme):
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-streamlit-dashboard==0.4.2 --enable
+```
+
+Core resolves dependencies and manages the provider's isolated Python environment.
+The Entry Register template already includes this provider.
+
+Core resolves the provider and all contributing plugin wheels (with their `ui`
+extras) together before replacing the worker. Changing any page package replaces
+the whole Dashboard. Browser sessions reconnect and session state may reset;
+business services and their persisted data remain independently owned.
+
+The provider binds an ephemeral private loopback port and reports it to core.
+Core owns the stable `/` gateway, management credentials and HTTP/WebSocket
+admission. Streamlit owns its server lifespan and script threads. A stuck script
+thread is a cleanup failure, never a successful in-process code reload.
+
+SDK 0.2 page contexts carry a host-issued reference for each browser connection.
+Pages use `context.can(scope)` to adapt controls; core checks every service call.
+Navigation filters page scopes and the plugin-management page requires
+`system.plugins.read`. Its mutation controls require the relevant management
+scopes. A password without system grants cannot reach these operations through
+the bridge. Incoming browser identity headers are not trusted.
+
+The shared header displays local control, protected access or public access with
+its reason. It remains present when the separate Dashboard Auth plugin is
+unavailable. Its one-second refresh is presentation polling and does not count
+as password activity. Use `activity=False` for other background service polling.
+
+`prepare` imports and validates page entry points without rendering them. A
+catalog epoch becomes visible only on `commit`; `abort` preserves live navigation.
+The management page submits operations to core and reads their journal; it does
+not install packages or access SQLite itself.
+
+For enable, reload, disable, stop and remove, choose **Preview operation**, review
+the affected plugins, then choose **Apply enable/reload/disable/stop/remove**.
+A preview does not change plugin state. Only stop offers the separate force-stop
+option; temporary runtime validation is offered only for validate.
+
+Pending operations update automatically. Completion or errors appear beside the
+controls, and the operation ID stays in the page URL so a browser refresh or
+Dashboard replacement can resume reading its result. Operation history can reopen
+a preview or result. Disabled plugins remain in the management list for re-enabling;
+their pages and tools disappear after the disable operation completes.
+Disabled plugins default to **enable** and do not offer reload/disable/stop.
+Enable restores the installed version; update stages a freshly resolved package.
+
+With core 0.5.0+, **Operations** queries the complete core journal with plugin,
+action and result filters. It defaults to 10 rows, with 25/50 options and
+Newer/Older navigation. Each row has a permanent operation number, browser-local
+creation time, action, target and result. Preview rows include the intended action
+(for example, `plan enable`). Viewing a result uses its durable UUID.
+The refresh button aligns with the bottom of the page-size selector, at the right
+edge. Newer and Older sit at opposite edges of one pagination row.
+
+Page navigation retains a sequence boundary so new arrivals do not shift older
+pages. **Refresh history**, changing filters or submitting an operation starts
+at the latest first page. The count indicates newer arrivals; statuses remain
+current. Read-only operators can filter, page and inspect results, while apply
+and cancel retain their existing scope checks.
+
+The **Plugin dependencies & impact** accordion sits directly below the status
+table and starts collapsed. It reads core's `dependency_graph` diagnostics
+(core 0.4.0+) under the existing `system.plugins.read` permission. Nodes show
+Cordis lifecycle state and current health; arrows run from consumer to supplier.
+Solid lines are required services, dashed lines optional services, and dotted
+lines presentation providers. Missing suppliers and inactive plugins stay visible.
+
+Select a plugin and **reload** or **disable** to highlight the lifecycle cohort,
+optional consumers, and page/tool/document entries that may reconnect or refresh.
+The cohort comes from core's actual planner. Presentation refreshes do not imply
+that the provider or every page's business process restarts. Use the full-screen
+control to enlarge the graph; the relationship table includes exact service names
+and versions.
+
+This view never installs, validates, submits an operation, or changes composition.
+It describes selected versions; inactive declarations are labeled `last_candidate`.
+New candidates or pending configuration changes can produce a different plan, so
+the existing **Preview operation** / **Apply** workflow remains authoritative.
+Refreshing status refreshes the graph too. An older core shows an upgrade hint.
+
+The graph is generated from core state, including newly installed plugins and
+their declared dependencies. `plugin new` only creates source and does not add a
+node; use `plugin add` to install it. Refresh status after changes made elsewhere.
+This is a refreshed snapshot, not a continuously pushed graph animation.
+
+Development: `uv sync --group dev`, `uv run pytest -q`, `uv build --no-sources`.
+Each lifecycle integration test uses a fresh subprocess because Streamlit's
+runtime singleton belongs to the process, not a reloadable plugin object.
+
+For fresh-environment CI checks, run
+`uv run --isolated --no-project --python 3.14.7 python -I scripts/validate.py`.
+See [CI and package publishing](docs/ci.md) for GitHub Actions, validation artifacts,
+pinned SDK prerequisites and manual TestPyPI/PyPI Trusted Publishing 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_streamlit_dashboard-0.4.2/README.md

@@ -0,0 +1,117 @@
+# Toolframe Streamlit Dashboard
+
+This provider runs one native Streamlit process for the shared UI environment.
+Business plugins contribute synchronous `render(context)` pages; navigation and
+plugin management are provided here. Pages use the SDK's synchronous
+`context.services.require(name, version=1).call(method, params)` proxy.
+The Streamlit toolbar uses viewer mode, hiding its Deploy and developer controls.
+Its native running indicator shows a circular spinner instead of cycling sports
+icons. The Running label, Stop button and connection indicators remain available;
+reduced-motion preferences disable the rotation. The narrowly scoped styling
+targets Streamlit 1.61's busy-widget test ID and should be checked on upgrades.
+Plugin lifecycle operations remain available on the Toolframe management page.
+
+## Install
+
+Install the provider into a running [Toolframe application](https://github.com/toolframe/toolframe-core#readme):
+
+```sh
+toolframe --home APP plugin add pypi:toolframe-streamlit-dashboard==0.4.2 --enable
+```
+
+Core resolves dependencies and manages the provider's isolated Python environment.
+The Entry Register template already includes this provider.
+
+Core resolves the provider and all contributing plugin wheels (with their `ui`
+extras) together before replacing the worker. Changing any page package replaces
+the whole Dashboard. Browser sessions reconnect and session state may reset;
+business services and their persisted data remain independently owned.
+
+The provider binds an ephemeral private loopback port and reports it to core.
+Core owns the stable `/` gateway, management credentials and HTTP/WebSocket
+admission. Streamlit owns its server lifespan and script threads. A stuck script
+thread is a cleanup failure, never a successful in-process code reload.
+
+SDK 0.2 page contexts carry a host-issued reference for each browser connection.
+Pages use `context.can(scope)` to adapt controls; core checks every service call.
+Navigation filters page scopes and the plugin-management page requires
+`system.plugins.read`. Its mutation controls require the relevant management
+scopes. A password without system grants cannot reach these operations through
+the bridge. Incoming browser identity headers are not trusted.
+
+The shared header displays local control, protected access or public access with
+its reason. It remains present when the separate Dashboard Auth plugin is
+unavailable. Its one-second refresh is presentation polling and does not count
+as password activity. Use `activity=False` for other background service polling.
+
+`prepare` imports and validates page entry points without rendering them. A
+catalog epoch becomes visible only on `commit`; `abort` preserves live navigation.
+The management page submits operations to core and reads their journal; it does
+not install packages or access SQLite itself.
+
+For enable, reload, disable, stop and remove, choose **Preview operation**, review
+the affected plugins, then choose **Apply enable/reload/disable/stop/remove**.
+A preview does not change plugin state. Only stop offers the separate force-stop
+option; temporary runtime validation is offered only for validate.
+
+Pending operations update automatically. Completion or errors appear beside the
+controls, and the operation ID stays in the page URL so a browser refresh or
+Dashboard replacement can resume reading its result. Operation history can reopen
+a preview or result. Disabled plugins remain in the management list for re-enabling;
+their pages and tools disappear after the disable operation completes.
+Disabled plugins default to **enable** and do not offer reload/disable/stop.
+Enable restores the installed version; update stages a freshly resolved package.
+
+With core 0.5.0+, **Operations** queries the complete core journal with plugin,
+action and result filters. It defaults to 10 rows, with 25/50 options and
+Newer/Older navigation. Each row has a permanent operation number, browser-local
+creation time, action, target and result. Preview rows include the intended action
+(for example, `plan enable`). Viewing a result uses its durable UUID.
+The refresh button aligns with the bottom of the page-size selector, at the right
+edge. Newer and Older sit at opposite edges of one pagination row.
+
+Page navigation retains a sequence boundary so new arrivals do not shift older
+pages. **Refresh history**, changing filters or submitting an operation starts
+at the latest first page. The count indicates newer arrivals; statuses remain
+current. Read-only operators can filter, page and inspect results, while apply
+and cancel retain their existing scope checks.
+
+The **Plugin dependencies & impact** accordion sits directly below the status
+table and starts collapsed. It reads core's `dependency_graph` diagnostics
+(core 0.4.0+) under the existing `system.plugins.read` permission. Nodes show
+Cordis lifecycle state and current health; arrows run from consumer to supplier.
+Solid lines are required services, dashed lines optional services, and dotted
+lines presentation providers. Missing suppliers and inactive plugins stay visible.
+
+Select a plugin and **reload** or **disable** to highlight the lifecycle cohort,
+optional consumers, and page/tool/document entries that may reconnect or refresh.
+The cohort comes from core's actual planner. Presentation refreshes do not imply
+that the provider or every page's business process restarts. Use the full-screen
+control to enlarge the graph; the relationship table includes exact service names
+and versions.
+
+This view never installs, validates, submits an operation, or changes composition.
+It describes selected versions; inactive declarations are labeled `last_candidate`.
+New candidates or pending configuration changes can produce a different plan, so
+the existing **Preview operation** / **Apply** workflow remains authoritative.
+Refreshing status refreshes the graph too. An older core shows an upgrade hint.
+
+The graph is generated from core state, including newly installed plugins and
+their declared dependencies. `plugin new` only creates source and does not add a
+node; use `plugin add` to install it. Refresh status after changes made elsewhere.
+This is a refreshed snapshot, not a continuously pushed graph animation.
+
+Development: `uv sync --group dev`, `uv run pytest -q`, `uv build --no-sources`.
+Each lifecycle integration test uses a fresh subprocess because Streamlit's
+runtime singleton belongs to the process, not a reloadable plugin object.
+
+For fresh-environment CI checks, run
+`uv run --isolated --no-project --python 3.14.7 python -I scripts/validate.py`.
+See [CI and package publishing](docs/ci.md) for GitHub Actions, validation artifacts,
+pinned SDK prerequisites and manual TestPyPI/PyPI Trusted Publishing 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).