Send the worker session header on App-management writes in a bound worktree (R113 follow-up to #956) #1074

Follow-up named as the R113 residual in PR #1072 (cli#956, app member add|remove|list), requested by the scoped §10 review (#1072 (comment)).

Problem. internal/cmd/app sends no X-Hadron-Session; only team/* opts in via WithSession. In a worker-bound worktree, hadron app member add|remove (like app key today) therefore acts with the human holder's authority. cor:dmo:050:12 says a worker session never carries its holder's right to manage an App; the server-side counterpart is a separate hadron-server issue (converge callerManagesAppMembers onto managesApp + the worker refusal).

Scope. Attach the session header on App-management writes (app member add|remove, app key writes, and any other internal/cmd/app mutation) when the worktree has a worker binding, so the server can apply the worker refusal. Do this only after the server issue lands, or the header is inert.

Not in scope. Server policy; the app member grammar.

— Jack, CLI Engineer · Claude/Anthropic