Plugin check: Run node "${PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Migrate Power Pages Web API Wildcards

Replace every deprecated Webapi/<table>/fields = * value with the smallest explicit column set proven by the site's actual Web API behavior.

The LLM owns source discovery, call-chain reasoning, field decisions, report writing, and edits. Use the bundled script only to retrieve authoritative Dataverse table schema; it must not decide which columns the code needs.

Support both:

• traditional sites with HTML, JavaScript, Liquid, web templates, and aggregate YAML;
• SPA sites with React, Vue, Angular, Astro, TypeScript, downloaded deployment YAML, or mixed custom JavaScript.

Initial request: $ARGUMENTS

Non-negotiable rules

1. Review every discovered source table Web API call, including shared wrappers, dynamic builders, and response consumers.
2. Review every configuration scope and deployment-profile copy.
3. Map request EntitySetName values to setting logical names using table schema. Never singularize, pluralize, or guess.
4. Treat * as unsupported for reads, writes, aggregates, FetchXML, files, and images.
5. Give every wildcard an exact proposed replacement before editing anything.
6. Report every already-explicit fields setting, including missing and potentially unnecessary columns.
7. Never apply a partial wildcard plan. Resolve all wildcards and call-site rows first.
8. Keep reports free of absolute local paths, tokens, URLs, data values, filter literals, request bodies, response bodies, and source snippets, and build them only by rendering the bundled template with the bundled script.
9. Preserve unrelated YAML structure and values.
10. Verify with a fresh discovery pass, not remembered inventory.
11. Leave only the rendered report and its icon in the migration output directory.
12. Never download or upload site content until the user has explicitly confirmed the environment, website, site type, data model, and deployment profile. Neither transfer can be reverted.
13. Run smoke tests only after explicit approval, and never issue POST, PATCH, PUT, or DELETE Web API calls against a deployed site. Testing a write destroys real record data.

Read references/column-analysis.md before analyzing calls. Read references/configuration-and-reporting.md before inventorying settings or writing the report. Read references/site-transfer.md before any download or upload.

Phase 1: Prepare

Goal: Resolve the project, confirm the site, and protect existing work.

1. Create all seven tasks from Progress tracking.
2. Resolve PROJECT_ROOT from $ARGUMENTS or the current directory.
3. Detect site markers independently:
   • powerpages.config.json indicates an SPA site;
   • root website.yml, root sitesetting.yml, or .powerpages-site/ indicates downloaded declarative artifacts;
   • when both appear, scan both layouts.
4. Read .solution-manifest.json when present. This migration changes existing settings; do not create or select another solution.
5. Inspect git status. Never discard, hide, or include unrelated user changes.
6. Run node --version.
7. Confirm assets/migration-report-template.html and scripts/render-migration-report.js are readable, and stop if either is missing.
8. Read references/site-transfer.md, then confirm the environment, website name and WebSiteId, site type, data model, deployment profile, and target path with the user. Check each against pac auth who, pac env who, and pac pages list, and stop on any mismatch. Never infer one from a folder name or an active default.

Analyzing the wrong site produces confident, wrong fixes, so settle identity before reading any setting. Download only when the user wants a fresh copy or PROJECT_ROOT holds no site content; downloading replaces local files and cannot be reverted.

🚦 Gate (consent · migrate-webapi-selectall:1.download-site): Approve the download only after displaying the confirmed environment, website name and ID, site type, data model, target path, and the exact command. Canceling leaves local content untouched and continues against the existing copy.

Use AskUserQuestion: Download the confirmed site or Use the local copy. Repeat step 3 after any download.

Output: Project root, site layouts, solution context, git state, confirmed site identity, and a downloaded copy when approved.

Phase 2: Build the complete inventory

Goal: Find every configuration and candidate source Web API call before reasoning about columns.

2.1 Inventory configuration scopes

Use Glob, Grep, and Read to inspect:

• every sitesetting.yml;
• every *.sitesetting.yml;
• .powerpages-site/site-settings/;
• deployment-profile and environment-specific copies.

Record every Webapi/<table>/fields and Webapi/<table>/enabled entry with its relative file, line, scope, key style, and current value. Classify fields settings as:

• wildcard;
• explicit;
• missing for an enabled table;
• duplicate only within the same configuration scope.

Do not treat identical settings in different deployment profiles as duplicates. Record every profile name and which settings it overrides. Never assume the default profile is the intended deployment profile.

Query Dataverse once per unique table, never once per configuration.

2.2 Inventory source calls

Analyze only authoritative, editable source files. Never inspect compiled or generated code.

For SPA sites:

1. Read powerpages.config.json, package.json, and present framework or bundler configuration before searching calls.
2. Treat compiledPath and every configured build-output directory as a hard exclusion.
3. Exclude .powerpages-site/web-files/, node_modules/, coverage and cache directories, source maps, minified bundles, framework output directories, and content-hashed assets matching <entry-name>-<content-hash>.<extension>.
4. Use .powerpages-site/site-settings/ only for configuration inventory, never for source analysis.
5. Search editable roots such as configured source directories and framework application directories.

For traditional sites, search editable JavaScript, Liquid, web templates, web files, and other authored source. Do not exclude an authored traditional web file merely because it is deployed as a web file.

Search source extensions including .js, .jsx, .ts, .tsx, .vue, .html, .htm, .liquid, .aspx, .ascx, .cshtml, and XML web templates. If a call exists only in compiled, minified, generated, or content-hashed output, record a missing-source blocker and stop the migration. Do not infer columns from that output.

Search for:

• /_api/, encoded variants, split URL fragments, and API base constants;
• fetch, Axios, XMLHttpRequest, jQuery AJAX, webapi.safeAjax, shell.ajaxSafePost, and custom request wrappers;
• entity-set constants, query builders, FetchXML builders, and body builders;
• callers and consumers imported from other files.

For each source candidate, record relative path, line, method, endpoint expression, and wrapper chain. A comment, example, or non-table endpoint still needs an explicit disposition. Excluded build outputs are never recorded.

Write the settings inventory to docs/webapi-selectall-migration/migration-report.json and render the draft report as described in references/configuration-and-reporting.md. Do not propose fields yet.

Stop if any in-scope source or configuration file cannot be read.

🚦 Gate (plan · migrate-webapi-selectall:2.confirm-scope): Confirm the project, configuration scopes and profiles, wildcard count, explicit-setting count, and source inventory before schema retrieval. Canceling leaves only the read-only draft report.

Use AskUserQuestion to confirm or cancel. Expand the inventory and repeat this phase if the user identifies another source or deployment scope.

Phase 3: Retrieve schema and resolve columns

Goal: Use authoritative names while letting the LLM determine actual usage.

3.1 Retrieve only relevant table schema

Build the initial unique list containing:

• logical table names from all Web API settings;
• entity-set names from all candidate table calls;
• entity-set names directly present in bind targets or related-table calls.

Do not treat a navigation-property name as a table identifier. Its target logical name is authoritative only after relationship metadata resolves it.

Resolve the environment URL from confirmed project context or pac env who. If unavailable, ask for the URL as data gathering; never ask for or accept an access token.

Write every deduplicated identifier, one per line, to docs/webapi-selectall-migration/table-identifiers.txt. Run:

node "${PLUGIN_ROOT}/skills/migrate-webapi-selectall/scripts/query-table-schema.js" --project-root "<PROJECT_ROOT>" --environment-url "<ENVIRONMENT_URL>" --tables-file "<PROJECT_ROOT>/docs/webapi-selectall-migration/table-identifiers.txt" --output "<PROJECT_ROOT>/docs/webapi-selectall-migration/table-schema.json"

If an identifier does not resolve, trace the code or obtain the correct contract; do not guess.

After the initial snapshot:

1. Match every used $expand navigation property against its source table's returned relationship metadata.
2. Collect only target logical names absent from all existing snapshots.
3. Write those names to table-identifiers-pass-<N>.txt and query them to table-schema.pass-<N>.json.
4. Repeat for nested expansion paths until every used navigation segment is resolved.

Treat table-schema.json and all numbered snapshots as one schema package. Never requery a logical table already present in that package, and never launch concurrent schema queries.

Identifier lists and schema snapshots are working files. Keep them until verification finishes, then delete them in Phase 7.

3.2 Analyze every call and consumer

For every source inventory row:

1. Read the complete enclosing function or template block.
2. Trace imported wrappers, URL variables, query builders, body builders, response mappers, types, components, templates, and every caller.
3. Follow conditional branches, spreads, dynamic arrays, and runtime configuration.
4. Map the entity set to its logical table using the schema package.
5. Apply every rule in references/column-analysis.md.
6. Record requirements per owning logical table, not merely per request.
7. Classify the row as mapped, non-table, or not-a-call.
8. Leave the row unresolved if any runtime branch or consumer remains unknown.

One logical table is normally reached from several places. Collect every call site for a table before proposing its fields: duplicated or competing wrappers, per-page scripts, different query shapes, and repeated calls in the same file. A later call site for an already-analyzed table can still add columns, so never stop at the first one.

For normal record GETs without $select, derive output fields from every consumer and propose a source edit adding the smallest explicit projection. Filters, ordering, and other query fields still belong in the fields setting, even when they should not be added to the output projection.

Keep the response projection and fields-setting allowlist as separate sets. Never add a filter-only, order-only, grouping-only, or write-only column to an existing $select unless a response consumer also reads it.

3.3 Build configuration proposals

For each wildcard setting:

1. Union the proven requirements from every call site that reaches that logical table within the applicable site behavior.

2. Validate each proposed name against the schema package.

3. Link every proposed column to source path and line or a user-confirmed external contract.

4. Produce the exact replacement:

   Webapi/<table>/fields = <column-name-1>,<column-name-2>,<column-name-3>
   

5. Keep the proposal unresolved if it is empty or any evidence is incomplete.

For each already-explicit setting:

• compare configured columns with proven required columns;
• classify it as exact, missing required columns, potentially overbroad, or externally justified;
• include an exact proposed fix for every gap;
• do not silently change it.

Update the report. Resolve all wildcard and call-site rows before continuing.

Output: Evidence-complete report with exact wildcard replacements and all already-explicit configurations.

Phase 4: Review the complete plan

Goal: Present the full exposure reduction before edits.

Show:

• wildcard issues found and the exact replacement for each;
• evidence for every proposed column;
• source GETs requiring $select;
• already-explicit settings and any missing or excess columns;
• any missing or duplicate settings found during inventory;
• zero unresolved call sites.

🚦 Gate (consent · migrate-webapi-selectall:4.apply-plan): Approve all wildcard replacements, required source projections, optional explicit-setting hardening, and local edits. Canceling preserves only the report.

Use AskUserQuestion with:

• Apply all wildcard fixes and approved explicit fixes;
• Apply all wildcard fixes only;
• Cancel.

Never offer a subset of wildcard fixes.

Phase 5: Apply approved edits

Goal: Update source projections and every wildcard setting.

1. Use Edit to add approved $select projections. Preserve methods, filters, ordering, expansion, pagination, encoding, Liquid expressions, and error handling.
2. Use Edit to replace every wildcard value in every scope and profile. Preserve identifiers, key names, quoting, indentation, comments, and unrelated values.
3. Apply already-explicit changes only when included in the selected approval.
4. Re-read every changed block immediately and update report status.

If any edit fails or a file changed since review, stop. Do not continue with a partial configuration set and do not perform a broad rollback over user work.

Output: All approved local edits and updated report.

Phase 6: Verify independently

Goal: Prove the migration without trusting prior notes.

1. Repeat Phase 2 discovery from scratch.
2. Confirm every configuration scope contains zero Webapi/<table>/fields wildcard values.
3. Compare each migrated value with its approved exact replacement.
4. Reopen every call site and replay the coverage analysis:
   • mapped table and method remain correct;
   • required setting columns are present;
   • normal record GETs use explicit $select;
   • expanded, lookup, write, FetchXML, file, and image columns remain covered.
5. Run the existing project build for SPA sites. For traditional sites, inspect edited JavaScript and Liquid syntax and use existing site tests when available.
6. Finalize the report status and every entry status, then delete the previous migration-report.html and re-render it from the updated data file.

Do not claim full hardening while explicit configuration gaps remain. Use the partial status defined in the reporting contract when applicable.

Output: Final report and verified local migration.

Phase 7: Deploy and summarize

Goal: Publish only verified changes.

Re-confirm every identity detail in references/site-transfer.md with the user immediately before uploading, and display the exact command. Select the deployment profile the user reviewed, and use default only when they name it. Any change of environment, website, data model, or profile requires a separate deployment approval.

🚦 Gate (final · migrate-webapi-selectall:7.deploy): Approve the verified migration for the displayed environment, website, site type, data model, and deployment profile. Canceling preserves local edits and the final report without changing the live site.

Use AskUserQuestion: Deploy now or Keep local only.

• Re-run pac auth who and pac env who, and stop on any mismatch. pac pages upload-code-site accepts no --environment and targets whatever the active authentication profile reports.
• For SPA sites, confirm .powerpages-site contains the approved configuration edits, run the existing production build, then run pac pages upload-code-site --rootPath "<PROJECT_ROOT>" --siteName "<SITE_NAME>".
• For traditional sites, run pac pages upload --path "<PROJECT_ROOT>" --environment "<ENVIRONMENT>" --modelVersion "<Standard|Enhanced>" --deploymentProfile "<PROFILE>".

Never substitute one upload command for the other. Each corrupts the other site type, and the damage cannot be reverted.

After deployment, list the read paths a smoke test would exercise: GET calls, $select projections, $expand, FetchXML, and aggregates. Never run one unprompted.

🚦 Gate (progress · migrate-webapi-selectall:7.smoke-test): Approve the listed read-path smoke test against the deployed site. Canceling skips it and reports the deployed migration as unverified.

Use AskUserQuestion: Run the read-path smoke test or Skip verification.

Never issue write, file, or image requests. Ask the user to exercise those paths themselves against disposable records.

Treat HTTP 403 responses as evidence to investigate and never restore *. Do not add a column under the prior approval. Return to Phase 3, update the exact plan and report, repeat the Phase 4 approval, independently verify in Phase 6, and obtain a new Phase 7 deployment approval.

Delete every working file created during the migration, keeping only docs/webapi-selectall-migration/migration-report.html and the power-pages-icon.png the renderer places beside it:

• table-identifiers.txt and table-identifiers-pass-<N>.txt;
• table-schema.json and table-schema.pass-<N>.json;
• migration-report.json.

Delete only files this migration created, and confirm the directory holds the report and its icon alone. Skip cleanup while returning to an earlier phase, and delete the regenerated files once that pass finishes.

Record usage by following ${PLUGIN_ROOT}/references/skill-tracking-reference.md with --skillName "MigrateWebapiSelectall".

Summarize wildcard counts, explicit reviews, source edits, report path, verification, deployment, and every path left unverified.

Progress tracking

Create these tasks before Phase 1:

Mark each task in_progress when starting and completed when finished.

Begin with Phase 1: Prepare.