@codyswann/lisa 2.109.0 → 2.110.1

package/package.json

@@ -82,7 +82,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

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

@@ -10,7 +10,8 @@ Create (or update) a PRD issue in the configured source repo. Invoked by `lisa:p
 when `source = github`; do not call directly from a vendor-neutral caller.
 
 `$ARGUMENTS` carries the `lisa:prd-source-write` spec: `title`, `body` (full PRD markdown),
-`initial_role` (`draft` | `ready`, default `draft`), `dedupe_key`, `marker`, optional `source_ref`.
+`initial_role` (`draft` | `ready`, default `draft`), `dedupe_key`, `marker`, optional `source_ref`,
+and optional `ideation_ledger_payload` from `lisa:project-ideation` via `lisa:research`.
 
 ## Phase 1 — Resolve repo and PRD lifecycle labels
 
@@ -63,6 +64,40 @@ 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`, carries a project-ideation marker, or includes
+`ideation_ledger_payload`, 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. Populate the fields from
+`ideation_ledger_payload` when present, falling back to `marker`, `initial_role`, repo config, and
+runtime metadata only for missing fields. 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 +105,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 +119,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/prd-source-write/SKILL.md

@@ -27,6 +27,17 @@ dedupe_key: "<stable-key>"           # e.g. project-ideation's idea key
 marker: "[lisa-project-ideation] idea=<stable-key>"   # embedded in the PRD body for dedupe
 origin: { tool: project-ideation | research | manual }
 source_ref: "<optional existing PRD ref to force an update>"
+ideation_ledger_payload:              # optional; forwarded unchanged to the vendor writer
+  selected_marker: "<same value as marker>"
+  automation_id: "<Codex/Claude automation id or unavailable>"
+  automation_memory_path: "<path or unavailable>"
+  repo: "<org>/<repo or detected repo identity>"
+  prd_ready: true|false
+  persona_names: ["<derived persona name>"]
+  persona_evidence_refs: ["<file/doc/table/release ref>"]
+  selected_idea: "<selected idea title/key>"
+  rejected_overlap_candidates: ["<issue refs/titles considered and rejected>"]
+  expected_empirical_verification_artifact: "<artifact ref or unavailable>"
 ```
 
 `initial_role` semantics are uniform across vendors (the role STRINGS resolve per vendor from
@@ -72,6 +83,10 @@ prior PRD-source-write behavior to preserve, so omitted means `draft`.
    the applied role (`draft`/`ready`), the dedupe marker, and whether it was created or reused.
    Downstream callers (research, project-ideation) parse this — do not paraphrase.
 
+When `ideation_ledger_payload` is present, this shim still does not render or interpret it. Forward
+the object verbatim to the selected vendor writer so source-specific rendering remains behind the
+configured writer and the dispatch layer never bypasses source selection.
+
 ## Rules
 
 - Never bypass dispatch — a vendor-neutral caller calling a `*-write-prd` skill directly defeats the
@@ -80,5 +95,7 @@ prior PRD-source-write behavior to preserve, so omitted means `draft`.
   and fallback behavior belongs in the vendor writers and follows the `usage-accounting` contract.
 - Never accept a source outside `{notion, confluence, github, linear}`. `jira` and `file` fail loudly.
 - Never mutate the spec between layers. The vendor writers define their own create/dedupe contract.
+- Never drop, rename, or vendor-render `ideation_ledger_payload`; it is a pass-through payload for
+  the configured writer.
 - Never invent a PRD lifecycle role string — resolve every role from `config-resolution` per vendor.
 - Idempotency is the vendor writer's job (marker search before create); this shim only routes.

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

@@ -155,7 +155,13 @@ For each idea in the creation set, invoke `/lisa:research` with:
   grounding and the empirical verification plan),
 - `prd_ready` (this run's flag — `lisa:research` maps it to draft vs prd-ready),
 - a stable **dedupe marker** (see below) so a re-run references the existing PRD instead of creating
-  a duplicate.
+  a duplicate,
+- a structured `ideation_ledger_payload` handoff containing the selected marker, automation id and
+  memory path when available, persona names, persona evidence references, rejected overlap
+  candidates, repo identity, `prd_ready`, selected idea title/key, and the expected empirical
+  verification artifact. This payload is the only ideation-run metadata channel between
+  `project-ideation`, `research`, `prd-source-write`, and the vendor writer; keep GitHub-specific
+  rendering out of this skill.
 
 `lisa:research` synthesizes the PRD and creates it in the configured source via
 `lisa:prd-source-write`. `project-ideation` never writes to the source directly — it delegates, so

package/plugins/lisa/skills/research/SKILL.md

@@ -16,6 +16,12 @@ Produce a PRD for the problem in `$ARGUMENTS`, then create it in the configured
 - `dedupe_key` / `marker` (optional) — a stable dedupe marker (e.g. supplied by
   `lisa:project-ideation`) embedded in the created PRD so re-runs reference the existing PRD rather
   than creating a duplicate.
+- `ideation_ledger_payload` (optional, required when invoked by `lisa:project-ideation`) — a
+  structured metadata object to forward unchanged to `lisa:prd-source-write`. It carries the
+  selected marker, automation id/path when available, persona names, persona evidence references,
+  rejected overlap candidates, repo identity, `prd_ready`, selected idea title/key, and expected
+  empirical verification artifact. `research` may use these fields to inform the PRD body, but must
+  not discard, rename, or vendor-render them.
 
 ## Orchestration: agent team
 
@@ -55,5 +61,8 @@ source — there is no loose document artifact.** Before handing the synthesized
 `lisa:usage-accounting` so the PRD body carries the canonical `## Lisa Usage` ledger from creation
 time onward. If the runtime does not expose trustworthy usage, the direct entry must still be
 written with `source: unavailable` and nullable token/cost fields rather than silently omitting the
-Research row. A `source` must be configured; if it is not, stop and report it rather than emitting
-a document. The Plan flow consumes the created PRD next.
+Research row. If the call includes `ideation_ledger_payload`, pass that object through in the
+`lisa:prd-source-write` spec unchanged alongside `marker`, `dedupe_key`, and `initial_role`; this is
+the vendor-neutral handoff that lets the configured writer render an auditable run ledger without
+`research` bypassing source selection. A `source` must be configured; if it is not, stop and report
+it rather than emitting a document. The Plan flow consumes the created PRD next.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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.109.0",
+  "version": "2.110.1",
   "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/skills/github-write-prd/SKILL.md

@@ -10,7 +10,8 @@ Create (or update) a PRD issue in the configured source repo. Invoked by `lisa:p
 when `source = github`; do not call directly from a vendor-neutral caller.
 
 `$ARGUMENTS` carries the `lisa:prd-source-write` spec: `title`, `body` (full PRD markdown),
-`initial_role` (`draft` | `ready`, default `draft`), `dedupe_key`, `marker`, optional `source_ref`.
+`initial_role` (`draft` | `ready`, default `draft`), `dedupe_key`, `marker`, optional `source_ref`,
+and optional `ideation_ledger_payload` from `lisa:project-ideation` via `lisa:research`.
 
 ## Phase 1 — Resolve repo and PRD lifecycle labels
 
@@ -63,6 +64,40 @@ 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`, carries a project-ideation marker, or includes
+`ideation_ledger_payload`, 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. Populate the fields from
+`ideation_ledger_payload` when present, falling back to `marker`, `initial_role`, repo config, and
+runtime metadata only for missing fields. 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 +105,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 +119,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/prd-source-write/SKILL.md

@@ -27,6 +27,17 @@ dedupe_key: "<stable-key>"           # e.g. project-ideation's idea key
 marker: "[lisa-project-ideation] idea=<stable-key>"   # embedded in the PRD body for dedupe
 origin: { tool: project-ideation | research | manual }
 source_ref: "<optional existing PRD ref to force an update>"
+ideation_ledger_payload:              # optional; forwarded unchanged to the vendor writer
+  selected_marker: "<same value as marker>"
+  automation_id: "<Codex/Claude automation id or unavailable>"
+  automation_memory_path: "<path or unavailable>"
+  repo: "<org>/<repo or detected repo identity>"
+  prd_ready: true|false
+  persona_names: ["<derived persona name>"]
+  persona_evidence_refs: ["<file/doc/table/release ref>"]
+  selected_idea: "<selected idea title/key>"
+  rejected_overlap_candidates: ["<issue refs/titles considered and rejected>"]
+  expected_empirical_verification_artifact: "<artifact ref or unavailable>"
 ```
 
 `initial_role` semantics are uniform across vendors (the role STRINGS resolve per vendor from
@@ -72,6 +83,10 @@ prior PRD-source-write behavior to preserve, so omitted means `draft`.
    the applied role (`draft`/`ready`), the dedupe marker, and whether it was created or reused.
    Downstream callers (research, project-ideation) parse this — do not paraphrase.
 
+When `ideation_ledger_payload` is present, this shim still does not render or interpret it. Forward
+the object verbatim to the selected vendor writer so source-specific rendering remains behind the
+configured writer and the dispatch layer never bypasses source selection.
+
 ## Rules
 
 - Never bypass dispatch — a vendor-neutral caller calling a `*-write-prd` skill directly defeats the
@@ -80,5 +95,7 @@ prior PRD-source-write behavior to preserve, so omitted means `draft`.
   and fallback behavior belongs in the vendor writers and follows the `usage-accounting` contract.
 - Never accept a source outside `{notion, confluence, github, linear}`. `jira` and `file` fail loudly.
 - Never mutate the spec between layers. The vendor writers define their own create/dedupe contract.
+- Never drop, rename, or vendor-render `ideation_ledger_payload`; it is a pass-through payload for
+  the configured writer.
 - Never invent a PRD lifecycle role string — resolve every role from `config-resolution` per vendor.
 - Idempotency is the vendor writer's job (marker search before create); this shim only routes.

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

@@ -155,7 +155,13 @@ For each idea in the creation set, invoke `/lisa:research` with:
   grounding and the empirical verification plan),
 - `prd_ready` (this run's flag — `lisa:research` maps it to draft vs prd-ready),
 - a stable **dedupe marker** (see below) so a re-run references the existing PRD instead of creating
-  a duplicate.
+  a duplicate,
+- a structured `ideation_ledger_payload` handoff containing the selected marker, automation id and
+  memory path when available, persona names, persona evidence references, rejected overlap
+  candidates, repo identity, `prd_ready`, selected idea title/key, and the expected empirical
+  verification artifact. This payload is the only ideation-run metadata channel between
+  `project-ideation`, `research`, `prd-source-write`, and the vendor writer; keep GitHub-specific
+  rendering out of this skill.
 
 `lisa:research` synthesizes the PRD and creates it in the configured source via
 `lisa:prd-source-write`. `project-ideation` never writes to the source directly — it delegates, so

package/plugins/src/base/skills/research/SKILL.md

@@ -16,6 +16,12 @@ Produce a PRD for the problem in `$ARGUMENTS`, then create it in the configured
 - `dedupe_key` / `marker` (optional) — a stable dedupe marker (e.g. supplied by
   `lisa:project-ideation`) embedded in the created PRD so re-runs reference the existing PRD rather
   than creating a duplicate.
+- `ideation_ledger_payload` (optional, required when invoked by `lisa:project-ideation`) — a
+  structured metadata object to forward unchanged to `lisa:prd-source-write`. It carries the
+  selected marker, automation id/path when available, persona names, persona evidence references,
+  rejected overlap candidates, repo identity, `prd_ready`, selected idea title/key, and expected
+  empirical verification artifact. `research` may use these fields to inform the PRD body, but must
+  not discard, rename, or vendor-render them.
 
 ## Orchestration: agent team
 
@@ -55,5 +61,8 @@ source — there is no loose document artifact.** Before handing the synthesized
 `lisa:usage-accounting` so the PRD body carries the canonical `## Lisa Usage` ledger from creation
 time onward. If the runtime does not expose trustworthy usage, the direct entry must still be
 written with `source: unavailable` and nullable token/cost fields rather than silently omitting the
-Research row. A `source` must be configured; if it is not, stop and report it rather than emitting
-a document. The Plan flow consumes the created PRD next.
+Research row. If the call includes `ideation_ledger_payload`, pass that object through in the
+`lisa:prd-source-write` spec unchanged alongside `marker`, `dedupe_key`, and `initial_role`; this is
+the vendor-neutral handoff that lets the configured writer render an auditable run ledger without
+`research` bypassing source selection. A `source` must be configured; if it is not, stop and report
+it rather than emitting a document. The Plan flow consumes the created PRD next.

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;