{"version":"2.1.274","anchor":"published-artifact-tool-description-now-scans-referenced-fil","canonical_anchor":"published-artifact-tool-description-now-scans-referenced-fil","heading":"Published-artifact tool description now scans referenced files for links and reports coverage","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/published-artifact-tool-description-now-scans-referenced-fil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Published-artifact tool description now scans referenced files for links and reports coverage\n\nArtifact tool's action summary now scans referenced files for links and reports coverage\n\n**What**\n\nWhen an artifact is created or updated, the human-readable summary of that action now scans each referenced or attached file for links, when a root path is available, and appends notes such as `[file N: ...]` or `[N listed file(s): ...]`. If some files were skipped because of scan limits, it now shows a count like `(K not examined for links)`. Large file lists are also now paginated differently, and base-path\/root link information is included.\n\n**Why**\n\nThis gives you more visibility into what links were found (or missed) across the files involved in an artifact action, making it clearer when a summary is incomplete due to scan limits.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}