Add approved controlled browser draft action

[AetherAI3]

Summary

• Add aether pc draft-browser <aether-cloud|claude|chatgpt> for one line of text in a disposable Edge profile. Page opening and text insertion need separate fresh local approvals; --yes and headless CLI runs refuse approval.
• Bind insertion to one observed empty textarea or contenteditable element. Recheck origin, tab count, loader, backend element, layout box, and empty state before focus and text insertion. Verify the resulting value with a fixed boolean probe in an isolated browser world. Keep text out of receipts and the audit journal.
• Add bounded cancellation, a distinct browser.draft v2 map row, command metadata, documentation, and Windows Edge regression fixtures.

Verification

• 27 focused PC tests passed on Windows Edge. Five action and cancellation fixtures passed again after the final driver changes.
• npm run verify:production passed on the rebased head; it packed, installed, and launched 940 package files.
• A separate clean Windows tarball install reported aether.pc/2 and refused draft-browser --yes with exit 3.
• An initial full npm test run had 2,804 passes, 13 skips, and one generated-command-digest failure after the manifest changed. Regenerating canonical docs made the failed production-verifier test pass; the full suite was not repeated after that repair.

Qualification limits

This is a source candidate. The installed package has not completed an interactive draft insertion on a real site. A disposable profile may encounter a login page with no composer. Focus or typing may cause a site to save or transmit data, as the second approval says. No generic send/click action, personal-profile attachment, authenticated-session proof, published npm release, or hosted PC broker route is claimed.