Replace ct or ./dist/ct with deno task ct in docs

Author: bfollington

.claude/agents/pattern-dev-guide.md

@@ -7,7 +7,7 @@ color: orange
 You are an expert CommonTools pattern development guide specializing in helping users create, modify, and network patterns using the ct utility. You have deep knowledge of the CommonTools framework, pattern practices, and the ct command-line interface.
 
 **Critical Prerequisites**:
-- Run `./dist/ct --help` and `./dist/ct charm --help` to discover ct binary commands
+- Run `deno task ct --help` and `deno task ct charm --help` to discover ct binary commands
 - You MUST search for and read `COMPONENTS.md` and `RECIPES.md` files in the user's pattern workspace before working on patterns
 - Read `HANDLERS.md` when encountering event handler errors
 - The user should have already run the space setup script or have an existing space
@@ -68,13 +68,13 @@ When working with UI handlers, ensure users understand:
 
 **Command Quick Reference**:
 You should be fluent in all ct commands:
-- `ct charm getsrc/setsrc` - Get/update pattern source
-- `ct dev [pattern] --no-run` - Test syntax
-- `ct charm new` - Create new charm
-- `ct charm link` - Connect charms
-- `ct charm inspect` - View charm details
-- `ct charm get/set` - Manipulate cell data
-- `ct charm ls` - List all charms
+- `deno task ct charm getsrc/setsrc` - Get/update pattern source
+- `deno task ct dev [pattern] --no-run` - Test syntax
+- `deno task ct charm new` - Create new charm
+- `deno task ct charm link` - Connect charms
+- `deno task ct charm inspect` - View charm details
+- `deno task ct charm get/set` - Manipulate cell data
+- `deno task ct charm ls` - List all charms
 
 **Error Handling Approach**:
 - Parse and explain syntax errors clearly

.claude/agents/research-specialist.md

@@ -7,7 +7,7 @@ color: pink
 
 You are a research specialist with expertise in systematic codebase investigation and technical analysis. Your role is to conduct thorough, methodical research on any topic or question using all available tools and resources.
 
-**CRITICAL FIRST STEP**: Run `./dist/ct --help` and `./dist/ct charm --help` to understand available ct commands.
+**CRITICAL FIRST STEP**: Run `deno task ct --help` and `deno task ct charm --help` to understand available ct commands.
 
 **Your Research Methodology**:
 

.claude/commands/link-github.md

@@ -24,10 +24,10 @@ This command finds GitHub URLs in page.tsx charms and creates linked GitHub repo
 ### Step 1: Find Page Charms
 ```bash
 # List all charms
-./dist/ct charm ls --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME]
+deno task ct charm ls --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME]
 
 # For each charm, check if it's a page by trying to get its outline
-./dist/ct charm get --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [CHARM_ID] outline
+deno task ct charm get --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [CHARM_ID] outline
 
 # If this returns data with a 'root' structure, it's a page charm
 ```
@@ -37,10 +37,10 @@ For each page charm:
 ```bash
 # IMPORTANT: For efficiency, especially when re-scanning, use jq to avoid pulling massive attachment data
 # Get only nodes with empty attachments (unlinked URLs)
-./dist/ct charm get --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [CHARM_ID] outline | jq '.root.children[].children[] | select(.attachments == []) | {body: .body, path: path(.)}'
+deno task ct charm get --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [CHARM_ID] outline | jq '.root.children[].children[] | select(.attachments == []) | {body: .body, path: path(.)}'
 
 # Or for a specific path to avoid large JSON responses:
-./dist/ct charm get --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [CHARM_ID] outline | jq '.root.children[0].children[3]'
+deno task ct charm get --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [CHARM_ID] outline | jq '.root.children[0].children[3]'
 
 # Look for patterns like: https://github.com/[owner]/[repo]
 ```
@@ -49,17 +49,17 @@ For each page charm:
 For each unique GitHub URL found:
 ```bash
 # Create new github-repo-fetcher charm
-./dist/ct charm new --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] [RECIPES_PATH]/github-repo-fetcher.tsx
+deno task ct charm new --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] [RECIPES_PATH]/github-repo-fetcher.tsx
 
 # Set the repoUrl input (note the double quotes in the echo)
-echo '"https://github.com/owner/repo"' | ./dist/ct charm set --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [NEW_CHARM_ID] repoUrl --input
+echo '"https://github.com/owner/repo"' | deno task ct charm set --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] --charm [NEW_CHARM_ID] repoUrl --input
 ```
 
 ### Step 4: Link to Page Attachments
 For each node containing a GitHub URL:
 ```bash
 # Link the github fetcher charm to the node's attachments array at index 0
-./dist/ct charm link --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] [GITHUB_FETCHER_CHARM_ID] [PAGE_CHARM_ID]/[PATH_TO_NODE]/attachments/0
+deno task ct charm link --identity [IDENTITY_FILE] --api-url [API_URL] --space [SPACE_NAME] [GITHUB_FETCHER_CHARM_ID] [PAGE_CHARM_ID]/[PATH_TO_NODE]/attachments/0
 
 # Example path: charm1/outline/root/children/1/attachments/0
 ```
@@ -101,24 +101,24 @@ When searching:
 
 ```bash
 # Step 1: List charms
-./dist/ct charm ls --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev
+deno task ct charm ls --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev
 # Returns: charm1, charm2, charm3
 
 # Step 2: Check each for outline
-./dist/ct charm get --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev --charm charm1 outline
+deno task ct charm get --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev --charm charm1 outline
 # Returns outline data - this is a page charm!
 
 # Step 3: Found https://github.com/vercel/next.js in outline/root/children/0/body
 
 # Step 4: Create fetcher
-./dist/ct charm new --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev ~/code/recipes/recipes/github-repo-fetcher.tsx
+deno task ct charm new --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev ~/code/recipes/recipes/github-repo-fetcher.tsx
 # Returns: newcharm123
 
 # Step 5: Configure fetcher
-echo '"https://github.com/vercel/next.js"' | ./dist/ct charm set --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev --charm newcharm123 repoUrl --input
+echo '"https://github.com/vercel/next.js"' | deno task ct charm set --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev --charm newcharm123 repoUrl --input
 
 # Step 6: Link to page
-./dist/ct charm link --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev newcharm123 charm1/outline/root/children/0/attachments/0
+deno task ct charm link --identity ~/dev/.ct.key --api-url https://toolshed.saga-castor.ts.net --space 2025-08-06-ben-dev newcharm123 charm1/outline/root/children/0/attachments/0
 ```
 
 ## Summary Output

.claude/commands/todos.md

@@ -19,9 +19,9 @@ Direct todo management using CommonTools:
 - Space: Use date-based naming like `2025-07-15-claude-dev` (format: YYYY-MM-DD-claude-dev)
 
 **Quick CT Commands:**
-- READ: `./dist/ct charm get [params] --charm [id] [path]`
-- SET: `echo '[value]' | ./dist/ct charm set [params] --charm [id] [path]`
-- CALL: `echo '[json]' | ./dist/ct charm call [params] --charm [id] [handler]`
+- READ: `deno task ct charm get [params] --charm [id] [path]`
+- SET: `echo '[value]' | deno task ct charm set [params] --charm [id] [path]`
+- CALL: `echo '[json]' | deno task ct charm call [params] --charm [id] [handler]`
 
 **Todo Operations:**
 - Add item: `echo '{"title": "text"}' | ct charm call [params] --charm [id] addItem`

.claude/page-manager-helper.sh

@@ -27,42 +27,33 @@ Use this skill for:
 
 ```bash
 # Top-level commands
-./dist/ct --help
+deno task ct --help
 
 # Charm subcommands
-./dist/ct charm --help
+deno task ct charm --help
 
 # Specific command details
-./dist/ct charm get --help
-./dist/ct charm link --help
-./dist/ct dev --help
+deno task ct charm get --help
+deno task ct charm link --help
+deno task ct dev --help
 ```
 
 **Why this matters:** The tool's `--help` output is the authoritative source of truth. As new features are added or flags change, `--help` stays current automatically.
 
-## Running CT: Binary vs Source
+## Running CT
 
-The `ct` command can be run in two ways:
+The `ct` command is run via:
 
-**1. As a compiled binary (recommended for production):**
 ```bash
-./dist/ct [command]
+deno task ct [command]
 ```
 
-Verify the binary exists with `ls -la ./dist/ct`. If missing, build it:
-```bash
-deno task build-binaries --cli-only
-```
+This is the recommended approach for all users. If you use `ct` frequently, you can create a shell alias:
 
-**2. From source (for active development):**
 ```bash
-deno task ct [command]
+alias ct="deno task ct"
 ```
 
-Use this when actively developing the ct tool itself.
-
-**Default approach:** Try `./dist/ct` first; if the binary doesn't exist, use `deno task ct`.
-
 ## Prerequisites and Setup
 
 ### Identity Management
@@ -74,19 +65,19 @@ ls -la claude.key
 
 If missing, create one:
 ```bash
-./dist/ct id new > claude.key
+deno task ct id new > claude.key
 ```
 
 To get the DID (Decentralized Identifier):
 ```bash
-./dist/ct id did claude.key
+deno task ct id did claude.key
 ```
 
 ### Recipe Development Setup
 
 When working in a recipes repository, initialize TypeScript support:
 ```bash
-./dist/ct init
+deno task ct init
 ```
 
 This creates/updates `tsconfig.json` with proper type definitions.
@@ -110,15 +101,15 @@ Use `ct dev` for rapid iteration during recipe development:
 
 ```bash
 # Type check and execute
-./dist/ct dev ./recipe.tsx
+deno task ct dev ./recipe.tsx
 
 # Type check only (no execution)
-./dist/ct dev ./recipe.tsx --no-run
+deno task ct dev ./recipe.tsx --no-run
 ```
 
 **Discover more options:**
 ```bash
-./dist/ct dev --help
+deno task ct dev --help
 ```
 
 ### 2. Deploying and Managing Charms
@@ -131,7 +122,7 @@ Use `ct dev` for rapid iteration during recipe development:
 
 **Discover commands:**
 ```bash
-./dist/ct charm --help
+deno task ct charm --help
 ```
 
 ### 3. Reading and Writing Charm Data
@@ -163,13 +154,13 @@ Linking creates reactive data flow between charms:
 
 **Example pattern:**
 ```bash
-./dist/ct charm link -i claude.key -a https://toolshed.saga-castor.ts.net/ -s space \
+deno task ct charm link -i claude.key -a https://toolshed.saga-castor.ts.net/ -s space \
   sourceCharmID/emails targetCharmID/emailData
 ```
 
 **Discover linking options:**
 ```bash
-./dist/ct charm link --help
+deno task ct charm link --help
 ```
 
 ### 5. Visualizing Space Architecture
@@ -178,10 +169,10 @@ Use `ct charm map` to understand charm relationships:
 
 ```bash
 # ASCII map
-./dist/ct charm map -i claude.key -a https://toolshed.saga-castor.ts.net/ -s space
+deno task ct charm map -i claude.key -a https://toolshed.saga-castor.ts.net/ -s space
 
 # Graphviz DOT format (for visualization tools)
-./dist/ct charm map -i claude.key -a https://toolshed.saga-castor.ts.net/ -s space --format dot
+deno task ct charm map -i claude.key -a https://toolshed.saga-castor.ts.net/ -s space --format dot
 ```
 
 ## Common Patterns and Gotchas
@@ -202,13 +193,13 @@ All values passed to `set` and `call` must be valid JSON:
 
 ```bash
 # Strings (note the nested quotes)
-echo '"hello world"' | ./dist/ct charm set ... title
+echo '"hello world"' | deno task ct charm set ... title
 
 # Numbers
-echo '42' | ./dist/ct charm set ... count
+echo '42' | deno task ct charm set ... count
 
 # Objects
-echo '{"name": "John"}' | ./dist/ct charm set ... user
+echo '{"name": "John"}' | deno task ct charm set ... user
 ```
 
 ### Error Handling
@@ -220,7 +211,7 @@ echo '{"name": "John"}' | ./dist/ct charm set ... user
 - JSON parse error → Check JSON formatting (proper quotes, no trailing commas)
 
 **Debugging steps:**
-1. For recipe errors: Run `./dist/ct dev [recipe] --no-run` to check syntax
+1. For recipe errors: Run `deno task ct dev [recipe] --no-run` to check syntax
 2. For connection issues: Verify Tailnet connection for `*.ts.net` URLs
 3. For data issues: Use `ct charm inspect` to examine charm state
 4. For linking issues: Use `ct charm map` to visualize connections

.claude/skills/ct/SKILL.md

@@ -12,7 +12,7 @@ CommonTools provides well-known IDs for accessing system-level data within a spa
 
 **Example:**
 ```bash
-./dist/ct charm link --identity claude.key --api-url https://toolshed.saga-castor.ts.net/ --space [space] baedreiahv63wxwgaem4hzjkizl4qncfgvca7pj5cvdon7cukumfon3ioye [target-charm]/allCharms
+deno task ct charm link --identity claude.key --api-url https://toolshed.saga-castor.ts.net/ --space [space] baedreiahv63wxwgaem4hzjkizl4qncfgvca7pj5cvdon7cukumfon3ioye [target-charm]/allCharms
 ```
 
 **Use Cases:**