fix(server): wire Memory.node into the delivered httpapi app graph - #313
Merged
Conversation
feat(core): release v1.0.23 — built-in /dag-init and /dag-auto ultra-flow commands
…ssue #311) Memory.node appeared in every consumer's dependency array, but LayerNode builds feed dependencies only to a node's own implementation body without re-export — the ambient context delivered to live sessions is the mergeAll of the app group's direct members at server.ts buildLayer call site, which lacked Memory.node. All five serviceOption(Memory.Service) guards therefore silently resolved None: /memory answered 'remains off' and memory_search 'Unabailable' despite a valid identity and init stamp. Add Memory.node to the app group and export the app graph so the new regression test builds the exact production delivery graph: one probe asserts Memory.Service is reachable inside it, one drives the real /memory command end-to-end. Reverting the wiring turns the test 0/2 with the literal symptom.
Drop the retired V2 session vocabulary, point extenders at src/memory and src/config references, and record the /dag-* command family, template precedence, the /init memory-activation gate, and the release-notes template requirement.
This was referenced Aug 17, 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
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.
Closes #311
根因（debug-repair-full 四泳道仲裁实证，指纹 sha256:37c7ee25…）
五处
Effect.serviceOption(Memory.Service)守卫（/memory 拦截器、memory_search 工具、system prompt、compaction、bootstrap）全部静默解析为 None。Memory.node出现在每个消费方的依赖数组里——看起来接着线——但 LayerNode 构建只把依赖喂给节点自身实现体、不做再导出；真实交付给会话的环境上下文是server.ts唯一buildLayer(app)调用点的 app 组直接成员 mergeAll，该组缺 Memory.node。这与本文件 SettingsHook/HookRewakeLive 注释记载的已知失效类同源，serviceOption使缺线静默 no-op。修复（最小因果改动）
server.ts：app 组补Memory.node（带 fix(memory): /memory on and memory_search unreachable in live session despite valid identity and init stamp #311 注释）+export const app——导出装配图使回归测试构建生产同款交付图而非手抄节点清单test/server/httpapi-memory-wiring.test.ts：①装配图内断言 Memory.Service 可达（五处守卫的同款解析路径）②端到端驱动真实/memory on命令断言 "Memory on"验证（全部会话内复跑）
范围守卫：零 core 改动、零守卫串改动、零激活模型改动 → 无需 SDK 再生。AGENTS.md 为随附文档提交（已过 review 验证 docs-only）。
交付链说明
export const app是故意暴露的装配缝：回归锁定的是 server.ts:323 交付的环境图本身，任何未来改动若使 Memory 离开交付图将立即以真实症状失败。