update-spec

Capture executable contracts and coding knowledge by triggering a structured workflow that appends signatures, contracts, and validation matrices into .trellis/spec/ documents after completing a feature or bug fix.

Code-spec documentation for infra and cross-layer changes must include mandatory sections for scope, signatures, contracts, validation matrices, test cases, and wrong-versus-correct examples to ensure governance and reproducibility.

Update code-spec documents for design decisions when a feature is delivered, a bug is fixed, a new pattern is discovered, or cross-layer contracts change to maintain traceable links between revisions and test points.

Enforce a stepwise template for validation matrices and test points by using a structured update workflow that requires mandatory sections for signatures, contracts, validation rules, and cases before finalizing the spec.

This code-spec workflow operates without external dependencies or components, relying entirely on its internal structured template to capture signatures, contracts, and validation rules into .trellis/spec/ documents.

Maintain living contracts and validation rules after debugging to ensure that infra and cross-layer changes remain traceable to spec revisions and test points, preserving governance and reproducibility across the codebase.