Add FetchXML Generator, PCF, Custom APIs, Copilot tools and multi-component guides (#233)
Five pages the wiki had no coverage of at all, each a step-by-step guide rather than a feature list:
FetchXML Generator — why it works on the literal in your code instead of a separate file, the lens,
answering for placeholders, the results view, the generator, and what "Save to code" guarantees.
Five screenshots from the e2e suite driving the real UI.
PCF Controls — the Field/Dataset and None/React choices and what they mean, the eight card actions,
and when to use the harness versus debugging the deployed control on a live form.
Custom APIs — definition-as-code, generating the handler and the typed client, what the deploy
reconciles, and two honest caveats: Run Custom API is Global-binding-only, and the deploy's
create/update/delete calls are not yet verified against a live environment.
Copilot tools — the five tools, the read-only default, the per-call confirmation, and that no tool
output can carry a secret.
Multi-component repos — what makes a component, why the root owns the connection, how a command
picks its target, and the trap of pasting a connection into a subfolder (it stops following the
root).
Corrections to existing pages: legacy plugin support was removed in 1.0.3 (three pages still promised
"removed in 0.9.0"); the one Windows-only feature is profile CAPTURE, not the spkl path; and the replay
does not use the profiler's assemblies — it decodes the profile with Microsoft.Xrm.Sdk alone, which is
what lets it run in CI.
Upgrading-Projects guide (legacy plugin path, config refresh diffs, version reference); refresh Home/Plugins/Portals/Webresources for pac + cross-platform + 0.7/0.8 features