feat(hcp): persist session history in Room - #324
Closed
daniele21 wants to merge 19 commits into
Closed
Conversation
daniele21
force-pushed
the
agent/hcp-g-session-telemetry
branch
from
August 18, 2026 14:50
1b94631 to
76604ef
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Superseded for integration by #346. This PR is the obsolete stacked HCP-15 branch based on the pre-replay session-contract line. #346 replays only the HCP-15 Room session-history slice onto
dev, preserving the already-integrated HCP-14 contract and avoiding stale stacked history. Keep this PR/branch only as historical recovery context until #346 is safely integrated; do not merge, rebase, or continue implementation here.Original scope:
Implements HCP-15 persistence foundation as a stacked child of session-contract PR #321.
Changes:
inference_sessionstable and generationsession_id/use_case_revision/binding_revisioncolumns;SessionTelemetryRepositoryon the same DB/executor lifecycle;This still does not switch the phone app composition from in-memory to Room or instrument session lifecycle; those remain HCP-16/phone composition follow-ups.