@cyber-dash-tech/revela 0.15.2 → 0.15.3

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.
@@ -1,25 +1,7 @@
1
- import { openRefineDeck } from "../refine/open"
2
-
3
1
  export async function handleInspect(
4
2
  options: { client: any; sessionID: string; workspaceRoot: string; openBrowser?: boolean },
5
3
  send: (text: string) => Promise<void>,
6
4
  ): Promise<void> {
7
- try {
8
- const result = openRefineDeck("", {
9
- client: options.client,
10
- sessionID: options.sessionID,
11
- workspaceRoot: options.workspaceRoot,
12
- mode: "inspect",
13
- openBrowser: options.openBrowser,
14
- })
15
- await send(
16
- `\`/revela inspect\` is deprecated. Opened \`/revela refine\` in Inspect mode for the active HTML deck.\n` +
17
- `File: \`${result.deck.file}\`\n` +
18
- `${result.stateNote}\n` +
19
- `URL: ${result.url}\n\n` +
20
- `Use \`/revela refine\` directly going forward. Use Ctrl/Cmd-click in the browser to reference deck elements, then use the Inspect tab for read-only Source/Purpose review. There is no chat box or freeform prompt.`
21
- )
22
- } catch (e: any) {
23
- await send(`**Inspect failed:** ${e.message || String(e)}`)
24
- }
5
+ void options
6
+ await send("`/revela inspect` is no longer a public command. Use `/revela refine --deck` and the Inspect tab for grounded Source/Purpose/Narrative Reading.")
25
7
  }
@@ -34,7 +34,7 @@ export function parseStoryArgs(param: string): ParseStoryArgsResult {
34
34
  if (token.startsWith("--language=")) {
35
35
  return { ok: false, error: "Usage: `/revela story --language <language>` or `/revela story -l <language>`. Do not use `--language=<language>`." }
36
36
  }
37
- return { ok: false, error: "Usage: `/revela story [--language <language> | -l <language>]`. Use `/revela review` for a readiness report." }
37
+ return { ok: false, error: "Usage: `/revela story [--language <language> | -l <language>]`." }
38
38
  }
39
39
 
40
40
  return { ok: true, args: { language } }
@@ -130,9 +130,9 @@ export function buildNarrativeViewPrompt(options: { workspaceRoot: string; langu
130
130
  return `Prepare the read-only Revela narrative UI display model.
131
131
 
132
132
  Target language request: ${options.language}
133
- - The language value is passed from the user's /revela narrative arguments. Interpret it as the desired UI/display language.
133
+ - The language value is passed from the user's /revela story arguments. Interpret it as the desired UI/display language.
134
134
  - Examples: --cn maps to zh-CN, --jp maps to ja-JP, while --fr, --de, --es, --ko, --Arabic, --Portuguese-BR, or a written language name should be localized normally into that requested language.
135
- - Default /revela narrative language is en when the user provides no language request.
135
+ - Default /revela story language is en when the user provides no language request.
136
136
 
137
137
  You must call the \`revela-narrative-view\` tool exactly once.
138
138
 
@@ -1,7 +1,7 @@
1
1
  /**
2
2
  * lib/commands/pdf.ts
3
3
  *
4
- * Handler for `/revela pdf <file_path>` — exports an HTML slide deck to PDF.
4
+ * Handler for `/revela export --deck pdf <file_path>` — exports an HTML slide deck to PDF.
5
5
  *
6
6
  * Output: same directory and base name as the input, with .pdf extension.
7
7
  * Example: decks/my-deck.html → decks/my-deck.pdf
@@ -24,8 +24,8 @@ export async function handlePdf(
24
24
 
25
25
  if (!resolvedFile) {
26
26
  await send(
27
- "**Usage:** `/revela pdf [file_path]`\n\n" +
28
- "Example: `/revela pdf decks/my-deck.html`"
27
+ "**Usage:** `/revela export --deck pdf [file_path]`\n\n" +
28
+ "Example: `/revela export --deck pdf decks/my-deck.html`"
29
29
  )
30
30
  return
31
31
  }
@@ -1,7 +1,7 @@
1
1
  /**
2
2
  * lib/commands/pptx.ts
3
3
  *
4
- * Handler for `/revela pptx [file_path]` — exports an HTML slide deck to PPTX.
4
+ * Handler for `/revela export --deck pptx [file_path]` — exports an HTML slide deck to PPTX.
5
5
  *
6
6
  * Output: same directory and base name as the input, with .pptx extension.
7
7
  * Example: decks/my-deck.html → decks/my-deck.pptx
@@ -64,7 +64,7 @@ export function resolvePptxDeck(workspaceRoot: string, filePath = ""): ResolvedP
64
64
  throw new Error("No deck HTML found in decks/. Generate a deck first or pass a file path.")
65
65
  }
66
66
  if (htmlFiles.length > 1) {
67
- throw new Error("This workspace contains multiple deck HTML files. Run `/revela pptx decks/<file>.html` to choose one.")
67
+ throw new Error("This workspace contains multiple deck HTML files. Run `/revela export --deck pptx decks/<file>.html` to choose one.")
68
68
  }
69
69
 
70
70
  const absoluteFile = resolve(root, htmlFiles[0])
@@ -18,7 +18,7 @@ Goal:
18
18
  - Treat this as a narrative readiness review, not a deck HTML write-readiness review.
19
19
  - Do not write, patch, or directly edit ${DECKS_STATE_FILE}. Use the \`revela-decks\` tool for all state changes.
20
20
  - Call \`revela-decks\` action \`reviewNarrative\` as the authoritative deterministic readiness engine.
21
- - Do not call \`revela-decks\` action \`review\` here. That action is the deck/artifact gate and belongs to \`/revela make deck --review\`.
21
+ - Do not call \`revela-decks\` action \`review\` here. That action is the deck/artifact gate inside \`/revela make --deck\` after the deck plan is confirmed.
22
22
  - Do not treat legacy \`writeReadiness.status\`, old review snapshots, or an existing HTML deck as narrative approval.
23
23
  - Do not write or overwrite \`decks/*.html\` during narrative review.
24
24
  - If the narrative is \`ready_for_approval\`, ask whether the user wants to approve it or revise it. Do not approve automatically.
@@ -50,7 +50,7 @@ Report format:
50
50
  - If warnings exist, list them after blockers as residual risks.
51
51
  - If approval is missing, ask whether the user wants to approve the narrative or revise it.
52
52
  - If approval is stale, say the prior approval no longer matches the current narrative hash.
53
- - Keep deck/artifact readiness separate. If the user wants to review slide-writing readiness, tell them to run \`/revela make deck --review\`.
53
+ - Keep deck/artifact readiness separate. If the user wants to write or review deck artifacts, tell them to run \`/revela make --deck\`.
54
54
 
55
55
  Rules:
56
56
  - Do not write or overwrite \`decks/*.html\` during narrative review.
@@ -79,6 +79,7 @@ Goal:
79
79
  - Treat this as the explicit transition from approved narrative state to user-confirmed deck planning.
80
80
  - Use the deck-render prompt mode for design, layout, component, HTML, QA, and deck artifact rules.
81
81
  - Default behavior is two-stage: first show the compiled deck plan with low-fidelity layout sketches, then stop for user confirmation before any artifact review or HTML writing.
82
+ - Every deck plan must include Cover, Table of Contents, and Closing slides. The TOC must show 3-5 chapter headings that match the deck's slide groups.
82
83
  - Do not write or overwrite \`decks/*.html\` until the narrative handoff, explicit user deck-plan confirmation, and deck/artifact gate are all satisfied.
83
84
  - Do not treat legacy \`writeReadiness.status\`, old review snapshots, or existing HTML decks as narrative approval.
84
85
  - Do not bypass the deck HTML contract, review snapshot freshness, source-trace expectations, or export preflight protections.
@@ -93,19 +94,22 @@ Workflow:
93
94
  3. If narrative readiness is \`approved\`, continue. If it is \`ready_for_approval\`, ask the user for explicit approval before continuing. If it is blocked, stale, or needs research, stop and report the smallest next action. Do not call \`approveNarrative\` unless the user explicitly approves or requests a render override.
94
95
  4. After approval or explicit render override exists, call \`revela-decks\` action \`compileDeckPlan\`. This projects canonical narrative claims and evidence bindings into compatibility \`slides[]\` and \`slides[].evidence[]\`; it must not write HTML.
95
96
  5. If \`compileDeckPlan\` returns \`skipped\`, stop and report the reason. Do not invent slide specs manually to bypass approval.
96
- 6. Present the compiled deck plan to the user and include a low-fidelity layout sketch for every slide. The sketch is ASCII/text structure only; do not generate visual images or HTML mockups.
97
+ 6. Present the compiled deck plan to the user and include a low-fidelity layout sketch for every slide. The plan must identify the chapter structure first: 3-5 chapter headings, each chapter's slide range, and which non-structural slides belong to each chapter. The sketch is ASCII/text structure only; do not generate visual images or HTML mockups.
97
98
  7. Stop after presenting the plan. Ask the user to confirm or request changes. Do not call \`revela-decks review\`, do not fetch design context, and do not write HTML in the same turn unless the user had already explicitly confirmed the current plan before this command.
98
99
  8. Only after explicit user confirmation of the current slide plan, call \`revela-decks\` action \`confirmDeckPlan\` with \`approvalBy=user\` and a compact \`approvalNote\`.
99
100
  9. After confirmation is recorded, ask for or confirm visual design only after the narrative deck plan exists. Fetch required design layouts/components with \`revela-designs read\` as needed.
100
101
  10. Update only deck/artifact metadata through \`revela-decks upsertDeck\` / \`upsertSlides\` when required by confirmed design/layout choices. Do not change canonical narrative claims unless the user asks to revise the narrative.
101
102
  11. Call \`revela-decks\` action \`review\` as the artifact gate. It computes \`writeReadiness\` and review snapshots for deck HTML writing. If it reports \`slide_plan_unconfirmed\`, stop and ask for explicit deck-plan confirmation.
102
- 12. Write \`decks/*.html\` only if the deck/artifact gate is ready and all deck HTML contract requirements can be satisfied. After each HTML write, the system automatically runs artifact QA before opening Refine.
103
- 13. If post-write artifact QA reports hard errors, fix them and let QA run again. Refine opens only after hard errors pass. Density warnings about thin claim/evidence substance should be reported and improved when useful, but they do not block Refine.
103
+ 12. Write \`decks/*.html\` only if the deck/artifact gate is ready and all deck HTML contract requirements can be satisfied. Generate the artifact chapter by chapter instead of drafting all content slides in one broad pass. Keep the HTML file valid after every write, preserve already-written slides, and update one chapter's slide sections at a time.
104
+ 13. For each chapter, make every content slide carry a distinct claim, evidence item, comparison, risk, or action. If a chapter lacks enough substance for its allocated slides, merge weak slides or reduce the slide count instead of creating sparse filler.
105
+ 14. After each HTML write, the system automatically runs artifact QA before opening Refine. If post-write artifact QA reports hard errors, fix them and let QA run again. Refine opens only after hard errors pass. Density warnings about thin claim/evidence substance should be reported and improved when useful, but they do not block Refine.
104
106
 
105
107
  Deck plan report format:
106
108
  - Start with \`Deck plan: awaiting confirmation\` when a plan was compiled and has not yet been confirmed.
107
109
  - Include narrative readiness status and narrative hash when available.
108
110
  - Include whether \`compileDeckPlan\` compiled or skipped.
111
+ - Include \`Required structure: Cover + Table of Contents + Closing\` and do not omit any of those slides.
112
+ - Include a \`Chapters\` section before the slide list. It must list 3-5 TOC headings, their slide ranges, and the non-structural slides assigned to each chapter.
109
113
  - For every slide, include: slide index, title, purpose, narrative role, low-fidelity layout sketch, layout, components, primary/supporting claim ids, evidence binding ids or source summary, visual intent, and caveats/unsupported scope.
110
114
  - Use this sketch style or similarly simple ASCII boxes:
111
115
 
@@ -135,12 +139,15 @@ Caveats / unsupported scope:
135
139
  Report format before any HTML write after confirmation:
136
140
  - Start with \`Deck handoff: <status>\`.
137
141
  - Include which user-confirmed plan, approved narrative hash, and deck review snapshot authorized the artifact work.
142
+ - Include the chapter currently being generated and confirm already-written slides are being preserved.
138
143
  - If deck/artifact review is blocked, list blockers separately from narrative blockers.
139
144
  - After writing HTML, read the appended \`Artifact QA\` report from the tool output. If it failed, fix hard errors before considering the deck ready for Refine.
140
145
 
141
146
  Rules:
142
147
  - \`compileDeckPlan\` is the canonical narrative-to-deck planning path. Do not manually invent slide specs to avoid it.
143
148
  - Deck slide specs are render-target projections. Canonical narrative remains the authority for audience, decision, claims, evidence boundaries, objections, risks, and approval.
149
+ - Cover, Table of Contents, and Closing are mandatory deck structure. TOC chapter headings must match the chapter grouping used for generation.
150
+ - Do not generate the complete deck content in one broad pass after confirmation. Work chapter by chapter while keeping the artifact valid after each write.
144
151
  - Applying evidence candidates, rewriting canonical claims, or approving narratives requires explicit user instruction.
145
152
  - If the user requests slide order, layout, component, or visual-intent changes that do not alter meaning, update only the deck projection through \`upsertSlides\` and present the revised plan for confirmation.
146
153
  - If the user requests claim, evidence, caveat, decision, or recommendation meaning changes, update canonical narrative first and rerun narrative review/approval or explicit render override before compiling a new deck plan.
@@ -165,7 +172,7 @@ export function buildDeckReviewPrompt({
165
172
 
166
173
  Goal:
167
174
  - Use ${DECKS_STATE_FILE} as the source of truth for whether the current workspace deck is ready to be written to \`decks/*.html\`.
168
- - Treat this as an artifact gate for deck rendering, not strategic narrative approval. Narrative readiness reports are reviewed by \`/revela review\`.
175
+ - Treat this as an artifact gate for deck rendering, not strategic narrative approval. Narrative readiness is reviewed through \`/revela story\`.
169
176
  - Preserve the deck spec for future sessions: every slide's content, layout, components, evidence, visuals, production status, and the 0.9 narrative compiler brief when available.
170
177
  - Do not write, patch, or directly edit ${DECKS_STATE_FILE}. Use the \`revela-decks\` tool for all state changes.
171
178
  - Let \`revela-decks\` action \`review\` compute writeReadiness; do not manually set readiness to ready.
@@ -661,7 +661,7 @@ export function evaluateDeckStateWriteReadiness(state: DecksState, filePath: str
661
661
  type: "missing_slide_spec",
662
662
  severity: "blocker",
663
663
  message,
664
- suggestedAction: "Run /revela make deck --review and resolve all readiness blockers before writing deck HTML.",
664
+ suggestedAction: "Run /revela make --deck and resolve all readiness blockers before writing deck HTML.",
665
665
  })
666
666
  }
667
667
  if (deck.writeReadiness.blockers.length > 0) {
@@ -671,7 +671,7 @@ export function evaluateDeckStateWriteReadiness(state: DecksState, filePath: str
671
671
  type: "missing_slide_spec",
672
672
  severity: "blocker",
673
673
  message,
674
- suggestedAction: "Resolve the stored writeReadiness blockers and rerun /revela make deck --review.",
674
+ suggestedAction: "Resolve the stored writeReadiness blockers and rerun /revela make --deck.",
675
675
  })
676
676
  }
677
677
  if (normalized.reviews.length > 0) {
@@ -684,7 +684,7 @@ export function evaluateDeckStateWriteReadiness(state: DecksState, filePath: str
684
684
  type: "missing_slide_spec",
685
685
  severity: "blocker",
686
686
  message,
687
- suggestedAction: "Run /revela make deck --review so readiness is recorded against the current active render target.",
687
+ suggestedAction: "Run /revela make --deck so readiness is recorded against the current active render target.",
688
688
  })
689
689
  } else if (!isReviewSnapshotCurrent(normalized, snapshot, deck.slug)) {
690
690
  const message = "Latest review snapshot is stale for the current deck, sources, evidence, narrative state, or render target"
@@ -693,7 +693,7 @@ export function evaluateDeckStateWriteReadiness(state: DecksState, filePath: str
693
693
  type: "missing_slide_spec",
694
694
  severity: "blocker",
695
695
  message,
696
- suggestedAction: "Run /revela make deck --review again after the latest state changes before writing deck HTML.",
696
+ suggestedAction: "Run /revela make --deck again after the latest state changes before writing deck HTML.",
697
697
  })
698
698
  } else if (snapshot.status !== "ready") {
699
699
  const message = `Latest review snapshot is ${snapshot.status}, not ready`
@@ -702,7 +702,7 @@ export function evaluateDeckStateWriteReadiness(state: DecksState, filePath: str
702
702
  type: "missing_slide_spec",
703
703
  severity: "blocker",
704
704
  message,
705
- suggestedAction: "Resolve review blockers and rerun /revela make deck --review before writing deck HTML.",
705
+ suggestedAction: "Resolve review blockers and rerun /revela make --deck before writing deck HTML.",
706
706
  })
707
707
  }
708
708
  }
@@ -748,7 +748,7 @@ export function buildDecksStatePromptLayer(workspaceRoot: string, maxChars = 140
748
748
  }
749
749
  let text = JSON.stringify(compact, null, 2)
750
750
  if (text.length > maxChars) text = text.slice(0, maxChars).trimEnd() + "\n[DECKS.json state truncated for prompt size.]"
751
- return `---\n\n# Revela Workspace State From ${DECKS_STATE_FILE}\n\n\`\`\`json\n${text}\n\`\`\`\n\nRules for this state layer:\n- Treat ${DECKS_STATE_FILE} as the source of truth for the single current deck's specs, slide plan, evidence, render targets, and write readiness.\n- The decks map is compatibility storage; operate only on the current workspace deck.\n- ${DECKS_STATE_FILE} deck slides use 1-based \`slides[].index\` values. Render every HTML \`<section class="slide">\` with a matching 1-based \`data-slide-index\` attribute, and do not use 0-based \`data-index\` as slide identity.\n- The active HTML deck is represented as a \`renderTarget\` of type \`html_deck\`; PDF/PPTX exports should be recorded as derived render targets, not as separate deck specs.\n- \`writeReadiness\` is a compatibility projection for the /revela make deck generation workflow, not a hard blocker for targeted artifact-level HTML fixes.\n- Do not edit ${DECKS_STATE_FILE} directly; use the revela-decks tool.\n- For /revela make deck generated HTML, use the current deck's outputPath and satisfy the deck HTML contract. For targeted artifact-level edits, patch the requested deck HTML directly without treating \`writeReadiness\` or \`planReview\` as a precondition.`
751
+ return `---\n\n# Revela Workspace State From ${DECKS_STATE_FILE}\n\n\`\`\`json\n${text}\n\`\`\`\n\nRules for this state layer:\n- Treat ${DECKS_STATE_FILE} as the source of truth for the single current deck's specs, slide plan, evidence, render targets, and write readiness.\n- The decks map is compatibility storage; operate only on the current workspace deck.\n- ${DECKS_STATE_FILE} deck slides use 1-based \`slides[].index\` values. Render every HTML \`<section class="slide">\` with a matching 1-based \`data-slide-index\` attribute, and do not use 0-based \`data-index\` as slide identity.\n- The active HTML deck is represented as a \`renderTarget\` of type \`html_deck\`; PDF/PPTX exports should be recorded as derived render targets, not as separate deck specs.\n- \`writeReadiness\` is a compatibility projection for the /revela make --deck generation workflow, not a hard blocker for targeted artifact-level HTML fixes.\n- Do not edit ${DECKS_STATE_FILE} directly; use the revela-decks tool.\n- For /revela make --deck generated HTML, use the current deck's outputPath and satisfy the deck HTML contract. For targeted artifact-level edits, patch the requested deck HTML directly without treating \`writeReadiness\` or \`planReview\` as a precondition.`
752
752
  }
753
753
 
754
754
  function compactWorkspaceForPrompt(workspace: DecksState["workspace"]): DecksState["workspace"] {
@@ -84,7 +84,7 @@ function inferSlides(filePath: string): SlideSpec[] {
84
84
  evidence: [],
85
85
  visuals: [],
86
86
  status: "ready",
87
- notes: "Inferred automatically by /revela edit preflight.",
87
+ notes: "Inferred automatically by /revela refine --deck preflight.",
88
88
  }
89
89
  })
90
90
  }
@@ -12,7 +12,7 @@ export interface EditableDeck {
12
12
 
13
13
  export function resolveEditableDeck(workspaceRoot: string, input = ""): EditableDeck {
14
14
  if (input.trim()) {
15
- throw new Error("/revela refine does not accept a target. It opens the active HTML deck or the only HTML deck in decks/.")
15
+ throw new Error("/revela refine --deck does not accept a target. It opens the active HTML deck or the only HTML deck in decks/.")
16
16
  }
17
17
 
18
18
  if (hasDecksState(workspaceRoot)) {
@@ -484,7 +484,7 @@ export function renderInspectorShell(token: string): string {
484
484
  <aside>
485
485
  <div>
486
486
  <h1>Evidence Inspector</h1>
487
- <p class="hint">Cmd/Ctrl-click slide elements to attach them as references, exactly like /revela edit. Then click <b>Inspect Selection</b>. This is not chat.</p>
487
+ <p class="hint">Cmd/Ctrl-click slide elements to attach them as references in /revela refine --deck. Then click <b>Inspect Selection</b>. This is not chat.</p>
488
488
  </div>
489
489
  <div id="selection" class="selection">
490
490
  <strong>Selection</strong>
@@ -632,7 +632,7 @@ export function renderInspectorShell(token: string): string {
632
632
  if (bindAttempts >= 80) {
633
633
  clearInterval(bindTimer);
634
634
  bindTimer = 0;
635
- setBindingStatus('error', 'Selection binding timed out. Reopen /revela inspect or reload this page.');
635
+ setBindingStatus('error', 'Selection binding timed out. Reopen /revela refine --deck or reload this page.');
636
636
  }
637
637
  }, 150);
638
638
  }
@@ -7,8 +7,10 @@
7
7
  *
8
8
  * Deck-render mode:
9
9
  * Layer 1: SKILL.md — legacy deck render protocol (HTML rules, quality)
10
- * Layer 2: DOMAIN.md — domain structure/terminology
11
- * Layer 3: DESIGN.md — visual style (colors, fonts, animations, layout)
10
+ * Layer 2: DESIGN.md — visual style (colors, fonts, animations, layout)
11
+ *
12
+ * Domain guidance is intentionally narrative-only. Deck-render mode must render
13
+ * the approved canonical narrative instead of re-interpreting domain semantics.
12
14
  *
13
15
  * When the active DESIGN.md has @section markers, only the global section,
14
16
  * layouts section, and a generated component index are injected into the
@@ -87,19 +89,23 @@ export function buildPrompt(optionsOrDesignName?: BuildPromptOptions | string, l
87
89
  ? "<!-- - preview.html — canonical visual reference (read this before generating slides) -->"
88
90
  : "<!-- - (no preview.html for this design) -->"
89
91
 
90
- // Layer 2 — DOMAIN.md skill text (may be empty for "general")
92
+ // Layer 2 — DOMAIN.md skill text (narrative mode only). Deck-render mode
93
+ // renders the approved canonical narrative and must not re-interpret domain
94
+ // semantics from the full domain prompt.
91
95
  let domainSkill = ""
92
- try {
93
- domainSkill = getDomainSkillMd(domain)
94
- } catch (e) {
95
- // Domain not installed or empty — proceed without domain layer
96
- promptLog.warn("domain skill not foundbuilding without domain layer", {
97
- domain,
98
- error: e instanceof Error ? e.message : String(e),
99
- })
96
+ if (mode === "narrative") {
97
+ try {
98
+ domainSkill = getDomainSkillMd(domain)
99
+ } catch (e) {
100
+ // Domain not installed or empty proceed without domain layer
101
+ promptLog.warn("domain skill not found — building without domain layer", {
102
+ domain,
103
+ error: e instanceof Error ? e.message : String(e),
104
+ })
105
+ }
100
106
  }
101
107
 
102
- // Layer 3 — DESIGN.md: deck-render only. Narrative mode must not inject
108
+ // DESIGN.md: deck-render only. Narrative mode must not inject
103
109
  // visual CSS, layout catalogs, component indexes, or HTML skeleton rules.
104
110
  const designSkill = mode === "deck-render" ? buildDesignLayer(design) : ""
105
111
 
@@ -107,7 +113,7 @@ export function buildPrompt(optionsOrDesignName?: BuildPromptOptions | string, l
107
113
  const header = mode === "deck-render"
108
114
  ? `<!-- Revela prompt mode: deck-render -->\n` +
109
115
  `<!-- Active design: ${design} -->\n` +
110
- `<!-- Active domain: ${domain} -->\n` +
116
+ `<!-- Active domain: ${domain} (not injected in deck-render mode) -->\n` +
111
117
  `<!-- Design files: ${designDir}/ -->\n` +
112
118
  `<!-- - DESIGN.md — metadata + style instructions (injected below) -->\n` +
113
119
  `${previewLine}\n\n`
@@ -115,7 +121,7 @@ export function buildPrompt(optionsOrDesignName?: BuildPromptOptions | string, l
115
121
  `<!-- Active domain: ${domain} -->\n` +
116
122
  `<!-- Design layer intentionally omitted in narrative mode. Use deck-render mode before writing deck artifacts. -->\n\n`
117
123
 
118
- // Concatenation: Header → Skill → Domain → Design (deck-render only)
124
+ // Concatenation: Header → Skill → Domain (narrative only) → Design (deck-render only)
119
125
  const parts = [header, coreSkill]
120
126
  if (domainSkill) {
121
127
  parts.push(`\n\n---\n\n${domainSkill}`)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cyber-dash-tech/revela",
3
- "version": "0.15.2",
3
+ "version": "0.15.3",
4
4
  "description": "OpenCode plugin that turns AI into an HTML slide deck generator",
5
5
  "type": "module",
6
6
  "main": "./index.ts",