@supercorks/krnl 0.1.7 → 0.1.12

package/README.md

@@ -68,7 +68,7 @@ Status and explanatory text share one row, for example **Done · Stopped in Code
 Version **0.1.3 or later** supports mapping task name prefixes. For example, a prefix of `👩‍⚕️`
 creates `👩‍⚕️ MELLA-284: Investigate an issue`. A blank prefix keeps the normal name. Project
 mapping settings take precedence over organization settings, and changes apply only to new tasks.
-Kernel explains when an older companion needs this update; existing task monitoring continues.
+Kernel and this companion use the current protocol together.
 
 Repeated connection reuses the machine identity. Review changed hook commands in `/hooks` if Node
 moved. After updating Node, run `krnl connect codex` to refresh the service’s executable path.
@@ -147,8 +147,25 @@ Existing task tab using its deep link or a title search.
 
 Draft uses the saved project folder and desktop model/reasoning settings. Work applies the mapping's
 settings and starts the first turn through app-server; the task is visible in desktop but cannot
-accept desktop replies until that turn finishes or is released for input. Legacy Plan receipts
-remain supported. Upgrading preserves existing tasks, worktrees, receipts, and hook paths.
+accept desktop replies until that turn finishes or is released for input. Choose Plan inside Codex
+after opening a Draft; Kernel dispatches only Draft and Work.
+
+Both modes use the same concise instructions: gather context from the task before
+starting, and ask the user when something is unclear. Task details appear in a fenced YAML block,
+with null or empty fields omitted and meaningful `false` and `0` values preserved. Draft keeps
+its task title first and its automatic-linking reference in the YAML `href` field.
+The prompt also asks for approval for any proposed Kernel task updates when the work is done.
+
+CLI 0.1.12 requires the prompt rendered and frozen by Kernel at submission. It forwards that text
+unchanged and has no local prompt template. Future wording and YAML changes need only a web
+deployment. Work also requires resolved model/reasoning settings; neither is supplied by a legacy
+fallback. Heartbeats and status reports use the current format without feature negotiation.
+
+Deploy Kernel and update this companion together. Setup uses `krnl login` and `krnl connect codex`
+with all-saved-project consent; manual pairing and per-project allowlist commands are removed.
+For this one-time cutover, convert settled old launch receipts to current watch records while the
+service is stopped and its local lock is held. Preserve a private backup and all task IDs, status
+sequences and delivery state. Do not interrupt an active first turn to perform the cutover.
 
 Interrupted draft dispatch is not repeated automatically. If Kernel cannot confirm opening, check
 Codex before opening another draft. Hooks inspect only the submitted prompt to match a pending
@@ -169,7 +186,7 @@ Healthy tasks continue independently. Do not delete receipts or blocked records
 an uncertain launch. Remote revocation stops dispatch; run `krnl login` and `krnl connect codex`
 to authorize again. A connection replaced by another process requires `krnl connect codex`.
 
-Kernel expires machine connectivity after 30 seconds. With a compatible server it also expires
+Kernel expires machine connectivity after 30 seconds. It also expires
 each task observation after at most 90 seconds; a heartbeat alone does not make an old task
 status current. Uncertain or expired observations show Disconnected until trustworthy evidence
 returns. Supported Codex metadata cannot reconstruct every missed desktop event, especially a
@@ -180,6 +197,15 @@ companion claims the launch; afterward, continue in Codex. Search has a separate
 a 30-second total deadline, and never applies late results after cancellation. Browser timeouts
 preserve input and cached content so the same request can be reconciled safely.
 
+## Shared threads (0.1.8+)
+
+One Codex thread can be linked to several Kernel tasks through each task's Existing task tab.
+Every linked task receives activity and waiting status; linking or completing a Codex turn does
+not change the Kernel tasks' lifecycle. Linking the same thread to the same task again is safe.
+Install the current CLI and run `krnl connect codex` with the current Kernel server.
+Hooks update every association and retain an event until all receipt writes succeed, including
+across restarts.
+
 ## Bundled third-party software
 
 This executable includes Zod under the following license: