{"version":"2.1.274","anchor":"artifact-page-data-reads-gained-a-manifeststore-usageconte","canonical_anchor":"artifact-page-data-reads-gained-a-manifeststore-usageconte","heading":"Artifact page-data reads gained a manifest\/store-usage\/content-store surface (manifestPaths, storeDocuments, contentStore)","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-page-data-reads-gained-a-manifeststore-usageconte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact page-data reads gained a manifest\/store-usage\/content-store surface (manifestPaths, storeDocuments, contentStore)\n\nArtifact file reads can now include manifest paths, store usage documents, and a content store reference\n\n**Unclear.** The finding shows these fields were added to the read result but not how or where Claude Code uses them afterward.\n\n**What**\n\nWhen Claude Code reads an artifact's page data, the result can now include three new pieces of information that did not exist before:\n\n- `manifestPaths`, a list derived from the artifact's files\n\n- `storeDocuments`, derived from database usage data\n\n- `contentStore`, a value checked against a new validation pattern\n\n**Why**\n\nThis gives Claude Code more detail about an artifact's underlying storage and file manifest when reading it, though the finding does not say what these fields are used for downstream.\n\n- Area: Artifacts\n- Names: `manifestPaths`, `storeDocuments`, `contentStore`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}