@dboio/cli 0.19.0 → 0.19.2

package/plugins/claude/track/skills/changelog/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: changelog
+description: >-
+  Changelog and Track API logging instructions. Load this skill at SessionStart
+  or any time Claude needs to know when and how to write changelog.md entries
+  and submit log entries to the Track task_log API. Applies to all projects
+  unless the local CLAUDE.md explicitly opts out.
+user-invokable: false
+---
+
+# Changelog & Track Logging
+
+Track all changes made by Claude across sessions. Log entries **after** making changes, not before.
+
+## Opt-out
+
+If the current project's CLAUDE.md (or any CLAUDE.md in the directory hierarchy) contains an explicit directive such as **"Do not write changelog entries or call the Track API for this project"** or **"Skip all changelog.md writes and Track API calls"**, honour it and do not log anything for that project. The local directive overrides these instructions.
+
+## When to log
+
+- **Always**: after writing or editing source files in any project
+- **Additionally for DBO apps** (has `.dbo/` or `.app/config.json`): after pushing any asset to the server
+
+## File location
+
+- `<project-memory-dir>/changelog.md`
+- The project memory directory is the per-project auto-memory path shown in the session context (e.g., `~/.claude/projects/<encoded-path>/memory/`)
+- If `changelog.md` does not exist, create it with the header row before adding the first entry
+
+## Format
+
+```
+| Date | Time | Asset Type | Name | UID | Description |
+|------|------|-----------|------|-----|-------------|
+| YYYY-MM-DD | HH:MM | type | Name | uid | Short description |
+```
+
+- **Date**: `YYYY-MM-DD`
+- **Time**: `HH:MM` in the user's local timezone (24-hour format)
+- **DBO projects**: Asset Type from `_entity` in the metadata JSON (output, content, entity, security, site, etc.)
+- **Non-DBO projects**: Asset Type is the file role (e.g., view, model, controller, service, config). UID column can be left as `---`
+- **Description**: 50–75 chars max, focus on *why* not *what*
+
+## Track API — Remote task_log
+
+In addition to the local `changelog.md`, write each log entry to the centralized Track `task_log` table via the REST API. This applies from **any project**, not just Track itself.
+
+### Auth
+
+- Cookie file: `~/.claude/track-cookies.txt`
+- To log in: user runs `~/.claude/track-changelog` in a terminal
+- Track domain: `beta-track.dbo.io`
+
+### Session check (run once per session, before the first log entry)
+
+```bash
+curl -s -b ~/.claude/track-cookies.txt 'https://beta-track.dbo.io/api/o/asqor6nmxuiwqbhldlki7g'
+```
+
+- Returns a JSON array with `ContactID`, `FirstName`, etc. → session is valid; use the `ContactID` value for all log entries this session
+- Returns `[]` → **not logged in**. Tell the user: "Track Access Denied. Run `~/.claude/track-changelog` and try again." Do NOT retry or attempt to log in on their behalf.
+
+### Writing a log entry
+
+```bash
+curl -s -b ~/.claude/track-cookies.txt \
+  'https://beta-track.dbo.io/api/input/submit?_confirm=true' \
+  --data-urlencode 'RowID:add1;column:todoes.task_log.ContactID=<ContactID from session>' \
+  --data-urlencode 'RowID:add1;column:todoes.task_log.AssistantContactID=27' \
+  --data-urlencode 'RowID:add1;column:todoes.task_log.Date=_{now}' \
+  --data-urlencode 'RowID:add1;column:todoes.task_log.Summary=<summary, max 100 chars>' \
+  --data-urlencode 'RowID:add1;column:todoes.task_log.Description=<detailed description>'
+```
+
+Field notes:
+- **ContactID**: from the session check response (the human user's ID)
+- **AssistantContactID**: always `27` (Claude's fixed Contact ID in Track)
+- **Date**: `_{now}` — the server resolves this to the current datetime
+- **Summary**: short title of what was done, max 100 chars
+- **Description**: detailed explanation of why/how the change was made; can be longer. ASCII only — no unicode arrows, emoji, or non-ASCII characters
+- **TaskID**: include if the work relates to a known task: `--data-urlencode 'RowID:add1;column:todoes.task_log.TaskID=<id>'`
+- **TimeID**: omit (a server trigger will associate it automatically)
+
+### Error handling
+
+- If the API returns `"Successful": false` or an HTTP error, write the entry to `changelog.md` anyway and warn the user about the Track API failure
+- If the session expires mid-conversation (403 or `[]` on a subsequent check), tell the user to re-run `~/.claude/track-changelog`

package/src/commands/clone.js

@@ -1095,34 +1095,8 @@ export async function performClone(source, options = {}) {
   const effectiveDomain = options.domain || config.domain;
   let appJson;
 
-  // Fetch schema if missing, explicitly requested, or server has a newer version
+  // Load local schema (server fetch deferred until after auth validation)
   let schema = await loadSchema();
-  let shouldFetch = !schema || options.schema;
-  if (!shouldFetch && schema) {
-    try {
-      shouldFetch = await isSchemaStale({ domain: effectiveDomain, verbose: options.verbose });
-      if (shouldFetch) log.dim(`  Server schema is newer — refreshing _system dependency baseline`);
-    } catch {
-      // Can't check — continue with local schema
-    }
-  }
-  if (shouldFetch) {
-    try {
-      schema = await fetchSchema({ domain: effectiveDomain, verbose: options.verbose });
-      await saveSchema(schema);
-      log.dim(`  Refreshed _system dependency baseline`);
-    } catch (err) {
-      if (!schema) log.warn(`  Could not fetch schema: ${err.message}`);
-      // Continue with stale schema or null
-    }
-  }
-
-  // Regenerate metadata_schema.json for any new entity types
-  if (schema) {
-    const existing = await loadMetadataSchema();
-    const updated = generateMetadataFromSchema(schema, existing ?? {});
-    await saveMetadataSchema(updated);
-  }
 
   // Step 1: Source mismatch detection (skip in pull mode)
   // Warn when the user provides an explicit source that differs from the stored one.
@@ -1148,7 +1122,9 @@ export async function performClone(source, options = {}) {
     }
   }
 
-  // Step 2: Load the app JSON — retry loop with fallback prompt on failure
+  // Step 2: Load the app JSON — retry loop with fallback prompt on failure.
+  // This runs BEFORE schema/dependency sync so that the login prompt fires
+  // here if the session is expired (not buried inside a silent dependency clone).
   let activeSource = source;
   while (true) {
     try {
@@ -1178,6 +1154,35 @@ export async function performClone(source, options = {}) {
     throw new Error('Invalid app JSON: missing UID or children');
   }
 
+  // Fetch schema if missing, explicitly requested, or server has a newer version.
+  // Runs AFTER app fetch so that login prompt fires first on expired session.
+  let shouldFetchSchema = !schema || options.schema;
+  if (!shouldFetchSchema && schema) {
+    try {
+      shouldFetchSchema = await isSchemaStale({ domain: effectiveDomain, verbose: options.verbose });
+      if (shouldFetchSchema) log.dim(`  Server schema is newer — refreshing _system dependency baseline`);
+    } catch {
+      // Can't check — continue with local schema
+    }
+  }
+  if (shouldFetchSchema) {
+    try {
+      schema = await fetchSchema({ domain: effectiveDomain, verbose: options.verbose });
+      await saveSchema(schema);
+      log.dim(`  Refreshed _system dependency baseline`);
+    } catch (err) {
+      if (!schema) log.warn(`  Could not fetch schema: ${err.message}`);
+      // Continue with stale schema or null
+    }
+  }
+
+  // Regenerate metadata_schema.json for any new entity types
+  if (schema) {
+    const existing = await loadMetadataSchema();
+    const updated = generateMetadataFromSchema(schema, existing ?? {});
+    await saveMetadataSchema(updated);
+  }
+
   // Domain change detection
   if (effectiveDomain) {
     const { changed, proceed } = await checkDomainChange(effectiveDomain, options);

package/plugins/claude/dbo/skills/cli/SKILL.md

@@ -1,97 +0,0 @@
----
-name: cli
-description: Run DBO.io CLI commands for local file sync, project management, and deployment (push/pull/clone/add/rm/diff/build/deploy). NOT for direct API operations — use docs/ for that.
-allowed-tools: Read, Write, Glob, Bash(git status:*), Bash(git branch:*), Bash(git diff:*), Bash(ls:*), Bash(dbo init:*), Bash(dbo login:*), Bash(dbo status:*), Bash(dbo deploy:*), Bash(dbo add:*), Bash(dbo clone:*), Bash(dbo push:*), Bash(dbo pull:*), Bash(dbo diff:*), Bash(dbo rm:*), Bash(dbo mv:*), Bash(dbo run:*), Bash(dbo install:*), Bash(git stash:*), Bash(grep:*), Bash(which dbo:*)
-user-invokable: true
----
-
-# DBO CLI Skill
-
-Run `dbo` CLI commands for local file sync, project management, and deployment.
-
-## When to use this skill
-
-Use this skill when the user wants to:
-- Run a local workflow command (push, pull, clone, add, rm, diff, build, deploy)
-- Set up a project (`dbo init`, `dbo login`, `dbo clone`)
-- Deploy files to the server (`dbo push`, `dbo deploy`)
-
-## When NOT to use this skill
-
-Do NOT use this skill for direct API operations. The following CLI commands are thin wrappers around REST endpoints — use the `docs/` reference instead for the canonical API syntax:
-- `dbo input` wraps `POST /api/input/submit` — use `docs/dbo-cheat-sheet.md`
-- `dbo output` wraps `GET /api/output/` — use `docs/dbo-output-query.md`
-- `dbo content` wraps `GET /api/content/` — use `docs/dbo-cheat-sheet.md`
-- `dbo media` wraps `GET /api/media/` — use `docs/dbo-cheat-sheet.md`
-- `dbo upload` wraps `POST /api/upload/submit` — use `docs/dbo-cheat-sheet.md`
-- `dbo message` wraps `GET /api/message/` — use `docs/dbo-cheat-sheet.md`
-- `dbo cache` wraps `/api/cache/` — use `docs/dbo-cheat-sheet.md`
-
-Also do NOT use this skill for:
-- **Entity schemas / column names** — use `docs/dbo-core-entities.md`
-- **Token/tag syntax** (`#{...}`, `<#_embed>`, etc.) — use `docs/dbo-cheat-sheet.md`
-- **Building server-side templates or content records** — use `docs/`
-
-All doc files are bundled in the `docs/` subdirectory of this plugin (copied during npm publish). When working in the repo, the API docs are at the repo root `docs/` and the CLI README is at `tools/cli/README.md`.
-
-For detailed CLI command flags, options, and behavior — read `docs/dbo-cli-readme.md`.
-
-## Running commands
-
-**If `$ARGUMENTS` is empty**, show the command table and guide interactively.
-
-**If `$ARGUMENTS` is provided**, check if command exists in the command table in the available commands (use best guess, eg: initialize => init), then on match run the command:**:
-
-```bash
-dbo $ARGUMENTS
-```
-
-## Command overview
-
-These are the local workflow commands this skill covers:
-
-| Command | Description |
-|---------|-------------|
-| `init` | Initialize .dbo/ configuration |
-| `login` / `logout` | Authenticate / clear session |
-| `status` | Show config, domain, session info |
-| `clone` | Clone an app to local project |
-| `pull` | Pull records to local files |
-| `push` | Push local changes (default: current dir) |
-| `add` | Add a new file to DBO.io |
-| `diff` | Compare local vs server |
-| `rm` | Remove file, stage server deletion |
-| `deploy` | Deploy via .dbo/deploy_config.json manifest |
-| `build` | Run build hooks (.dbo/scripts.json) |
-| `run` | Run named script (.dbo/scripts.json) |
-| `install` | Install/upgrade CLI, plugins (alias: `i`) |
-
-## Common workflows
-
-```bash
-# Setup
-dbo init --domain my-domain.com --app myapp --clone
-dbo login
-
-# Edit and push
-dbo push                          # push all changes in current dir
-dbo push lib/bins/app/assets/     # push specific directory
-dbo push colors.css               # push single file
-
-# Build and push (with script hooks)
-dbo build                         # run build hooks only
-dbo push                          # build + push (hooks run automatically)
-dbo push --no-build               # push without build phase
-dbo push --no-scripts             # push without any hooks
-
-# Pull
-dbo pull -e content --filter 'AppID=10100'
-
-# Add new files
-dbo add assets/css/newstyle.css
-dbo add .                         # scan for un-added files
-
-# Compare and merge
-dbo diff                          # compare all local vs server
-dbo diff -y                       # auto-accept all server changes
-```