Skip to content

test(mcp): fix summary_available time-bomb tests (main red as of 2026-07-01) #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tachyon-beep merged 1 commit into from
Jul 1, 2026
Merged

test(mcp): fix summary_available time-bomb tests (main red as of 2026-07-01) #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions crates/loomweave-mcp/tests/storage_tools.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6854,7 +6854,13 @@ async fn orientation_pack_dossier_summary_available_true_when_cached() {
)
.expect("upsert summary cache");

let state = state_for(project.path(), &db_path);
// Pin the clock just after the seeded created_at so the cache is
// unambiguously fresh: with the real wall clock, the 2026-01-01 row ages
// past the 180-day summary-cache horizon and summary_available flips to
// false (a time-bomb that fires on 2026-07-01). This test is about the
// key MATCH, not freshness, so freeze time to isolate that.
let state =
state_for(project.path(), &db_path).with_clock(|| "2026-01-02T00:00:00Z".to_owned());
let out = call_tool(
&state,
"orientation_pack",
Expand Down Expand Up @@ -6902,7 +6908,12 @@ async fn orientation_pack_dossier_summary_available_false_on_stale_cache_key() {
)
.expect("upsert summary cache");

let state = state_for(project.path(), &db_path);
// Pin the clock just after the seeded created_at so freshness is NOT a
// factor: the row must read as false purely because the model_tier key
// mismatches, not because the 2026-01-01 row aged past the cache horizon
// under the real wall clock (which would make it false for the wrong reason).
let state =
state_for(project.path(), &db_path).with_clock(|| "2026-01-02T00:00:00Z".to_owned());
let out = call_tool(
&state,
"orientation_pack",
Expand Down