Spec traceability

The app's spec says what to build, and every piece of work can prove which part of it it serves: each requirement, screen, decision and non-negotiable has a stable ID in a markdown spec folder; the first failing test, the code comment, the end-to-end flow, the commit body and the report quote that ID; and two scripts print any entry verbatim and prove that every citation in the repo and its history resolves. Works the same for iOS and Android; an app without a spec gets a clean NOT APPLICABLE.

Rules that must hold