{"version":"2.1.234","anchor":"artifact-tool-logs-why-it-exposed-the-actions-it-did","canonical_anchor":"artifact-tool-logs-why-it-exposed-the-actions-it-did","heading":"Artifact tool logs why it exposed the actions it did","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/artifact-tool-logs-why-it-exposed-the-actions-it-did","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Artifact tool logs why it exposed the actions it did\n\nA debug line now records why the artifact tool offered the actions it did.\n\n**What**\n\nBuilding 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.\n\n**Details**\n\n- The line covers capabilities, comments, db, assets, read_page_data, where the flag value came from, and a freshness indicator.\n- Whether remote watch is unsupported is recorded into session state at the same time.\n- Diagnostic only, and it runs on every schema build.\n\n**Evidence**\n\n`Artifact input schema built: capabilities=`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}