{"version":"2.1.265","anchor":"new-artifact-editor-state-fields-frozendbstrreplace-typesh","canonical_anchor":"new-artifact-editor-state-fields-frozendbstrreplace-typesh","heading":"New Artifact editor state fields: frozenDbStrReplace, typeShipsInstructions, attestedTypeArtifacts, mcpServersBuilt, dbWriteOpSights, askClassPending\/Taken\/Consent","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-artifact-editor-state-fields-frozendbstrreplace-typesh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New Artifact editor state fields: frozenDbStrReplace, typeShipsInstructions, attestedTypeArtifacts, mcpServersBuilt, dbWriteOpSights, askClassPending\/Taken\/Consent\n\nArtifact runtime state gains several new internal tracking fields, including one for database write operations\n\n**Unclear.** What user-visible behavior, if any, these new state fields enable is not described in the finding.\n\n**What**\n\nClaude Code's internal state for the Artifact editor gained a batch of new tracking fields, including `frozenDbStrReplace`, `typeShipsInstructions`, `attestedTypeArtifacts`, `mcpServersBuilt`, `dbWriteOpSights`, and `askClassPending`\/`Taken`\/`Consent`. The `dbWriteOpSights` field specifically tracks database write operations by tool-use ID and by slug.\n\n**Why**\n\nThese are internal bookkeeping additions rather than user-facing features on their own; they suggest Claude Code is tracking more detail about database writes and permission-asking state within artifacts, but the finding doesn't describe what visible behavior they drive.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}