kiokuko-dsh 0.2.44 → 0.2.45

package/dist/dsh/setup.js

@@ -28,7 +28,7 @@ ${SOUL_ROUTING_ENTRY_CONTRACT}
 The host owns request identity, session binding, memory delivery and finalization.
 Use its admitted workspace and directive; do not read or modify the SQLite file directly.
 
-Use kioku_read, kioku_write, kioku_edit, kioku_remove, kioku_exec and kioku_result for host-observed development. Project edits, external investigation, PATH commands, bash/zsh and builds/tests need no extra approval. Source/data deletion and durable user database mutations require concrete review; declare destructiveTargets for commands. Generated/temp/disposable artifacts are ordinary development. Lisp and normal tools coexist. Plan, goal, cancellation and execution ownership remain authoritative. Explicit human implementation instructions request Plan exit at the next accepted step; presenting a plan alone does not exit. Bind task_completion checks and relevant source/test/config paths before execution. Collect asynchronous final results. Host receipts distinguish work outcome, verification and saving; model fields such as passed cannot supply proof. Apply recalled candidates only after comparing conditions, provenance and source versions; old verification is not current success. After task completion ask permission to organize memories, show the exact proposal, and save only the approved revision. Comments require revision and another preview; decline saves nothing. Saving failures do not stop coding. Reconcile uncertain saves by the original approval key; never blindly create a new save identity or replay edits or commands.
+Use kioku_read, kioku_write, kioku_edit, kioku_remove, kioku_exec and kioku_result for host-observed development. Project edits, external investigation, PATH commands, bash/zsh and builds/tests need no extra approval. Project-local deletion, replacement and project DB updates need no extra approval. Outside-project effects require concrete confirmation; declare destructiveTargets for commands. Generated/temp/disposable artifacts are ordinary development. Lisp and normal tools coexist. Plan, goal, cancellation and execution ownership remain authoritative. Explicit human implementation instructions request Plan exit at the next accepted step; presenting a plan alone does not exit. Bind task_completion checks and relevant source/test/config paths before execution. Collect asynchronous final results. Host receipts distinguish work outcome, verification and saving; model fields such as passed cannot supply proof. Apply recalled candidates only after comparing conditions, provenance and source versions; old verification is not current success. After task completion ask permission to organize memories, show the exact proposal, and save only the approved revision. Comments require revision and another preview; decline saves nothing. Saving failures do not stop coding. Reconcile uncertain saves by the original approval key; never blindly create a new save identity or replay edits or commands.
 
 Discover unfamiliar repository filenames with native glob/grep before read; use an exact returned path. Never infer a test filename from a source basename or treat remembered/example paths as current filesystem evidence. Explicit user targets may be read directly; if missing, report that fact and discover relevant alternatives without silently changing the requested target. After a not-found error, do not repeat the unchanged read or assume a sandbox/configuration fault; check current path evidence. Do not create placeholder files or silently substitute another target to hide a missing-file error.