sminos plane: mark the rows off the live chain in DX4 (7.179.0)

.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "doperpowers",
       "description": "Emerges by humans, Converges by Agent",
-      "version": "7.178.0",
+      "version": "7.179.0",
       "source": "./",
       "author": {
         "name": "SSFSKIM",

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "doperpowers",
   "description": "Emerges by humans, Converges by Agents",
-  "version": "7.178.0",
+  "version": "7.179.0",
   "author": {
     "name": "SSFSKIM",
     "email": "supremekim17@gmail.com"

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "doperpowers",
-  "version": "7.178.0",
+  "version": "7.179.0",
   "description": "One software-development methodology for coding agents, sized by the work: brainstorm, design, spec, TDD, review, ship — one spec that carries its plan of work as milestones: one milestone runs in order from the spec, several run a fresh subagent per milestone reviewed at each dependency frontier, and the same method runs unattended on the board loop.",
   "author": {
     "name": "SSFSKIM",

docs/doperpowers/TECH-DEBT.md

@@ -453,3 +453,34 @@ the spec's Decision Log entry "the branch review round"
   path did, until it framed its texts) can produce two identical wakes in that
   window, the second dropped. T3. Trigger: a sender of `deliver` that does
   not frame its text.
+
+## sminos plane: the live chain (2026-10-18, PR #239)
+
+- **A row whose parent never comes stays unmarked, and so does all that
+  follows it.** The chain places a row only once its parent is placed (the
+  engine writes a child a few ms ahead of its parent around a session's
+  start). A transcript whose first row names a parent outside the file — 1 of
+  1,500 on this machine, a resumed subagent — leaves every row unplaced: the
+  desk draws them all, as before the chain. The engine's loader treats such a
+  row as a root. Trigger: a transcript the desk draws with a dead branch whose
+  rows the plane left unplaced; then place a parent that has not come after a
+  bound (rows read) as a root.
+- **An Esc's retraction lands with the branch's first row, not at the Esc.**
+  The interactive engine writes nothing when an Esc hands a prompt back; the
+  rows it left behind go off when the next row is written (the prompt sent
+  again, a delivery, a system notice). Until then the desk draws them as
+  live. Its SDK rewind writes a `last-prompt {rewound: true}` anchor, which
+  has no uuid and is no row here. Trigger: the owner reading a handed-back
+  prompt as sent, or a desk-side rewind control (whose anchor the plane would
+  then read).
+- **An Esc that empties the conversation leaves no branch.** When the Esc
+  hands back a session's first prompt (nothing before it), the engine writes
+  its next row (a re-appended delivery, the wake) under the file's stale
+  leaf, the abandoned turn's last row. The file's chain then runs through the
+  prompt the live conversation no longer holds, and the engine's own resume
+  would rebuild it too. The only trace is a `last-prompt {leafUuid:
+  "00000000-…", explicit: true}` written after the next turn's first rows
+  (2.1.300 class `ydt`): it says a rewind happened, not where. Seen in
+  #238's evidence (run 7, `restore`). The desk keeps #42's frame-line fold
+  for the delivery; the prompt draws as read. Trigger: the engine writing
+  a null parent there, or a rewind trace that names the cut.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "doperpowers",
-  "version": "7.178.0",
+  "version": "7.179.0",
   "description": "Doperpowers skills and runtime bootstrap for coding agents",
   "type": "module",
   "keywords": [