contracts

Make internal Go interfaces testable by defining a contract.go file per package to establish a stable public surface, then generate mocks and observability seams automatically via forge generate. This enables behavior validation without side effects.

A contract.go file defines an internal Go package's public surface as an interface for consumers. You need one when establishing test seams for greenfield packages or migrating existing packages to enforce strict contract linting and mock generation.

Generate mocks and observability middleware for Go interfaces by adding an internal/<package>/contract.go file and running forge generate. This produces logging, tracing, metrics, and test scaffolding around the contract boundary automatically.

Enforce strict interface naming conventions and prevent missing contracts in Go by configuring forge lint --contract with forge.yaml. This catches missing contracts immediately as a change is introduced, satisfying functional linting requirements.

Migrate existing Go packages to a contract workflow by introducing a contract.go file to define the interface, then running forge generate to produce mocks and observe wiring hooks. Apply strict contract linting via forge.yaml to prevent regressions.

Generated mock artifacts in Go contract testing should not be hand-edited because regeneration rules override manual changes during forge generate. Hand-editing breaks strict contract linting and disrupts the automated observability integration and middleware seams.