add-table-to-offline-profile

1**Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first.
2 
3**References:**
4 
5- [dataverse-offline-api.md](${PLUGIN_ROOT}/shared/references/dataverse-offline-api.md) §4 + §7 — POST item + PATCH selectedcolumns
6- [offline-profile-reconciliation.md](${PLUGIN_ROOT}/shared/references/offline-profile-reconciliation.md) — the `schemaColumns` baseline written in Step 7
7 
8# Add Table to Offline Profile
9 
10Add a single table to an existing Mobile Offline Profile. Most common flow: user ran `/add-dataverse` to add a new table to their app, now wants that table available offline too.
11 
12Equivalent to running `/setup-offline-profile` and seeing the existing profile (extend-mode), but skips the per-table questionnaire for the tables already in the profile — only configures the new one.
13 
14## Invocation context and root binding
15 
16This internal helper is always a **child invocation**. Before any project read or
17command, execute [app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
18Require the owner's absolute `working_dir`; `--working-dir`, when supplied, must
19identify that same native-canonical root. Missing, relative, or conflicting root
20context returns `NEEDS_CONTEXT` before project access; an inaccessible directory
21is `BLOCKED`. Never use the launch cwd or introduce another root resolver.
22 
23Receive `MOBILE_APP_ORCHESTRATING=1`, `orchestrator`, `working_dir`, `phase`,
24…