run-wenlan

# Run wenlan-server (dev) Build: `cargo build -p wenlan-server -p wenlan` (add `-p wenlan-mcp` for the MCP bridge). ## Ports — one allocation, no guessing Three ports exist and they are not interchangeable. Stopping "the isolated daemon" on the wrong one leaves a live daemon behind and reports success. | Port | Owner | Notes | |---|---|---| | 7878 | the user's real daemon | never kill casually, never verify against | | 17878 | manual isolated instance (this skill) | the recipes below | | 17881 | `scripts/smoke-cli.sh` | `PORT=` overrides | | 17882 | `scripts/smoke-mcp.sh` | `PORT=` overrides; runs alongside the CLI smoke | The smokes own their own ports so both can run at once. Do not repoint them at 17878 — a manual daemon and a smoke would then fight over one listener, and the smoke's ownership assertion would fail on a daemon it did not start. ## Isolated instance (default for verification) Never verify against the shared prod daemon on :7878 — dev and prod share the platform data dir by default. Isolating the port and `WENLAN_DATA_DIR` is not enough: the default pages folder is `.wenlan/pages` under the OS user-home, NOT under `WENLAN_DATA_DIR`, so a capture will write into the user's real notes unless `knowledge_path` is set explicitly. Write the scratch `config.json` BEFORE the daemon starts, then read the live value back from `/api/knowledge/path` — the daemon reloads config per request, so a value written afterwards proves nothing about what was already ingeste...