Update FlowStudio Power Automate skills (#1664)

* feat(flowstudio): align Power Automate skills with MCP server v1.1.6

Foundation skill (flowstudio-power-automate-mcp) rewritten to use the
server's new tool_search and list_skills meta-tools (v1.1.5+) for
discovery instead of cataloging every tool by hand. Cut from 519 to
295 lines. New "Which Skill to Use When" intent-keyed decision tree
points at the four specialized skills.

Build/debug/governance/monitoring updated for use-case framing. Tools
that genuinely cross tiers (e.g. debug skill borrowing
get_store_flow_summary) are correct when the workflow needs them — the
split between skills is by use-case intent, not by tool partition.

Build skill: new Step 3a Resolving Dynamic Connector Values covers
get_live_dynamic_options outer-parameter auto-bridge (v1.1.6+) and the
AadGraph user-picker fallback via shared_office365users.SearchUserV2
(replaces broken builtInOperation:AadGraph.GetUsers).

Debug skill: Outlook user-picker failure note pointing at the fallback.

Monitoring skill description disambiguates from the server's monitor-flow
tool bundle (runtime control of a single flow) — this skill is
tenant-wide health analytics over the cached store.

All 5 skills validate via npm run skill:validate; line endings LF only;
codespell clean; auto-regenerated docs/README.skills.md included.

* fix(flowstudio): remove deprecated tool references

The v1.1.5 MCP server release marked 5 tools [DEPRECATED] but the
previous alignment commit missed them. Replacements per server source:

- get_live_flow_http_schema → read trigger.inputs.schema from get_live_flow
- get_live_flow_trigger_url → read trigger.metadata.callbackUrl from get_live_flow
- get_store_flow_trigger_url → get_store_flow.triggerUrl field
- get_store_flow_errors → get_store_flow_runs(status=["Failed"])
- set_store_flow_state → set_live_flow_state

Touches build, debug, governance, monitoring SKILL.md and the
foundation skill's tool-reference.md. Remaining mentions of the
deprecated names are intentional — they live in deprecation notices
naming the obsolete wrapper alongside its replacement.

* Update FlowStudio Power Automate skills

* Cover latest FlowStudio MCP actions

* Trim FlowStudio Power Automate skills

* Number FlowStudio build workflow steps

skills/flowstudio-power-automate-build/references/action-patterns-connectors.md

@@ -132,6 +132,10 @@ Result reference: `@body('Get_SP_Item')?['FieldName']`
 }
 ```
 
+> `PatchItem` can validate required SharePoint columns even when you are not
+> changing those fields. Echo unchanged required fields from the trigger or a
+> prior Get Item action, for example `item/Title`, and use internal field names.
+
 ---
 
 ### SharePoint — File Upsert (Create or Overwrite in Document Library)
@@ -286,6 +290,10 @@ SharePoint REST API via the `HttpRequest` operation:
 > The `HttpRequest` operation reuses the existing SharePoint connection — no extra
 > authentication needed. Use this when the standard Update Item connector can't
 > reach the target list (different site collection, or you need raw REST control).
+> Keep the connector-specific parameter names exactly as shown:
+> `parameters/method`, `parameters/uri`, `parameters/headers`, and
+> `parameters/body`. The body is a JSON string, and `parameters/uri` is relative
+> to the SharePoint `dataset`.
 
 ---
 
@@ -340,6 +348,22 @@ the file; the flow downloads and filters it for before/after comparisons.
 
 ---
 
+## Excel Online
+
+### Excel — Run Office Script
+
+Office Script actions require real workbook and script identifiers at save time.
+Do not deploy placeholder `scriptId` values; `update_live_flow` can fail during
+dynamic operation validation even before a test run exists.
+
+Use `describe_live_connector` or `get_live_dynamic_options` when available, or
+ask the user for the workbook and script if they are not discoverable. If a real
+`scriptId` still cannot be resolved, ask the user to add the Run script action
+once in the designer, then read the flow definition and preserve the resolved
+parameters.
+
+---
+
 ## Outlook
 
 ### Outlook — Send Email
@@ -479,6 +503,20 @@ For 1:1 ("Chat with Flow bot"), use `"location": "Chat with Flow bot"` and set
 
 ---
 
+## Copilot Studio
+
+### Copilot Studio — Invoke Agent
+
+When using the Copilot Studio connector, publish the agent before running the
+flow. Draft/test agents can exist in the studio canvas but still be unavailable
+or stale through the flow connector endpoint.
+
+If a connector action fails with an unavailable-agent or endpoint-style error,
+publish the agent, wait briefly for propagation, then resubmit the same flow run
+before changing the flow definition.
+
+---
+
 ## Approvals
 
 ### Split Approval (Create → Wait)