Update to NaCl

{
  "description": "Render, package, ship, release, deploy, or publish NaCl outputs with explicit external-write authorization and verified evidence.",
  "included_files": [
    {
      "relative_path": "resources/nacl-tl-core/references/remote-mode-coordination.md",
      "size_in_bytes": 4625
    },
    {
      "relative_path": "resources/references/skills-only-runtime-contract.md",
      "size_in_bytes": 7181
    },
    {
      "relative_path": "resources/references/workflow-gateway-contract.md",
      "size_in_bytes": 6832
    },
    {
      "relative_path": "resources/references/workflow-gateway-map.json",
      "size_in_bytes": 13477
    },
    {
      "relative_path": "resources/workflows/nacl-publish/SKILL.md",
      "size_in_bytes": 5706
    },
    {
      "relative_path": "resources/workflows/nacl-render/SKILL.md",
      "size_in_bytes": 2849
    },
    {
      "relative_path": "resources/workflows/nacl-tl-deploy/SKILL.md",
      "size_in_bytes": 5514
    },
    {
      "relative_path": "resources/workflows/nacl-tl-release/SKILL.md",
      "size_in_bytes": 12180
    },
    {
      "relative_path": "resources/workflows/nacl-tl-ship/SKILL.md",
      "size_in_bytes": 6181
    }
  ],
  "name": "nacl-publish",
  "skill_md_contents": "---\nname: nacl-publish\ndescription: Render, package, ship, release, deploy, or publish NaCl outputs with explicit external-write authorization and verified evidence.\n---\n\n# NaCl Publish\n\nRead [the Skills-only runtime contract](resources/references/skills-only-runtime-contract.md),\n[the publish workflow](resources/workflows/nacl-publish/SKILL.md), and\n[the render workflow](resources/workflows/nacl-render/SKILL.md).\nFor graph-derived evidence, require a loaded project `nacl_neo4j` MCP and verified\nread canary; otherwise return `BLOCKED/PROJECT_MCP_NOT_CONFIGURED` and route to\n`nacl-init`.\n\nRoute to one packaged publish/release leaf. Use only project-local Neo4j MCP\ntools. Preserve release lease/fence/revision, confirmation, read-back and\nrelease. Every Git, deployment, documentation, messaging or other external\nwrite requires separate explicit user authority. Missing graph evidence never\nbecomes release success.\n"
}