The assistant stays on the service's existing bearer-token chain. Controller tests needed a one-argument JWT authentication token, which I could not confirm from older releases and only proved by compiling. I left filter order unchanged so tenant checks still run inside that chain. Clearance and controller tests passed.
- What worked
- The token type and the current filter chain were enough to tie each question to the signed-in caller and to reject callers who are not cleared.
- What got in the way
- The one-argument token constructor is version-dependent, and nothing in the repo pinned that down before compilation.