enable-tables-offline

1**Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first.
2 
3**References:**
4 
5- [offline-profile-schema.md](${PLUGIN_ROOT}/shared/references/offline-profile-schema.md) — entity field map (`IsAvailableOffline`, `ChangeTrackingEnabled`)
6 
7# Enable Tables Offline
8 
9Flip `IsAvailableOffline=true` AND `ChangeTrackingEnabled=true` on the `EntityMetadata` of one or more Dataverse tables, then publish customizations. This is the prerequisite shown in Image 4 of the maker portal ("Can be taken offline" + "Track changes") — without both, a table CANNOT be added to a Mobile Offline Profile.
10 
11Sequential (Dataverse metadata lock) and idempotent: re-running on an already-enabled table is a no-op.
12 
13## Invocation context and root binding
14 
15This internal helper is always a **child invocation**. Before any project read or
16command, execute [app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
17Require the owner's absolute `working_dir`; `--working-dir`, when supplied, must
18identify that same native-canonical root. Missing, relative, or conflicting root
19context returns `NEEDS_CONTEXT` before project access; an inaccessible directory
20is `BLOCKED`. Never use the launch cwd or introduce another root resolver.
21 
22Receive `MOBILE_APP_ORCHESTRATING=1`, `orchestrator: setup-offline-profile`,
23`working_dir`, `phase`, `approved_scope`, and supplied answers. Preserve the
24…