Skip to content

verify-pyprocar: make fetched fixtures read-only at the OS level #288

Closed

Description

@lllangWV

Found by a reflect pass over the #277-#279 autopilot session.

The in-process audit-hook guard against writes into data/ took #264 plus #270 to cover dir_fd, symlink, link, chmod and utime, caused a CI failure without data/ and a false positive, and every agent brief still repeats the no-write ban by hand.

Suggested mechanism: verify.sh fetch runs chmod -R a-w on each fetched fixture, $H run works only on its reflink copy under data/verify-runs/, and a doctor check reports any writable fixture. The OS then refuses stray writes regardless of code path.

Activity

  1. 4 remaining items

  2. lllangWV commented on Oct 5, 2026

    @lllangWV
    MemberAuthor

    Fixed in dev by #303. verify.sh fetch now locks fetched fixtures read-only, run works on a writable copy, and doctor reports writable and unlockable fixtures. Every verify.sh command writes only strictly below the resolved data root; the documented worktree-own and cache writes are the exceptions. tests/test_fixture_copies.py bans raw fixture copies in tests. The verdicts (5 rounds) are on #303. The one-time lock for the shared data/ is in the PR body; run it from a checkout at merged dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions