add-sample-data

> **Plugin check**: Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"` — if it outputs a message, show it to the user before proceeding. # Add Sample Data Populate Dataverse tables with sample records via OData API so users can test and demo their Power Pages sites. ## Core Principles - **Respect insertion order**: Always insert parent/referenced tables before child/referencing tables so lookup IDs are available when needed. - **Use TaskCreate/TaskUpdate**: Track all progress throughout all phases -- create the todo list upfront with all phases before starting any work. - **Fail gracefully**: On insertion failure, log the error and continue with remaining records -- never attempt automated rollback. **Initial request:** $ARGUMENTS --- ## Phase 1: Verify Prerequisites **Goal**: Confirm PAC CLI auth, acquire an Azure CLI token, and verify API access **Actions**: 1. Create todo list with all 6 phases (see [Progress Tracking](#progress-tracking) table) 2. Follow the prerequisite steps in `${CLAUDE_PLUGIN_ROOT}/references/dataverse-prerequisites.md` to verify PAC CLI auth, acquire an Azure CLI token, and confirm API access. Store the environment URL as `$envUrl`. **Output**: Authenticated session with valid token and confirmed API access --- ## Phase 2: Discover Tables **Goal**: Find the custom tables available in the user's Dataverse environment **Actions**: ### Path A: Read `.datamodel-manifest.json` (Preferred) Check if `.datamodel-manifest.json` exist...