fix: let agents publish work from managed worktrees they created (#201883)

* fix(gateway): let write-scoped agents publish unowned managed worktrees

github_publish tells an unbound conversation to publish with workspacePath
set to its checkout, but sessions.github.publish validated that path with
the sessions.create cwd rule, which only admits agent workspace folders.
A managed worktree made through worktrees.create lives under the worktree
root, so the Gateway refused it with "missing scope: operator.admin".
Subagents never hold operator.admin, so the work could not be published.

Admit a live managed worktree that no session owns when the caller holds
operator.write and the record's repository root passes the rule
worktrees.create and worktrees.branches already apply (agent workspace or
recorded project). Session-owned worktrees, callers with only
operator.sessions.write, and other host paths are still refused. The
refusal now lists the admitted paths instead of only naming the scope.

* test(gateway): pin managed worktree publication at source admission

The managed-worktree case asserted the new refusal wording before it published, so against the old handler it failed on wording rather than on admission. Assert the wording once on the host-path refusal and keep this case's refusals scope-only; the old handler now fails at the publish itself.