secure-development-playbook
Retrieve Pi secure-development guidance once for a stable engineering task, reconcile its coverage with current repository evidence, and submit targeted feedback only after tenant verification and fresh explicit confirmation.
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.