Make completion alias assertion order independent
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# ReleaseKit v0.9.0 implementation plan
|
||||
|
||||
Status: planned; Stages 1–6 are not started.
|
||||
Status: Stage 1 complete; Stages 2–6 are not started.
|
||||
|
||||
Implement these stages in integer order during one end-to-end sprint. The target
|
||||
audience is the Luna coding agent. Intermediate stages may temporarily leave
|
||||
@@ -56,7 +56,9 @@ new validators, or add a local recovery implementation.
|
||||
|
||||
## Stage 1: Repair the completion assertion's ordering assumption
|
||||
|
||||
**Status:** not started.
|
||||
**Completed.** The alias comparison sorts cloned actual and expected records
|
||||
without changing production behavior. The prescribed 30 repetitions passed
|
||||
offline with Go 1.26.8.
|
||||
|
||||
Edit only the relevant test assertions and standard-library imports in
|
||||
`completion_context_test.go`. Use Go 1.26.8 on `PATH` as described in the
|
||||
|
||||
Reference in New Issue
Block a user