What
Marking an artifact comment resolved is attempted first against the session-scoped endpoint, and a server refusal of that token no longer fails the action. The client retries the plain resolve endpoint, and the telemetry now tells a refused token apart from a route that was never there.
Details
- The refusal is a 403 whose response body carries the marker "CCR agent tokens cannot call this route", and only that case triggers the new path.
- Refusals are logged under
artifact_comment_session_resolvewith the outcomesession_route_ccr_denied. - A 404 from the session route still falls back as before and still logs the older outcome
session_route_fell_back. - The fallback request sent to the plain resolve endpoint is itself unchanged; only the trigger condition and the reported outcome are new.
Evidence
CCR agent tokens cannot call this route, session_route_ccr_denied
Strings lifted out of the shipped bundle, so the claim above can be checked against them.