What
Resolving a comment thread on a published artifact can now report "not resolved (another user's activation)" and "not resolved (unavailable from this session)" instead of a generic failure, and the resolve request tries a session-scoped route first.
Details
- If the session-scoped route returns a 404 that is not a missing-thread error, the request falls back to the older route and records that it fell back.
- The two new refusals come from server responses: one for a comment raised by a different user's session, and one where the server says the action requires a claude.ai session.
- The 404 message no longer mentions the artifact being republished.
Evidence
session_route_fell_back, not resolved (unavailable from this session)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.