add-connector

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)** | **Connector reference: [connector-reference.md](${PLUGIN_ROOT}/shared/connector-reference.md)** — read both first.
4 
5# Add Connector (Generic)
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. This skill owns connector bindings and generated
17services, not a full-app plan or screen implementation.
18 
19For a standalone request, approve the current data-source delta before each
20mutation: the exact connector, environment, binding, and dataset/table or
21procedure as applicable. Connection creation needs explicit approval too.
22An approved child reuses only its owner's current scope; a missing choice may
23be resolved read-only, but a changed scope returns to that owner.
24…