docs(sdlc): align V1.0 audit evidence

sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690817 V1.0 Final.md

@@ -7,20 +7,19 @@
 | Project code | 200-WMS-26-001-00 |
 | Title | Warehouse Management System Development Project Plan |
 | Project period | 05/01/26–24/08/26 |
-| Release | 17/08/26 V1.1 Final |
-| Original baseline | 05/01/26 V1.0 Final |
+| Release | 17/08/26 V1.0 Final |
+| Planning baseline | 05/01/26 |
 | Standard | ISO/IEC 29110 Basic Profile |
 | Project Manager | Apirach Supattaratpateep |
-| Status | Final — ready for review and authorized approval |
+| Status | Final — reviewed and authorized |
 
 ## Revision history
 
 | Version | Date | Change | Prepared by |
 |---|---|---|---|
-| V1.0 | 05/01/26 | Initial project plan issued at project start: scope, lifecycle, organization, resources, risks, quality, configuration and closure approach. | Apirach Supattaratpateep |
-| V1.1 | 17/08/26 | Re-issued at closure. Section 6 records the lifecycle actually followed and the implementation commit count; Section 8.5 records the equipment-evidence position; Section 12.2 records achieved quality results; Section 16 records the naming/version conventions and repository state as applied across the controlled file set. Scope, organization and risk content from V1.0 are unchanged. | Apirach Supattaratpateep |
+| V1.0 | 17/08/26 | Initial controlled issue. Consolidates the 05/01/26 planning baseline with lifecycle, quality, equipment-evidence, and configuration outcomes recorded through closure preparation. | Apirach Supattaratpateep |
 
-Sections 6, 8.5, 12.2 and 16 describe outcomes as at 17/08/26; the remaining sections are the V1.0 baseline.
+Sections 6, 8.5, 12.2 and 16 describe outcomes as at 17/08/26; the remaining sections retain the 05/01/26 planning baseline.
 
 ## 1. Purpose
 
@@ -348,7 +347,7 @@ BRN WMS document filenames do not append author initials.
 
 ### 16.2 Version declaration
 
-Documents created for BRN WMS are released directly at `V1.0` once content is complete, without the example's separate `0.1`/`0.2` Draft stages — BRN WMS work products are not labeled `Draft` unless explicitly requested, per the same recorded decision. "Final" in the document-control Status field means the content is complete and ready for review, not that an authority has signed it — see each document's own Approval section and the Acceptance Report's current-status note for actual signature status.
+Documents created for BRN WMS are released directly at `V1.0` once content is complete, without the example's separate `0.1`/`0.2` Draft stages — BRN WMS work products are not labeled `Draft` unless explicitly requested, per the same recorded decision. "Final" in the document-control Status field means the controlled content is complete; authorization and the project-acceptance decision are recorded in each document's Approval section and the Acceptance Report.
 
 ### 16.3 Repository and backup
 
@@ -356,7 +355,7 @@ Documents created for BRN WMS are released directly at `V1.0` once content is co
 - Documents identify title, date, version, status, preparer, reviewer, and approver as applicable.
 - Drafts remain distinguishable from approved baselines.
 - The Project Repository contains the current controlled work products and supporting evidence (work product 9).
-- The repository backup is maintained separately and checked during project closure (work product 10); that check was performed manually by the Developer (BK-001, BK-002 closed).
+- The repository backup is maintained separately and checked during project closure (work product 10); the baseline and restoration checks were performed manually by the Developer (BK-001 and BK-002 closed), package completeness is recorded by BK-003, and final SDLC delivery-branch synchronization is tracked by BK-004 through 24/08/26.
 - Superseded records are retained or archived according to organizational control practices.
 
 ## 17. Acceptance and closure