add-sample-data

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)** — read first.
4 
5# Add Sample Data
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 media paths and retries; never inherit a prior `cd`.
11 
12Populate Dataverse tables with realistic sample records so a freshly-scaffolded code app shows real-looking data on first launch. Generates rows from each table's schema and inserts them in dependency order. Use after `/add-dataverse` (or `/setup-datamodel`) has created the tables.
13 
14## Core principles
15 
16- **Coverage within approved scope, not the entire manifest.** Cover each eligible
17  approved table with a small useful dataset. The manifest is verified app
18  inventory and can include retiring or unrelated tables; its presence is not
19  permission to seed them. Scope and retirement exclusions override every
20  coverage, fanout, prototype-reuse, media, and retry rule below.
21- **Insertion order matters.** Parent / referenced tables must be inserted before child / referencing tables so lookup IDs are available.
22…