fix(web): kick refusals reach the caller, and correct a stale comment

[cvince]

kick had no wrapper at all — three refusals ended in console.error + process.exit(1), and its own catch blocks did the same, so nothing could route to displayErrorAndExit. This adds the execute() → _execute() wrapper its siblings already have and turns the refusals into coded throws.

refusal	code
member not found	MEMBER_NOT_FOUND (minted — distinct from PERMISSION_DENIED, which means the caller may not remove members; here there is simply nobody by that address)
list members failed	SERVICE_ERROR
remove member failed	SERVICE_ERROR

Terminal behaviour is unchanged — displayErrorAndExit still prints to the terminal and still exits 1. What changes is that a --web caller stops getting nothing.

The stale comment is the part worth reading

KickOpts.web claimed:

src/index.ts does not read it for kick yet, so this path is live and tested but not reachable from argv

index.ts has been threading it all along:

await cmd.execute(email, { web: command.optsWithGlobals().web === true })

So every refusal in this file was reachable under --web while a comment said they were not. This is the second such comment tonight — orgCommand carried one making the same false claim about its own web path. Both understated real exposure. A comment cannot notice it has gone out of date.

Not included, with reasons

• connectCommand — line 174 is reachable under --web (browser picker shown, user declines → refusal with no page). But execute returns { linked: boolean } and calls itself recursively, so a wrapper around a Promise<never> handler changes the return contract. Not contained; needs a deliberate decision.
• editCommand — its guards fall outside its routing try.
• recoverCommand — no outer routing try at all; 7 exit sites.

Suite: 1849 pass, 0 fail.