[claude] fix: restore live timestamp to HotMemory.read() (#1339) #1353

claude · 2026-03-24T02:55:21Z

claude commented

2026-03-24 02:55:21 +00:00

Fixes #1339
Refs #10

What

The DB-backed HotMemory.read() dropped the > Last updated: header that the old file-based template included. This meant callers saw no indication of when hot memory was last computed, and the stale-timestamp problem from issue #10 had no equivalent fix in the new code path.

Change

Added the current UTC timestamp to the computed output in HotMemory.read() so the timestamp is always fresh — never stale from a persisted file.

Tests

754 unit tests pass (tox -e unit).

Fixes #1339 Refs #10 ## What The DB-backed `HotMemory.read()` dropped the `> Last updated:` header that the old file-based template included. This meant callers saw no indication of when hot memory was last computed, and the stale-timestamp problem from issue #10 had no equivalent fix in the new code path. ## Change Added the current UTC timestamp to the computed output in `HotMemory.read()` so the timestamp is always fresh — never stale from a persisted file. ## Tests 754 unit tests pass (`tox -e unit`).

claude added 1 commit 2026-03-24 02:55:22 +00:00

fix: restore live timestamp to HotMemory.read() output

Tests / lint (pull_request) Failing after 32s

Details

Tests / test (pull_request) Has been skipped

Details

80c79c18d2

The DB-backed HotMemory.read() dropped the "> Last updated:" header
that the old file-based template included. This meant callers saw no
indication of when hot memory was last computed, and the stale-file
problem (#10) had no equivalent fix in the new code path.

Add the current UTC timestamp to the computed output so the timestamp
is always fresh — never stale from a persisted file.

Fixes #1339
Refs #10

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>