Field note /
Moving execution settings to the operator's machine came with no recorded check
The portfolio moved Agent-Workflow's execution permissions, paths and model choices out of its repository into the host's configuration. Nothing yet records that the host settings match the earlier protections.
How the finding changed
Belief
Removing machine-specific execution settings from the repository would keep it clean and the workflow portable.
Evidence
A separately reviewed change cut the repository's execution file down to a compatibility stub. Settings that used to live in the repository (paths, permissions, model defaults, plugin choices) moved to the operator's own machine.
Contradiction
The repository can no longer show that the intended permissions or clean-source checks are active, and a missing host setting may fall back to a default. Moving configuration changes where decisions are made. Those decisions still need checking.
Correction
Keep repository intent and host-specific execution settings separate. Collect the effective host configuration and each run's policy as their own acceptance evidence.
Current claim boundary
The repository-side change is merged. The reviewed change includes no Agent-Workflow run and no recorded check that the host policy reproduces the earlier protections. That is a gap in the evidence. It does not show the host is misconfigured.
Evidence
The repository-side change is in an access-controlled portfolio PR. No private operator paths, credentials, effective host configuration or raw lab notes are shown.