kiokuko-dsh 0.2.8 → 0.2.9

package/docs/dsh-plugin.md

@@ -15,6 +15,46 @@ The current runtime target is **DSH 0.2.1-alpha.2**. Older runtime records remai
 
 CI uses the canonical DSH fixture for native history, routing and packed Web lifecycle coverage. Historical source-repair CLI tests use the current catalog's historical codecs for v0/v3 fixtures. Local tests do not prove an npm `--latest` update or the user's running profile. The E2E runner defaults to the manifest's compatibility target; `KIOKUKO_EXPECTED_DSH_VERSION` selects an explicit fixture version. `KIOKUKO_DSH_CLI_ONLY=1` runs only the packed Web lifecycle and requires `KIOKUKO_REQUIRE_DSH_CLI=1`.
 
+## Task state and explicit operations
+
+`/kioku-task status` reads the current task from the existing Kiokuko ledger. All
+task categories use `ToDo`, `Working`, `Pending`, `Done`, and `Ignore`; an
+implementation task may additionally have a coding Goal. Research, writing,
+analysis, and conversation do not acquire a coding Goal merely to track state.
+
+```text
+/kioku-task create research Inspect this repository's startup behavior
+/kioku-task start
+/kioku-task wait
+/kioku-task resume
+/kioku-task complete --evidence <host-observed-reference>
+/kioku-task ignore --reason The requested investigation is no longer needed
+```
+
+Operations may name an existing task ID after the operation. `create` takes an
+existing task category and the exact requested work. `ignore` requires a reason.
+`complete` accepts repeated `--evidence` references to successful operations
+observed by the host in the current execution generation.
+Words such as “start”, “done”, or “ignore” inside ordinary messages, quoted text,
+code, or tool output do not perform these operations. The model's structured
+`task_operation` tool uses the same owner, repository, revision, and generation
+checks and retains native tool permissions.
+
+Only `Working` permits managed effects. A stop request stays `Working` with a
+pending-stop marker until the native agent, owned processes, child agents, and
+managed Lisp workers have stopped. `Done` requires current host-observed
+verification evidence. A failure or cancellation retains its actual outcome
+and becomes `Pending`; it is never treated as `Ignore`. Reopening terminal work
+requires an explicit resume and a new generation. Old results cannot complete
+or modify that new generation. Model changes transfer the same task to the
+verified primary continuation; CLI resume rereads its persisted state.
+
+Jev/Laya interpretations are advisory. If they are unavailable or abstain, the
+host records an unresolved decision and accepts a validated main-model
+interpretation or an explicit operation. The original request and authority
+checks remain in force. The CLI displays this SQLite snapshot and committed
+events; ordinary conversation text and native todo items are not state evidence.
+
 ## Model tool exposure
 
 `toolExposure.mode` defaults to `auto`. On verified OpenAI API routes, normal
@@ -50,6 +90,23 @@ pnpm dsh plugin --profile web add kiokuko-dsh
 pnpm dsh --profile web --dump-config
 ```
 
+For the [dsh-cli](https://github.com/askdkc/dsh-cli) terminal UI, use its `dsh-cli` profile:
+
+```bash
+pnpm dsh plugin --profile dsh-cli add @askdkc/dsh-cli
+pnpm dsh plugin --profile dsh-cli add kiokuko-dsh
+pnpm dsh --profile dsh-cli
+```
+
+Skip the first command if the UI bundle is already installed. `web` and `dsh-cli` have separate package and bundle lists; installing Kiokuko into one does not enable it in the other. `add` installs and registers the bundle. Use `update` only after installation:
+
+```bash
+pnpm dsh plugin --profile dsh-cli update kiokuko-dsh --latest
+pnpm dsh --profile dsh-cli
+```
+
+The remaining examples use `web`; substitute `dsh-cli` for that profile. With a globally installed `dsh`, omit `pnpm`.
+
 For a direct GitHub install, run the following from a DeepSeek Harness checkout:
 
 ```bash
@@ -155,7 +212,7 @@ Use the affected profile in place of `web`. For GitHub or local installs, reinst
 
 The guarded bundle entry prints these next steps for dependency-import failures and Kiokuko activation failures, then preserves the original rejection. It cannot print before DSH resolves that entry or when DSH never activates it because a required service is unavailable; those errors remain DSH-owned. The public library imports are unchanged.
 
-Released v0/v1/v2 history readers are bundled privately into the npm artifact. Their DSH packages are build dependencies only, so installing Kiokuko does not hoist an older DSH LLM over the running host. This preserves the released readers rather than substituting the current host's history format. Other plugins may still install conflicting DSH packages; inspect their dependency paths if the same Typert error persists.
+Released v0/v1/v2/v3 history readers are bundled privately into the npm artifact. Their DSH packages are build dependencies only, so installing Kiokuko does not hoist an older DSH LLM over the running host. This preserves the released readers rather than substituting the current host's history format. Other plugins may still install conflicting DSH packages; inspect their dependency paths if the same Typert error persists.
 
 ## Remove
 
@@ -325,9 +382,9 @@ limit. The package is therefore not represented as a small, auto-approved
 plugin.
 
 The manifest declares MIT licensing, the canonical GitHub repository, Node.js
-`>=24.16.0`, DSH `0.2.1-alpha.2`, and the verified `web` profile. Other DSH
+`>=24.16.0`, DSH `0.2.1-alpha.2`, and the `web` and `dsh-cli` profiles. Other DSH
 releases and `headless` remain unverified until a matching disposable-profile
-run is recorded.
+run is recorded. The legacy `dsh-tui` profile declaration is retained for existing installations.
 
 Runtime effects are explicit:
 
@@ -529,19 +586,38 @@ them for cursor-backed finalization/export and records cache usage. Without a ds
 as `unsupported`; CI sets `KIOKUKO_REQUIRE_DSH_CLI=1` so absence is a failure
 rather than an unverified success.
 
-The current compatibility measurement is:
+The terminal profile has a separate acceptance runner. Supply a built DSH CLI,
+packed UI and Kiokuko tarballs, the installed `node-pty/package.json`, and a
+package manifest from which `@xterm/headless` resolves:
+
+```bash
+npm run test:cli-profile -- /path/to/dsh/bin.js /path/to/dsh-cli.tgz /path/to/kiokuko-dsh.tgz /path/to/node-pty/package.json /path/to/dsh-cli/package.json
+```
+
+It uses a temporary HOME and profile, checks registry `add` and `update --latest`,
+loads the supplied tarballs, and drives a real terminal through normal input,
+Esc cancellation, Lisp evaluation, shutdown, and JSONL resume. SBCL must already
+be installed for Lisp evaluation. It sends the first Kiokuko slash command as
+soon as the terminal accepts input, without waiting for plugin registration,
+and verifies that the command never reaches the model. The model provider is a
+scripted offline fixture: this checks host integration, not real-model behavior. Runtime package
+paths and versions are recorded with the result. Missing prerequisites and
+runtime errors fail the runner rather than count as successful acceptance.
+
+The compatibility coverage is:
 
 | Harness profile | Status |
 |---|---|
-| web | verified by the disposable rc.1 install/start/uninstall run |
+| web | disposable install/start/uninstall runner and native integration tests |
+| dsh-cli | isolated packed-profile install/update and interactive terminal runner |
 | headless | unknown; not declared as supported |
 | sdk | unsupported until a real Loader/SDK host is supplied |
 | acp | unsupported until a real Loader/ACP host is supplied |
 | sdk-minimal | unsupported until a real Loader/SDK host is supplied |
 
-The `web` status is evidence-based only after the disposable rc.1 run. An
-unavailable DeepSeek binary leaves a profile unverified; it is never converted
-into a passing runtime claim.
+Run the corresponding acceptance test against the intended DSH installation.
+An unavailable DeepSeek binary leaves a profile unverified; it is never
+converted into a passing runtime claim.
 
 ## DSH acceptance boundary
 
@@ -549,7 +625,8 @@ DSH acceptance is limited to the DSH surface and the directly relevant
 Kiokuko contracts listed by the DSH verifier set. There is no generic Kiokuko
 HTTP, TCP, or standalone Web product surface in this package. The only Web
 lifecycle checked here is the DeepSeek Harness `web` profile loading and
-unloading this plugin. An unavailable DeepSeek CLI is reported as
+unloading this plugin; terminal coverage uses the separate `dsh-cli` profile.
+An unavailable DeepSeek CLI is reported as
 `unsupported`, never as a successful install or runtime execution.
 
 ## AgenticReplay recording

package/docs/getting-started.md

@@ -14,6 +14,16 @@ pnpm dsh plugin --profile web add kiokuko-dsh
 pnpm dsh --profile web --dump-config
 ```
 
+For the dsh-cli terminal UI, use the separate `dsh-cli` profile:
+
+```bash
+pnpm dsh plugin --profile dsh-cli add @askdkc/dsh-cli
+pnpm dsh plugin --profile dsh-cli add kiokuko-dsh
+pnpm dsh --profile dsh-cli
+```
+
+Skip the first command when the UI bundle is already installed. For later Kiokuko updates, use `pnpm dsh plugin --profile dsh-cli update kiokuko-dsh --latest`, then restart that profile. The following Web examples use `web`; substitute `dsh-cli` when working with the terminal profile.
+
 To install directly from GitHub, run this from a DeepSeek Harness checkout:
 
 ```bash

package/docs/guardrail-licenses/Apache-2.0.txt

@@ -0,0 +1,73 @@
+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.

package/docs/guardrail-licenses/BSD-2-Clause.txt

@@ -0,0 +1,9 @@
+Copyright (c) <year> <owner> 
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/docs/guardrail-licenses/COPYRIGHT-Rust.txt

@@ -0,0 +1,34 @@
+Short version for non-lawyers:
+
+The Rust Project is dual-licensed under Apache 2.0 and MIT
+terms.
+
+It is Copyright (c) The Rust Project Contributors.
+
+Longer version:
+
+Copyrights in the Rust project are retained by their contributors. No
+copyright assignment is required to contribute to the Rust project.
+
+Some files include explicit copyright notices and/or license notices.
+For full authorship information, see the version control history or
+<https://thanks.rust-lang.org>
+
+Except as otherwise noted, Rust is licensed under the Apache License, Version
+2.0 <LICENSE-APACHE> or <http://www.apache.org/licenses/LICENSE-2.0> or the MIT
+license <LICENSE-MIT> or <http://opensource.org/licenses/MIT>, at your option.
+
+We track licenses for third-party materials in two ways:
+
+* We use [REUSE](https://reuse.software) to track license information for
+  in-tree source files - both those authored by the Rust project and those
+  authored by third parties. See `REUSE.toml`, and our cached output of the
+  `reuse` tool which is committed to `license-metadata.json`.
+* We use `cargo` to track license information for out-of-tree dependencies.
+
+These two sources of information are collected by the tool `generate-copyright`
+into a file called `COPYRIGHT.html`, which is shipped with each binary release
+of Rust. Please refer to that file for detailed information as to the components of
+any given Rust release. We also produce a `COPYRIGHT-library.html` file which only
+covers the subset of source code used in the Rust Standard Library, as opposed
+to the toolchain as a whole.