@tenonhq/dovetail-core 0.0.120 → 0.0.122

package/skills/dove-manage-update-sets.md

@@ -68,9 +68,9 @@ The dashboard reads scopes from `dove.config.js` and stores selections in `.dove
 
 `createUpdateSet`, `switchUpdateSet`, and `push --updateSet` now write the affected scope's entry into `.dove-update-sets.json` as part of activating the set, so the routing file, the active set, and the push destination stay consistent. Each prints the resolved destination, e.g. `Push routing updated: x_cadso_core -> FEAT-123 (sys_id)`, and every push prints `Update set routing (from .dove-update-sets.json): <scope> -> <name> (<sys_id>)` so you can see exactly where captures land. If you edit `.dove-update-sets.json` by hand, that entry wins until you switch sets again.
 
-### Multi-Scope Update Set Monitoring
+### Multi-Scope Update Set Check
 
-When using `npx dove watchAllScopes`, update set status is automatically checked every 2 minutes. It warns if any scope is using the DEFAULT update set (a common mistake that puts changes in the wrong place).
+Before every push, run `npx dove currentUpdateSet` for each scope you are about to touch (or open the dashboard with `npx dove dashboard`). A scope still on its DEFAULT update set is a common mistake that puts changes in the wrong place — `push` also prints the resolved routing per scope so you can catch it in the output.
 
 ### Recommended Workflow
 
@@ -79,7 +79,7 @@ When using `npx dove watchAllScopes`, update set status is automatically checked
    npx dove createUpdateSet --name "FEAT-123 Add User Dashboard" --scope x_cadso_core
    ```
 
-2. **During development:** Use `npx dove dev` or `npx dove watchAllScopes`. Changes go into the active update set.
+2. **During development:** Edit locally, then `npx dove push --diff <branch>`. Changes go into the active update set for each file's scope.
 
 3. **Check status:** `npx dove currentUpdateSet` to verify you are in the right update set.
 
@@ -90,5 +90,5 @@ When using `npx dove watchAllScopes`, update set status is automatically checked
 ### Common Issues
 
 - **"No update set selected"** -- You are using the Default update set. Create or switch to a named one.
-- **Changes going to wrong scope** -- In multi-scope mode, use `npx dove watchAllScopes` which auto-switches scopes. Single-scope `npx dove dev` only works for one scope.
+- **Changes going to wrong scope** -- `npx dove push` routes each record by its scope's entry in `.dove-update-sets.json`; a scope with no entry falls back to the session's current scope/set. Map every scope you touch (`createUpdateSet` / `switchUpdateSet --scope <scope>`) before a multi-scope push, and check the file sits under the right scope's `sourceDirectory` and in that scope's `dove.manifest.<scope>.json`.
 - **Update set not found** -- Check the scope filter. Update sets are scope-specific.

package/skills/dove-setup-project.md

@@ -69,8 +69,12 @@ dovetail-debug-*.log
 
 #### Start development
 ```bash
-npx dove dev
+npx dove status              # confirm instance, scope, user
+npx dove refresh             # pull the manifest + files
+# ...edit files...
+npx dove push --diff main    # push only what changed vs the branch
 ```
+Sync is headless and explicit: `refresh` before you start, `push` when you are done. There is no always-on sync step in this flow.
 
 ### Scenario 2: Add a New Scope (Multi-Scope Setup)
 
@@ -102,11 +106,13 @@ If hitting rate limits:
 npx dove initScopes --delay 1000
 ```
 
-#### Watch all scopes simultaneously
+#### Sync across all scopes
 ```bash
-npx dove watchAllScopes
+npx dove refresh                 # all declared scopes
+npx dove refresh -s x_cadso_work # one scope
+npx dove push --diff main        # one command for a multi-scope change
 ```
-Watches all scope directories, auto-switches ServiceNow scope context per file, monitors update set status every 2 minutes.
+`push` reads each file's scope from its manifest and, when `.dove-update-sets.json` maps that scope to an update set (`createUpdateSet` / `switchUpdateSet` write the mapping), routes the record into that scope's set server-side. Map every scope you are about to touch first — the server session scope is only swapped once, to the first file's scope, so an unmapped second scope is the thing to avoid. Confirm with `npx dove currentUpdateSet --scope <scope>` before pushing.
 
 #### Download a single scope
 ```bash
@@ -150,6 +156,6 @@ project/
 | `npx dove initScopes` | Download all configured scopes |
 | `npx dove download <scope>` | Download a specific scope (destructive) |
 | `npx dove refresh` | Refresh manifest, download new files only |
-| `npx dove dev` | Start single-scope watch mode |
-| `npx dove watchAllScopes` | Start multi-scope watch mode |
+| `npx dove push --diff <branch>` | Push only the files changed vs a branch (all scopes) |
+| `npx dove push` | Push every local file (all scopes) |
 | `npx dove status` | Show connected instance, scope, user |

package/skills/dove-troubleshoot-sync.md

@@ -32,11 +32,11 @@ Ask the user which symptom they are experiencing (if not already clear):
 
 ### Diagnostic A: Files Not Pushing
 
-1. **Check dev mode is running:** `npx dove dev` or `npx dove watchAllScopes`
+1. **Push explicitly:** saving a file does not sync it on its own. Run `npx dove push --diff <branch>` (or `npx dove push` for everything) and read the per-file output.
 2. **Check the file is in the manifest:** Look in `dove.manifest.json` or `dove.manifest.<scope>.json` for the table/record/field entry. If missing, run `npx dove refresh`.
 3. **Check file extension matches a rule:** The file extension must match a `match` regex in `dove.config.js` rules. If no rule matches, the file content is pushed as-is (no build).
 4. **Check debug logs:** Re-run the command with `--debug` (or `DOVETAIL_DEBUG=1`) to write a `dovetail-debug-*.log` file in the project root, then inspect it. Debug logs are opt-in — without the flag no log file is produced.
-5. **Try manual push:** `npx dove push` to push all files and see errors.
+5. **Confirm on the instance:** `npx dove status` for the connection, then verify the record changed on the instance — never infer success from the push exit code alone.
 
 ### Diagnostic B: Authentication/Connection Failure
 
@@ -63,7 +63,7 @@ Dovetail checks that your local manifest scope matches the active scope on the S
 
 1. **Check current scope:** `npx dove currentScope`
 2. **Change scope:** `npx dove changeScope --scope x_cadso_core`
-3. **For multi-scope watch:** `npx dove watchAllScopes` handles scope switching automatically per file.
+3. **For multi-scope pushes:** `npx dove push` swaps the server session scope once (to the first file's scope) and routes each record through its scope's update set from `.dove-update-sets.json`. Make sure every scope in the push has a mapping (`npx dove switchUpdateSet --scope <scope> ...`), or push one scope at a time with a path target (`npx dove push src/x_cadso_core`).
 4. **Force scope swap on push:** `npx dove push --scopeSwap`
 
 ### Diagnostic D: Build/Transform Errors