edit-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) — refreshing the `schemaColumns` baseline after a column edit
7 
8# Edit Offline Profile
9 
10Re-run a single piece of an existing profile — change one table's row scope, update the column list, adjust sync frequency, or rename the profile. Avoids the cognitive cost of walking the full /setup-offline-profile wizard for a one-line change.
11 
12Scope: existing profile (read from `<working_dir>/offline-profile.json` or
13`--profile-id`); edits at the table-item granularity. To ADD a new table return to
14the owner for `/add-table-to-offline-profile`; deleting an entire profile is
15outside this helper's scope, not an automatic recovery.
16 
17## Invocation context and root binding
18 
19This internal helper is always a **child invocation**. Before any project read or
20command, execute [app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
21Require the owner's absolute `working_dir`; `--working-dir`, when supplied, must
22identify that same native-canonical root. Missing, relative, or conflicting root
23context returns `NEEDS_CONTEXT` before project access; an inaccessible directory
24…