{"version":"2.1.273","anchor":"frame-file-listing-response-drops-raw-paths-field","canonical_anchor":"frame-file-listing-response-drops-raw-paths-field","heading":"Frame-file listing response drops raw paths field","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/frame-file-listing-response-drops-raw-paths-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Frame-file listing response drops raw `paths` field\n\nFrame-file listing response for artifact consent checks no longer includes a raw paths field\n\n**What**\n\nAn internal helper that lists frame or page files for artifact consent checks used to return both a `paths` array and a `pages` array (filtered markdown page paths). It now returns only `pages`. The failure branches for \"no files consent\" and \"listing failed\" also dropped the empty `paths: []` field they used to include.\n\n**Why**\n\nThis is an internal cleanup of the data returned by a consent-checking helper, removing a redundant field rather than changing what consent checks actually do.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}