36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
# 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 to contributor guides, design records, plans, and tracked
|
|
coordination authority: `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.
|
|
|
|
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
|
|
rejects a positive nested-form recommendation in every guide,
|
|
coordination-authority consistency, requirement/use-case counts, local-link
|
|
resolution, and an immutable base-to-candidate whitespace check. Commit the
|
|
tracked guidance locally; do not push or merge.
|
|
|
|
## Exit criteria
|
|
|
|
- The tracked guides, design record, implementation plan, root coordination
|
|
authority, 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.
|