fix(remote): merge-time fixes for Wake-on-LAN

The MAC-count limit lived in two places that disagreed. RemoteHostSchema.wakeMac's
128-character cap admits seven comma-separated MACs while parseMacList takes at most
four, all-or-nothing, so a five-MAC value validated, was written to remote-hosts.json,
and then resolved to NO wake target: POST /api/sessions/:id/wake answered
"No wake-on-LAN target configured for this host" and the banner offered "Configure WoL"
for a host the user had just configured. MAX_WAKE_MACS now lives in
src/config/remote-wake-limits.ts and both sides refine against it. Its own module
because src/remote-wake.ts is import-fenced to session-routes.ts and server.ts (the
wiring guard that stops a watcher waking a host), and because schemas.ts must not drag
dgram/net/child_process into every request-validating module.

The documented 40 s request budget also omitted the wake's own cost. A `command` target
is bounded by REMOTE_WAKE_COMMAND_TIMEOUT_MS and runs BEFORE the readiness poll, so a
slow one pushed a wakeCommand host's worst case to ~68 s, past the 60 s
proxy_read_timeout the budget exists to stay under. _wakeAndWait now subtracts the
wake's measured elapsed time from the readiness budget, floored at one poll interval so
a wake that ate the whole budget still gets one probe. A magic packet is effectively
instant and is unaffected, which is why live testing never saw it.

Also: the two new endpoints are documented in docs/api-reference.md with the import
fence stated as the rule it is, CLAUDE.md's frontend module count moves to 34, and the
release changesets carry the Thanks section.

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

.changeset/release-thanks.md

@@ -0,0 +1,9 @@
+---
+"aicodeman": patch
+---
+
+### Thanks
+
+- @irisitymichaelgrundberg for three terminal fixes in one release: keeping the output a pane capture could not contain (#436), replaying a capture at the geometry it was taken at (#435, five rounds and a Playwright suite that fails against the merge base), and trimming the padding out of a copied selection (#451), where the scan-instead-of-regex call avoided a 2.9s freeze nobody would have traced back to a copy.
+- @timkjr for a first contribution that found a real silent failure: the Instance count stepper next to the Run button had only ever applied to Claude, so on the other eight run modes it launched one session and said nothing (#454).
+- @Randalix for Wake-on-LAN on remote hosts (#439), built and live-tested against a real sleeping machine, and for reading the whole diff again between rounds rather than only the parts that were asked about.

.changeset/remote-wake-on-lan.md

@@ -0,0 +1,18 @@
+---
+"aicodeman": minor
+---
+
+feat(remote): wake a sleeping remote host from Codeman
+
+A remote SSH case pointing at a machine that suspends used to fail the same way every
+time: the session was there, the host was not, and typing into it went nowhere. A host
+can now carry a wake target, either a MAC address for Wake-on-LAN (Codeman builds the
+magic packet itself, so nothing reaches a shell) or a wake command of your own, and
+Codeman uses it when you ask for the host: when you type into a sleeping session, when
+you press the wake button on the banner, or when you start or attach a session on that
+host. Input you type while it wakes is buffered and flushed once it is back, up to 4 KB,
+and a chunk over that is refused outright rather than delivered as a fragment.
+
+Waking only ever happens because you asked. No watcher, dropped-session handler or
+boot-recovery path can reach it, since a machine woken by a reconnect watcher would come
+back seconds after every suspend.