npm - @open-agent-toolkit/cli - Versions diffs - 0.2.20 → 0.2.22 - Mend

@open-agent-toolkit/cli 0.2.20 → 0.2.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (58) hide show

package/assets/skills/oat-brainstorm/scripts/server.cjs CHANGED Viewed

@@ -5,11 +5,14 @@ const path = require('path');
 // ========== WebSocket Protocol (RFC 6455) ==========
-const OPCODES = { TEXT: 0x01, CLOSE: 0x08, PING: 0x09, PONG: 0x0A };
+const OPCODES = { TEXT: 0x01, CLOSE: 0x08, PING: 0x09, PONG: 0x0a };
 const WS_MAGIC = '258EAFA5-E914-47DA-95CA-C5AB0DC85B11';
 function computeAcceptKey(clientKey) {
-  return crypto.createHash('sha1').update(clientKey + WS_MAGIC).digest('base64');
+  return crypto
+    .createHash('sha1')
+    .update(clientKey + WS_MAGIC)
+    .digest('base64');
 }
 function encodeFrame(opcode, payload) {
@@ -40,9 +43,9 @@ function decodeFrame(buffer) {
   if (buffer.length < 2) return null;
   const secondByte = buffer[1];
-  const opcode = buffer[0] & 0x0F;
+  const opcode = buffer[0] & 0x0f;
   const masked = (secondByte & 0x80) !== 0;
-  let payloadLen = secondByte & 0x7F;
+  let payloadLen = secondByte & 0x7f;
   let offset = 2;
   if (!masked) throw new Error('Client frames must be masked');
@@ -73,18 +76,29 @@ function decodeFrame(buffer) {
 // ========== Configuration ==========
-const PORT = process.env.BRAINSTORM_PORT || (49152 + Math.floor(Math.random() * 16383));
+const PORT =
+  process.env.BRAINSTORM_PORT || 49152 + Math.floor(Math.random() * 16383);
 const HOST = process.env.BRAINSTORM_HOST || '127.0.0.1';
-const URL_HOST = process.env.BRAINSTORM_URL_HOST || (HOST === '127.0.0.1' ? 'localhost' : HOST);
+const URL_HOST =
+  process.env.BRAINSTORM_URL_HOST ||
+  (HOST === '127.0.0.1' ? 'localhost' : HOST);
 const SESSION_DIR = process.env.BRAINSTORM_DIR || '/tmp/brainstorm';
 const CONTENT_DIR = path.join(SESSION_DIR, 'content');
 const STATE_DIR = path.join(SESSION_DIR, 'state');
-let ownerPid = process.env.BRAINSTORM_OWNER_PID ? Number(process.env.BRAINSTORM_OWNER_PID) : null;
+let ownerPid = process.env.BRAINSTORM_OWNER_PID
+  ? Number(process.env.BRAINSTORM_OWNER_PID)
+  : null;
 const MIME_TYPES = {
-  '.html': 'text/html', '.css': 'text/css', '.js': 'application/javascript',
-  '.json': 'application/json', '.png': 'image/png', '.jpg': 'image/jpeg',
-  '.jpeg': 'image/jpeg', '.gif': 'image/gif', '.svg': 'image/svg+xml'
+  '.html': 'text/html',
+  '.css': 'text/css',
+  '.js': 'application/javascript',
+  '.json': 'application/json',
+  '.png': 'image/png',
+  '.jpg': 'image/jpeg',
+  '.jpeg': 'image/jpeg',
+  '.gif': 'image/gif',
+  '.svg': 'image/svg+xml',
 };
 // ========== Templates and Constants ==========
@@ -98,9 +112,15 @@ h1 { color: #333; } p { color: #666; }</style>
 <body><h1>Brainstorm Companion</h1>
 <p>Waiting for the agent to push a screen...</p></body></html>`;
-const frameTemplate = fs.readFileSync(path.join(__dirname, 'frame-template.html'), 'utf-8');
-const helperScript = fs.readFileSync(path.join(__dirname, 'helper.js'), 'utf-8');
-const helperInjection = '<script>\n' + helperScript + '\n</script>';
+const frameTemplate = fs.readFileSync(
+  path.join(__dirname, 'frame-template.html'),
+  'utf-8',
+);
+const helperScript = fs.readFileSync(
+  path.join(__dirname, 'helper.js'),
+  'utf-8',
+);
+const helperInjection = `<script>\n${helperScript}\n</script>`;
 // ========== Helper Functions ==========
@@ -114,9 +134,10 @@ function wrapInFrame(content) {
 }
 function getNewestScreen() {
-  const files = fs.readdirSync(CONTENT_DIR)
-    .filter(f => f.endsWith('.html'))
-    .map(f => {
+  const files = fs
+    .readdirSync(CONTENT_DIR)
+    .filter((f) => f.endsWith('.html'))
+    .map((f) => {
       const fp = path.join(CONTENT_DIR, f);
       return { path: fp, mtime: fs.statSync(fp).mtime.getTime() };
     })
@@ -131,11 +152,13 @@ function handleRequest(req, res) {
   if (req.method === 'GET' && req.url === '/') {
     const screenFile = getNewestScreen();
     let html = screenFile
-      ? (raw => isFullDocument(raw) ? raw : wrapInFrame(raw))(fs.readFileSync(screenFile, 'utf-8'))
+      ? ((raw) => (isFullDocument(raw) ? raw : wrapInFrame(raw)))(
+          fs.readFileSync(screenFile, 'utf-8'),
+        )
       : WAITING_PAGE;
     if (html.includes('</body>')) {
-      html = html.replace('</body>', helperInjection + '\n</body>');
+      html = html.replace('</body>', `${helperInjection}\n</body>`);
     } else {
       html += helperInjection;
     }
@@ -166,14 +189,17 @@ const clients = new Set();
 function handleUpgrade(req, socket) {
   const key = req.headers['sec-websocket-key'];
-  if (!key) { socket.destroy(); return; }
+  if (!key) {
+    socket.destroy();
+    return;
+  }
   const accept = computeAcceptKey(key);
   socket.write(
     'HTTP/1.1 101 Switching Protocols\r\n' +
-    'Upgrade: websocket\r\n' +
-    'Connection: Upgrade\r\n' +
-    'Sec-WebSocket-Accept: ' + accept + '\r\n\r\n'
+      'Upgrade: websocket\r\n' +
+      'Connection: Upgrade\r\n' +
+      `Sec-WebSocket-Accept: ${accept}\r\n\r\n`,
   );
   let buffer = Buffer.alloc(0);
@@ -185,7 +211,7 @@ function handleUpgrade(req, socket) {
       let result;
       try {
         result = decodeFrame(buffer);
-      } catch (e) {
+      } catch {
         socket.end(encodeFrame(OPCODES.CLOSE, Buffer.alloc(0)));
         clients.delete(socket);
         return;
@@ -233,14 +259,18 @@ function handleMessage(text) {
   console.log(JSON.stringify({ source: 'user-event', ...event }));
   if (event.choice) {
     const eventsFile = path.join(STATE_DIR, 'events');
-    fs.appendFileSync(eventsFile, JSON.stringify(event) + '\n');
+    fs.appendFileSync(eventsFile, `${JSON.stringify(event)}\n`);
   }
 }
 function broadcast(msg) {
   const frame = encodeFrame(OPCODES.TEXT, Buffer.from(JSON.stringify(msg)));
   for (const socket of clients) {
-    try { socket.write(frame); } catch (e) { clients.delete(socket); }
+    try {
+      socket.write(frame);
+    } catch {
+      clients.delete(socket);
+    }
   }
 }
@@ -260,14 +290,15 @@ const debounceTimers = new Map();
 // ========== Server Startup ==========
 function startServer() {
-  if (!fs.existsSync(CONTENT_DIR)) fs.mkdirSync(CONTENT_DIR, { recursive: true });
+  if (!fs.existsSync(CONTENT_DIR))
+    fs.mkdirSync(CONTENT_DIR, { recursive: true });
   if (!fs.existsSync(STATE_DIR)) fs.mkdirSync(STATE_DIR, { recursive: true });
   // Track known files to distinguish new screens from updates.
   // macOS fs.watch reports 'rename' for both new files and overwrites,
   // so we can't rely on eventType alone.
   const knownFiles = new Set(
-    fs.readdirSync(CONTENT_DIR).filter(f => f.endsWith('.html'))
+    fs.readdirSync(CONTENT_DIR).filter((f) => f.endsWith('.html')),
   );
   const server = http.createServer(handleRequest);
@@ -276,25 +307,31 @@ function startServer() {
   const watcher = fs.watch(CONTENT_DIR, (eventType, filename) => {
     if (!filename || !filename.endsWith('.html')) return;
-    if (debounceTimers.has(filename)) clearTimeout(debounceTimers.get(filename));
-    debounceTimers.set(filename, setTimeout(() => {
-      debounceTimers.delete(filename);
-      const filePath = path.join(CONTENT_DIR, filename);
-      if (!fs.existsSync(filePath)) return; // file was deleted
-      touchActivity();
-      if (!knownFiles.has(filename)) {
-        knownFiles.add(filename);
-        const eventsFile = path.join(STATE_DIR, 'events');
-        if (fs.existsSync(eventsFile)) fs.unlinkSync(eventsFile);
-        console.log(JSON.stringify({ type: 'screen-added', file: filePath }));
-      } else {
-        console.log(JSON.stringify({ type: 'screen-updated', file: filePath }));
-      }
+    if (debounceTimers.has(filename))
+      clearTimeout(debounceTimers.get(filename));
+    debounceTimers.set(
+      filename,
+      setTimeout(() => {
+        debounceTimers.delete(filename);
+        const filePath = path.join(CONTENT_DIR, filename);
+        if (!fs.existsSync(filePath)) return; // file was deleted
+        touchActivity();
+        if (!knownFiles.has(filename)) {
+          knownFiles.add(filename);
+          const eventsFile = path.join(STATE_DIR, 'events');
+          if (fs.existsSync(eventsFile)) fs.unlinkSync(eventsFile);
+          console.log(JSON.stringify({ type: 'screen-added', file: filePath }));
+        } else {
+          console.log(
+            JSON.stringify({ type: 'screen-updated', file: filePath }),
+          );
+        }
-      broadcast({ type: 'reload' });
-    }, 100));
+        broadcast({ type: 'reload' });
+      }, 100),
+    );
   });
   watcher.on('error', (err) => console.error('fs.watch error:', err.message));
@@ -304,7 +341,7 @@ function startServer() {
     if (fs.existsSync(infoFile)) fs.unlinkSync(infoFile);
     fs.writeFileSync(
       path.join(STATE_DIR, 'server-stopped'),
-      JSON.stringify({ reason, timestamp: Date.now() }) + '\n'
+      `${JSON.stringify({ reason, timestamp: Date.now() })}\n`,
     );
     watcher.close();
     clearInterval(lifecycleCheck);
@@ -313,13 +350,19 @@ function startServer() {
   function ownerAlive() {
     if (!ownerPid) return true;
-    try { process.kill(ownerPid, 0); return true; } catch (e) { return e.code === 'EPERM'; }
+    try {
+      process.kill(ownerPid, 0);
+      return true;
+    } catch (e) {
+      return e.code === 'EPERM';
+    }
   }
   // Check every 60s: exit if owner process died or idle for 30 minutes
   const lifecycleCheck = setInterval(() => {
     if (!ownerAlive()) shutdown('owner process exited');
-    else if (Date.now() - lastActivity > IDLE_TIMEOUT_MS) shutdown('idle timeout');
+    else if (Date.now() - lastActivity > IDLE_TIMEOUT_MS)
+      shutdown('idle timeout');
   }, 60 * 1000);
   lifecycleCheck.unref();
@@ -327,10 +370,17 @@ function startServer() {
   // was wrong (common on WSL, Tailscale SSH, and cross-user scenarios).
   // Disable monitoring and rely on the idle timeout instead.
   if (ownerPid) {
-    try { process.kill(ownerPid, 0); }
-    catch (e) {
+    try {
+      process.kill(ownerPid, 0);
+    } catch (e) {
       if (e.code !== 'EPERM') {
-        console.log(JSON.stringify({ type: 'owner-pid-invalid', pid: ownerPid, reason: 'dead at startup' }));
+        console.log(
+          JSON.stringify({
+            type: 'owner-pid-invalid',
+            pid: ownerPid,
+            reason: 'dead at startup',
+          }),
+        );
         ownerPid = null;
       }
     }
@@ -338,12 +388,16 @@ function startServer() {
   server.listen(PORT, HOST, () => {
     const info = JSON.stringify({
-      type: 'server-started', port: Number(PORT), host: HOST,
-      url_host: URL_HOST, url: 'http://' + URL_HOST + ':' + PORT,
-      screen_dir: CONTENT_DIR, state_dir: STATE_DIR
+      type: 'server-started',
+      port: Number(PORT),
+      host: HOST,
+      url_host: URL_HOST,
+      url: `http://${URL_HOST}:${PORT}`,
+      screen_dir: CONTENT_DIR,
+      state_dir: STATE_DIR,
     });
     console.log(info);
-    fs.writeFileSync(path.join(STATE_DIR, 'server-info'), info + '\n');
+    fs.writeFileSync(path.join(STATE_DIR, 'server-info'), `${info}\n`);
   });
 }

package/assets/skills/oat-explainer-kit/SKILL.md CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 name: oat-explainer-kit
-version: 1.0.1
+version: 1.0.3
 description: Use when building project explainers or recaps from OAT configuration, state, and lifecycle artifacts.
 disable-model-invocation: false
 user-invocable: true
@@ -19,6 +19,7 @@ Adapt OAT project context into the versioned request consumed by the canonical
 - Derive canonical project or repository output roots.
 - Bind OAT lifecycle artifacts to generic recipe source roles.
 - Resolve project explainer and recap intent before invoking the core.
+- Require lifecycle callers to construct a brief-aware author seam.
 ## Dependency Direction
@@ -33,7 +34,7 @@ rollback, and operator-owned real-wrapper gate, use `references/migration.md`.
 Before reading OAT config or invoking the core, call
 `scripts/check-core.mjs#checkCoreCompatibility` with this installed skill
-directory and minimum core version `1.0.0`. Continue only when it returns
+directory and minimum core version `2.0.0`. Continue only when it returns
 `ok: true`.
 - Missing core: stop and show
@@ -54,7 +55,7 @@ Call `scripts/run.mjs#runOatExplainer` with the repository root, project
 invocation, active project path, recipe, slug, lifecycle mode, and any explicit
 runtime overrides. The adapter:
-1. checks the user-scoped installed core at minimum version `1.0.0`;
+1. checks the user-scoped installed core at minimum version `2.0.0`;
 2. resolves only the public `explainers.*` and `workflow.explainers.*` keys;
 3. derives the canonical project output root;
 4. binds approved OAT artifacts to the recipe's single `project` source set;
@@ -68,13 +69,19 @@ Missing optional artifacts are omitted, but at least one approved lifecycle
 artifact is required. An explicit supplied fact-base path bypasses artifact
 federation and is passed through as `factBase.mode: supplied`.
+Before invocation, read `references/author-callback.md` and construct exactly
+one provider-neutral author seam in both modes: in-process callers supply
+`author`, while JSON/CLI callers supply `authorModulePath` naming a module with
+an `author` function export. The callback consumes `author-request/v2` with the
+recipe brief and fact base inlined, plus theme and any recipe-selected artistic
+shell. It may propose expansion only through recipe profile IDs. The adapter
+validates and resolves that executable input before passing it to
+`core.runExplainer`; callbacks and module paths never enter the persisted run
+request.
 Unattended project runs pass `approved-oat-artifacts` provenance to the core's
-content-approval seam and never prompt. Every unattended run also requires
-exactly one provider-neutral author seam: in-process callers supply `author`,
-while JSON/CLI callers supply `authorModulePath` naming a module with an
-`author` function export. The adapter validates and resolves that executable
-input before passing it to `core.runExplainer`; callbacks and module paths never
-enter the persisted run request.
+content-approval seam and never prompt. Automated completion and
+implementation-tail recaps always use `mode: unattended`.
 Federated runs still require an explicit provider-neutral critic callback.
 In-process callers may supply `critic` (or `coreOptions.critic` for

package/assets/skills/oat-explainer-kit/references/author-callback.md ADDED Viewed

@@ -0,0 +1,51 @@
+# Author callback contract
+Lifecycle callers own the executable author seam; the explainer core owns
+construction of each author request. In-process callers pass an `author`
+callback to `runOatExplainer`. JSON-only and official CLI callers pass
+`authorModulePath`, which must name a module with an `author` function export.
+Provide exactly one of those inputs in both interactive and unattended modes.
+The callback or module may use any provider, but its request and result remain
+provider-neutral.
+## Request handling
+The callback receives one `explainer-kit.author-request/v2` per artifact. The
+core constructs that request from recipe-owned policy:
+- `brief` contains the prose loaded from the floor entry or expansion profile's
+  `briefRef`; the author must treat the inlined brief as its editorial contract.
+- `factBase` contains the reconciled evidence for the run. Ground claims in that
+  fact base and do not replace it with ambient project context.
+- `authoring` selects the output path. Return Markdown for `markdown` and a
+  complete HTML document for `html`.
+- `theme` is attached to every request. HTML requests also carry the
+  recipe-selected `shell`; use it as the starting canvas while following the
+  brief's license to elaborate.
+- A floor request may include `floor.requiredNarrative`, which identifies the
+  narrative coverage checked later as non-blocking guidelines.
+Return one matching `explainer-kit.author-result/v2`: preserve `artifactId`,
+set exactly one of `content.markdown` or `content.html`, and include
+`provenance`. Do not persist provider credentials or callback configuration in
+the result.
+## Expansion
+Only a floor result may propose expansion. Put each proposal in
+`proposedArtifacts` as `{id, profileId, rationale}`. Do not choose an artifact
+type, authoring mode, brief, or shell in the proposal; the referenced recipe
+profile, selected by `profileId`, owns those values.
+The core validates proposal IDs, profile membership, collisions, and finite
+caps. It rejects malformed proposals, records over-limit proposals as warnings,
+and issues a new author request for every accepted artifact. Handle each
+follow-up request independently and do not recursively propose more artifacts.
+## Lifecycle invocation
+Automated project-completion and implementation-tail recaps always call
+`runOatExplainer` with `mode: unattended`. They construct the author seam before
+invocation and supply it alongside the existing provider-neutral `critic` or
+validated `criticModulePath`. Interactive invocations use the same author
+contract; only the later approval behavior differs.

package/assets/skills/oat-explainer-kit/references/lifecycle-contract.md CHANGED Viewed

@@ -71,18 +71,20 @@ On a stale-write conflict, the caller must re-read state, resolve precedence
 again, and decide whether a write is still required. It must not retry the old
 record blindly.
-## Unattended author execution
+## Author execution
-Every unattended adapter run must provide exactly one provider-neutral author
-seam. In-process callers pass `author`; JSON-only and official CLI callers put
-`authorModulePath` in the adapter context, naming a module whose `author` export
-is a function. Missing module files, invalid exports, and direct-plus-module
-conflicts fail at the adapter boundary.
+Every adapter run in both interactive and unattended modes must provide exactly
+one provider-neutral author seam. In-process callers pass `author`; JSON-only
+and official CLI callers put `authorModulePath` in the adapter context, naming
+a module whose `author` export is a function. Missing module files, invalid
+exports, and direct-plus-module conflicts fail at the adapter boundary. See
+`author-callback.md` for brief, fact-base, shell, theme, result, and expansion
+handling.
 The resolved callback is passed only as the `author` option to
 `core.runExplainer`. It is never copied into `ExplainerRunRequestV1`,
-`run-request.json`, or another retained data contract. Interactive runs may
-omit an author and retain their existing reviewed-source path.
+`run-request.json`, or another retained data contract. Interactive runs use the
+same author contract and differ only at the later approval gate.
 ## Tracked-run finalization

package/assets/skills/oat-explainer-kit/scripts/resolve-intent.mjs CHANGED Viewed

@@ -130,6 +130,20 @@ export function validateIntentRecord(product, record) {
   return record;
 }
+export function explainerModeForIntent(intent) {
+  if (
+    !intent ||
+    typeof intent !== 'object' ||
+    intent.product !== 'projectRecap' ||
+    intent.decision !== 'generate'
+  ) {
+    throw new Error(
+      'Only a generated projectRecap intent can select completion-chain explainer mode.',
+    );
+  }
+  return 'unattended';
+}
 function resolveAutonomous({
   product,
   state,

package/assets/skills/oat-explainer-kit/scripts/run.mjs CHANGED Viewed

@@ -12,7 +12,7 @@ import {
 } from './resolve-config.mjs';
 import { resolveExplainerOutputRoot } from './resolve-paths.mjs';
-const MINIMUM_CORE_VERSION = '1.0.0';
+const MINIMUM_CORE_VERSION = '2.0.0';
 const ADAPTER_ROOT = resolve(dirname(fileURLToPath(import.meta.url)), '..');
 export async function runOatExplainer({
@@ -114,7 +114,6 @@ export async function runOatExplainer({
     author,
     authorModulePath,
     coreOptions,
-    mode: request.mode,
   });
   const lifecycleCritic = await resolveLifecycleCritic({
     critic,
@@ -141,6 +140,7 @@ export async function runOatExplainer({
     request,
     manifest,
     result,
+    marking: result.marking ?? null,
     outputRoot,
   };
 }
@@ -149,7 +149,6 @@ async function resolveLifecycleAuthor({
   author,
   authorModulePath,
   coreOptions,
-  mode,
 }) {
   if (coreOptions?.author !== undefined) {
     throw new TypeError(
@@ -166,14 +165,11 @@ async function resolveLifecycleAuthor({
   }
   if (author === undefined && authorModulePath === undefined) {
-    if (mode === 'unattended') {
-      const error = new Error(
-        'Unattended OAT explainer runs require exactly one provider-neutral author callback or author module entry point.',
-      );
-      error.code = 'E_AUTHOR_REQUIRED';
-      throw error;
-    }
-    return null;
+    const error = new Error(
+      'Unattended and interactive OAT explainer runs require exactly one provider-neutral author callback or author module entry point.',
+    );
+    error.code = 'E_AUTHOR_REQUIRED';
+    throw error;
   }
   if (authorModulePath === undefined) {
     return author;

package/assets/skills/oat-project-complete/SKILL.md CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 name: oat-project-complete
-version: 1.5.4
+version: 1.6.0
 description: Use when all implementation work is finished and the project is ready to close. Marks the OAT project lifecycle as complete.
 disable-model-invocation: true
 user-invocable: true
@@ -282,7 +282,23 @@ When `SHOULD_GENERATE_RECAP="true"`, inspect manifests under
 `{PROJECT_PATH}/explainers/` before generating. A fresh `project-recap` manifest for the current completed implementation is reused without invoking the adapter again. Fresh means the manifest identifies recipe `project-recap`, belongs to this project, has a terminal outcome, and its recorded source hashes match the current approved implementation inputs, including the refreshed summary when present.
 If no fresh recap exists, invoke `scripts/run.mjs#runOatExplainer` exactly once with recipe `project-recap`, project invocation, the active project, and unattended lifecycle mode so approved OAT artifacts do not trigger a second content prompt. A failed adapter run warns but does not block completion. Use a returned valid terminal `project-recap` manifest as the selected run; do not rerun to improve its outcome.
-Supply the provider-neutral critic callback (or validated critic module entry point for JSON/CLI invocation) on every federated adapter run.
+Before that invocation, construct exactly one brief-aware, provider-neutral
+author seam as documented by
+`oat-explainer-kit/references/author-callback.md`. In-process callers pass
+`author`; JSON/CLI callers pass a validated `authorModulePath`. Supply it
+alongside the existing `critic` callback (or validated
+`criticModulePath`), and invoke the recap with `mode: unattended`.
+The author seam is the recap's quality mechanism, so derive its output from the
+request rather than from ambient context or a stock recap shape. Cover every
+`floor.requiredNarrative` section, ground each claim in the supplied `factBase`,
+and follow the inlined `brief` for structure — evidence tables for the
+implementation and validation sections, at least one high-level architecture
+diagram, and lists where material is enumerable. A recap whose warnings include
+`guideline-narrative-coverage-missing`, `guideline-structured-depth-missing`, or
+`guideline-architecture-diagram-missing` is thin: it still completes, but treat
+those warnings as the signal that the authored content did not use the evidence
+it was given.
 Set `SELECTED_PROJECT_RECAP_RUN` only to the final selected `project-recap` run. The value must be project-relative in the form `explainers/<run-slug>` so it can be passed safely to the archive CLI. An incomplete, stale, wrong-project, or `project-explainer` manifest is never selected as the final recap.

package/assets/skills/oat-project-implement/SKILL.md CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 name: oat-project-implement
-version: 2.1.9
+version: 2.2.0
 description: Use when plan.md is ready for execution. Dispatches one phase implementer per phase, owns independent phase review and bounded fix routing, and supports plan-declared worktree-isolated parallel phases.
 oat_gateable: true
 argument-hint: '[--retry-limit <N>] [--dry-run]'

package/assets/skills/oat-project-implement/references/completion-and-closeout.md CHANGED Viewed

@@ -751,7 +751,13 @@ Before generating, inspect the active project's explainer runs. A fresh `project
 Resolve recap intent through `oat-explainer-kit`. When `OAT_AUTONOMOUS=1` and no fresh recap exists, attempt `project-recap` exactly once; missing or stale persisted intent cannot suppress this autonomous attempt. Interactive mode honors the adapter's resolved persisted or workflow intent.
 Invoke the `oat-explainer-kit` adapter first, then run its shared tracked-run finalizer in `dedicated` mode for a successful build. Use the adapter result and finalizer result as returned; do not improvise commits, durability evidence, or reruns. Outcomes `failed` and `built-not-durable` are recorded warnings, never blockers for final HiLL approval, completion reporting, or later PR steps.
-Supply the provider-neutral critic callback (or validated critic module entry point for JSON/CLI invocation) on every federated adapter run.
+For an adapter invocation, construct exactly one brief-aware,
+provider-neutral author seam using
+`oat-explainer-kit/references/author-callback.md`. In-process callers pass
+`author`; JSON/CLI callers pass a validated `authorModulePath`. Supply it
+alongside the existing `critic` callback (or validated
+`criticModulePath`), and always invoke this implementation-tail recap with
+`mode: unattended`.
 Always include the selected or attempted recap's outcome and run path in the
 implementation completion report. If `summary.md` exists, append or refresh its

package/assets/skills/oat-wave-execute/SKILL.md CHANGED Viewed

@@ -1,6 +1,6 @@
 ---
 name: oat-wave-execute
-version: 1.7.1
+version: 1.8.0
 description: Use when executing a wave of external implementation plans as a wrapper OAT project — scaffolding, drift refresh, parallel worktree groups, briefs, gates, merge choreography, and closeout.
 argument-hint: '<wave-id> [plan-names...] (e.g. wave-2 http-listener-before-indexing ...)'
 disable-model-invocation: false
@@ -411,24 +411,17 @@ exactly:
 `schemaVersion, generatedAt, mode, freshnessPolicy, sources, claims, unresolvedClaims, overrides`.
 The caller also owns CONTENT AUTHORING, exactly as it owns critic execution and
-fact-base synthesis: the kit's pipeline validates structure and fact
-consistency, but nothing in it owns prose quality. An unattended recap run
-without a caller-supplied authoring path emits raw federated artifact text as
-deck prose (stoa W6 live evidence, run-19af6e55: implementation.md pasted
-verbatim, frontmatter included, tables flattened to run-on prose — every
-automated gate passed it). The explainer-kit now enforces this seam: every
-unattended run requires exactly one provider-neutral author seam — in-process
-callers supply an `author(request)` callback; JSON/CLI callers supply
-`authorModulePath` naming a module with an `author` function export. The core
-invokes it once per recipe artifact with an `explainer-kit.author-request/v1`
-document and expects an `explainer-kit.author-result/v1` reply; runs fail if
-the author is absent, returns an invalid result, or copies excessive verbatim
-source text. Recap callers MUST satisfy that seam by authoring content from
-the synthesized fact base plus the recipe outline (LLM-authored from
-summary/synthesis material, as the operator-approved W6 rebuild demonstrates)
-or NOT run the unattended build, recording the skip disposition per the
-optional-step rule. Callbacks and module paths never enter the persisted run
-request.
+fact-base synthesis: the kit validates structure and fact consistency, but
+nothing in it owns prose quality. Every recap run requires exactly one
+provider-neutral author seam — in-process callers supply an `author(request)`
+callback; JSON/CLI callers supply `authorModulePath` naming a module with an
+`author` function export. The core invokes it for every floor and accepted
+expansion artifact with `author-request/v2`: the artifact brief is inlined,
+the fact base is attached, and artistic requests include the resolved theme
+and hash-pinned shell. Authors may propose only recipe-declared expansion
+profiles and return `author-result/v2`; runs fail on absent or invalid author
+results or excessive verbatim source copying. Callbacks and module paths never
+enter persisted run requests.
 The mechanical caller constructs an `explainer-kit.run-request/v1` document whose
 required keys are exactly: