v1.14.2 — agent-tunnel: reuse handle names, revoke, forget --handle

Patch release — fixes agent-tunnel handle/thread lifecycle gaps: you couldn't
reuse a published handle name once its owning session was gone.
#91 · closes
#90.

🐛 Fixes

• Reuse a freed handle name. Re-sharing a handle that was revoked (>share off, or the new revoke below) now works from a different session —
  previously a revoked record blocked the name forever. A cross-session reclaim
  is a fresh publish and no longer inherits the old owner's access level.
• agent-tunnel revoke <handle> — release a published handle from outside
  its session (the in-session >share off only works while you still have that
  session). Existing bound forks keep working; new threads can't open on the
  handle until it's re-shared.
• agent-tunnel forget --handle <name> — close all threads of a handle in
  one go (a handle opened in several Discord threads shows several rows in
  forks); previously only --thread <key> (one) or --all.

Closing a thread (!done) still does not unpublish the handle — that's
deliberate (one publish can serve many threads; the owner controls its
lifecycle). Free a name with >share off (in-session) or agent-tunnel revoke
(out-of-session).

Heads-up: the name-reuse fix lives in the >share plugin hook, so plugin
users need the agent-tunnel plugin updated to get it; revoke /
forget --handle ship in the claude-code-tools package.