You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(memory): wire ctx into unified DSH memory pull - #121
Finish the ctx × z0intelligence integration from #116 on top of the current unified-memory wiring branch, and make it usable from DSH without putting ctx on the latency-critical push path.
Supersedes the isolated integration direction in #117; this PR ports that read-only adapter into the full memory surface.
add ctx as the fourth pull layer of the unified z0 memory surface;
derive project scope from ctx cwd; unknown scope fails closed instead of becoming user-global;
preserve the ctx Core generation in the memory snapshot;
bypass the brief cache when ctx participates so a stale Core generation cannot be served;
add exact ctx:event:<id> hydration to inspect;
expose ctx through the read-only z0-memory MCP profile used by DSH;
keep the automatic agent/pre-step push path on temporal + AgentsView + TencentDB only (ctx remains outside the 300 ms budget);
add one combined DSH patch: harness-adapters/dsh-z0intelligence/z0-dsh.cordis.yml.
DSH run
export Z0INT_PYTHON="${Z0INT_PYTHON:-$HOME/.z0int/bin/python}"
dsh web --patch "$PWD/harness-adapters/dsh-z0intelligence/z0-dsh.cordis.yml"
This starts the existing capture/shadow seam and the read-only z0-memory stdio MCP. The model can use memory_search and exact inspect hydration; ctx failure remains an explicit layer miss and AgentsView/EventLog/TencentDB continue independently.
Current local-ingest context
The current ctx import is expanding Claude Code/Hermes roots. DSH's native session.v3 zstd store is currently reported empty by ctx and OpenCode still has mixed-format rejects. This PR deliberately does not depend on those imports: incomplete ctx coverage degrades to the existing z0 memory layers.
DSH chore(deps): bump actions/stale from 9 to 11 #5 is only the experimental push A/B arm: z0int context resolve -> agent/pre-step -> actual model request, with off/shadow/inject and default off.
That lets the acceptance matrix compare pull vs native automatic injection without prematurely putting ctx inside the 300 ms push budget. Promotion still requires the real-history matrix + verified answer/token/latency evidence.
Memory issues are now reconciled under #22; #116 names this PR as the current ctx/DSH pull integration, superseding #117's isolated direction. Keep the pull-versus-push boundary, read-only/semantic opt-ins and existing scoped snapshot/receipt contracts. This remains branch-only at audited head 158931b1a6429bfc70fd1c87d80d6e8ee8ebb966; neither #122's setup receipt nor the old bakeoff proves the real-history handoff here. The remaining gate is source-backed model-visible use plus correction/staleness/duplicate/scope negative controls, using the shared evaluation rather than a new benchmark.
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
area:docsDocumentationarea:verifyTests, mutation, evidenceparkedClosed under the salvage plan; branch kept; reopen when something that runs needs it
1 participant
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.
Goal
Finish the ctx × z0intelligence integration from #116 on top of the current unified-memory wiring branch, and make it usable from DSH without putting ctx on the latency-critical push path.
Supersedes the isolated integration direction in #117; this PR ports that read-only adapter into the full memory surface.
What changes
CtxHistoryCapabilityfrom feat(memory): add read-only ctx history capability #117, preserving--refresh off, Core generation identity, exact event/session locators, zero-write env guards and semantic opt-in;--include-current-sessionand keyword--termalternatives to address the feat(memory): add read-only ctx history capability #117 bakeoff findings;cwd; unknown scope fails closed instead of becoming user-global;ctx:event:<id>hydration toinspect;z0-memoryMCP profile used by DSH;agent/pre-steppush path on temporal + AgentsView + TencentDB only (ctx remains outside the 300 ms budget);harness-adapters/dsh-z0intelligence/z0-dsh.cordis.yml.DSH run
This starts the existing capture/shadow seam and the read-only
z0-memorystdio MCP. The model can usememory_searchand exactinspecthydration; ctx failure remains an explicit layer miss and AgentsView/EventLog/TencentDB continue independently.Current local-ingest context
The current ctx import is expanding Claude Code/Hermes roots. DSH's native
session.v3zstd store is currently reported empty by ctx and OpenCode still has mixed-format rejects. This PR deliberately does not depend on those imports: incomplete ctx coverage degrades to the existing z0 memory layers.Invariants
No ctx import/index/setup/write command is added. No AODL authority changes. No direct memory DB replacement.
Verification
Deterministic tests cover the ported ctx protocol adapter, scope filtering, Core-generation snapshot changes, exact hydration, missing-ctx behavior, MCP pull-layer selection, and the DSH pull-vs-push boundary.
Closes the DSH integration slice of #116; keep #116 open for the real-history acceptance matrix and ctx provider/Blame parity.