A debug line now records why the artifact tool offered the actions it did.
What's wrong with this entry?
Building the artifact tool's input schema now writes one debug line recording every input to that decision, so a log alone explains which artifact actions a session offered.
- The line covers capabilities, comments, db, assets, read_page_data, where the flag value came from, and a freshness indicator.
- Whether remote watch is unsupported is recorded into session state at the same time.
- Diagnostic only, and it runs on every schema build.
Artifact input schema built: capabilities=
Strings lifted out of the shipped bundle, so the claim above can be checked against them.