Conversation
…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.
…t probe GitLab's /api/v4/version requires authentication by API design, so a healthy self-hosted instance answers a bare curl with 401. The probe text listed the authenticated call as an alternative, so agents following it verbatim burned a failed round before discovering this (hit live against git.ycgame.com). Encode both facts: a 401 is positive evidence that the endpoint exists and answers, and glab api version is the re-verification step after auth passes.
fix(server): wire Memory.node into the delivered httpapi app graph
fix(core): encode GitLab version-endpoint auth in dag-init probe
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.
本批次（dev → main）
#313 → Closes #311：修复 Memory 服务在实机会话不可达——server.ts 交付图 app 组补 Memory.node，新增装配缝回归测试（回退即红复现字面症状）。四泳道仲裁 ACCEPT，指纹绑定。
#314 → Closes #312：dag-init 自建 GitLab 探测编码版本端点认证语义（401=阳性证据 + 鉴权后 glab 复核），消除 agent 必吃一次的失败回合。
dev 验证状态
main 门禁
Typecheck + Unit Tests (linux) + E2E (linux/windows) 四项全绿后合并。