c0b736e5037ce4c57e009c5109746aec8c22fe49
- A SOP posted with no id lands on sop__<project_id>, the id pushSOP has always used. Creating (or moving in) a SOP under any other id on a project is refused with 400. - While a project has a complete SOP, writing another complete one needs Project Admin (the existing rule only checked the posted row). - New project_baseline_sop(): canonical row when complete, else the latest complete (pre-D20 rows). Used by /api/sops/latest with complete=true&project_id, project_summary, project_sop_team and project_qa_group, so a rogue row made before the fix cannot stay the baseline or the mail routing. - Existing rows under other ids stay and keep their old rules. Security review SEC-02 (a project_user took over the baseline and the PM/CM/QA mail routing with one POST). security_check.py: 36/36 with D19-D21. Againstda1325c: 7 D20 checks fail (the findings). Smoke test 27/27; seed_demo writes the canonical id. (cherry picked from commit7bd5ab104d)
Description
No description provided
Languages
Python
53.8%
JavaScript
30.1%
HTML
7.9%
CSS
7.8%
Shell
0.3%