Problem
JSON search output has paths and scores but no timestamp for when the index was built. Tools reporting "snapshot from June 16" can't get this information without reading the raw index file and parsing generated_at themselves.
ContextIndex.GeneratedAt already exists in .ctx/ctx_index.json but is not surfaced in search-hints output.
Proposed Solution
Add index_generated_at to JSON output (part of the envelope from #2):
{
"source": "snapshot",
"index_generated_at": "2026-06-16T10:00:00Z",
"results": [...]
}
Or as standalone top-level field if envelope approach is rejected.
Implementation Notes
ContextIndex.GeneratedAt is already populated by init, watch, and sync
- Pass it through to the JSON serialization layer in
command_search.go
- For memory search, the watch server could include it in the response (or client reads from index file)
Acceptance Criteria
Problem
JSON search output has paths and scores but no timestamp for when the index was built. Tools reporting "snapshot from June 16" can't get this information without reading the raw index file and parsing
generated_atthemselves.ContextIndex.GeneratedAtalready exists in.ctx/ctx_index.jsonbut is not surfaced in search-hints output.Proposed Solution
Add
index_generated_atto JSON output (part of the envelope from #2):{ "source": "snapshot", "index_generated_at": "2026-06-16T10:00:00Z", "results": [...] }Or as standalone top-level field if envelope approach is rejected.
Implementation Notes
ContextIndex.GeneratedAtis already populated byinit,watch, andsynccommand_search.goAcceptance Criteria
--jsonoutput includesindex_generated_atin ISO 8601 format