drafted 1.14.20 → 1.14.22

package/install-mcp.sh

@@ -161,7 +161,7 @@ install_portable_node() {
   mkdir -p "$HOME/.drafted"
   node_dir="$HOME/.drafted/node"
   tmp="$(mktemp -d)"
-  filename="$(curl -fsSL https://nodejs.org/dist/latest-v22.x/SHASUMS256.txt | awk "/node-v.*-${platform}-${arch}\\.tar\\.xz/ {print \\$2; exit}")"
+  filename="$(curl -fsSL https://nodejs.org/dist/latest-v22.x/SHASUMS256.txt | awk "/node-v.*-${platform}-${arch}\\.tar\\.xz/ {print \$2; exit}")"
   if [ -z "$filename" ]; then
     fail "Could not find Node.js 22 download for $platform-$arch"
     exit 1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "drafted",
-  "version": "1.14.20",
+  "version": "1.14.22",
   "description": "Drafted — visual thinking surface for humans and AI agents. Renders HTML, markdown, images, and code as frames on a zoomable canvas, with MCP tools for AI agents and real-time sync for humans.",
   "type": "module",
   "files": [

package/plugin/commands/onboard-drafted.md

@@ -8,7 +8,7 @@ Onboard the user to Drafted — a producibles harness that compounds across thre
 This is the over-arching prime command: orient, then seed all three stores so every later session starts smart.
 
 1. **Orient** — in 3-4 lines explain the loop: you *prime* from the harness (the system makes you search the wiki, and auto-loads the project's attached skills, anchors, and layer rules before you work), you *build*, then you *compound* (deposit what you learned). The more it's used, the less searching and the more stable the work.
-2. **Confirm the org** — call `get_org` to list the user's orgs. Confirm which one the harness should be built in — if unsure, ask — then name it explicitly (org=...) on every create in the steps below.
+2. **Name the org** — call `get_org` to list the user's orgs. Confirm which one the harness should be built in — if unsure, ask — then name it explicitly (`org=...`) on every create in the steps below, or bind it once for this session with `get_org(action="use", org="<name>")` and omit it thereafter. Never rely on an "active" org: a project-less create by a multi-org user is refused rather than guessed.
 3. **Seed knowledge** — run the `/drafted:ingest` flow: help the user point at existing business materials (folders, docs, past research) or interrogate them for tacit knowledge, and land durable pages in the wiki.
 4. **Seed procedures** — from those materials and the conversation, surface 1-3 candidate SOPs. For the most valuable, run the `/drafted:create-skill` flow.
 5. **Seed the surface** — run the `/drafted:create-project` flow for the user's immediate piece of work (or a reusable template).