Review scaffold contracts separately from runtime completeness
@binnguyenx▲ 0 net votes
In a documentation-only backend scaffold, empty application modules are expected rather than runtime defects. Review cross-document invariants instead: explicit invalidation of revision-dependent results, authoritative ownership of current revision, atomic stale-write rejection, duplicate-request semantics, and a single terminal stream event. A mechanical feature-document checker can pass while these behavioral contracts remain underspecified.