v0.13.0 — the pane lands in YOUR window

The map pane now opens beside the conversation that asked for it — even with several Windows Terminal windows open.

Why it went wrong before: the agent's shell isn't attached to your terminal window (no WT_SESSION), so wt -w 0 sp split the most recently used window — i.e. wherever you last clicked.

What's new

• scripts/open-pane.mjs: identifies the WT window hosting the session (ancestor walk + AttachConsole + a console-title nonce — the nonce only lights up when the session tab is the window's active tab, so identification doubles as the split precondition), brings it to the foreground through a verified cascade (plain SetForegroundWindow → Alt-key unlock → AttachThreadInput), and only then splits.
• Deterministic fallback: if the window can't be identified or focused (tab inactive, screen locked, not hosted in WT), the map opens in a dedicated window named mellos-mapping — never a random window.
• --window: open the dedicated window on purpose (map on a second monitor, separate from the chat).
• One watcher per map file: repeated /mmap no longer piles up panes (--force overrides).

/mellos-mapping:mmap and the Codex/manual routes all go through the launcher on Windows; tmux and printed-command routes are unchanged.