Harness V2 Rules

Harness V2 should be treated as a contract surface. Future changes need to preserve deterministic behavior, explicit fixtures, and clear failure meaning.

Overview

The harness exists to protect product-critical generation paths and prevent silent regressions.

Rules

• Keep inputs explicit and repeatable.
• Make expected outputs stable enough for review.
• Avoid changing fixture semantics without updating the related lesson or task note.
• Treat harness failures as contract failures until proven otherwise.

Related Docs

See CRLF Test Failure for a concrete portability lesson.