Publish v0.7.0 with three automatic investigation packages, each scoped to one role and step. Planner and Reviewer guidance uses assigned read roots; Implementer guidance uses the admitted command/filesystem boundary. Identical text resources share the investigation method without a multi-role manifest.
Evidence
Before: the new role-investigation test failed because the packages did not exist. After: python -m unittest tests.test_packages -v passed all 14 tests at a74cdc7574. RelayView's public source verifier also verified the published v0.7.0 tag, file hashes, package identities and reproducible archive digests.
Documentation disposition
updated — README and NOTICE identify support and original MIT redistribution provenance.
Ablation decision: not_required — extraction of existing investigation intent; no added capability or quality mechanism.
Merge Danger
Two-way door for future selection; published v0.7.0 is immutable. Stop selecting it to roll back, retaining the tag and bytes for recorded assignments. Scope: instruction packages only.
Reviewer prerequisites
Python 3, no external dependencies or paid calls.
Verification
python -m unittest tests.test_packages -v
Expected: 14 passing tests. Automated checks establish package structure/content and reproducibility, not model compliance. Operator acceptance remains required.
## Summary
Publish v0.7.0 with three automatic investigation packages, each scoped to one role and step. Planner and Reviewer guidance uses assigned read roots; Implementer guidance uses the admitted command/filesystem boundary. Identical text resources share the investigation method without a multi-role manifest.
## Evidence
Before: the new role-investigation test failed because the packages did not exist. After: `python -m unittest tests.test_packages -v` passed all 14 tests at a74cdc757438e01a0885e1f4418a6932d8901811. RelayView's public source verifier also verified the published v0.7.0 tag, file hashes, package identities and reproducible archive digests.
## Documentation disposition
updated — README and NOTICE identify support and original MIT redistribution provenance.
Ablation decision: not_required — extraction of existing investigation intent; no added capability or quality mechanism.
## Merge Danger
Two-way door for future selection; published v0.7.0 is immutable. Stop selecting it to roll back, retaining the tag and bytes for recorded assignments. Scope: instruction packages only.
## Reviewer prerequisites
Python 3, no external dependencies or paid calls.
## Verification
```sh
python -m unittest tests.test_packages -v
```
Expected: 14 passing tests. Automated checks establish package structure/content and reproducibility, not model compliance. Operator acceptance remains required.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Publish v0.7.0 with three automatic investigation packages, each scoped to one role and step. Planner and Reviewer guidance uses assigned read roots; Implementer guidance uses the admitted command/filesystem boundary. Identical text resources share the investigation method without a multi-role manifest.
Evidence
Before: the new role-investigation test failed because the packages did not exist. After:
python -m unittest tests.test_packages -vpassed all 14 tests ata74cdc7574. RelayView's public source verifier also verified the published v0.7.0 tag, file hashes, package identities and reproducible archive digests.Documentation disposition
updated — README and NOTICE identify support and original MIT redistribution provenance.
Ablation decision: not_required — extraction of existing investigation intent; no added capability or quality mechanism.
Merge Danger
Two-way door for future selection; published v0.7.0 is immutable. Stop selecting it to roll back, retaining the tag and bytes for recorded assignments. Scope: instruction packages only.
Reviewer prerequisites
Python 3, no external dependencies or paid calls.
Verification
Expected: 14 passing tests. Automated checks establish package structure/content and reproducibility, not model compliance. Operator acceptance remains required.