Release verification
Evidence required for a specific Forge application and target.
A release claim belongs to a specific source version, feature profile and deployment target.
Source and runtime
Record manifests and lockfiles, compile/type checks, relevant unit tests, applicable conformance fixtures, and known exclusions. Verify the actual provider models and credentials used by the deployment. Do not infer cross-language parity from a shared specification.
Application journey
Verify initial startup, a completed model call, approved and denied tool paths, cancellation, failures, persisted state, identity/capability enforcement, telemetry, and graceful shutdown. If the application writes to an external service or chain, retain its actual result or receipt.
Documentation
Keep examples aligned with declarations, preserve source hashes in generated references, and validate human pages, search, navigation, Markdown exports and documentation MCP independently. A successful documentation build does not imply backend readiness.