Update to Arrowgram

{
  "name": "arrowgram",
  "description": "Create, edit, validate, preview, diff, snapshot, and build file-backed Arrowgram diagram or paper workspaces with @hotdocx/arrowgram-agent.",
  "included_files": [],
  "skill_md_contents": "---\nname: arrowgram\ndescription: Create, edit, validate, preview, diff, snapshot, and build file-backed Arrowgram diagram or paper workspaces with @hotdocx/arrowgram-agent.\n---\n\n# Arrowgram\n\nUse this skill when the user asks Codex to create, edit, fix, validate, preview, diff, snapshot, or build an Arrowgram diagram or paper workspace.\n\n## Workspace Model\n\nArrowgram workspaces are file-backed. Treat source files as the editable artifact and generated output as disposable build output.\n\nCommon source files:\n\n- `arrowgram.workspace.json`: workspace manifest.\n- `paper.md`: Markdown paper or slide source.\n- `paper.css`: paper styling.\n- `diagram.json`: standalone diagram source.\n\nDo not edit `dist/` as source. Rebuild it with `arrowgram-agent build`.\n\n## Commands\n\nUse the pinned portable package command from ordinary Arrowgram workspaces:\n\n```bash\nnpx -y @hotdocx/arrowgram-agent@0.1.6 <command> [args...]\n```\n\nKeep this version pin unless the plugin is deliberately upgraded and acceptance-tested against a\nnewer agent release. An unversioned `npx` command follows npm's `latest` tag and is less\nreproducible.\n\nWhen developing inside the Arrowgram monorepo itself, the repo-local helper is also available:\n\n```bash\nnode plugins/arrowgram/scripts/arrowgram-agent.mjs <command> [args...]\n```\n\nDo not assume that repository-relative helper path exists in an arbitrary user workspace.\n\nCore commands:\n\n```bash\nnpx -y @hotdocx/arrowgram-agent@0.1.6 init --type paper --root .\nnpx -y @hotdocx/arrowgram-agent@0.1.6 init --type diagram --root .\nnpx -y @hotdocx/arrowgram-agent@0.1.6 validate --root .\nnpx -y @hotdocx/arrowgram-agent@0.1.6 dev --root . --host 127.0.0.1 --port 4173\nnpx -y @hotdocx/arrowgram-agent@0.1.6 build --root . --out dist\n```\n\n## Workflow\n\n1. Inspect the workspace before editing. Read `arrowgram.workspace.json` first when it exists.\n2. If there is no workspace, initialize one with `init --type paper` unless the user explicitly asks for a standalone diagram.\n3. Edit the whole underlying representation: Markdown, CSS, and JSON source files. Do not attempt to drive the editor UI through granular actions unless the user asks for browser testing.\n4. Validate after source edits with `validate --root .`.\n5. Build static output when the user needs publishable files.\n6. If a dev server is useful, run `dev` and share the local URL. Do not leave a required server session running unintentionally at the end of the task.\n\n## Diagram JSON Guidance\n\nFollow the repository's authoritative schema in `docs/ARROWGRAM_SPEC.md` and `packages/arrowgram/arrowgram.schema.json`.\n\nUse descriptive IDs for nodes and arrows. Use LaTeX labels where appropriate. Preserve existing layout intent unless the user asks for redesign.\n\n## Paper Markdown Guidance\n\nPapers use normal Markdown with optional YAML frontmatter. Embed diagrams as JSON inside:\n\n```html\n<div class=\"arrowgram\">\n{\n  \"nodes\": [],\n  \"arrows\": []\n}\n</div>\n```\n\nReveal-style slides use a line containing only `---` outside code fences.\n\n## Diff And Snapshot Semantics\n\n`arrowgram-agent dev` exposes whole-artifact bridge endpoints under `/__arrowgram`.\n\n- `GET /__arrowgram/status`: current workspace state.\n- `GET /__arrowgram/diff`: source-file diff against the last saved git snapshot when a git baseline is available.\n- `POST /__arrowgram/snapshot`: create a git snapshot for the manifest and referenced source files.\n\nFor normal Codex CLI work, use git diff/status directly when no bridge server is running. Do not invent a Codex-turn baseline.\n\n## Safety\n\n- Keep source edits scoped to the Arrowgram workspace unless the user requests repository changes.\n- Do not commit secrets, API keys, generated `dist/`, or editor caches.\n- Validate JSON with the Arrowgram CLI rather than relying on visual inspection alone.\n- When fixing invalid JSON, preserve user-authored content and formatting where practical.\n"
}