Harness spec 1.1.0: one plan, prototypes and the library shared; the CLI implements it

The spec: plan_write and plan_update (new, shared, offered in every mode) and
plan_submit (now shared) keep one structured plan — findings, objectives,
phases of tasks — in place of the todo list, which lives on as a former name
of plan_write. The shared system text is one text for both projects, with
variables for what differs; the mode texts, a prototypes block and a library
block are shared. acp.md: the client hands the device what only it knows
(context, library, prototypes), the plan travels as a structure (plan_state),
library calls carry the chat's scope, and a client may rewind a session.
loop.json says its numbers as numbers. Four conformance areas: plan,
prototype, library_scope, toolcall_index.

The CLI: the plan is kept per session in the store and drawn above the prompt
and on the approval card; the prompt is assembled from the spec's texts with
their variables filled; the link reads the instance's instructions,
personalization, knowledge scope and prototype offer, sends the plan as a
structure and answers rewind; library calls to the instance carry the session
as scope; a prototype written in the terminal is saved as a file and named in
the transcript; a tool-call fragment without an index continues the last call;
the default theme is Moria; dead exports and Hermes leftovers removed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

src/doctor.ts

@@ -5,8 +5,9 @@
 // that comes first on PATH, it is what `lembas` runs — and the person typing it gets a Python
 // traceback or a web server instead of this program. install.sh says so when it installs; this says
 // so whenever the configuration is checked.
-import { accessSync, constants, openSync, readSync, closeSync, realpathSync, statSync } from "node:fs"
+import { accessSync, constants, openSync, readSync, closeSync, statSync } from "node:fs"
 import { delimiter, dirname, join } from "node:path"
+import { realPath } from "./permission/evaluate.ts"
 
 /** The first `lembas` on `path`, the way a shell finds it. */
 export function firstOnPath(name: string, path = process.env.PATH ?? ""): string | undefined {
@@ -22,18 +23,10 @@ export function firstOnPath(name: string, path = process.env.PATH ?? ""): string
   return undefined
 }
 
-function real(p: string): string {
-  try {
-    return realpathSync(p)
-  } catch {
-    return p
-  }
-}
-
 /** Whether a file is a Python script (its first line a `#!` naming python). */
 export function isPythonScript(file: string): boolean {
   try {
-    const fd = openSync(real(file), "r")
+    const fd = openSync(realPath(file), "r")
     const buf = Buffer.alloc(300)
     const n = readSync(fd, buf, 0, 300, 0)
     closeSync(fd)
@@ -51,7 +44,7 @@ export function lembasShadowed(o: { path?: string; self?: string } = {}): string
   const self = "self" in o ? o.self : /(^|\/)bun$/.test(process.execPath) ? undefined : process.execPath
   const found = firstOnPath("lembas", o.path)
   if (!found) return undefined
-  if (self && real(found) === real(self)) return undefined
+  if (self && realPath(found) === realPath(self)) return undefined
   const python = isPythonScript(found)
   if (!python && !self) return undefined
   const what = python ? "a Python console script — most likely the LLeMbas server's own `lembas`" : "another program"