Component
Provider-scope preview, dispatch preflight, and verification-copy path validation
Summary
Provider-free preview and provider dispatch do not enforce the same owner-private path contract, and verification-copy requires more than its CLI wording communicates.
Sanitized observations
- A provider-scope file under a non-owner-private parent was accepted by transmission preview and produced an exact selected-content/transmission digest.
- Dispatch with the same file and approved digest then stopped before provider launch with
provider scope must be one owner-private regular file.
- Separately,
verification-copy --destination NEW_PRIVATE_DIRECTORY rejected a new destination below a sticky temporary root because the parent was not already owner-private. The help names only the destination requirement, not the ancestor requirement.
These were preflight failures and did not consume provider attempts.
Expected behavior
- Transmission preview should enforce every path-ownership condition that dispatch will enforce for the same scope file.
- Help and errors should state whether the file itself, its immediate parent, or its full ancestor chain must be owner-private.
verification-copy should either create a safe new private child under an allowed temporary root or clearly require an already-private parent and show a safe preparation example.
Impact
The current mismatch invalidates an already-reviewed transmission preview at launch time and makes safe verification-copy setup trial-and-error. It creates avoidable approval churn without improving the eventual security boundary.
Environment
- codex-agy-worker skill: 0.16.0
- agy: 1.1.26
- OS/architecture: macOS arm64
Component
Provider-scope preview, dispatch preflight, and verification-copy path validation
Summary
Provider-free preview and provider dispatch do not enforce the same owner-private path contract, and
verification-copyrequires more than its CLI wording communicates.Sanitized observations
provider scope must be one owner-private regular file.verification-copy --destination NEW_PRIVATE_DIRECTORYrejected a new destination below a sticky temporary root because the parent was not already owner-private. The help names only the destination requirement, not the ancestor requirement.These were preflight failures and did not consume provider attempts.
Expected behavior
verification-copyshould either create a safe new private child under an allowed temporary root or clearly require an already-private parent and show a safe preparation example.Impact
The current mismatch invalidates an already-reviewed transmission preview at launch time and makes safe verification-copy setup trial-and-error. It creates avoidable approval churn without improving the eventual security boundary.
Environment