docs(sdlc): hold meetings on weekdays, 5+ days after reviewed commits

sdlc/ISO29110-audit-prep.md

@@ -31,7 +31,7 @@
 
 | Point | What to show | What to say |
 |---|---|---|
-| No change requests in 8 months | Change Report parts 1–3; Minutes of Meeting 23 May (Rack → Bin), 3 Aug and 14 Aug (Task 4.7) | "Change control was used: 3 items were judged against the criteria and none qualified." Rehearse the advisor's test: "if we removed it, could we still deliver?" |
+| No change requests in 8 months | Change Report parts 1–3; Minutes of Meeting 18 May (Rack → Bin), 10 Aug (Task 4.7 decided) and 19 Aug / 24 Aug (Task 4.7 done) | "Change control was used: 3 items were judged against the criteria and none qualified." Rehearse the advisor's test: "if we removed it, could we still deliver?" |
 | All 45 test cases passed in one run | Correction Register: 28 issues found and fixed during development, each linked to a commit and a test case; Test Case and Test Procedures pass rule: defects logged and retested until they pass | "The formal run came after the defects were fixed, so a clean run is the result of that work." If git history has real failing test runs, have one ready |
 | Risks never re-rated | Software Project Plan R1–R8; risk table in every Progress Status Record | Pick 1–2 risks that actually occurred (R1 → Rack/Bin decision; R7 → evidence prepared before UAT) and show where they were handled. Do not change ratings in the records now |
 | Interviews must match the documents | One rehearsal session with the three people | Developer: how a defect is logged (ISS-002 → commit `92d116f` → TC-UN08.002). QA: run TC-UN08.002 (rollback test). PM: trace CR13:001 → SR09:003 → UN08.002 → TC-UN08.002 → Passed in Test Report and Validation Results |