docs: define durable fix branch workflow

2026-08-15 14:18:13 +07:00
parent 8be1b754e1
commit f013ad7707
6 changed files with 87 additions and 0 deletions
@@ -0,0 +1,29 @@
+# Access, Navigation, Icon, and Intern Picker Fix Plan
+
+## Scope
+
+Record the durable workflow for the targeted fixes in this plan. This plan does
+not change product behavior, dependencies, schemas, or the five persistent
+feature-branch ownership areas.
+
+## Implementation steps
+
+1. Prove RED: the contributor guides lack the realizable repair-branch name.
+2. Add one branch rule everywhere contributors, coordinators, and requirement
+   reviewers rely on it: `work/fix/<feature>/<what-fix>` from verified `main`.
+3. State why `work/<feature>/fix/<what-fix>` is invalid while its persistent
+   `work/<feature>` ref exists.
+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 exact searches, requirement/use-case counts, local-link
+   resolution, and whitespace validation. Commit the tracked guidance locally;
+   do not push or merge.
+
+## Exit criteria
+
+- The tracked guides, design record, implementation plan, and evidence record
+  agree on the same repair-branch spelling.
+- The local authoritative, explained, simple, and generated SRS catalogues keep
+  exactly 260 unique requirement IDs and the SRS keeps 14 use cases.
+- The forbidden nested form is documented only as forbidden, not as a usable
+  branch name.