docs: require complete targeted repair workflow

2026-08-15 14:56:14 +07:00
parent 10196d55b0
commit 445e4fedeb
7 changed files with 41 additions and 0 deletions
@@ -14,6 +14,9 @@ feature-branch ownership areas.
   `main`.
 3. State why `work/<feature>/fix/<what-fix>` is invalid while its persistent
   `work/<feature>` ref exists.
+
+Every targeted repair starts from the taskmaster-verified latest `main`, uses TDD RED → GREEN, adds Javadoc during implementation, records companion evidence, undergoes independent review, and uses a normal, non-force merge only when separately authorized.
+
 4. Regenerate the local SRS after amending the existing operational requirement;
   do not add a requirement ID or a use case.
 5. Prove GREEN with the executable six-guide regression that independently
@@ -23,6 +23,8 @@ The forbidden form is `work/<feature>/fix/<what-fix>`. A repair owner preserves
 other worktrees, records RED and GREEN evidence, commits locally, and does not
 push or merge without separate authority.

+Every targeted repair starts from the taskmaster-verified latest `main`, uses TDD RED → GREEN, adds Javadoc during implementation, records companion evidence, undergoes independent review, and uses a normal, non-force merge only when separately authorized.
+
 ## Consequences

 - Persistent feature branches remain available for their iteration ownership.