marfrit/aish
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

TC #73 — Phase 7 :cost detail 3-level deterministic sort #73

New Issue
Closed
opened 2026-05-16 23:03:28 +00:00 by claude-noether · 1 comment
claude-noether commented 2026-05-16 23:03:28 +00:00
Collaborator
Copy Link
Copy Source

Scenario

Multiple slots; some with equal cost.

Expected

Sort order: (cost desc, model asc, category asc). Re-running :cost detail produces identical row order each time (no shuffle on equal-cost rows because of the model/category tiebreaker).
R7 — table.sort is unstable; the 3-key sort makes it deterministic.

## Scenario Multiple slots; some with equal cost. ## Expected Sort order: (cost desc, model asc, category asc). Re-running `:cost detail` produces identical row order each time (no shuffle on equal-cost rows because of the model/category tiebreaker). R7 — table.sort is unstable; the 3-key sort makes it deterministic.
claude-noether added the test-case label 2026-05-16 23:03:28 +00:00
claude-noether commented 2026-05-16 23:04:18 +00:00
Author
Collaborator
Copy Link
Copy Source

Verified PASS via autonomous test driver at commit 1f34b6d (Phase 7 implement-complete).

3-level sort (cost desc, model asc, category asc) deterministic across 3 runs on 3 equal-cost rows. Order: a_model/delegate, a_model/main, b_model/main — correct tiebreaker.

Closed by Phase 7 verify.

Verified PASS via autonomous test driver at commit `1f34b6d` (Phase 7 implement-complete). 3-level sort (cost desc, model asc, category asc) deterministic across 3 runs on 3 equal-cost rows. Order: a_model/delegate, a_model/main, b_model/main — correct tiebreaker. Closed by Phase 7 verify.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Behavior diverges from documented or expected operation.
 feature request
User-facing capability that aish does not yet have.
 recommendation
Concrete suggestion (config, deployment, integration) outside the strict feature/bug split.
 security
Affects credential/key/PII handling, sandboxing, or trust boundaries.
 test-case
User-runnable test scenario; comment to confirm pass or add `bug` tag on fail
No Label test-case
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude-noether (Claude (noether)) marfrit (Markus Fritsche)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marfrit/aish#73
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?