[Milestone 3 prerequisite] Create and populate `bench/policy-compliance-fixtures` with 6 verification tasks

[telleroutlook]

🤖 Auto-filed as prerequisite sub-issue for symbolic comparison analysis.

Parent Issue: [milestone Milestone 3 ] bench/symbolic-comparison.md — comparative analysis: symbolic execution vs concrete testing on 6 verification tasks from policy-compliance fixtures; report path coverage and constraint solving time

Problem: The symbolic-comparison.md document cannot be generated because:

1. The policy-compliance fixtures directory/verification tasks do not exist yet
2. These 6 verification tasks are the input data for the comparative analysis
3. Without defined test cases, there is nothing to compare between symbolic execution and concrete testing

Sub-issue Tasks:

1. Create bench/policy-compliance-fixtures/ directory structure
2. Define and implement 6 verification tasks that exercise:
   • Path coverage (different branches/conditions)
   • Constraint complexity (simple to complex conditions)
   • Policy compliance scenarios (authorization, resource access, etc.)
3. Document each fixture with:
   • Expected behavior description
   • Known paths/branches
   • Policy rules being tested
4. Ensure fixtures are runnable by both symbolic execution and concrete testing frameworks

Acceptance Criteria:

• Directory bench/policy-compliance-fixtures/ exists with 6 distinct verification task files
• Each task has documentation describing its expected behavior and policy rules
• Tasks can be executed by the concrete testing framework
• Tasks are compatible with symbolic execution (once Z3 integration is complete)
• Fixtures cover a range of complexity (simple conditions, complex constraints, nested policies)

Once complete, the parent issue can be resolved by running both symbolic execution and concrete testing on these fixtures and generating the comparative analysis in bench/symbolic-comparison.md.

Estimated complexity: Medium - requires domain expertise in policy compliance scenarios and constraint design

[telleroutlook]

Verify-first found this issue is already implemented at :0. Closing without spawning implementation work.