docs: fix inaccurate MCP standalone target guidance in create workflow prompt (#520)

The note in Step 8 incorrectly stated that only containerized MCPs (with
`container:`) work in the standalone target. In fact, both containerized
MCPs and remote HTTP MCPs (with `url:`) are fully supported in standalone.

The generate_mcpg_config function in src/compile/common.rs handles both
transports via build_stdio_mcpg_server and build_http_mcpg_server, and
both standalone.rs and onees.rs call the same function.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: github-actions[bot]

prompts/create-ado-agentic-workflow.md

@@ -226,7 +226,7 @@ mcp-servers:
 
 > **Security**: All `mcp-servers:` entries must have an explicit `allowed:` list.
 >
-> **Standalone target** (the default): MCPs without a `container:` or `url:` field are skipped at compile time with a compile-time warning — they have no effect and will not be available to the agent. For the standalone target, use only **custom** containerized MCPs with a `container:` field.
+> **Standalone target** (the default): MCPs without a `container:` or `url:` field are skipped at compile time with a compile-time warning — they have no effect and will not be available to the agent. Both containerized MCPs (with `container:`) and remote HTTP MCPs (with `url:`) are supported in standalone target.
 
 ### Step 9 — Safe Outputs