feat(recall): add bounded atomic memory manifest by Tech-Circle-48 · Pull Request #2192 · oceanbase/powercontext

Tech-Circle-48 · 2026-10-22T07:35:28Z

Which issue or RFC does this PR close?

Rationale for this change

Agents currently need to retrieve memory content before deciding which entries are useful. A bounded, metadata-only manifest provides a cheaper first step, allowing agents to select entries before fetching their full content.

What changes are included in this PR?

Add a paginated Atomic Memory recall manifest through HTTP, MCP, and the Python client.
Store descriptions with memory revisions and their current search projections.
Generate descriptions alongside text during extraction and reconciliation.
Preserve model-free explicit writes by storing a bounded, single-line text preview when no description is supplied.
Update integration bindings, migration compatibility, documentation, and regression tests.

Are there any user-facing changes?

Add POST /v1/recall/manifest and get_recall_manifest.
This initial implementation covers active Atomic Memory only.
Callers may supply an optional description. Omitting it does not require an LLM.
Manifest reads return metadata without reading memory bodies or invoking models.
Historical memories without descriptions remain readable; their manifest descriptions may be null.
Manifest pagination defaults to 50 entries, with a maximum of 100.

How was this change tested?

make check
Python and JavaScript API generation consistency checks.
HTTP/MCP contract tests.
Non-Desktop Python regression suite: 6,175 passed, with 10 working-directory-dependent tests passing on rerun from the repository root; 593 skipped.
Dify and OpenDAL integration checks.
DSH unit and end-to-end tests, plus build reproducibility verification.
Manual Postman verification of memory writes and manifest responses.

AI usage statement

hidb4ai

The tagged manifest path rejects valid input, and the Desktop and skill-validation contracts need to be synchronized. Details inline.

hidb4ai

Rechecked at 080b2d2. The tag conversion and skill catalog fixes pass. A manifest pagination issue remains below; the Desktop contract mismatch is still reproducible and is followed up in its original thread.

hidb4ai

One blocking upgrade regression remains at 984101b7; details inline.

…n upgrade

hidb4ai

Rechecked b36f7615: the previous nonempty SQLite upgrade failure is fixed. The original reproduction now reaches v1_4_1_004 and verifies successfully.

Please address the remaining issues before merging:

The existing OceanBase exact-kind P2 remains unchanged: manifest() still uses plain kind == kind at runtime/atomic_memory.py:443, unlike the exact comparisons in list/search.
Current master aedf7beb already registers v1_4_1_004 for durable owner-recovery storage, while this branch uses the same revision/resource names for descriptions. git merge-tree confirms conflicts in the migration, schema resources, manifests and vector layout; GitHub also reports CONFLICTING. Please integrate both storage changes into a consistent registered chain and rerun upgrades and checks on the resulting merge.

CI attribution: the reported Main jobs ran merge commit 038a8f9c (b36f7615 merged into 927bb6ee), rather than the PR head alone. I reproduced the policy failure and the owner-recovery/cross-database E2E failures on that CI base without this PR; the PR head's own policy check passes. Please refresh the compatibility review for the final integrated tree and provide passing validation with the updated commit.

hireview001

CI failed: tests (3.14, unit) (failure).
CI failed: tests (3.11, unit) (failure).
CI failed: tests (3.13, unit) (failure).
CI failed: tests (3.12, unit) (failure).
CI failed: Main (failure). Failed steps: tests (3.12, unit) / Run unit tests; tests (3.13, unit) / Run unit tests; tests (3.11, unit) / Run unit tests.

PR oceanbase#2192 registers `v1_4_1_005` for the atomic memory description revision and opened six days earlier, so it keeps that number. Two open pull requests claiming one revision name would ship two different DDL sets and two different offline fingerprints under a single name, and the winner would depend on merge order. This PR moves to the next free number instead. The chain is otherwise unchanged: `down_revision` stays `v1_4_1_004`, the SQLite fingerprint is unchanged because inventory never contains the revision name, and `release/upgrade-support.json` is re-digested with `scripts/upgrade_release_gate.py::managed_digest`. When oceanbase#2192 lands first this revision will rebase onto it and point `down_revision` at its `v1_4_1_005`. Verified with `tests/test_migration_revision_names.py`, `test_full_server_migrations.py`, `test_portable_storage_migration.py`, `test_owner_recovery_migration.py`, `test_release140_server_migrations.py` and `test_server_migration_cli.py` (46 passed), plus a full `s1300`-to-head replay that reproduces every recorded fingerprint.

hireview001

CI failed: cindy-package (failure).
CI failed: Main (failure). Failed steps: cindy-package / Build and test the standalone Cindy archive.

…x/pr2192-resolve-conflicts-20261030

hidb4ai

LGTM

feat(recall): add bounded atomic memory manifest

8e919d8

Tech-Circle-48 requested review from AlexStocks, PsiACE, Zxf-xufeng, frostming, knqiufan, yihong0618 and zhanghuidinah as code owners October 22, 2026 07:35

Tech-Circle-48 added 4 commits October 22, 2026 15:43

chore(desktop): align generated files with upstream

6c3e4a9

fix: reconcile atomic memory processing changes

2fa557f

Merge branch 'master' into s3

dbf15ed

fix(memory): preserve model-free writes and integration compatibility

85e0303

Tech-Circle-48 requested a review from Alanxtl as a code owner October 22, 2026 09:01

hidb4ai reviewed Oct 22, 2026

View reviewed changes

Comment thread src/powercontext/server/atomic_memory.py Resolved

Comment thread desktop/ui/src/generated/api.d.ts Resolved

Comment thread src/powercontext/server/mcp.py Resolved

AlexStocks mentioned this pull request Oct 22, 2026

feat(processing): classify artifact processing failures with safe diagnostics (#2126) #2189

Merged

AlexStocks reviewed Oct 22, 2026

View reviewed changes

Comment thread src/powercontext/builtin/persistence/topic_memory_recovery_schema.py Resolved

AlexStocks reviewed Oct 22, 2026

View reviewed changes

Comment thread src/powercontext/builtin/runtime/composition.py Resolved

AlexStocks reviewed Oct 22, 2026

View reviewed changes

Comment thread src/powercontext/builtin/artifacts/atomic_memory/extraction.py Resolved

Tech-Circle-48 added 4 commits October 22, 2026 17:53

fix(memory): reject model-supplied creation metadata

7ce6f73

fix(runtime): preserve injected generation components

3909595

fix(migrations): recognize ALTER-added memory descriptions

73a645b

fix(evals): synchronize recall manifest tool catalog

7284c0c

Tech-Circle-48 requested a review from frf12 as a code owner October 22, 2026 10:10

Tech-Circle-48 added 2 commits October 22, 2026 18:19

fix(desktop): regenerate API and IPC contracts

36a446a

fix(tags): unwrap atomic memory HTTP tag filters

1da7621

hidb4ai reviewed Oct 22, 2026

View reviewed changes

Comment thread src/powercontext/builtin/runtime/atomic_memory.py Resolved

fix(recall): bound manifest cursor size

530b99c

Tech-Circle-48 force-pushed the s3 branch 2 times, most recently from a36e595 to 530b99c Compare October 23, 2026 02:20

Merge branch 'master' into s3

ec937dc

Tech-Circle-48 added 2 commits October 27, 2026 15:21

fix(ci): refresh desktop qualification and isolate upgrade test

3b8d3ff

Merge remote-tracking branch 'upstream/master' into s3

984101b

hidb4ai reviewed Oct 27, 2026

View reviewed changes

Comment thread ...tin/persistence/migrations/server_resources/versions/v1_4_1_004_atomic_memory_description.py Resolved

fix(migrations): validate legacy memory projections before descriptio…

b36f761

…n upgrade

hidb4ai reviewed Oct 28, 2026

View reviewed changes

Tech-Circle-48 added 3 commits October 28, 2026 16:48

fix(ci): resolve upstream migration and contract conflicts

99f0440

Merge branch 'master' into s3

7354022

Merge branch 'master' into s3

23c2827

AlexStocks reviewed Oct 28, 2026

View reviewed changes

Comment thread src/powercontext/builtin/runtime/atomic_memory.py Resolved

fix(recall): restore timing and extraction rules after merge

ce87f44

AlexStocks reviewed Oct 28, 2026

View reviewed changes

Comment thread src/powercontext/builtin/artifacts/prompt/builtin.py Resolved

hireview001 reviewed Oct 28, 2026

View reviewed changes

Tech-Circle-48 added 2 commits October 29, 2026 14:22

Merge branch 'master' into s3

1953951

fix(evaluation): refresh atomic extraction evidence

27d499e

AlexStocks reviewed Oct 29, 2026

View reviewed changes

Comment thread src/powercontext/builtin/persistence/migrations/server_resources/manifest.json Resolved

AlexStocks reviewed Oct 29, 2026

View reviewed changes

Comment thread openapi/powercontext.yaml Resolved

AlexStocks mentioned this pull request Oct 29, 2026

feat(runtime): durable Work Ledger rebased onto current master #2270

Open

hireview001 reviewed Oct 29, 2026

View reviewed changes

Comment thread src/powercontext/builtin/runtime/application.py Resolved

Tech-Circle-48 and others added 7 commits October 30, 2026 09:36

Merge commit '6bdba9bcc3e46aeca71c189bc0ebdc27b8bb72c5^1' into s3

6518f00

fix(cindy): rebuild worker with recall manifest operation

37089ed

fix(runtime): keep explicit memory writes outside generation slots

4028045

merge: sync master and reconcile persistence compatibility review

b7c1dd5

merge: resolve recall manifest conflicts with master

4b044eb

Merge remote-tracking branch 'refs/remotes/upstream/master' into code…

8835a3a

…x/pr2192-resolve-conflicts-20261030

merge: reconcile upgrade policy with master

751a0d9

hidb4ai approved these changes Oct 30, 2026

View reviewed changes

hidb4ai merged commit 90355b8 into oceanbase:master Oct 30, 2026
34 checks passed

AlexStocks mentioned this pull request Oct 30, 2026

feat(sources): preserve citation position locators #2296

Open

Fengzdadi mentioned this pull request Oct 31, 2026

fix(integrations): report a coded 404 as an invalid response in WorkBuddy and OpenCode #2322

Open

Conversation

Tech-Circle-48 commented Oct 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Which issue or RFC does this PR close?

Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

How was this change tested?

AI usage statement

Uh oh!

hidb4ai left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

hidb4ai left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

hidb4ai left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

hidb4ai left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

hireview001 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

hireview001 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

hidb4ai left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Tech-Circle-48 commented Oct 22, 2026 •

edited

Loading