Baixar wmux 3.28.1 per a Windows

Fixed
- The Git tab (worktrees + review roster) now finds the repo an agent is working in, even when the shell it runs in sits elsewhere. Repo context used to come only from the pane's shell working directory — but for an agent pane (Claude / Codex TUI) that is typically the directory the shell was started in (often the home dir), while the agent works in a repo somewhere else. Result: the sidebar showed the branch just fine, yet the Git tab said "not a git repository". Repo resolution now falls back to the hook-reported agent directory (the same value the sidebar branch badge already trusts) when the shell's own directory doesn't resolve to a repo.
- Resume no longer silently downgrades to --continue when the pane's tracked directory is stale. The resume chip/pill only offers the exact --resume <uuid> form (with the recorded permission flag) when the conversation's origin directory matches the pane's live directory — but it compared against the shell's tracked cwd, which goes stale across cd X; claude one-liners (no prompt render in between, so the shell never reports the new directory). A legitimate exact resume was then downgraded to --continue, dropping the permission flag and possibly resuming a different conversation. The match now also accepts the hook-reported agent directory (the same value the sidebar branch badge trusts). Nothing auto-runs either way — the command is only typed, and you press Enter.
- A pane's tracked working directory can no longer be corrupted by terminal output that looks like a shell prompt. Two guards, observed live (a pane's directory stored as the literal token path, which then broke Git-tab repo resolution): once a shell has proven it runs the wmux integration hook (it emitted an OSC 7), prompt-scrape directory detection is permanently disabled for that session — the hook is authoritative, so scraping could only ever add false positives; and scraped values must now be absolute (or ~-anchored) paths on every platform — a bare relative token is never a real working directory.
- The orchestrator can tell a pane that finished from a pane that asked you something. A pane's turn-end reached the orchestrator as "pane stopped" and nothing else, so the only way to learn why it stopped was to read the rendered terminal — where a question the agent printed looks exactly like text sitting in its input box. Orchestrators mis-read that: reporting panes as "still running" while they sat blocked on an unanswered question, and pressing Enter to "submit" a line that was never there. A turn-end now carries the agent's own closing words, lifted from its transcript rather than the screen, and a stop that ends in a question (including Korean endings that carry no ?) is stamped BLOCKED ON A QUESTION with the question quoted — the same treatment reviewer comments already get. The pane's question is also published as pendingQuestion on pane_list, so an orchestrator can check whether a pane is waiting on it without reading the terminal at all. Deliberately not a new agent status: waiting already meant "turn ended", and what was missing was the content, not another state.
- terminal_send_key no longer implies it submitted something. Sending enter returned a bare success whether or not anything was committed, which is what let an orchestrator report a blocked pane as working. Enter presses now come back with an explicit note that delivery is not submission, and the tool description points callers at terminal_send({ text, submit: true }) for answering an agent that is waiting on them.
What's Changed
- fix(macos): sign and notarize the DMG container, not just the app by @openwong2kim in #510
- fix: resolve the agent's real repo when the shell sits elsewhere (Git tab, cwd guards, resume chip) by @openwong2kim in #511
- docs(readme): cover macOS support by @openwong2kim in #512
- fix(deck): tell the orchestrator when a pane is blocked on a question by @openwong2kim in #513
- chore(release): 3.28.1 by @openwong2kim in #514
Full Changelog: v3.28.0...v3.28.1