An approved artifact tool call can no longer be redirected to a different project or action.
What's wrong with this entry?
Approving an artifact tool call now attaches a hidden marker recording exactly which action and which project were approved. Before the privileged step runs, that marker is read back and must match the action and project actually being executed, otherwise the call fails with asset_target_changed.
- Covers
list_assets,read_page_data,watch,read_dbandwrite_db. - The marker is stored as a non-enumerable property and read with
Reflect.get, so it cannot be spoofed by ordinary input fields. - An input carrying any of the other four consent markers is rejected outright.
- Unconditional; there is no flag to turn this off.
__artifactConsentPin
Strings lifted out of the shipped bundle, so the claim above can be checked against them.