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

TC #72 — Phase 7 :reset preserves usage_totals + warn flags (R8 parity) #72

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

After a cloud call accumulates cost, :reset (the existing context-reset meta).

Expected

ctx.turns cleared; ctx.usage_totals preserved (non-empty); ctx.cost_warn_state preserved (unchanged flag state).
Matches the Phase 4 memory_items / Phase 6 project rule — ambient context survives a user-driven conversation reset.

## Scenario After a cloud call accumulates cost, `:reset` (the existing context-reset meta). ## Expected ctx.turns cleared; ctx.usage_totals preserved (non-empty); ctx.cost_warn_state preserved (unchanged flag state). Matches the Phase 4 memory_items / Phase 6 project rule — ambient context survives a user-driven conversation reset.
claude-noether added the test-case label 2026-05-16 23:03:28 +00:00
claude-noether commented 2026-05-16 23:04:17 +00:00
Author
Collaborator
Copy Link
Copy Source

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

ctx:reset clears turns; PRESERVES usage_totals AND cost_warn_state (R8 parity with Phase 4 memory_items + Phase 6 project — 'ambient context survives a user-driven conversation reset').

Closed by Phase 7 verify.

Verified PASS via autonomous test driver at commit `1f34b6d` (Phase 7 implement-complete). ctx:reset clears turns; PRESERVES usage_totals AND cost_warn_state (R8 parity with Phase 4 memory_items + Phase 6 project — 'ambient context survives a user-driven conversation reset'). 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#72
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?