test: add reviewer v0.4 antagonist specs

[laynepenney]

Summary

• add Sprint C reviewer-framework v0.4 antagonist specs across reviewer, judge bridge, and suggestion-engine surfaces
• keep the pack OSS-safe by modeling temporal-like ambiguity geometrically rather than copying Conversa corpus material
• validate plugin seams for custom Predicate/Reviewer subclasses and chain composition

Spec Status

This PR is intentionally red-by-design.

Targeted slice result:

• python -m pytest -q tests/unit/test_reviewer.py tests/unit/test_judge.py tests/unit/test_suggestion_engine.py
• 104 passed, 3 failed
• ruff check tests/unit/test_reviewer.py tests/unit/test_judge.py tests/unit/test_suggestion_engine.py passes

Intended red seams:

1. JudgingReviewer does not clamp out-of-range adapter scores at the bridge
2. JudgingReviewer does not clamp negative adapter scores at the bridge
3. HallucinationSignalRule does not handle score=None safely

Boundary

• no Conversa corpus copied into OSS
• eval#1 category-scoping remains a separate slice and is not folded into this PR

[laynepenney]

Closing this red-by-design spec PR in favor of #9. The contract served its purpose, but should not take a knowingly failing test PR pre-v1.0. #9 carries the same spec tests plus the implementation, and the full slice is green there.

[laynepenney]

Closing this red-by-design spec PR in favor of #9. The contract served its purpose, but main should not take a knowingly failing test PR pre-v1.0. #9 carries the same spec tests plus the implementation, and the full slice is green there.