Artifacts get document read and write operations with separate remembered consent for each.
The document-store operations are part of the artifact database work that stays gated off.
What's wrong with this entry?
New read and write operations address documents by page address, collection path and document id, with errors for a bad address, an over-long composed path and a missing document id. Consent is remembered separately for reads and writes, and again separately for approvals given by a person in plan mode.
- The stored consent covers write approval, human write approval, and per-address lists for read consent and human read consent.
- Whether these operations are offered unconditionally or behind a flag is decided by the tool's schema, which is not resolved in this build.
doc_id is required for a get
Strings lifted out of the shipped bundle, so the claim above can be checked against them.