feat(storage): activate Postgres profiles with async agent persistence - #185
Draft
Yuge Zhang (ultmaster) wants to merge 2 commits into
Conversation
This was referenced Sep 14, 2026
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.
Migrates Agenetes thread, event, and turn persistence to async operations and activates Postgres across the application. With the adapter foundation in #184, all six structured/blob backend pairings become selectable, including Postgres with Azure Blob.
This is 2 of 2 stacked PRs, based on #184's foundation branch. Its diff contains the async persistence migration, Postgres conversation stores, application activation, product coverage, and final Phase 6 documentation. Merge #184 first, then retarget/rebase this PR onto
mainbefore merging it. The base branch inmicrosoft/Huabumirrors the foundation PR head; both PR heads remain on the fork.Persistence completes before notifications are emitted. Queued reports and shutdown await writes, and the event-tail fence handles concurrent persistence. Native Postgres conversation tables support the agent runtime; application callers now await persistence throughout. Configuration and the existing proposal document the supported profiles, capabilities, and remaining work.
Validation:
pnpm test:storage-backends: all 265 checks passed against disposable PostgreSQL and Azurite, including conversation and product coverage.Azure validation uses Azurite; live-account validation and multi-Server coordination remain outside this change.