@codyswann/lisa 2.108.0 → 2.110.0

package/package.json

@@ -82,7 +82,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/scripts/project-ideation-idempotency-harness.mjs

@@ -5,10 +5,17 @@
  * The harness runs a caller-supplied deterministic project-ideation command
  * twice, checks that exactly one open GitHub PRD contains the expected marker,
  * then optionally removes the automation memory file and verifies a third run
- * recreates memory without creating a duplicate PRD.
+ * recreates memory without creating a duplicate PRD. The recreated memory entry
+ * must include the advisory run fields project-ideation promises to write.
  */
 
-import { existsSync, mkdirSync, renameSync, rmSync } from "node:fs";
+import {
+  existsSync,
+  mkdirSync,
+  readFileSync,
+  renameSync,
+  rmSync,
+} from "node:fs";
 import { dirname, resolve } from "node:path";
 import { spawnSync } from "node:child_process";
 
@@ -190,7 +197,7 @@ function queryOpenIssuesByMarker(repo, marker) {
  * @param {string} marker
  * @param {string} command
  * @param {string} memoryFile
- * @returns {{ readonly count: number, readonly issue: Record<string, any>, readonly memoryRecreated: boolean }}
+ * @returns {{ readonly count: number, readonly issue: Record<string, any>, readonly memoryRecreated: boolean, readonly memoryFieldsRecorded: boolean }}
  */
 function runMissingMemoryVariant(repo, marker, command, memoryFile) {
   const backup = `${memoryFile}.project-ideation-idempotency-backup`;
@@ -208,9 +215,27 @@ function runMissingMemoryVariant(repo, marker, command, memoryFile) {
       marker,
       "after missing-memory run"
     );
+    const memoryRecreated = existsSync(memoryFile);
+    const memoryFieldsRecorded =
+      memoryRecreated &&
+      memoryContainsRunEntry(memoryFile, {
+        marker,
+        prdUrl: String(result.issue.url),
+      });
+
+    if (!memoryRecreated) {
+      fail(`Expected missing-memory run to recreate ${memoryFile}`);
+    }
+    if (!memoryFieldsRecorded) {
+      fail(
+        `Expected recreated memory to record marker, PRD URL, outcome, lifecycle_role, and source_agreement`
+      );
+    }
+
     return {
       ...result,
-      memoryRecreated: existsSync(memoryFile),
+      memoryRecreated,
+      memoryFieldsRecorded,
     };
   } finally {
     if (existsSync(backup)) {
@@ -221,6 +246,24 @@ function runMissingMemoryVariant(repo, marker, command, memoryFile) {
   }
 }
 
+/**
+ * @param {string} memoryFile
+ * @param {{ readonly marker: string, readonly prdUrl: string }} expected
+ * @returns {boolean}
+ */
+function memoryContainsRunEntry(memoryFile, expected) {
+  const memory = readFileSync(memoryFile, "utf8");
+  const requiredFragments = [
+    expected.marker,
+    expected.prdUrl,
+    "outcome:",
+    "lifecycle_role:",
+    "source_agreement:",
+  ];
+
+  return requiredFragments.every(fragment => memory.includes(fragment));
+}
+
 /**
  * @param {string} command
  * @param {readonly string[]} argv

package/plugins/lisa/skills/github-write-prd/SKILL.md

@@ -63,6 +63,37 @@ the single instance. If the live issue body already contains the canonical manag
 section, preserve it verbatim unless the caller intentionally supplied an updated canonical section;
 use the shared `usage-accounting` serializer/merge path rather than hand-editing ledger rows.
 
+**Exploratory ideation run ledger (both paths).** When the write was initiated by
+`lisa:project-ideation` or carries a project-ideation marker, persist a managed `## Exploratory
+Ideation Run Ledger` section in the PRD body. Prefer the managed section over a comment so the PRD
+itself remains the operator's source of truth; use a managed comment only if the body cannot be
+updated. Keep one managed section by replacing the content between stable markers:
+
+```markdown
+## Exploratory Ideation Run Ledger
+<!-- lisa:exploratory-ideation-run-ledger:start -->
+- timestamp: <ISO-8601 run timestamp>
+- automation_id: <Codex/Claude automation id or unavailable>
+- repo: <org>/<repo>
+- prd_ready: true|false
+- persona_evidence_refs: <comma-separated source refs or unavailable>
+- selected_idea: <selected idea title/key>
+- dedupe_marker: <MARKER>
+- prd_url: <created or reused PRD URL>
+- outcome: created|reused
+- lifecycle_role_after_write: draft|ready|in_review|blocked|ticketed|shipped|verified
+- rejected_overlap_candidates: <issue refs/titles considered and rejected, or none>
+- expected_empirical_verification_artifact: <artifact ref or unavailable>
+<!-- lisa:exploratory-ideation-run-ledger:end -->
+```
+
+On CREATE, write a ledger entry with `outcome: created`, the selected marker, the created PRD URL,
+and the lifecycle role applied by this write. On UPDATE/reuse, write `outcome: reused`, preserve the
+same dedupe marker, record the reused PRD URL, and report the lifecycle role that remains after
+reconciliation. If the live PRD has progressed past ready, do not downgrade it while recording the
+reuse ledger; the `lifecycle_role_after_write` value must be the existing progressed role. Preserve
+exactly one PRD lifecycle label in the same pass as the ledger write.
+
 **CREATE** (no existing issue):
 
 1. Write the marker-normalized PRD body to a temp file.
@@ -70,7 +101,11 @@ use the shared `usage-accounting` serializer/merge path rather than hand-editing
    gh issue create --repo "$ORG/$REPO" --title "$TITLE" --body-file /tmp/prd-body.md --label "$ROLE_LABEL"
    ```
 3. Capture the returned issue number/URL.
-4. If `github.projects.v2` is enabled, resolve the created PRD issue node id and invoke
+4. Rewrite the PRD body with the managed `## Exploratory Ideation Run Ledger` section populated for
+   `outcome: created` when the caller supplied project-ideation ledger inputs, then
+   `gh issue edit <n> --body-file /tmp/prd-body.md`. This second write is allowed because the URL is
+   not known until after creation.
+5. If `github.projects.v2` is enabled, resolve the created PRD issue node id and invoke
    `lisa:github-project-v2` with `operation: ensure-item` and `content_node_id: <issue-node-id>`.
    - `outcome: disabled` → continue normally.
    - `outcome: added` or `reused` → continue normally; membership is now present.
@@ -80,7 +115,9 @@ use the shared `usage-accounting` serializer/merge path rather than hand-editing
 **UPDATE** (existing issue or `source_ref`):
 
 1. `gh issue edit <n> --repo "$ORG/$REPO" --body-file /tmp/prd-body.md` with the **marker-normalized**
-   body (regenerate in place; never drop the marker or an existing managed `## Lisa Usage` section).
+   body (regenerate in place; never drop the marker, the managed `## Exploratory Ideation Run Ledger`
+   section, or an existing managed `## Lisa Usage` section). When the caller supplied
+   project-ideation ledger inputs, replace the managed ledger content with an `outcome: reused` entry.
 2. Reconcile the lifecycle label to **exactly one**: add `$ROLE_LABEL`, remove every other label in
    the resolved `${ALL_PRD_LABELS[@]}` set (the config-resolved names — not a hard-coded list) via
    `gh issue edit <n> --add-label / --remove-label`. Never leave a PRD carrying two lifecycle labels.

package/plugins/lisa/skills/project-ideation/SKILL.md

@@ -161,6 +161,26 @@ For each idea in the creation set, invoke `/lisa:research` with:
 `lisa:prd-source-write`. `project-ideation` never writes to the source directly — it delegates, so
 the PRD source stays switchable per project. Capture each returned PRD ref / URL / role / outcome.
 
+### Optional Codex automation memory
+
+When the run has a Codex automation id or memory path, maintain a concise local advisory ledger after
+the PRD source write returns. Resolve the memory path in this order:
+
+1. explicit `memory_file=<path>` or `automation_memory=<path>` argument, when supplied;
+2. `$CODEX_AUTOMATION_MEMORY`, when set;
+3. `$CODEX_HOME/automations/<automation_id>/memory.md`, when `automation_id=<id>` or
+   `$CODEX_AUTOMATION_ID` is available.
+
+Create the parent directory and `memory.md` if missing. Write one concise run entry keyed by the
+dedupe marker and run timestamp. The entry must include the marker, PRD URL/ref, outcome
+(`created | reused | updated | blocked`), lifecycle role (`draft | ready | blocked` or the returned
+source role), and `source_agreement` (`github-source-wins`, `memory-created`, `memory-updated`, or
+`memory-missing-runtime`). If memory says one thing but the PRD source search finds a matching open
+PRD, GitHub/source truth wins: reuse the source PRD and update memory rather than creating a
+duplicate. Keep memory advisory only; never use it to override lifecycle labels, source marker
+matches, or the PRD source writer's returned role. Do not store secrets, tokens, full PRD bodies, or
+private source excerpts in memory.
+
 ### Dedupe marker (stable, never title-based)
 
 Each created PRD carries the marker `[lisa-project-ideation] idea=<stable-key>`. Compute

package/plugins/lisa/skills/project-ideation/examples/idempotency-verification-harness.md

@@ -43,7 +43,8 @@ The harness performs the acceptance check in three phases:
    require exactly one match.
 2. Run the same command again, then require the open marker count to remain one.
 3. Move the automation memory file aside, run the command again, require the marker count to remain
-   one, and require the memory file to be recreated. The original memory file is restored at the end.
+   one, and require the memory file to be recreated with marker, PRD URL, outcome, lifecycle role,
+   and source agreement fields. The original memory file is restored at the end.
 
 ## Expected evidence
 
@@ -53,4 +54,4 @@ Capture the harness JSON output as:
 - `[EVIDENCE: memory-recreated-after-rerun]` from the missing-memory variant.
 
 The run passes only when all reported counts are `1`, the issue URL is the same across phases, and
-`memoryRecreated` is `true` when `--memory-file` is supplied.
+`memoryRecreated` and `memoryFieldsRecorded` are `true` when `--memory-file` is supplied.

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.108.0",
+  "version": "2.110.0",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/scripts/lint-wiki.mjs

@@ -317,4 +317,8 @@ if (asJson) {
   );
 }
 
-process.exit(blocking === 0 ? 0 : 1);
+// Set exitCode instead of calling process.exit() so a large `--json` payload
+// written to a pipe (e.g. captured via spawnSync by verify-migration) is fully
+// flushed before the process exits. process.exit() can truncate async stdout
+// writes at the OS pipe buffer (~64KB), corrupting the JSON for the reader.
+process.exitCode = blocking === 0 ? 0 : 1;

package/plugins/src/base/scripts/project-ideation-idempotency-harness.mjs

@@ -5,10 +5,17 @@
  * The harness runs a caller-supplied deterministic project-ideation command
  * twice, checks that exactly one open GitHub PRD contains the expected marker,
  * then optionally removes the automation memory file and verifies a third run
- * recreates memory without creating a duplicate PRD.
+ * recreates memory without creating a duplicate PRD. The recreated memory entry
+ * must include the advisory run fields project-ideation promises to write.
  */
 
-import { existsSync, mkdirSync, renameSync, rmSync } from "node:fs";
+import {
+  existsSync,
+  mkdirSync,
+  readFileSync,
+  renameSync,
+  rmSync,
+} from "node:fs";
 import { dirname, resolve } from "node:path";
 import { spawnSync } from "node:child_process";
 
@@ -190,7 +197,7 @@ function queryOpenIssuesByMarker(repo, marker) {
  * @param {string} marker
  * @param {string} command
  * @param {string} memoryFile
- * @returns {{ readonly count: number, readonly issue: Record<string, any>, readonly memoryRecreated: boolean }}
+ * @returns {{ readonly count: number, readonly issue: Record<string, any>, readonly memoryRecreated: boolean, readonly memoryFieldsRecorded: boolean }}
  */
 function runMissingMemoryVariant(repo, marker, command, memoryFile) {
   const backup = `${memoryFile}.project-ideation-idempotency-backup`;
@@ -208,9 +215,27 @@ function runMissingMemoryVariant(repo, marker, command, memoryFile) {
       marker,
       "after missing-memory run"
     );
+    const memoryRecreated = existsSync(memoryFile);
+    const memoryFieldsRecorded =
+      memoryRecreated &&
+      memoryContainsRunEntry(memoryFile, {
+        marker,
+        prdUrl: String(result.issue.url),
+      });
+
+    if (!memoryRecreated) {
+      fail(`Expected missing-memory run to recreate ${memoryFile}`);
+    }
+    if (!memoryFieldsRecorded) {
+      fail(
+        `Expected recreated memory to record marker, PRD URL, outcome, lifecycle_role, and source_agreement`
+      );
+    }
+
     return {
       ...result,
-      memoryRecreated: existsSync(memoryFile),
+      memoryRecreated,
+      memoryFieldsRecorded,
     };
   } finally {
     if (existsSync(backup)) {
@@ -221,6 +246,24 @@ function runMissingMemoryVariant(repo, marker, command, memoryFile) {
   }
 }
 
+/**
+ * @param {string} memoryFile
+ * @param {{ readonly marker: string, readonly prdUrl: string }} expected
+ * @returns {boolean}
+ */
+function memoryContainsRunEntry(memoryFile, expected) {
+  const memory = readFileSync(memoryFile, "utf8");
+  const requiredFragments = [
+    expected.marker,
+    expected.prdUrl,
+    "outcome:",
+    "lifecycle_role:",
+    "source_agreement:",
+  ];
+
+  return requiredFragments.every(fragment => memory.includes(fragment));
+}
+
 /**
  * @param {string} command
  * @param {readonly string[]} argv

package/plugins/src/base/skills/github-write-prd/SKILL.md

@@ -63,6 +63,37 @@ the single instance. If the live issue body already contains the canonical manag
 section, preserve it verbatim unless the caller intentionally supplied an updated canonical section;
 use the shared `usage-accounting` serializer/merge path rather than hand-editing ledger rows.
 
+**Exploratory ideation run ledger (both paths).** When the write was initiated by
+`lisa:project-ideation` or carries a project-ideation marker, persist a managed `## Exploratory
+Ideation Run Ledger` section in the PRD body. Prefer the managed section over a comment so the PRD
+itself remains the operator's source of truth; use a managed comment only if the body cannot be
+updated. Keep one managed section by replacing the content between stable markers:
+
+```markdown
+## Exploratory Ideation Run Ledger
+<!-- lisa:exploratory-ideation-run-ledger:start -->
+- timestamp: <ISO-8601 run timestamp>
+- automation_id: <Codex/Claude automation id or unavailable>
+- repo: <org>/<repo>
+- prd_ready: true|false
+- persona_evidence_refs: <comma-separated source refs or unavailable>
+- selected_idea: <selected idea title/key>
+- dedupe_marker: <MARKER>
+- prd_url: <created or reused PRD URL>
+- outcome: created|reused
+- lifecycle_role_after_write: draft|ready|in_review|blocked|ticketed|shipped|verified
+- rejected_overlap_candidates: <issue refs/titles considered and rejected, or none>
+- expected_empirical_verification_artifact: <artifact ref or unavailable>
+<!-- lisa:exploratory-ideation-run-ledger:end -->
+```
+
+On CREATE, write a ledger entry with `outcome: created`, the selected marker, the created PRD URL,
+and the lifecycle role applied by this write. On UPDATE/reuse, write `outcome: reused`, preserve the
+same dedupe marker, record the reused PRD URL, and report the lifecycle role that remains after
+reconciliation. If the live PRD has progressed past ready, do not downgrade it while recording the
+reuse ledger; the `lifecycle_role_after_write` value must be the existing progressed role. Preserve
+exactly one PRD lifecycle label in the same pass as the ledger write.
+
 **CREATE** (no existing issue):
 
 1. Write the marker-normalized PRD body to a temp file.
@@ -70,7 +101,11 @@ use the shared `usage-accounting` serializer/merge path rather than hand-editing
    gh issue create --repo "$ORG/$REPO" --title "$TITLE" --body-file /tmp/prd-body.md --label "$ROLE_LABEL"
    ```
 3. Capture the returned issue number/URL.
-4. If `github.projects.v2` is enabled, resolve the created PRD issue node id and invoke
+4. Rewrite the PRD body with the managed `## Exploratory Ideation Run Ledger` section populated for
+   `outcome: created` when the caller supplied project-ideation ledger inputs, then
+   `gh issue edit <n> --body-file /tmp/prd-body.md`. This second write is allowed because the URL is
+   not known until after creation.
+5. If `github.projects.v2` is enabled, resolve the created PRD issue node id and invoke
    `lisa:github-project-v2` with `operation: ensure-item` and `content_node_id: <issue-node-id>`.
    - `outcome: disabled` → continue normally.
    - `outcome: added` or `reused` → continue normally; membership is now present.
@@ -80,7 +115,9 @@ use the shared `usage-accounting` serializer/merge path rather than hand-editing
 **UPDATE** (existing issue or `source_ref`):
 
 1. `gh issue edit <n> --repo "$ORG/$REPO" --body-file /tmp/prd-body.md` with the **marker-normalized**
-   body (regenerate in place; never drop the marker or an existing managed `## Lisa Usage` section).
+   body (regenerate in place; never drop the marker, the managed `## Exploratory Ideation Run Ledger`
+   section, or an existing managed `## Lisa Usage` section). When the caller supplied
+   project-ideation ledger inputs, replace the managed ledger content with an `outcome: reused` entry.
 2. Reconcile the lifecycle label to **exactly one**: add `$ROLE_LABEL`, remove every other label in
    the resolved `${ALL_PRD_LABELS[@]}` set (the config-resolved names — not a hard-coded list) via
    `gh issue edit <n> --add-label / --remove-label`. Never leave a PRD carrying two lifecycle labels.

package/plugins/src/base/skills/project-ideation/SKILL.md

@@ -161,6 +161,26 @@ For each idea in the creation set, invoke `/lisa:research` with:
 `lisa:prd-source-write`. `project-ideation` never writes to the source directly — it delegates, so
 the PRD source stays switchable per project. Capture each returned PRD ref / URL / role / outcome.
 
+### Optional Codex automation memory
+
+When the run has a Codex automation id or memory path, maintain a concise local advisory ledger after
+the PRD source write returns. Resolve the memory path in this order:
+
+1. explicit `memory_file=<path>` or `automation_memory=<path>` argument, when supplied;
+2. `$CODEX_AUTOMATION_MEMORY`, when set;
+3. `$CODEX_HOME/automations/<automation_id>/memory.md`, when `automation_id=<id>` or
+   `$CODEX_AUTOMATION_ID` is available.
+
+Create the parent directory and `memory.md` if missing. Write one concise run entry keyed by the
+dedupe marker and run timestamp. The entry must include the marker, PRD URL/ref, outcome
+(`created | reused | updated | blocked`), lifecycle role (`draft | ready | blocked` or the returned
+source role), and `source_agreement` (`github-source-wins`, `memory-created`, `memory-updated`, or
+`memory-missing-runtime`). If memory says one thing but the PRD source search finds a matching open
+PRD, GitHub/source truth wins: reuse the source PRD and update memory rather than creating a
+duplicate. Keep memory advisory only; never use it to override lifecycle labels, source marker
+matches, or the PRD source writer's returned role. Do not store secrets, tokens, full PRD bodies, or
+private source excerpts in memory.
+
 ### Dedupe marker (stable, never title-based)
 
 Each created PRD carries the marker `[lisa-project-ideation] idea=<stable-key>`. Compute

package/plugins/src/base/skills/project-ideation/examples/idempotency-verification-harness.md

@@ -43,7 +43,8 @@ The harness performs the acceptance check in three phases:
    require exactly one match.
 2. Run the same command again, then require the open marker count to remain one.
 3. Move the automation memory file aside, run the command again, require the marker count to remain
-   one, and require the memory file to be recreated. The original memory file is restored at the end.
+   one, and require the memory file to be recreated with marker, PRD URL, outcome, lifecycle role,
+   and source agreement fields. The original memory file is restored at the end.
 
 ## Expected evidence
 
@@ -53,4 +54,4 @@ Capture the harness JSON output as:
 - `[EVIDENCE: memory-recreated-after-rerun]` from the missing-memory variant.
 
 The run passes only when all reported counts are `1`, the issue URL is the same across phases, and
-`memoryRecreated` is `true` when `--memory-file` is supplied.
+`memoryRecreated` and `memoryFieldsRecorded` are `true` when `--memory-file` is supplied.

package/plugins/src/wiki/scripts/lint-wiki.mjs

@@ -317,4 +317,8 @@ if (asJson) {
   );
 }
 
-process.exit(blocking === 0 ? 0 : 1);
+// Set exitCode instead of calling process.exit() so a large `--json` payload
+// written to a pipe (e.g. captured via spawnSync by verify-migration) is fully
+// flushed before the process exits. process.exit() can truncate async stdout
+// writes at the OS pipe buffer (~64KB), corrupting the JSON for the reader.
+process.exitCode = blocking === 0 ? 0 : 1;