Resolve pending commit links in the RC-009 change

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Review the Project Plan (RC-009) and accept v3
2026-10-06 21:55:34 +08:00 · 2026-10-06 21:55:08 +08:00 · 2026-10-06 15:46:50 +02:00
4 changed files with 68 additions and 14 deletions
@@ -15,7 +15,7 @@ document of a type. `Primary File` may contain a glob (e.g.
 | SA | Stakeholder Analysis | docs/stakeholder-analysis.md | 002 |
 | PP | Project Plan | docs/project-plan.md | 002 |
 | MIL | Milestone / Gateway | docs/milestones/*.md | 005 |
-| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 009 |
+| RC | SQA Review Record | docs/sqa/reviews/rc-*.md | 010 |
 | TM | Traceability Matrix | docs/sqa/traceability-matrix.md | 002 |
 ## Languages
@@ -9,21 +9,21 @@
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
-| 2026-10-05 | Accepted | Jens Tirsvad Nielsen | S01 | Initial version | [c0c3940] |
+| 2026-10-06 | Deprecated | Jens Tirsvad Nielsen | S01 | Added MIL-004 Code Review and CI | [8ef00aa] |
-| 2026-10-06 | Proposed | Jens Tirsvad Nielsen | S01 | Added MIL-004 Code Review and CI | [8ef00aa] |
+| 2026-10-06 | Accepted | Jens Tirsvad Nielsen | S01 | Fixed phase count, dependency overlap and stale risks and open issues (RC-009 actions) | [52b9725] |
 ---
 ## Purpose
-Schedule the three phases that take the coffee machine from empty repository to
+Schedule the four phases that take the coffee machine from empty repository to a
-published project, within the short assignment timeline in [BC-001].
+reviewed, published project, within the one-week duration in [BC-001].
 ## Planning Assumptions
 - Week 1 starts 2026-10-05; the plan ends by 2026-10-12.
 - Phase length: two to three days; S01 reviews each phase through a pull request (see [SA-001]).
- Each phase is one branch and one pull request.
+- Each phase is delivered through one or more branches and pull requests.
 ## Gateway Schedule
@@ -65,6 +65,8 @@ Project starts 2026-10-05
 MIL-001 -> MIL-002 -> MIL-003 -> MIL-004
 ```
 [MIL-004] may start once the [MIL-003] tests are merged, so their windows overlap; its decision follows the decision of [MIL-003].
 A No-Go moves all later dates by the same amount.
 ## Plan Risks
@@ -72,14 +74,11 @@ A No-Go moves all later dates by the same amount.
 | Risk | Impact | Mitigation |
 | --- | --- | --- |
 | The git host has no Actions runner | CI cannot run | Check the host first; if none, keep the workflow file and document the local commands |
 | README template not supplied | README task blocked | Ask S01 for the template before the task |
 | Doxygen not installed locally | Cannot verify docs | Document the install step in README |
 ## Open Issues
 - The README template referenced in the request ("template below") was not included.
 - No use cases or user stories are written; tasks are plain technical tasks implementing the assignment specification. S01 can ask for a use case ("Order a drink") if wanted.
 - Python ">3.13" is read as 3.13 or newer (`>=3.13`).
 ---
@@ -92,6 +91,6 @@ A No-Go moves all later dates by the same amount.
 [Milestone 40]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/milestone/40
 [Milestone 41]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/milestone/41
 [Milestone 42]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/milestone/42
 [c0c3940]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/c0c3940551db0d7d96492cc734976d0436051ff9
 [8ef00aa]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/8ef00aafaaa193ea565f1a45238d31e963a5e05d
 [Milestone 48]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/milestone/48
 [52b9725]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/52b972520d33dc3b50f1c050d874aaeb7293a557
@@ -0,0 +1,54 @@
 # RC-009 Project Plan v2 Review
 ## Metadata
 | Key | Value |
 | --- | --- |
 | ID | RC-009 |
 | CrossReference | [PP-001] |
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-06 | Proposed | Jens Tirsvad Nielsen | S01 | Initial version | [52b9725] |
 ---
 ## Artifact Under Review
 - Instance reviewed: [PP-001] (docs/project-plan.md, version 2 as reviewed; version 3 after the actions below)
 - Checklist used: none. The framework has no QC checklist for the Project Plan. The criteria below are taken from the required sections and the "Validating" note in the framework's Project Plan reference ([PP-reference]); they are an ad hoc list, not a `QC-*` checklist.
 - Independence: S01 is the only stakeholder and is also the recorded author, so the reviewer-is-not-author rule cannot be met. The document was written by Claude on S01's behalf; S01 reviews and signs. This is a known limit of a one-person project, not a clean independent review.
 ## Checklist Results
 | # | Criterion | Status | Evidence/Notes |
 | --- | --- | --- | --- |
 | 1 | Purpose states what is scheduled and over what constraint | Pass | Fixed in v3: it said "three phases" and "short assignment timeline"; it now says four phases and the one-week duration in [BC-001]. |
 | 2 | Planning assumptions give the start date and phase length, consistent with the Business Case duration | Pass | Start 2026-10-05, end 2026-10-12, as in the Business Case duration constraint. Fixed in v3: "one branch and one pull request per phase" did not match what happened. |
 | 3 | Gateway Schedule has one row per MIL-* document, with its Milestone link once synced | Pass | Four rows for MIL-001 to MIL-004; Milestones 40, 41, 42 and 48 are linked. |
 | 4 | Timeline diagram has one bar per phase and a marker per Go/No-Go decision | Pass | Four bars and four markers. The diagram was not rendered: no PlantUML server is configured. |
 | 5 | Scope Coverage maps every Business Case scope item to a gateway | Pass | All six In Scope items of BC-001 v4 map to MIL-001 to MIL-004 or to planning. |
 | 6 | Dependencies state the gateway order and what a No-Go does to later dates | Pass | Fixed in v3: the chain said MIL-004 follows MIL-003 but the windows overlap. The text now says MIL-004 may start once the MIL-003 tests are merged. |
 | 7 | Plan risks are specific to the plan and each has a mitigation | Pass | Fixed in v3: the "README template not supplied" risk was resolved and was removed. Two risks remain, each with a mitigation. |
 | 8 | Open Issues lists only unresolved items | Pass | Fixed in v3: the README template and the Python version reading were resolved (README written; BC-001 v4 states the reading). One open item remains: the optional use case. |
 | 9 | CrossReference cites the Business Case, the Stakeholder Analysis and every MIL-* document, and the links are defined | Pass | BC-001, SA-001 and MIL-001 to MIL-004 are cited and defined. |
 | 10 | Windows and decision dates agree with each MIL-* Target Date and the Business Case duration | Pass | Decision dates 2026-10-07, 10-10, 10-12, 10-12 equal the Target Dates; all lie inside 2026-10-05 to 2026-10-12. |
 ## Overall Verdict
 Go — every criterion passes. Five defects were found in version 2 (wrong phase count, wrong delivery assumption, dependency and window overlap, a resolved risk, resolved open issues) and fixed in the same change as PP-001 v3.
 ## Action Items
 | Action | Owner | Due |
 | --- | --- | --- |
 | Correct the phase count and the delivery assumption (done in v3) | S01 | 2026-10-06 |
 | State the MIL-003/MIL-004 overlap in Dependencies (done in v3) | S01 | 2026-10-06 |
 | Remove the resolved risk and open issues (done in v3) | S01 | 2026-10-06 |
 | Ask the framework to add a QC checklist for the Project Plan (upstream) | S01 | - |
 ---
 [PP-001]: ../../project-plan.md
 [PP-reference]: ../../../framework/.agents/skills/artifact/references/PP.md
 [52b9725]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/52b972520d33dc3b50f1c050d874aaeb7293a557
@@ -9,8 +9,8 @@
 ## Version History
 | Date | Status | Author | Reviewer | Change | Commit |
 | --- | --- | --- | --- | --- | --- |
 | 2026-10-06 | Proposed | Jens Tirsvad Nielsen | S01 | Added RC-006, RC-007 and the source code row | [00d47e2] |
 | 2026-10-06 | Proposed | Jens Tirsvad Nielsen | S01 | Business Case last reviewed in RC-008 | [71a27dd] |
 | 2026-10-06 | Proposed | Jens Tirsvad Nielsen | S01 | Project Plan last reviewed in RC-009 | [52b9725] |
 ---
@@ -26,7 +26,7 @@ artifact instance is created or reviewed.
 | --- | --- | --- | --- | --- |
 | [SA-001] | Stakeholder Analysis | - | [BC-001] | [RC-002] |
 | [BC-001] | Business Case | [SA-001] | [PP-001], [MIL-001], [MIL-002], [MIL-003], [MIL-004] | [RC-008] |
-| [PP-001] | Project Plan | [BC-001], [SA-001] | [MIL-001], [MIL-002], [MIL-003], [MIL-004] | - |
+| [PP-001] | Project Plan | [BC-001], [SA-001] | [MIL-001], [MIL-002], [MIL-003], [MIL-004] | [RC-009] |
 | [MIL-001] | Milestone | [BC-001], [PP-001] | - | [RC-003] |
 | [MIL-002] | Milestone | [BC-001], [PP-001] | - | [RC-004] |
 | [MIL-003] | Milestone | [BC-001], [PP-001] | - | [RC-005] |
@@ -36,7 +36,7 @@ artifact instance is created or reviewed.
 ## Coverage Notes
 - `-` in Upstream means foundational; in Downstream, nothing is built on it yet; in Last Reviewed, no `RC-*` exists yet.
- [PP-001] has no QC checklist in the framework, so it has no `RC-*`.
+- [PP-001] has no QC checklist in the framework; [RC-009] reviews it against criteria taken from the Project Plan reference.
 - No use case, domain model, design or data artifacts exist; the plan treats all tasks as plain technical tasks. The source code is reviewed in [RC-006].
 ---
@@ -55,5 +55,6 @@ artifact instance is created or reviewed.
 [RC-006]: ./reviews/rc-006-source-code.md
 [RC-007]: ./reviews/rc-007-mil-004.md
 [RC-008]: ./reviews/rc-008-business-case-v3.md
-[00d47e2]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/00d47e244c82007bbc55e18312649189b175ec10
+[RC-009]: ./reviews/rc-009-project-plan-v2.md
 [71a27dd]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/71a27ddc1f5555c1b836b1556fab292ebc9deb62
 [52b9725]: https://git.tirsystem.com/Tirsvad-Udemy-100_days_of_code/015-coffee_machine/commit/52b972520d33dc3b50f1c050d874aaeb7293a557
Author	SHA1	Message	Date
TirsvadandClaude Sonnet 5.5	865ca9cd35	Resolve pending commit links in the RC-009 change CI / checks (push) Successful in 50s Details CI / checks (pull_request) Successful in 49s Details Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-06 21:55:34 +08:00
Tirsvad	52b972520d	Review the Project Plan (RC-009) and accept v3 CI / checks (push) Successful in 53s Details Add RC-009 for the Project Plan against criteria taken from the Project Plan reference, since the framework has no QC checklist for it. Five defects found: wrong phase count, wrong delivery assumption, an overlapping MIL-003/MIL-004 schedule, and a stale risk and open issues. PP-001 v3 fixes them and is accepted; v2 is deprecated. The traceability matrix now points to RC-009. No issue closed: review and documentation only, no code changed.	2026-10-06 21:55:08 +08:00
Tirsvad	83f3acdc68	Merge pull request 'Re-review the Business Case (RC-008) and accept v4' (#31 ) from rc-008-business-case-v3 into main TirSystem/github-action: Sync GitHub mirror metadata / sync-metadata (push) Successful in 4s Details CI / checks (push) Successful in 51s Details Reviewed-on: Tirsvad-Udemy-100_days_of_code/015-coffee_machine#31	2026-10-06 15:46:50 +02:00