Actualize

This keeps your FPF assurance case synchronized with your actual codebase by running a three-part audit against git changes. It checks for configuration drift (package.json, Dockerfiles), flags evidence files that reference changed code as stale, and marks decisions that might need revisiting. You get a structured report showing exactly what changed and which parts of your knowledge base are now suspect. Run it before starting new work or after landing significant changes. The git diff approach is straightforward, though you'll still need judgment calls about whether stale evidence actually matters. Fits naturally into the FPF workflow if you're already maintaining evidence files and decision records.