@cyber-dash-tech/revela 0.17.21 → 0.17.23

package/plugins/revela/mcp/revela-server.ts

@@ -19,6 +19,9 @@ type RuntimeModule = {
   exportPptx(input: any): Promise<any>
   designList(): any
   designRead(input?: any): any
+  designInventory(input?: any): any
+  designReadLayout(input: any): any
+  designReadComponent(input: any): any
   designActivate(input: any): any
   designCreate(input: any): any
   designValidate(input: any): any
@@ -40,6 +43,10 @@ type RuntimeModule = {
   researchSave(input: any): any
   evaluateResearchFindings(input: any): any
   bindResearchFindings(input: any): any
+  prepareLocalMaterials(input: any): Promise<any>
+  extractMaterial(input: any): Promise<any>
+  recordMaterialReview(input: any): any
+  checkMaterialIntake(input: any): any
 }
 
 type MessageMode = "framed" | "raw"
@@ -121,6 +128,29 @@ const tools = [
       section: stringProp("Optional design section, such as rules, foundation, or chart-rules."),
     }),
   },
+  {
+    name: "revela_design_inventory",
+    description: "List the active or requested Revela design sections, layouts, and components.",
+    inputSchema: objectSchema({
+      name: stringProp("Optional design name."),
+    }),
+  },
+  {
+    name: "revela_design_read_layout",
+    description: "Read one or more layout blocks from the active or requested Revela design.",
+    inputSchema: objectSchema({
+      name: stringProp("Optional design name."),
+      layout: stringOrArrayProp("Layout name, comma-separated names, or an array of layout names."),
+    }, ["layout"]),
+  },
+  {
+    name: "revela_design_read_component",
+    description: "Read one or more component blocks from the active or requested Revela design.",
+    inputSchema: objectSchema({
+      name: stringProp("Optional design name."),
+      component: stringOrArrayProp("Component name, comma-separated names, or an array of component names."),
+    }, ["component"]),
+  },
   {
     name: "revela_design_activate",
     description: "Activate a Revela design for future deck planning and artifact generation.",
@@ -287,6 +317,43 @@ const tools = [
       evidenceId: stringProp("Optional canonical evidence node id override."),
     }, ["findingsFile"]),
   },
+  {
+    name: "revela_prepare_local_materials",
+    description: "Scan local workspace source materials, create/update the material-intake registry, and optionally extract Office/PDF files into read views.",
+    inputSchema: objectSchema({
+      workspaceRoot: stringProp("Optional workspace root."),
+      path: stringProp("Optional workspace-relative subdirectory to scan."),
+      maxDepth: numberProp("Maximum scan depth. Defaults to 2."),
+      autoExtract: booleanProp("Whether to extract Office/PDF sources during prepare. Defaults to true."),
+    }),
+  },
+  {
+    name: "revela_extract_document_materials",
+    description: "Extract text, manifest, read view, and embedded images from a workspace document. Supports pdf, pptx, docx, and xlsx.",
+    inputSchema: objectSchema({
+      workspaceRoot: stringProp("Optional workspace root."),
+      file: requiredStringProp("Workspace-relative source file path."),
+    }, ["file"]),
+  },
+  {
+    name: "revela_record_material_review",
+    description: "Record that an LLM has read extracted local material and decided what was merged, deferred, ignored, or left as a gap.",
+    inputSchema: objectSchema({
+      workspaceRoot: stringProp("Optional workspace root."),
+      sourcePath: requiredStringProp("Workspace-relative source file path."),
+      reviewedPaths: arrayProp("Workspace-relative extracted paths actually reviewed."),
+      reviewSummary: requiredStringProp("Concise summary of the reviewed material."),
+      narrativeDecisions: arrayObjectProp("Narrative decisions with kind, optional target, and rationale."),
+    }, ["sourcePath", "reviewedPaths", "reviewSummary", "narrativeDecisions"]),
+  },
+  {
+    name: "revela_check_material_intake",
+    description: "Check whether scanned Office/PDF sources were extracted and reviewed before being treated as narrative intake.",
+    inputSchema: objectSchema({
+      workspaceRoot: stringProp("Optional workspace root."),
+      strictness: enumProp(["authoring", "readiness", "render"], "Check strictness."),
+    }),
+  },
 ]
 
 let runtimePromise: Promise<RuntimeModule> | undefined
@@ -353,6 +420,9 @@ async function callTool(name: string, args: any): Promise<any> {
   if (name === "revela_export_pptx") return r.exportPptx(args)
   if (name === "revela_design_list") return r.designList()
   if (name === "revela_design_read") return r.designRead(args)
+  if (name === "revela_design_inventory") return r.designInventory(args)
+  if (name === "revela_design_read_layout") return r.designReadLayout(args)
+  if (name === "revela_design_read_component") return r.designReadComponent(args)
   if (name === "revela_design_activate") return r.designActivate(args)
   if (name === "revela_design_create") return r.designCreate(args)
   if (name === "revela_design_validate") return r.designValidate(args)
@@ -374,6 +444,10 @@ async function callTool(name: string, args: any): Promise<any> {
   if (name === "revela_research_save") return r.researchSave(args)
   if (name === "revela_evaluate_research_findings") return r.evaluateResearchFindings(args)
   if (name === "revela_bind_research_findings") return r.bindResearchFindings(args)
+  if (name === "revela_prepare_local_materials") return r.prepareLocalMaterials(args)
+  if (name === "revela_extract_document_materials") return r.extractMaterial(args)
+  if (name === "revela_record_material_review") return r.recordMaterialReview(args)
+  if (name === "revela_check_material_intake") return r.checkMaterialIntake(args)
   throw new Error(`Unknown tool: ${name}`)
 }
 
@@ -401,6 +475,10 @@ function booleanProp(description: string) {
   return { type: "boolean", description }
 }
 
+function numberProp(description: string) {
+  return { type: "number", description }
+}
+
 function enumProp(values: string[], description: string) {
   return { type: "string", enum: values, description }
 }
@@ -409,6 +487,33 @@ function arrayProp(description: string) {
   return { type: "array", items: { type: "string" }, description }
 }
 
+function stringOrArrayProp(description: string) {
+  return {
+    anyOf: [
+      { type: "string" },
+      { type: "array", items: { type: "string" } },
+    ],
+    description,
+  }
+}
+
+function arrayObjectProp(description: string) {
+  return {
+    type: "array",
+    description,
+    items: {
+      type: "object",
+      properties: {
+        kind: { type: "string", enum: ["merged", "gap", "ignored", "deferred"] },
+        target: { type: "string" },
+        rationale: { type: "string" },
+      },
+      required: ["kind", "rationale"],
+      additionalProperties: false,
+    },
+  }
+}
+
 function writeMessage(message: any, mode: MessageMode = activeResponseMode): void {
   activeResponseMode = mode
   const body = JSON.stringify(message)

package/plugins/revela/skills/revela-design/SKILL.md

@@ -11,11 +11,13 @@ Use this skill when the user asks about Revela designs or when generating deck H
 
 1. Call `revela_design_list` to inspect installed designs.
 2. Call `revela_design_read` with `section: "rules"` before writing or patching `decks/*.html`; this records the Codex hook context required for deck writes.
-3. When the user asks to switch designs for future work, call `revela_design_activate` with the requested design name, then read the active design again.
-4. For one-off deck generation with a requested design, read that design by name and pass `designName` to `revela_create_deck_foundation` without changing active design unless the user asked to switch.
-5. Use the current simplified built-in design grammar: `box`, `text-panel`, `media`, `echart-panel`, `data-table`, `steps`, `roadmap-horizontal`, `roadmap-vertical`, `hero`, `stat-card`, `quote`, `toc`, `page-number`, and `brand-watermark`.
-6. Fetch chart/design guidance before creating ECharts or complex layouts.
-7. Do not invent unsupported component names.
+3. Call `revela_design_inventory` before authoring or repairing `deck-plan/` so planned layout/component names come from the active design.
+4. Read required details with `revela_design_read_layout` and `revela_design_read_component` before writing slide HTML that uses those layouts/components.
+5. When the user asks to switch designs for future work, call `revela_design_activate` with the requested design name, then read the active design again.
+6. For one-off deck generation with a requested design, read that design by name, call `revela_design_inventory` with that name, and pass `designName` to `revela_create_deck_foundation` without changing active design unless the user asked to switch.
+7. Use the current simplified built-in design grammar: `box`, `text-panel`, `media`, `echart-panel`, `data-table`, `steps`, `roadmap-horizontal`, `roadmap-vertical`, `hero`, `stat-card`, `quote`, `toc`, `page-number`, and `brand-watermark`.
+8. Fetch chart/design guidance before creating ECharts or complex layouts.
+9. Do not invent unsupported component names.
 
 Deck HTML must keep exactly one direct `.slide-canvas` child inside every `<section class="slide" ...>`; place `.page` or layout containers inside `.slide-canvas`, not directly under `.slide`.
 

package/plugins/revela/skills/revela-init/SKILL.md

@@ -18,14 +18,24 @@ Use this skill when the user asks to start Revela, initialize the workspace, ing
 
 ## Workflow
 
-1. Inspect the workspace with normal Codex file tools. Stay inside the current workspace root.
-2. Prefer local source materials first: Markdown, text, CSV, PDFs, Office files, existing `researches/`, existing `revela-narrative/`, `deck-plan/`, and `decks/`.
-3. Call `revela_domain_list` and `revela_domain_read` for active domain guidance before authoring narrative meaning. Treat domain guidance as framing guidance, never as evidence.
-4. If `revela-narrative/` exists, call `revela_markdown_qa` and `revela_compile_narrative`.
-5. If the narrative vault is missing, create the initial `revela-narrative/` Markdown nodes directly with valid frontmatter and plain wikilink relations.
-6. Evidence nodes must preserve source, quote/snippet, support scope, unsupported scope, caveat, and strength before being treated as support.
-7. After writing narrative Markdown, call `revela_markdown_qa` and `revela_compile_narrative` again.
-8. End with a concise init report: local materials found, active domain, narrative graph status, open gaps, Markdown QA status, and next command/action.
+1. Call `revela_prepare_local_materials` first. Treat scan results as an intake registry and task list, not as source content.
+2. For any registry entry with `requiresExtraction: true`, do not read the original Office/PDF file directly for narrative intake. Use the returned `allowedReadPath` / `read_view_path`; if missing, call `revela_extract_document_materials` first.
+3. Prefer local source materials first: Markdown, text, CSV, PDFs, Office files, existing `researches/`, existing `revela-narrative/`, `deck-plan/`, and `decks/`.
+4. After reading extracted material views, call `revela_record_material_review` for each considered Office/PDF source. Record what was merged, deferred, ignored, or left as a gap.
+5. Call `revela_domain_list` and `revela_domain_read` for active domain guidance before authoring narrative meaning. Treat domain guidance as framing guidance, never as evidence.
+6. If `revela-narrative/` exists, call `revela_markdown_qa` and `revela_compile_narrative`.
+7. If the narrative vault is missing, create the initial `revela-narrative/` Markdown nodes directly with valid frontmatter and plain wikilink relations.
+8. Evidence nodes must preserve source, quote/snippet, support scope, unsupported scope, caveat, and strength before being treated as support.
+9. After writing narrative Markdown, call `revela_markdown_qa` and `revela_compile_narrative` again.
+10. Before the final report, call `revela_check_material_intake` and surface any warnings about scanned-but-unextracted, extracted-but-unreviewed, unsupported, failed, or text-only sources.
+11. End with a concise init report: local materials found, active domain, narrative graph status, material intake status, open gaps, Markdown QA status, and next command/action.
+
+## Material Intake Rules
+
+- Scan results only prove that files exist; they do not prove file content.
+- For `.docx`, `.pptx`, `.xlsx`, and `.pdf`, read the extracted `read_view_path` instead of using Codex/textutil/raw reads of the original file.
+- Extracted images are candidate materials only. Do not interpret them as evidence unless image meaning is explicitly reviewed or supplied by the user.
+- If a user explicitly asks for text-only inspection, report it as degraded intake and do not treat it as complete source review.
 
 ## Markdown Rules
 

package/plugins/revela/skills/revela-make-deck/SKILL.md

@@ -18,15 +18,16 @@ Use this skill when the user asks to make, generate, or update a Revela deck.
 
 1. Call `revela_compile_narrative` and `revela_markdown_qa`.
 2. Report narrative and Markdown diagnostics, but treat only malformed/unsafe files and technical artifact validity as hard blockers.
-3. Call `revela_read_deck_plan` as the required deck-plan preflight before any HTML generation.
-4. If `deck-plan/` is missing or incomplete, author or repair `deck-plan/index.md` and `deck-plan/slides/*.md` before calling `revela_create_deck_foundation`.
-5. Report deck-plan diagnostics before artifact generation, including stale narrative hashes, missing slide projections, missing evidence trace, caveats, or malformed plan files.
-6. Do not start HTML generation from narrative alone unless the user explicitly asks for a throwaway diagnostic smoke deck.
-7. For new HTML files, call `revela_create_deck_foundation`.
-8. Read active design guidance with `revela_design_list` and `revela_design_read` using `section: "rules"` before writing `decks/*.html`; fetch layouts/components/chart rules as needed. If the user asks to switch designs persistently, call `revela_design_activate`; if they ask for a one-off design, read that design by name and pass `designName` to `revela_create_deck_foundation`.
-9. Patch slides into the foundation between Revela slide markers. Preserve positive 1-based `data-slide-index` values. Every slide must use `<section class="slide" ...>` with exactly one direct `.slide-canvas` child.
-10. Generate chapter by chapter. Keep the HTML valid after each write.
-11. After every HTML write, call `revela_run_deck_qa` and repair hard errors before review or export.
+3. Call `revela_design_list`, `revela_design_read` using `section: "rules"`, and `revela_design_inventory` before authoring or repairing `deck-plan/`; deck-plan layout/component names must come from the selected design inventory.
+4. Call `revela_read_deck_plan` as the required deck-plan preflight before any HTML generation.
+5. If `deck-plan/` is missing or incomplete, author or repair `deck-plan/index.md` and `deck-plan/slides/*.md` before calling `revela_create_deck_foundation`; use only inventory-listed layouts/components in slide frontmatter and visual intent.
+6. Report deck-plan diagnostics before artifact generation, including stale narrative hashes, missing slide projections, missing evidence trace, caveats, malformed plan files, or layout/component names outside the active design inventory.
+7. Do not start HTML generation from narrative alone unless the user explicitly asks for a throwaway diagnostic smoke deck.
+8. For new HTML files, call `revela_create_deck_foundation`.
+9. Before patching slide HTML, read the specific layouts/components used by the deck plan with `revela_design_read_layout` and `revela_design_read_component`; fetch `section: "chart-rules"` and the `echart-panel` component before creating or changing ECharts. If the user asks to switch designs persistently, call `revela_design_activate`; if they ask for a one-off design, read that design by name, call `revela_design_inventory` with that name, and pass `designName` to `revela_create_deck_foundation`.
+10. Patch slides into the foundation between Revela slide markers. Preserve positive 1-based `data-slide-index` values. Every slide must use `<section class="slide" ...>` with exactly one direct `.slide-canvas` child.
+11. Generate chapter by chapter. Keep the HTML valid after each write.
+12. After every HTML write, call `revela_run_deck_qa` and repair hard errors before review or export.
 
 ## Generated Visual Assets