salt-tui 0.1.0__tar.gz

salt_tui-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,41 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test-package:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install development dependencies
+        run: python -m pip install -e ".[dev]"
+      - name: Test
+        run: python -m pytest -q
+      - name: Build wheel and source distribution
+        run: python -m build
+      - name: Validate metadata and contents
+        run: |
+          python -m twine check dist/*
+          python scripts/check_dist.py
+      - name: Install wheel in a clean environment
+        run: |
+          python -m venv "$RUNNER_TEMP/salt-tui-install"
+          "$RUNNER_TEMP/salt-tui-install/bin/python" -m pip install dist/*.whl
+          cd "$RUNNER_TEMP"
+          "$RUNNER_TEMP/salt-tui-install/bin/salt-tui" --version
+          "$RUNNER_TEMP/salt-tui-install/bin/salt-tui" --help
+          "$RUNNER_TEMP/salt-tui-install/bin/python" -m salt_tui --version
+      - name: pipx smoke test
+        run: |
+          python -m pip install pipx
+          export PIPX_HOME="$RUNNER_TEMP/pipx-home"
+          export PIPX_BIN_DIR="$RUNNER_TEMP/pipx-bin"
+          python -m pipx install dist/*.whl
+          "$PIPX_BIN_DIR/salt-tui" --version
+          python -m pipx uninstall salt-tui

salt_tui-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,49 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Check tag and PyPI version
+        run: python scripts/check_release.py
+      - name: Install development dependencies
+        run: python -m pip install -e ".[dev]"
+      - name: Test
+        run: python -m pytest -q
+      - name: Build
+        run: python -m build
+      - name: Validate distributions
+        run: |
+          python -m twine check dist/*
+          python scripts/check_dist.py
+      - uses: actions/upload-artifact@v4
+        with:
+          name: python-distributions
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: python-distributions
+          path: dist/
+      - name: Publish to PyPI using trusted publishing
+        uses: pypa/gh-action-pypi-publish@release/v1

salt_tui-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+.venv/
+dist/
+build/
+*.egg-info/
+__pycache__/
+.pytest_cache/
+*.pyc
+*.db
+*.sqlite
+*.sqlite3
+*.log
+.env
+.env.*

salt_tui-0.1.0/CHANGELOG.md

@@ -0,0 +1,6 @@
+# Changelog
+
+## 0.1.0
+
+- Initial packaged Salt TUI with CLI execution, history, events, state views, and diagnostics.
+- Added wheel, source distribution, pipx validation, and trusted publishing workflows.

salt_tui-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for 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.

salt_tui-0.1.0/PKG-INFO

@@ -0,0 +1,99 @@
+Metadata-Version: 2.5
+Name: salt-tui
+Version: 0.1.0
+Summary: A keyboard-driven SaltStack operations console
+Project-URL: Homepage, https://github.com/pratik-anurag/salt-tui
+Project-URL: Repository, https://github.com/pratik-anurag/salt-tui
+Project-URL: Issues, https://github.com/pratik-anurag/salt-tui/issues
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: System Administrators
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: System :: Systems Administration
+Requires-Python: >=3.11
+Requires-Dist: pygments>=2.16
+Requires-Dist: pyyaml>=6
+Requires-Dist: rich>=13.7
+Requires-Dist: textual<8,>=1.0
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: twine>=6; extra == 'dev'
+Provides-Extra: test
+Requires-Dist: pytest-asyncio>=0.23; extra == 'test'
+Requires-Dist: pytest>=8; extra == 'test'
+Description-Content-Type: text/markdown
+
+# Salt TUI
+
+A Textual frontend for Salt CLI operations, structured state returns, local history, and SLS exploration. Salt remains the source of truth for state rendering and execution.
+
+## Install
+
+Python 3.11 or newer and `pipx` are required. The package uses an isolated pipx environment and does not install into Salt's Python runtime. Once a release is published on PyPI:
+
+```sh
+pipx install salt-tui
+salt-tui
+```
+
+Upgrade with `pipx upgrade salt-tui` and uninstall with `pipx uninstall salt-tui`. Uninstalling leaves your configuration and history in your user directories. Check an installation without opening the TUI using `salt-tui --version` or `salt-tui --help`. Prereleases require an explicit request, such as `pipx install --pip-args='--pre' salt-tui`.
+
+For a development checkout:
+
+```sh
+git clone https://github.com/pratik-anurag/salt-tui.git
+cd salt-tui
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install -e '.[dev]'
+python -m pytest
+salt-tui
+python -m salt_tui --version
+```
+
+To test a local release artifact, run `python -m build` and then `pipx install ./dist/salt_tui-0.1.0-py3-none-any.whl`. Use the wheel name for the version you built. Salt CLI executables are discovered at runtime on `PATH`; Salt is not a Python dependency of this package.
+
+Without Salt binaries, the UI opens with capability information and retains local history and SLS browsing. With `salt`, master commands are available; `salt-call` enables local minion commands. The app also detects `salt-run` and `salt-key` for their supported views. Live Salt behavior depends on the installed Salt CLI and access to a Salt environment. This package has been exercised on macOS; Linux is used in CI.
+
+## Use
+
+`c` opens the generic command runner. Enter a normal Salt command, review the exact command preview, then run it. For state changes, a confirmation displays target, action, environment, and test mode. `Test first` adds `test=True` to state functions. `Run Live` publishes a state job asynchronously and opens minion progress when the Salt event bus is available. `e` opens the event stream and `v` returns to the selected live run. `r` opens state results; `f` and `Shift+F` visit failed states. `h` opens persisted history; highlight one run and press `x`, then another and `x` to compare state results. `s` browses configured local file roots and invokes Salt's `state.show_sls` or `state.show_low_sls` for compiled views. `g` opens the compiled dependency graph, where `u` and `n` follow connected states and `o` opens source. `j` shows Salt runner job data.
+
+`Ctrl+M` opens a paged state × minion matrix for the selected run, with fleet drift filters and per-state details.
+
+Direct entry points open the corresponding screen:
+
+```sh
+salt-tui sls nginx
+salt-tui run state.highstate
+salt-tui history
+salt-tui failures
+salt-tui events
+salt-tui intelligence
+salt-tui performance
+salt-tui runner
+salt-tui orchestration
+salt-tui targets
+salt-tui matrix
+salt-tui diagnostics --output ./salt-tui-diagnostics.zip
+```
+
+Configuration is read from `~/.config/salt-tui/config.toml` (or `$XDG_CONFIG_HOME/salt-tui/config.toml`). Copy `sample-config.toml` and adapt command paths and file roots. History defaults to `$XDG_DATA_HOME/salt-tui/history.db` or `~/.local/share/salt-tui/history.db`. It does not write into Salt's cache.
+
+See [architecture](docs/architecture.md), [Stage 2 progress](docs/stage2.md), [plugin API](docs/plugins.md), [keyboard shortcuts](docs/keys.md), and the [release checklist](docs/releasing.md).
+
+![Dashboard preview](docs/dashboard.svg)
+
+![Event stream preview](docs/events.svg)
+
+## Scope and limitations
+
+Stage 2 adds event streaming, live JID-correlated master state runs, compiled graph navigation, source links, combined history search, recurring failure patterns, slow-state analysis, runner execution, orchestration, and structured job inspection. Per-state progress requires Salt's `state_events` support. The TUI tries the Salt Python event API first, then `salt-run state.event`. If neither is available, the event screen reports that the bus is unavailable and `Run Live` is disabled. Rich minion metadata, broad target match counts, and full command autocomplete remain future work. The command runner supports arbitrary Salt CLI arguments; Salt-specific option ordering should be entered as a normal CLI line.

salt_tui-0.1.0/README.md

@@ -0,0 +1,66 @@
+# Salt TUI
+
+A Textual frontend for Salt CLI operations, structured state returns, local history, and SLS exploration. Salt remains the source of truth for state rendering and execution.
+
+## Install
+
+Python 3.11 or newer and `pipx` are required. The package uses an isolated pipx environment and does not install into Salt's Python runtime. Once a release is published on PyPI:
+
+```sh
+pipx install salt-tui
+salt-tui
+```
+
+Upgrade with `pipx upgrade salt-tui` and uninstall with `pipx uninstall salt-tui`. Uninstalling leaves your configuration and history in your user directories. Check an installation without opening the TUI using `salt-tui --version` or `salt-tui --help`. Prereleases require an explicit request, such as `pipx install --pip-args='--pre' salt-tui`.
+
+For a development checkout:
+
+```sh
+git clone https://github.com/pratik-anurag/salt-tui.git
+cd salt-tui
+python -m venv .venv
+. .venv/bin/activate
+python -m pip install -e '.[dev]'
+python -m pytest
+salt-tui
+python -m salt_tui --version
+```
+
+To test a local release artifact, run `python -m build` and then `pipx install ./dist/salt_tui-0.1.0-py3-none-any.whl`. Use the wheel name for the version you built. Salt CLI executables are discovered at runtime on `PATH`; Salt is not a Python dependency of this package.
+
+Without Salt binaries, the UI opens with capability information and retains local history and SLS browsing. With `salt`, master commands are available; `salt-call` enables local minion commands. The app also detects `salt-run` and `salt-key` for their supported views. Live Salt behavior depends on the installed Salt CLI and access to a Salt environment. This package has been exercised on macOS; Linux is used in CI.
+
+## Use
+
+`c` opens the generic command runner. Enter a normal Salt command, review the exact command preview, then run it. For state changes, a confirmation displays target, action, environment, and test mode. `Test first` adds `test=True` to state functions. `Run Live` publishes a state job asynchronously and opens minion progress when the Salt event bus is available. `e` opens the event stream and `v` returns to the selected live run. `r` opens state results; `f` and `Shift+F` visit failed states. `h` opens persisted history; highlight one run and press `x`, then another and `x` to compare state results. `s` browses configured local file roots and invokes Salt's `state.show_sls` or `state.show_low_sls` for compiled views. `g` opens the compiled dependency graph, where `u` and `n` follow connected states and `o` opens source. `j` shows Salt runner job data.
+
+`Ctrl+M` opens a paged state × minion matrix for the selected run, with fleet drift filters and per-state details.
+
+Direct entry points open the corresponding screen:
+
+```sh
+salt-tui sls nginx
+salt-tui run state.highstate
+salt-tui history
+salt-tui failures
+salt-tui events
+salt-tui intelligence
+salt-tui performance
+salt-tui runner
+salt-tui orchestration
+salt-tui targets
+salt-tui matrix
+salt-tui diagnostics --output ./salt-tui-diagnostics.zip
+```
+
+Configuration is read from `~/.config/salt-tui/config.toml` (or `$XDG_CONFIG_HOME/salt-tui/config.toml`). Copy `sample-config.toml` and adapt command paths and file roots. History defaults to `$XDG_DATA_HOME/salt-tui/history.db` or `~/.local/share/salt-tui/history.db`. It does not write into Salt's cache.
+
+See [architecture](docs/architecture.md), [Stage 2 progress](docs/stage2.md), [plugin API](docs/plugins.md), [keyboard shortcuts](docs/keys.md), and the [release checklist](docs/releasing.md).
+
+![Dashboard preview](docs/dashboard.svg)
+
+![Event stream preview](docs/events.svg)
+
+## Scope and limitations
+
+Stage 2 adds event streaming, live JID-correlated master state runs, compiled graph navigation, source links, combined history search, recurring failure patterns, slow-state analysis, runner execution, orchestration, and structured job inspection. Per-state progress requires Salt's `state_events` support. The TUI tries the Salt Python event API first, then `salt-run state.event`. If neither is available, the event screen reports that the bus is unavailable and `Run Live` is disabled. Rich minion metadata, broad target match counts, and full command autocomplete remain future work. The command runner supports arbitrary Salt CLI arguments; Salt-specific option ordering should be entered as a normal CLI line.

salt_tui-0.1.0/benchmarks/scale.py

@@ -0,0 +1,96 @@
+"""Synthetic scale benchmark; no Salt master required.
+
+Run after `pip install -e .`:
+    python benchmarks/scale.py --minions 10000 --states 20000 --history 1000000
+"""
+from __future__ import annotations
+
+import argparse
+import asyncio
+from pathlib import Path
+import sqlite3
+import tempfile
+from time import perf_counter
+
+from salt_tui.models import SaltEvent
+from salt_tui.salt.events import EventMonitor
+from salt_tui.sls.graph import StateGraph
+from salt_tui.storage.database import Database
+
+
+async def main() -> None:
+    parser = argparse.ArgumentParser()
+    parser.add_argument("--minions", type=int, default=10000)
+    parser.add_argument("--states", type=int, default=20000)
+    parser.add_argument("--history", type=int, default=1000000)
+    parser.add_argument("--events", type=int, default=100000)
+    args = parser.parse_args()
+    with tempfile.TemporaryDirectory() as temporary:
+        path = Path(temporary) / "scale.db"
+        db = Database(path)
+        await db.migrate()
+        chunks = []
+        for index in range(args.states):
+            chunk = {"__id__": f"state-{index}", "state": "test", "fun": "succeed_without_changes",
+                     "__sls__": f"formula.module{index % 100}", "name": f"state-{index}"}
+            if index:
+                chunk["require"] = [{"test": f"state-{index - 1}"}]
+            chunks.append(chunk)
+        started = perf_counter()
+        graph = StateGraph.from_low(chunks)
+        build_seconds = perf_counter() - started
+        started = perf_counter()
+        diagnostics = graph.diagnostics()
+        diagnostic_seconds = perf_counter() - started
+        with sqlite3.connect(path) as con:
+            con.execute("INSERT INTO runs (uuid,started_at,command,argv_json,status) VALUES (?,?,?,?,?)",
+                        ("scale", "2026-01-01T00:00:00+00:00", "synthetic", "[]", "success"))
+            run_id = con.execute("SELECT last_insert_rowid()").fetchone()[0]
+            con.executemany("INSERT INTO run_minion_progress (run_id,minion_id,status) VALUES (?,?,?)",
+                            ((run_id, f"minion-{index:05d}", "success") for index in range(args.minions)))
+            started = perf_counter()
+            batch = []
+            for index in range(args.history):
+                batch.append((run_id, f"minion-{index % max(1,args.minions):05d}", f"formula.module{index % 100}",
+                              f"state-{index % 1000}", "test", "succeed_without_changes", f"state-{index % 1000}",
+                              1, "{}", "ok", float(index % 1000)))
+                if len(batch) == 10000:
+                    con.executemany("""INSERT INTO state_results (run_id,minion_id,sls,state_id,state_module,state_function,name,
+                        result,changes_json,comment,duration_ms) VALUES (?,?,?,?,?,?,?,?,?,?,?)""", batch)
+                    batch.clear()
+            if batch:
+                con.executemany("""INSERT INTO state_results (run_id,minion_id,sls,state_id,state_module,state_function,name,
+                    result,changes_json,comment,duration_ms) VALUES (?,?,?,?,?,?,?,?,?,?,?)""", batch)
+        insert_seconds = perf_counter() - started
+        started = perf_counter()
+        minions = await db.progress(run_id)
+        progress_seconds = perf_counter() - started
+        started = perf_counter()
+        history = await db.slow_states(limit=50)
+        analytics_seconds = perf_counter() - started
+        started = perf_counter()
+        matrix = await db.matrix_summary(run_id, limit=200)
+        summary_seconds = perf_counter() - started
+        started = perf_counter()
+        visible_minions = await db.matrix_minions(run_id)
+        cells = await db.matrix_cells(run_id, visible_minions, [row["state_id"] for row in matrix])
+        cell_seconds = perf_counter() - started
+        monitor = EventMonitor(None, None, capacity=2000, queue_size=1000)
+        event = SaltEvent("2026-01-01T00:00:00+00:00", "salt/job/test/ret/web01", "job", {}, "test")
+        started = perf_counter()
+        for _ in range(args.events):
+            monitor.publish(event)
+        event_seconds = perf_counter() - started
+        print(f"Graph: {len(graph.nodes)} states, {len(graph.edges)} edges; build {build_seconds:.3f}s, diagnostics {diagnostic_seconds:.3f}s ({len(diagnostics)} hints)")
+        print(f"SQLite: {args.history} state rows inserted in {insert_seconds:.3f}s; {len(minions)} minion progress rows read in {progress_seconds:.3f}s")
+        print(f"Slow-state top {len(history)} groups: {analytics_seconds:.3f}s")
+        print(f"Matrix: {len(matrix)} state groups in {summary_seconds:.3f}s; {len(visible_minions)} minions, {len(cells)} visible cells in {cell_seconds:.3f}s")
+        print(f"Event ring: {args.events} synthetic events in {event_seconds:.3f}s; retained {len(monitor.recent)}")
+        with sqlite3.connect(path) as con:
+            for query in ("SELECT * FROM events WHERE jid='20261004150112345678' ORDER BY id DESC LIMIT 500",
+                          "SELECT * FROM state_results WHERE sls='formula.module1' AND state_id='state-1' AND state_module='test' AND state_function='succeed_without_changes' ORDER BY duration_ms LIMIT 1"):
+                print("PLAN", *con.execute("EXPLAIN QUERY PLAN " + query).fetchall())
+
+
+if __name__ == "__main__":
+    asyncio.run(main())

salt_tui-0.1.0/docs/architecture.md

@@ -0,0 +1,21 @@
+# Architecture
+
+The application uses Textual screens over a Salt service layer. The UI sends `CommandSpec` values to `SubprocessSaltClient`, which builds argument arrays and invokes Salt with `asyncio.create_subprocess_exec`. It never invokes a shell. Salt's JSON output is kept raw and normalized into minion and state rows. `Database` stores a run and its related records in one transaction through `asyncio.to_thread` and uses SQLite WAL mode. The source explorer reads configured `file_roots` only; authoritative high/low data and requisites come from `salt-call state.show_sls` and `state.show_low_sls`.
+
+Stage 2 Phase A adds an independent `EventSource` interface with a Salt Python adapter and a `salt-run state.event` adapter. `EventMonitor` owns subscription, reconnect, a bounded memory ring, and a bounded persistence queue. Migration 002 adds events and JID keyed run progress. Correlation uses exact JIDs only; it does not infer ownership from similar function names or time windows. See [Stage 2 plan](stage2.md).
+
+## Data flow
+
+1. User types a Salt CLI command. `parse_line` uses `shlex.split`, then `build_argv` adds JSON output where suitable.
+2. The command screen displays the exact generated command and requires confirmation for mutating commands.
+3. The service streams stdout/stderr into a bounded UI log and retains the full raw result.
+4. The parser extracts state return dictionaries; the database writes run, minion, state, failure, and log rows.
+5. History and state screens read indexed, paginated records and support failure navigation.
+
+## Boundaries
+
+`SaltClient` is a protocol, so a Salt Python API or remote API backend can later replace the CLI client. UI code has no subprocess calls. SQLite schema changes use numbered SQL migrations. The source browser is a navigation aid; Salt's compiled output remains authoritative. Only local Salt CLI workflows are implemented in this milestone.
+
+## Reliability
+
+The UI stays responsive through asyncio subprocesses and thread backed SQLite/file operations. History and log queries have limits. Normal test suite uses fixtures and a mocked subprocess and needs no Salt master. Errors retain the command, stdout, and stderr for reproduction.