When an artifact watch cannot start, Claude is told the plain reason instead of failing silently.
What's wrong with this entry?
If a live artifact subscription cannot be armed, the session now enqueues a notification stating the artifact is NOT being watched, with a plain reason: "could not connect", "artifact not found", "no live credential", or "watch limit reached". Previously this failed quietly.
- Notices are de-duplicated per artifact and reason, and cleared once a later arm attempt succeeds.
- A new status view reports each artifact as
armingorbacking_off, with failure counts and the next retry time.
watch limit reached
Strings lifted out of the shipped bundle, so the claim above can be checked against them.