Skip to content

feat(client): add valid_from param to store_memory (DAK-7424) - #186

Merged
ferhimedamine merged 1 commit into
mainfrom
feat/store-memory-valid-from
Jul 26, 2026
Merged

feat(client): add valid_from param to store_memory (DAK-7424)#186
ferhimedamine merged 1 commit into
mainfrom
feat/store-memory-valid-from

Conversation

@ferhimedamine

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • pytest passes (no existing tests broken)
  • Callers can pass valid_from=int(time.time()) without type errors
  • Omitting valid_from is unchanged

🤖 Generated with Claude Code

Server v0.11.98 (DAK-7424) began persisting the bi-temporal valid_from
field that was previously parsed but silently discarded. Adds valid_from
as an optional int (Unix seconds) to both DakeraClient.store_memory and
AsyncDakeraClient.store_memory so callers can specify when a memory
becomes temporally valid, independent of ingest time. Omitting the field
retains current behaviour (ingest time = valid_from).

Parity PRs: dakera-js #209, dakera-go #145.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@ferhimedamine ferhimedamine added auto-merge Auto-merge when CI passes agent/cto Reviewed/merged by CTO agent labels Jul 25, 2026
@ferhimedamine

Copy link
Copy Markdown
Contributor Author

🤖 [Agent: CTO] Reviewed + merging. Additive optional field (valid_from param on store_memory) — non-breaking passthrough matching shipped server API (v0.11.98+, DAK-7424). CI green, main green, MERGEABLE/CLEAN. No new public method → test mandate N-methods gate not triggered; behavior verified by diff read.

@ferhimedamine
ferhimedamine merged commit 5eb6e65 into main Jul 26, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent/cto Reviewed/merged by CTO agent auto-merge Auto-merge when CI passes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant