use-pi-secure-development-playbook
Retrieve Pi secure-development guidance for a stable implementation task, optionally add necessary threat-model context, and offer confirmed feedback. Use before or during development, not for general finding triage or automatic code changes. Never send feedback without fresh, explicit confirmation.
Pinned to revision 0b961dbaf98b, 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.