@lofcz/pptist 2.0.15 → 2.0.16

package/dist/embed/agentic-manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@lofcz/pptist",
-  "packageVersion": "2.0.15",
-  "generatedAt": "2026-06-17T04:24:25.505Z",
+  "packageVersion": "2.0.16",
+  "generatedAt": "2026-06-17T07:32:10.879Z",
   "summary": "Authoring guidance for the PPTist agentic bridge. The recommended way to build a deck from scratch: (1) pick ONE visual identity with styles.catalog -> deck.applyStyle (academic | minimal | bold | playful), then (2) for each slide pick a recipe from layouts.catalog and add it with slides.createFromLayout({ layoutId, slots }) — the engine themes, positions AND auto-fits every text box (via responsive measurement) so content never overflows. Author slot content as Markdown/plain text or structured values (arrays for bullets, { labels, series } for charts) — never hand-written HTML. Alternative: for pixel-perfect branded decks, use the built-in templates flow (deck.applyTemplate + slides.insertFromTemplate). Avoid blank slides.create / hand-placed elements unless neither a layout nor a template slide fits. Pair this with the machine schema (command payload/return types) in the same manifest.",
   "commandCount": 177,
   "designSystem": {
@@ -540,12 +540,11 @@
     {
       "name": "slides.createFromLayout",
       "domain": "slides",
-      "payload": "{ layoutId: string; slots?: Record<string, unknown>; index?: number; select?: boolean; backgroundMode?: PptistLayoutBackgroundMode }",
+      "payload": "PptistCreateFromLayoutInput",
       "returns": "PptistCreateFromLayoutResult",
-      "optional": true,
       "doc": {
         "summary": "Build + insert a themed slide from a layout id and content slots. The PREFERRED way to add a slide when building from scratch.",
-        "details": "The engine positions every element on the canvas, colors it from the active style preset (theme.styleId), and AUTO-FITS each text box's font size (responsive measurement) so text never overflows — you never pick coordinates, sizes, or colors. Author slot content as Markdown/plain text (titles, bullets, body) or structured values (arrays of strings for bullets; { labels, series, legends } for charts; rows for comparison). Returns the new slideId plus the created element ids.",
+        "details": "The engine positions every element on the canvas, colors it from the active style preset (theme.styleId), and AUTO-FITS each text box's font size (responsive measurement) so text never overflows — you never pick coordinates, sizes, or colors. Author slot content as Markdown/plain text (titles, bullets, body) or structured values (arrays of strings for bullets; { labels, series, legends } for charts; rows for comparison). Slot text supports inline math: wrap formulas in $…$ (inline) or $$…$$ (display) and they typeset via MathML (e.g. a bullet 'Příklad: $\\frac{3}{8} > \\frac{1}{8}$'). Write math this way inside the text — do NOT spell it as plain text and do NOT add a separate latex element for math that belongs in a sentence or bullet. Returns the new slideId plus the created element ids.",
         "params": [
           {
             "name": "layoutId",
@@ -1024,7 +1023,7 @@
       "returns": "PPTTextElement",
       "doc": {
         "summary": "Create a text element (manual placement). Author content as Markdown via `markdown` (recommended) or plain text via `content`.",
-        "details": "Pass `markdown` for formatted copy (the bridge converts it to the HTML PPTist stores). `content` is treated as literal markup — pass plain text there, or intentional HTML only when you specifically want to render markup (e.g. a code snippet). Do NOT type raw HTML tags into `markdown`: they are escaped and appear as literal text (the bridge warns when it detects this). The fallback color/font come from defaultColor/defaultFontName.",
+        "details": "Pass `markdown` for formatted copy (the bridge converts it to the HTML PPTist stores). Markdown supports inline math: $…$ (inline) and $$…$$ (display) typeset via MathML, so mix prose and formulas freely (e.g. 'Plocha je $\\pi r^2$'). `content` is treated as literal markup — pass plain text there, or intentional HTML only when you specifically want to render markup (e.g. a code snippet). Do NOT type raw HTML tags into `markdown`: they are escaped and appear as literal text (the bridge warns when it detects this). The fallback color/font come from defaultColor/defaultFontName.",
         "params": [
           {
             "name": "slideId",
@@ -1954,6 +1953,7 @@
     "PptistChartElementPatch": "export interface PptistChartElementPatch { chartType?: ChartType; data?: ChartData; options?: ChartOptions; fill?: PPTChartElement['fill']; outline?: Partial<NonNullable<PPTChartElement['outline']>>; themeColors?: string[]; textColor?: string; lineColor?: string }",
     "PptistCreateAudioInput": "export interface PptistCreateAudioInput extends PptistAudioElementPatch { id?: string; source?: PptistAudioSourceInput; slideId?: string; index?: number; select?: boolean }",
     "PptistCreateChartInput": "export type PptistCreateChartInput = PptistChartElementPatch & Partial<Pick<PPTChartElement, 'id' | 'left' | 'top' | 'width' | 'height' | 'rotate'>> & { slideId?: string; index?: number; select?: boolean }",
+    "PptistCreateFromLayoutInput": "export interface PptistCreateFromLayoutInput { layoutId: string; slots?: Record<string, unknown>; index?: number; select?: boolean; backgroundMode?: PptistLayoutBackgroundMode }",
     "PptistCreateFromLayoutResult": "export interface PptistCreateFromLayoutResult { slideId: string; layoutId: string; elementIds: string[]; textElementIds: string[] }",
     "PptistCreateLatexElementInput": "export interface PptistCreateLatexElementInput { slideId?: string; index?: number; element: PptistLatexElementInput; select?: boolean }",
     "PptistCreateLineElementInput": "export interface PptistCreateLineElementInput { slideId?: string; index?: number; element: PptistLineElementInput; select?: boolean }",