kandev-canvas-authoring

# Kandev canvas authoring Use one `read_canvas_authoring_skill_kandev` call without `path` when you need the authoring contract. That response is the complete core bundle. It includes this workflow, the manifest and browser protocol summary, appearance rules, the minimal scaffold, and the exact supporting-file inventory. Do not read the core bundle again during the same authoring task. ## Required workflow 1. Call `create_canvas_kandev` with a short title and an application summary. It creates an inactive task canvas and returns its source directory, manifest scaffold, initial permission policy, and exact scaffold inventory. 2. Use native file tools in that returned directory. The initial files are `manifest.yaml`, `index.html`, `appearance.js`, `script.js`, and `styles.css`. Replace or extend them in the same directory. 3. Keep every source path relative to the returned directory. Do not write outside it. Bundle executable dependencies. Node, a package manager, and a network build step are not available at runtime. 4. Run local checks, then call `publish_canvas_kandev` with the returned canvas ID and source path. Read validation diagnostics and correct rejected source before publishing again. The first valid release of a new owner-authorized task canvas uses the returned initial permission policy. It can activate without a second approval for its declared supported permissions. Kandev data access is limited to the current workspace, while the canv...