add-dataverse

1> **Plugin check**: Run `node "${PLUGIN_ROOT}/scripts/check-version.js"` - if it outputs a message, show it to the user before proceeding.
2 
3**📋 Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first.
4 
5# Add Dataverse
6 
7**App root:** before any project read or command, execute
8[app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
9Use its resolved absolute `working_dir` for every shell call and file tool,
10including referenced commands and delegated skills; never inherit a prior `cd`.
11 
12**Entry routing:** use the shared [App feature entry points](../../shared/shared-instructions.md#app-feature-entry-points)
13preflight before the workflow below.
14 
15**Invocation scope:** follow [Data-source invocation scope](../../shared/shared-instructions.md#data-source-invocation-scope)
16before the workflow below. Standalone calls use this skill's own data-delta
17approval and verification; do not start a full-app plan or screen workflow.
18 
19An existing plan alone does not mean it includes or approves the new request;
20never replay the old Data Model instead of resolving the requested delta.
21 
22**Removal branch:** after resolving invocation scope, `--remove` or an approved app-binding
23removal executes
24[data-source-removal.md](../../shared/references/data-source-removal.md), then
25returns without entering Steps 1-9. Removing a plan row is not implemented by
26…