Skip to content

tests: pin the symlink-loop-workspace basis; consider a record-in-bundle-namespace tripwire #97

Description

@SollanSystems

Two test-surface items from Slice 2 (PR #94):

  1. Task 1's fix round widened the handler so a WORKSPACE that is itself a symlink loop yields unresolvable instead of an uncaught pathlib RuntimeError (py≤3.12) — the argv[0] symlink-loop path is pinned, the workspace-root variant is not. Suggested test shape is in the Slice 2 SDD task-6 report §7 (cross-version + symlink-storage caveats noted there).

  2. reference/repo-os-contract.md §17 states an evidence record MUST NOT be named verify-*.json (it would become a phantom RED bundle in FCR), but nothing enforces it — the evidence scan could flag a record in the bundle namespace in ~2 lines.

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions