docs(skills): add live-edit-with-studio-pro user skill (mxcli over MCP)

Adds a user-facing skill for the intended deployment: mxcli driving an open
Studio Pro project over the built-in MCP server from the same machine (e.g. an
in-IDE terminal) — no devcontainer, no socat. Covers the hybrid model (local
reads via -p, live writes via MCP), the same-machine connection
(--mcp http://localhost/mcp --mcp-dial localhost:7782, keeping Host: localhost),
what can be changed, the PED-by-default / Concord-only-for-gaps rule, and the
unsaved-in-memory / no-DROP / -p-must-match caveats.

Authored in .claude/skills/mendix/ (the user-skill source) and synced to the
cmd/mxcli/skills/ embed dir via make sync-skills.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ako

.claude/skills/mendix/live-edit-with-studio-pro.md

@@ -0,0 +1,74 @@
+# Live-Editing an Open Studio Pro Project with mxcli (MCP)
+
+Use mxcli to change the model **while Studio Pro has the project open**, with edits
+appearing live in Studio Pro — no save-and-reopen cycle. This is the workflow when
+Claude Code runs on the same machine as Studio Pro (e.g. an in-IDE terminal).
+
+## When to use this skill
+
+- Studio Pro is open on the project and you want mxcli changes to show up live.
+- mxcli and Studio Pro run on the **same machine** (same `localhost`).
+
+If Studio Pro is **not** open, use the normal file-based flow instead
+(`mxcli -p app.mpr -c "..."` with no `--mcp`), which edits the `.mpr` on disk.
+
+## How it works (hybrid: local reads, live writes)
+
+- **Reads** come from the local `.mpr` you pass with `-p`.
+- **Writes** go to Studio Pro's live, in-memory model via its built-in MCP server.
+- Therefore **`-p` MUST be the exact project Studio Pro currently has open**, or
+  reads and writes will describe different projects.
+
+## Connect
+
+Studio Pro's MCP server listens on `localhost:7782` and requires the HTTP
+`Host` header to be `localhost` (a DNS-rebinding guard). Same-machine, **no
+port-forwarding/socat is needed**:
+
+```bash
+mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 \
+      -p /path/to/app.mpr \
+      -c "create entity MyModule.Customer"
+```
+
+`--mcp-dial localhost:7782` keeps the `Host` header `localhost` while dialing the
+port. (Plain `--mcp http://localhost:7782/mcp` may also work if your Studio Pro
+accepts a port-suffixed `Host` — try it; fall back to the `--mcp-dial` form if it
+is rejected.)
+
+Run a script the same way: `mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 -p app.mpr exec changes.mdl`.
+
+## What you can change via MCP
+
+Modules, entities (and attributes), associations, enumerations, view entities,
+microflows, and pages — plus `ALTER PAGE` (INSERT / DROP / REPLACE widgets, SET
+DataSource, SET Layout). New modules and their dependents resolve within the same
+run, so `create module X; create enumeration X.Status (...)` works in one script.
+
+## Two MCP servers — use the built-in one by default
+
+The machine may run two MCP servers:
+
+- **Studio Pro built-in (port 7782)** — model authoring. **Use this by default.**
+- **Concord (port 7783)** — a temporary gap-filler with operational/refactor tools
+  (`delete_document`, `save_all`, `run_app`, `check_model`). **Only** reach for
+  Concord when the built-in server lacks the capability you need.
+
+## Caveats
+
+- **Writes are unsaved.** They land in Studio Pro's in-memory model (shown as
+  unsaved). Save in Studio Pro to persist to disk.
+- **No DROP of standalone documents** (enumeration / microflow / page) through the
+  built-in server — it has no delete tool. Remove them in Studio Pro (or via
+  Concord's `delete_document`).
+- **`-p` must match the open project.** A mismatched `-p` silently reads the wrong
+  model.
+
+## Verify your change
+
+Read it back through the same connection (in-session edits are visible), or look
+in Studio Pro:
+
+```bash
+mxcli --mcp http://localhost/mcp --mcp-dial localhost:7782 -p app.mpr -c "show entities in MyModule"
+```