oh-my-agent-commandcode 0.0.0-stage → 20.38.4

package/skills/oma-slide/resources/assets/viewport-base.css

@@ -0,0 +1,257 @@
+/*
+ * viewport-base.css — oma-slide fixed-stage shared CSS
+ *
+ * Usage: paste or <link> into a single-file deck, viewer.html, or any per-slide fragment.
+ * No build step required. Self-contained.
+ *
+ * Stage model: 1920×1080 px authored size.
+ * The entire .deck-stage is scaled uniformly with transform: scale() so it
+ * always fits the viewport while preserving pixel-exact geometry.
+ * Letterbox (horizontal bars) or pillarbox (vertical bars) fill the rest.
+ *
+ * NEVER reflow slides by changing the stage dimensions per viewport.
+ * NEVER use display:none / display:block to hide/show slides —
+ * later layout classes can override those and show all slides at once.
+ * Use .active / .visible (visibility + opacity + pointer-events) instead.
+ */
+
+/* ─── Reset / base ───────────────────────────────────────────────────── */
+*,
+*::before,
+*::after {
+  box-sizing: border-box;
+  margin: 0;
+  padding: 0;
+}
+
+/* ─── Viewport container ─────────────────────────────────────────────── */
+/*
+ * .deck-viewport fills the browser window and provides the black letterbox /
+ * pillarbox background. The stage is absolutely centred inside it.
+ */
+.deck-viewport {
+  position: fixed;
+  inset: 0;
+  width: 100vw;
+  height: 100vh;
+  overflow: hidden;
+  background: #000;
+  display: flex;
+  align-items: center;
+  justify-content: center;
+}
+
+/* ─── Fixed 1920×1080 stage ──────────────────────────────────────────── */
+/*
+ * .deck-stage is always authored at exactly 1920×1080 px.
+ * deck-stage.js calculates scale = Math.min(vw/1920, vh/1080) and applies
+ * transform: scale(scale) here. transform-origin is top-left so the maths
+ * in the JS stays simple (translate the stage to centre manually).
+ *
+ * DO NOT change width/height — that would break the validator's geometry contract.
+ */
+.deck-stage {
+  position: relative;
+  width: 1920px;
+  height: 1080px;
+  transform-origin: top left;
+  /* transform: scale(…) injected by deck-stage.js at runtime */
+  overflow: hidden;
+  background: #fff;
+  /* GPU compositing layer — avoids subpixel paint during scale animation */
+  will-change: transform;
+}
+
+/* ─── Individual slides ──────────────────────────────────────────────── */
+/*
+ * Each .slide is absolutely positioned to fill the entire stage.
+ * Visibility is controlled exclusively via .active and .visible classes —
+ * never via display:none / display:block.
+ *
+ * Base state: invisible and non-interactive.
+ */
+.slide {
+  position: absolute;
+  inset: 0;
+  width: 1920px;
+  height: 1080px;
+  overflow: hidden;
+
+  /* Hidden by default — do NOT change to display:none */
+  visibility: hidden;
+  opacity: 0;
+  pointer-events: none;
+
+  /* Default transition for enter/exit (overridden per-theme) */
+  transition:
+    opacity 0.35s ease,
+    visibility 0s linear 0.35s;
+}
+
+/*
+ * .active — the slide scheduled to be fully visible.
+ * Applied by deck-stage.js when navigating TO this slide.
+ * visibility fires immediately; opacity transitions in.
+ */
+.slide.active {
+  visibility: visible;
+  opacity: 1;
+  pointer-events: auto;
+  transition:
+    opacity 0.35s ease,
+    visibility 0s linear 0s;
+  z-index: 1;
+}
+
+/*
+ * .visible — a slide that was active and is fading out.
+ * Applied briefly during a cross-fade so the outgoing slide stays rendered
+ * while the incoming one fades in.
+ */
+.slide.visible {
+  visibility: visible;
+  opacity: 0;
+  pointer-events: none;
+  transition:
+    opacity 0.35s ease,
+    visibility 0s linear 0.35s;
+  z-index: 0;
+}
+
+/* ─── Nav controls (viewer / viewer.html) ────────────────────────────── */
+/*
+ * Minimal accessible navigation buttons injected by deck-stage.js.
+ * Visible focus states are REQUIRED (WCAG 2.4.7 / 2.4.11).
+ */
+.deck-nav {
+  position: fixed;
+  bottom: 1.5rem;
+  left: 50%;
+  transform: translateX(-50%);
+  display: flex;
+  gap: 0.75rem;
+  z-index: 100;
+  /* Hide during full-screen presentation; show on hover */
+  opacity: 0.15;
+  transition: opacity 0.2s ease;
+}
+
+.deck-nav:hover,
+.deck-nav:focus-within {
+  opacity: 1;
+}
+
+.deck-nav button {
+  appearance: none;
+  border: 2px solid rgba(255, 255, 255, 0.7);
+  background: rgba(0, 0, 0, 0.55);
+  color: #fff;
+  border-radius: 0.375rem;
+  padding: 0.4rem 0.9rem;
+  font-size: 0.875rem;
+  cursor: pointer;
+  line-height: 1;
+  font-family: system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
+}
+
+.deck-nav button:hover {
+  background: rgba(0, 0, 0, 0.8);
+  border-color: #fff;
+}
+
+/* REQUIRED: visible focus ring for keyboard nav */
+.deck-nav button:focus-visible {
+  outline: 3px solid #4af;
+  outline-offset: 2px;
+}
+
+/* ─── Slide counter ──────────────────────────────────────────────────── */
+.deck-counter {
+  position: fixed;
+  bottom: 1.5rem;
+  right: 1.5rem;
+  color: rgba(255, 255, 255, 0.5);
+  font-size: 0.75rem;
+  font-family: system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
+  z-index: 100;
+  letter-spacing: 0.05em;
+  pointer-events: none;
+  user-select: none;
+}
+
+/* ─── Print / Save-as-PDF ────────────────────────────────────────────── */
+/*
+ * Print: one slide per page at design size.
+ * deck-stage.js removes the transform scale so the browser sees
+ * a 1920×1080-equivalent layout. Each slide prints as its own page.
+ */
+@media print {
+  html,
+  body {
+    margin: 0;
+    padding: 0;
+  }
+
+  .deck-viewport {
+    position: static;
+    width: auto;
+    height: auto;
+    overflow: visible;
+    background: transparent;
+    display: block;
+  }
+
+  /*
+   * No !important needed: the only thing that could keep a transform here is the
+   * INLINE scale deck-stage.js applies, and that is cleared at the source on
+   * `beforeprint` — fired by the browser on Ctrl+P and dispatched explicitly by
+   * the headless PDF export (export/pdf.ts) before page.pdf().
+   */
+  .deck-stage {
+    position: static;
+    width: 1920px;
+    height: 1080px;
+    transform: none;
+    overflow: visible;
+    will-change: auto;
+  }
+
+  /* Deck chrome has no competing author/inline rule — plain display:none wins. */
+  .deck-nav,
+  .deck-counter {
+    display: none;
+  }
+
+  /*
+   * Show all slides, each on its own page.
+   *
+   * No !important: in the MERGED viewer/bundle the per-slide author rule
+   * `.slide { position: absolute }` is scoped to `#slide-NN` (id, specificity
+   * 1,0,0) and would outrank this generic `.slide` (0,1,0). Rather than fight it
+   * with !important, the bundler (buildPrintPaginationReset in scope-css.ts)
+   * emits a matching `#slide-NN` reset AFTER the author styles, which wins by
+   * source order at equal specificity. This generic rule remains the baseline
+   * for standalone/unscoped slides and supplies the page-break declarations.
+   */
+  .slide {
+    position: relative;
+    inset: auto;
+    visibility: visible;
+    opacity: 1;
+    pointer-events: none;
+    transition: none;
+    page-break-after: always;
+    break-after: page;
+  }
+
+  /* No trailing blank page: the last slide must not force a page break. */
+  .slide:last-child {
+    page-break-after: auto;
+    break-after: auto;
+  }
+
+  .slide.active,
+  .slide.visible {
+    z-index: auto;
+  }
+}

package/skills/oma-slide/resources/canva-integration.md

@@ -0,0 +1,203 @@
+# Canva MCP Integration — oma-slide
+
+> Optional export/import channel connecting oma-slide decks to Canva via the Canva Remote MCP server.
+> This channel is **never required** — all existing local export paths (HTML, PDF, PNG, PPTX) remain fully functional without it.
+
+## Prerequisites
+
+### Canva Remote MCP Server
+
+- **Endpoint:** `https://mcp.canva.com/mcp`
+- **Transport:** Streamable HTTP (remote MCP)
+- **Authentication:** OAuth 2.0 via Canva Connect — user must authorize the MCP connection through their Canva account.
+
+### MCP Client Configuration
+
+The Canva Remote MCP server must be registered in the project's MCP client configuration.
+Canva uses a **remote URL** transport — no local npm package or binary is required.
+
+The config entry shape (inside `mcpServers`):
+
+```json
+"canva": {
+  "url": "https://mcp.canva.com/mcp"
+}
+```
+
+> **Note (Antigravity CLI):** Some agy versions use `serverUrl` instead of `url` for
+> remote MCP servers. The auto-provisioning step detects the existing convention in
+> the target config file and matches it.
+
+#### Vendor-specific config file locations
+
+| Vendor | Scope | Config file | Key path |
+|--------|-------|-------------|----------|
+| Claude / Cursor | project | `.mcp.json` | `mcpServers.canva` |
+| Gemini VS Code Extension | project | `.gemini/settings.json` | `mcpServers.canva` |
+| Antigravity CLI (agy) | project | `.agents/mcp_config.json` | `mcpServers.canva` |
+| Antigravity CLI (agy) | user global | `~/.gemini/antigravity-cli/mcp_config.json` | `mcpServers.canva` |
+| Antigravity shared | user global (IDE+CLI) | `~/.gemini/config/mcp_config.json` | `mcpServers.canva` |
+| OMA shared | project | `.agents/mcp.json` | `mcpServers.canva` |
+
+All config files use the same `{ "url": "https://mcp.canva.com/mcp" }` shape
+(or `{ "serverUrl": ... }` for Antigravity if that convention is detected).
+
+### Available capabilities
+
+Use the connected server's tool list and parameter schemas as the execution contract.
+Tool availability depends on account permissions, plan, and the current server. Do not
+assume brand-template autofill or a particular export format is available.
+
+## Canva MCP Tool Mapping
+
+The following are names in the official remote server documentation. Client wrappers
+may normalize their names; resolve the callable tools before invoking them.
+
+| Operation | Documented remote tool | Contract |
+|---|---|---|
+| Browse or verify access | `search-designs` | Use the discovered query/filter schema |
+| Read a design | `get-design` | Supply an authorized design ID |
+| Export from Canva | `export-design` | Check supported formats in the tool schema |
+| Import an existing deck | `import-design-from-url` | Requires a URL Canva can retrieve; a local path is not a URL |
+| Upload an image asset | `upload-asset-from-url` | Requires a publicly accessible HTTPS asset URL |
+
+`upload-asset-from-url` uploads an asset; it does not create a presentation or map an
+array of asset IDs to pages. Do not invent a presentation-creation call that maps an asset-ID array to pages,
+or pass a local filepath to a URL-upload tool.
+
+References: [official MCP tools](https://www.canva.dev/docs/apps/mcp/tools/),
+[URL asset upload](https://www.canva.dev/docs/apps/mcp/tools/upload-asset-from-url/).
+
+## Export Pipeline: oma-slide → Canva
+
+Trigger: the user requests a Canva export.
+
+1. Discover the connected tools and probe access with `search-designs` using its schema.
+   On authentication failure, explain the required OAuth connection and retain the local deck.
+2. Produce a local deck with `oma slide export pptx --workspace <deck-dir>`.
+3. If `import-design-from-url` is available, inspect its accepted formats and parameters.
+   Use an existing Canva-readable URL authorized for this transfer. A local filepath cannot
+   be passed to the remote server.
+4. If only local files exist, deliver the PPTX for manual Canva import or resolve a suitable
+   transfer destination with the user. Do not publish the file or enable public sharing merely
+   to satisfy the remote tool's URL requirement.
+5. Follow the tool's returned status/job schema. Report the returned Canva design URL only
+   after the complete deck has imported. A missing or failed page makes the transfer incomplete;
+   report it rather than silently skipping slides.
+
+PPTX output is raster-backed: each slide is a PNG, so importing it does not make text
+editable. Editable Canva content requires a separately supported editing workflow.
+
+## Import Pipeline: Canva → oma-slide
+
+Trigger: the user supplies a Canva design URL/ID or requests an import.
+
+1. Resolve the design ID from the supplied URL or use `search-designs` when browsing is needed.
+2. Read the design with `get-design` and inspect available export formats.
+3. Request PPTX through `export-design` when supported. Follow its returned status and download
+   URL schema; do not assume a fixed polling API.
+4. Download the completed export into `<workdir>/imports/`, then use
+   `oma slide import pptx <downloaded.pptx> --workspace <deck-dir>`.
+5. Use the imported content as the base for any requested revision. If PPTX is unavailable,
+   explain the supported alternatives before changing format.
+
+## Browse Pipeline
+
+Use `search-designs` with the user's query and present matching titles/URLs. Continue
+with the selected design only within the requested operation's scope.
+
+## Error Handling
+
+| Error | Response |
+|---|---|
+| Server not configured | Offer the setup below when Canva was requested |
+| OAuth or permission failure | Explain the missing access; retain local outputs |
+| Local filepath supplied to URL tool | Use an authorized reachable URL or deliver a local file for manual import |
+| Unsupported import/export format | Report the capability limit and supported alternatives |
+| Transfer or job failure | Report the incomplete transfer; do not present skipped pages as success |
+| Design not found | Show the requested ID and optionally search with the supplied query |
+
+---
+
+## Auto-Provisioning: Canva MCP Setup
+
+When the skill detects that Canva MCP is not configured and the user has requested a Canva
+operation, the skill **offers** to add the Canva MCP entry to the project config files.
+
+### Detection
+
+The skill checks for the `canva` key in `mcpServers` across known config files:
+
+```
+Project-level:
+1. .agents/mcp.json                               (OMA shared SSOT)
+2. .agents/mcp_config.json                         (Antigravity CLI project-scoped config)
+3. .mcp.json                                       (Claude / Cursor project config)
+4. .gemini/settings.json                            (Gemini VS Code Extension project settings)
+
+User-global (optional, only if project-level is absent):
+5. ~/.gemini/antigravity-cli/mcp_config.json        (agy CLI global config)
+6. ~/.gemini/config/mcp_config.json                 (Antigravity shared IDE+CLI config)
+```
+
+If `canva` is absent from **all** project-level files, the skill surfaces a setup prompt.
+User-global files are checked as a fallback — if Canva is configured globally but not
+in the project, the skill notifies instead of re-provisioning.
+
+### Setup Prompt
+
+Ask the user:
+> "Canva MCP is not configured in this project. Would you like me to add it to your
+>  MCP config files? This adds `{ "url": "https://mcp.canva.com/mcp" }` to
+>  mcpServers — no local packages are installed."
+
+Options:
+- **Yes, add to all config files** — write to all detected config files
+- **Yes, add to current vendor only** — write to the active vendor's config only
+- **No, skip Canva** — proceed without Canva; use local exports
+
+### Provisioning Steps
+
+For each target config file:
+
+1. **Read** the existing JSON file.
+2. **Parse** and verify it has a `mcpServers` object.
+3. **Add** the `canva` entry:
+   ```json
+   "canva": {
+     "url": "https://mcp.canva.com/mcp"
+   }
+   ```
+4. **Write** the updated JSON back with the same formatting (2-space indent).
+5. **Verify** the file is valid JSON after write.
+
+### Post-Provisioning
+
+After writing config files:
+
+1. **Notify the user** that a session restart may be needed for the MCP client to pick up
+   the new server. Some runtimes (e.g., Gemini CLI) require a restart; others hot-reload.
+2. **Attempt a probe** (`search-designs` using the discovered schema) — if it succeeds, continue with the Canva operation.
+   If it fails (expected on first run before OAuth), notify:
+   > "Canva MCP config added. You'll need to authenticate with Canva on first use.
+   >  The OAuth flow will be triggered automatically by your MCP client."
+3. **Record the setup** through the configured session-memory capability when available. If it is
+   unavailable, rely on the existing config file after checking it before any future prompt.
+
+### Config File Safety
+
+- **Never overwrite** an existing `canva` entry — if it exists with different settings, skip.
+- **Never modify** non-`mcpServers` fields in any config file.
+- **Backup** is not created (JSON merge is additive and reversible by removing the key).
+- **`.agents/` SSOT rule**: the skill writes to `.agents/mcp.json` and `.agents/mcp_config.json`
+  only when the user explicitly approves. This is a config-level change, not a skill definition change.
+
+---
+
+## Security Considerations
+
+1. **OAuth tokens are managed by the MCP client** — the skill never handles or stores Canva credentials.
+2. **Design data is sent to Canva through the MCP server** — the skill only sends/receives files and metadata.
+3. **Uploaded assets are stored in the user's Canva account** — the skill does not control retention or sharing.
+4. **No Canva API calls outside MCP** — all Canva interactions go through the registered MCP server tools.
+5. **Auto-provisioning is user-approved** — the skill never writes MCP config without explicit user consent.

package/skills/oma-slide/resources/checklist.md

@@ -0,0 +1,46 @@
+# Pre-Delivery Checklist — oma-slide
+
+Run this gate after Phase 5 (Review) and before Phase 6 delivery (bundle/export).
+Every item maps to a SKILL.md guardrail or the validator contract in `fixed-stage.md`.
+
+## Gate (must pass)
+
+- [ ] `oma slide validate --workspace "$DECK_DIR" --output json` passes, or the surfaced diff was explicitly approved by the user after 3 auto-fix iterations
+- [ ] Every slide root carries `data-om-validate` (validator contract)
+- [ ] All slides authored at the fixed 1920×1080 stage in px units (no vw/vh/% layout)
+- [ ] All `<img src>` / `<video src>` point to local `./assets/<file>` only — no remote URLs
+- [ ] `meta.json` is current: `{ title, order[], style, density, speakerNotes }` matches the actual `slide-NN.html` set
+
+## Accessibility
+
+- [ ] Nav controls have visible focus states (`.deck-nav button:focus-visible`)
+- [ ] CJK text present → Pretendard font included on those slides
+
+## Delivery artifacts
+
+<!-- oma-docs:ignore-start -->
+- [ ] `oma slide bundle --workspace "$DECK_DIR"` produced `out/deck.html` and it opens in a browser
+<!-- oma-docs:ignore-end -->
+- [ ] If `./assets/` contains video: user was warned the bundle is not fully self-contained
+- [ ] PPTX export (if requested) labeled **experimental** in user-facing output
+- [ ] Canva export (if performed): design URL included in the delivery summary
+
+## Delivery summary (Phase 6c)
+
+<!-- oma-docs:ignore-start -->
+- [ ] Reported: workdir path, slide file list, `out/deck.html` path, export paths, validate status
+<!-- oma-docs:ignore-end -->
+- [ ] Reported: any `TODO(oma-deferred)` items (e.g., unresolved image generation placeholders)
+
+## Native PPTX route (`resources/native-pptx.md`)
+
+Replaces the HTML gate above when Phase 0 selected `native-pptx`.
+
+- [ ] ppt-master resolved from the runtime catalog or `bunx skills use`; source, version, and `SKILL_DIR` recorded
+- [ ] Bundle complete and `$SKILL_DIR/scripts/attribution_guard.py` exited 0
+- [ ] Python packages installed only after explicit user consent (or already present)
+- [ ] Upstream final quality gate passed for the selected route
+- [ ] PPTX present under `<project>/exports/`; project under `.agents/results/slides/<session-id>/`
+- [ ] AI images came from oma-image via Path B, or the user explicitly chose another path
+- [ ] No upstream file was copied, vendored, or edited
+- [ ] Delivery summary lists the PPTX path, upstream version, route and gates, and image sources