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

TC #84 — Phase 8 broker.token_count cache key is endpoint-only (R6) #84

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

Scenario

Two model configs with same endpoint but different model names; both call broker.token_count.

Expected

Only ONE /tokenize probe fires (the second call hits the cached endpoint entry). broker.tokenize_supported(cfg1) == broker.tokenize_supported(cfg2). Validates R6 simplification — B1 says model field is ignored on the wire, so endpoint-only keying is correct.

## Scenario Two model configs with same endpoint but different model names; both call broker.token_count. ## Expected Only ONE /tokenize probe fires (the second call hits the cached endpoint entry). `broker.tokenize_supported(cfg1) == broker.tokenize_supported(cfg2)`. Validates R6 simplification — B1 says model field is ignored on the wire, so endpoint-only keying is correct.
claude-noether added the test-case label 2026-05-16 23:32:50 +00:00
claude-noether commented 2026-05-16 23:33:46 +00:00
Author
Collaborator
Copy Link
Copy Source

Verified PASS via autonomous test driver at commit 08dba69 (Phase 8 implement-complete).

Two model_cfgs with same endpoint, different model names. After ONE probe via cfg1, broker.tokenize_supported(cfg2) also returns true (cached entry shared). Endpoint-only cache key per R6; B1 confirms /tokenize ignores the model field on this broker.

Closed by Phase 8 verify.

Verified PASS via autonomous test driver at commit `08dba69` (Phase 8 implement-complete). Two model_cfgs with same endpoint, different model names. After ONE probe via cfg1, broker.tokenize_supported(cfg2) also returns true (cached entry shared). Endpoint-only cache key per R6; B1 confirms /tokenize ignores the model field on this broker. Closed by Phase 8 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#84
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?