lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(specs): mark four finished specs implemented

Browse source 
scheduler-sim-diagnostics, scheduler-sim-live-allocation, xce-test-cli-ux
and eliminate-frontend-makefile had every sub-task checked but their
parent boxes and spec.json phase still read tasks-generated.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-09-29 13:00:11 +00:00
parent 7b001cb0f7
commit c2b3bf6473
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
7 changed files with 19 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

4
.kiro/specs/scheduler-sim-diagnostics/tasks.md
View file

@ -75,7 +75,7 @@
- _Requirements: 6.1, 6.3, 6.5, 5.3_
- _Boundary: Shared Units Formatter, REPL Limit Info Command (the retyped composer and its thin-wrapper callers live in `repl_info.c`/`repl_fmt.c`)_
- [ ] 8. Core: Human-readable configured-setting display
- [x] 8. Core: Human-readable configured-setting display
- [x] 8.1 Add a display-mode-aware way to render a limit's configured setting
- New entry point produces the same configured-setting output the existing formatter already produces, except a byte-valued, non-percentage resource's amount renders in human-readable form according to a supplied display mode
- The existing formatter's own output is provably unchanged for every input it can be given — proven by its complete pre-existing test coverage continuing to pass with zero modification
@ -99,7 +99,7 @@
- _Depends: 7_ — task 7 retypes the exact shared formatting call chain this task's fix flows through (the limit usage display's classification feeds into that same composer); sequencing after 7 avoids two tasks editing overlapping logic in an uncoordinated order, not a data dependency on any new symbol this task itself needs
- _Boundary: REPL Limit Info Command_
- [ ] 10. Validation: Confirm correctness, consistency, and no regression
- [x] 10. Validation: Confirm correctness, consistency, and no regression
- [x] 10.1 Re-verify existing test coverage against the corrected usage display
- Task 9 found that fixing the resource-classification defect did NOT break any pre-existing assertion outright — instead, several existing assertions on the live usage display's amounts turned out to be loose substring checks against whole-number fixture values, which happen to still match the corrected, human-augmented output by coincidence of formatting (the old expected text is a literal prefix of the new one) rather than by genuinely exercising the fix
- Identify every such loose, coincidentally-still-passing assertion, and strengthen each one to assert the actual corrected output precisely enough that it would fail if the resource-classification fix were reverted