@sagmans/dsh-tui 0.1.0 → 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -7
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,11 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
Interactive terminal (TUI) surface for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness): use `dsh` in a terminal instead of a browser.
|
|
4
4
|
|
|
5
|
-
Status: **v1 feature-complete
|
|
5
|
+
Status: **v1 feature-complete; `0.1.0` is published.** The surface owns the alternate screen, streams assistant text as markdown, renders every tool's own card, answers approvals and questions, restores and names stored conversations, switches model mid-session, runs any of the four shipped agent modes and switches between them before a session's first turn, reads a child agent's conversation in place, keeps the goal, plan mode, todo list, delegations, and background jobs above the editor with a status line below it, and hands the terminal back on every graceful exit. Publication is tag-driven with GitHub OIDC provenance and no stored npm token; see [RELEASE.md](RELEASE.md).
|
|
6
6
|
|
|
7
7
|
## Install
|
|
8
8
|
|
|
9
|
-
A profile keeps this plugin as one bundle layer. Install it from a checkout of this repository, or from the registry
|
|
9
|
+
A profile keeps this plugin as one bundle layer. Install it from a checkout of this repository, or from the registry (`0.1.0` or later). Both paths need Node.js >= 22.19 and `pnpm` on `PATH`. Both need a real terminal: stdin and stdout must be TTYs.
|
|
10
10
|
|
|
11
11
|
### From a plugin checkout
|
|
12
12
|
|
|
@@ -28,7 +28,7 @@ dsh plugin --profile tui add @sagmans/dsh-tui@latest
|
|
|
28
28
|
dsh --profile tui
|
|
29
29
|
```
|
|
30
30
|
|
|
31
|
-
|
|
31
|
+
`0.1.0` is published, so this path works today. A checkout stays the path for unreleased work.
|
|
32
32
|
|
|
33
33
|
### Confirm the plugin mounted
|
|
34
34
|
|
|
@@ -241,11 +241,11 @@ The automated checks drive a real PTY, but they run on this machine's terminal.
|
|
|
241
241
|
|
|
242
242
|
Published artefacts carry a provenance attestation, which only a CI provider can issue, so releases ship from the tag workflow rather than a laptop.
|
|
243
243
|
|
|
244
|
-
1. Bump `version` in `package.json` and
|
|
245
|
-
2.
|
|
246
|
-
3. `.github/workflows/release.yml` re-runs typecheck, tests, and the package smoke
|
|
244
|
+
1. Bump `version` in `package.json`, land it on `main` through a reviewed PR, and wait for CI to pass on the merged SHA.
|
|
245
|
+
2. Tag that SHA with a signed tag and push it. The tag ruleset admits repository admins only.
|
|
246
|
+
3. `.github/workflows/release.yml` re-runs typecheck, tests, and the package smoke; the publish job then waits for a maintainer's approval on the `npm-release` environment before it publishes with OIDC trusted publishing and automatic provenance.
|
|
247
247
|
|
|
248
|
-
The workflow
|
|
248
|
+
The workflow stores no npm token: the registry trusts `release.yml` on the `npm-release` environment, and [`scripts/npm/release.py`](scripts/npm/release.py) creates both the environment and that trust. The full runbook is [RELEASE.md](RELEASE.md).
|
|
249
249
|
|
|
250
250
|
## Limitations
|
|
251
251
|
|