@rwoll/canvas-kit 0.1.0 → 0.1.1

package/README.md

@@ -1,9 +1,29 @@
 # @rwoll/canvas-kit
 
-Build Copilot canvas extensions with TypeScript and React. A canvas is an
-interactive panel that the agent opens with `open_canvas` and drives with
-`invoke_canvas_action`. A canvas package declares its state and actions once, and
-the kit supplies everything else.
+**Copilot canvases you can change, test, and share.** Build the release boards,
+triage queues, and review tools that you and your agent work in together: state
+and actions in TypeScript, UI in React, and canvas-kit handles the rest.
+
+- **React components.** Typed hooks wire your components to live state; share them
+  across canvases to stay on brand.
+- **Live, two-way canvases.** The agent's changes appear instantly, it reads yours,
+  and a button can hand it the next task.
+- **Saved, shared documents.** One board per repository: every chat on the release
+  updates it, and tomorrow's chat picks up where today's left off.
+- **Scheduled jobs.** Refresh pull request checks every 15 minutes or prune last
+  week's triaged tests, even with no chat open. Users can pause or retime them.
+- **A fast dev loop.** Preview changes live in your browser with no reinstalling,
+  then test as the agent and the user with Playwright.
+- **Share with one push.** `git push` publishes your canvases, skills, agents, and
+  MCP servers for your users to install in two commands.
+
+For a one-off view, plain HTML is fine. canvas-kit is for canvases you keep and
+share. See the [project README](https://github.com/rwoll/canvas-kit#readme) for
+screenshots and example canvases.
+
+A canvas is an interactive panel that the agent opens with `open_canvas` and
+drives with `invoke_canvas_action`. A canvas package declares its state and
+actions once, and the kit supplies everything else. This guide covers the API.
 
 ## Quickstart
 
@@ -251,15 +271,19 @@ so it is safe while chats have the canvas open.
 
 ```sh
 # In a canvas package after `pnpm build`, or with --plugin for an installed plugin
-npx canvas-kit run
-npx canvas-kit run prune_triaged --plugin ~/.copilot/installed-plugins/my-marketplace/flaky-tests
+npx @rwoll/canvas-kit run
+npx @rwoll/canvas-kit run prune_triaged --plugin ~/.copilot/installed-plugins/my-marketplace/flaky-tests
 ```
 
+In a canvas package, `npx` runs the `@rwoll/canvas-kit` it installed; elsewhere it
+downloads it. Always give the scoped name: the unscoped `canvas-kit` on npm is a
+different package.
+
 Run it at least as often as the shortest interval users may pick. For example,
 every 15 minutes with cron (`crontab -e`):
 
 ```text
-*/15 * * * * cd ~/canvases/flaky-tests && npx canvas-kit run >> /tmp/flaky-tests-jobs.log 2>&1
+*/15 * * * * cd ~/canvases/flaky-tests && npx @rwoll/canvas-kit run >> /tmp/flaky-tests-jobs.log 2>&1
 ```
 
 Or with a launchd agent on macOS, in `~/Library/LaunchAgents/com.example.flaky-tests-jobs.plist`, loaded
@@ -273,7 +297,7 @@ with `launchctl load ~/Library/LaunchAgents/com.example.flaky-tests-jobs.plist`:
   <key>Label</key><string>com.example.flaky-tests-jobs</string>
   <key>WorkingDirectory</key><string>/Users/me/canvases/flaky-tests</string>
   <key>ProgramArguments</key>
-  <array><string>/opt/homebrew/bin/npx</string><string>canvas-kit</string><string>run</string></array>
+  <array><string>/opt/homebrew/bin/npx</string><string>@rwoll/canvas-kit</string><string>run</string></array>
   <key>StartInterval</key><integer>900</integer>
 </dict>
 </plist>

package/cli/release.json

@@ -1,4 +1,4 @@
 {
-  "commit": "52402d766586ecddd90e25b9769d12c65fa9cb15",
-  "tag": "v0.1.0"
+  "commit": "cabdbbe7f0cf60228d8e6e04bdf1fbe9841f1e14",
+  "tag": "v0.1.1"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rwoll/canvas-kit",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Build Copilot canvas extensions with TypeScript and React: typed state and actions, a secure local host, a Vite build, test helpers, and marketplace publishing.",
   "keywords": [
     "copilot",