{"version":"2.1.247","anchor":"artifact-reads-record-whether-the-fetch-was-direct","canonical_anchor":"artifact-reads-record-whether-the-fetch-was-direct","heading":"Artifact reads record whether the fetch was direct","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-reads-record-whether-the-fetch-was-direct","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact reads record whether the fetch was direct\n\nArtifact reads now record whether the fetch was direct, and refusal text moved to one helper.\n\n**What**\n\nThe artifact file-read telemetry event now carries an `agent_direct` field when the read result reports one, and the long refusal text for resubmitting an identical publish is assembled in one helper instead of inline.\n\n**Details**\n\n- The helper returns both the refusal text and its reason code.\n- Comment-thread response mapping was folded into a shared helper on the same path.\n\n**Evidence**\n\n`agent_direct`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}