Best possible solution:

Park this protected draft while maintainers resolve or review #95087 as the combined replacement, or explicitly revive this smaller slice with real QMD mapped-identity proof.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is an internal staged refactor/migration PR rather than a standalone bug report. Source inspection shows the intended mapped-identity path, but this PR body and comments do not show real QMD export/search proof.

Is this the best way to solve the issue?

Unclear for this PR as the landing path: the QMD mapping shape is plausible, but the author now points to #95087 as the combined replacement. The best solution depends on maintainer stack direction and a clean replacement branch or fresh proof for this smaller slice.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against a594d2ce7325.

Label justifications:

• P2: This is a normal-priority internal memory-core migration slice with bounded scope but meaningful session search visibility impact.
• merge-risk: 🚨 session-state: The PR changes how QMD search artifacts resolve to session identity before visibility filtering, which could mis-associate or hide session history if mappings are stale or wrong.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body and comments list tests/checks and supersession notes, but do not include redacted live output, logs, terminal output, screenshots, recordings, or linked artifacts showing after-fix QMD mapped identity behavior; after adding proof, update the PR body so ClawSweeper can re-review, or ask a maintainer to comment @clawsweeper re-review.

PR surface:

Source +425, Tests +242. Total +667 across 4 files.

What I checked:

• Repository policy applied: Root policy requires full AGENTS review and treats plugin APIs, auth/session state, persisted preferences, migrations, fallback behavior, and session-state surfaces as compatibility-sensitive review areas. (AGENTS.md:28, a594d2ce7325)
• Scoped extension policy applied: The scoped extensions guide says bundled plugin production code should use plugin SDK imports and treats extension files as private unless promoted through documented plugin surfaces. (extensions/AGENTS.md:27, a594d2ce7325)
• Live PR state is protected and unproven: GitHub reports this PR open, draft, mergeable, labeled maintainer and status: 📣 needs proof, and the PR body has no real behavior proof section; the author comments twice say it is superseded by refactor: add memory and QMD session identity mapping #95087. (c14d91e43907)
• Current main does not implement the mapping: Current main has no qmd-session-artifacts module, QMD_SESSION_ARTIFACT symbol, openclaw_qmd_session_artifacts table, or readQmdSessionArtifactIdentity path under the relevant memory-core/session files. (a594d2ce7325)
• Current main uses filename-derived visibility: The current visibility filter still calls extractTranscriptIdentityFromSessionsMemoryHit(hit.path) directly for session hits, so QMD Markdown artifact names remain part of the identity fallback path on main. (extensions/memory-core/src/session-search-visibility.ts:87, a594d2ce7325)
• Current main exports QMD markdown without identity mapping: Current exportSessions() writes <session>.md artifacts and tracks exported state, but does not persist a separate artifact-to-session mapping. (extensions/memory-core/src/memory/qmd-manager.ts:2528, a594d2ce7325)

Likely related people:

• jalehman: Authored the current PR, the proof-positive replacement PR, and the merged adjacent SDK transcript identity target API that this QMD mapping builds on. (role: recent Path 3 API contributor and stack context holder; confidence: high; commits: c14d91e43907, 0c90ccb6c280, 7a0d36f3d0e1; files: extensions/memory-core/src/qmd-session-artifacts.ts, extensions/memory-core/src/memory/qmd-manager.ts, extensions/memory-core/src/session-search-visibility.ts)
• vincentkoc: Current-main blame and recent history for the visibility filter, QMD manager, and memory host types point to recent work by Vincent Koc on the affected area. (role: recent memory-core and QMD area contributor; confidence: high; commits: 095a44c8de4d, c645ec4555c0, 118a4974966d; files: extensions/memory-core/src/session-search-visibility.ts, extensions/memory-core/src/memory/qmd-manager.ts, packages/memory-host-sdk/src/host/types.ts)
• steipete: Shortlog and path history show substantial earlier ownership of qmd-manager.ts and memory/QMD architecture refactors adjacent to this change. (role: major QMD and memory refactor contributor; confidence: medium; commits: 77e6e4cf87f7, 645c7b189757, 30c686423f12; files: extensions/memory-core/src/memory/qmd-manager.ts)
• Takhoffman: Path history shows adjacent QMD recall and memory excerpt work that shares the search-result visibility surface touched here. (role: adjacent QMD search/context contributor; confidence: medium; commits: 4f00b769251d, 885209ed0330; files: extensions/memory-core/src/memory/qmd-manager.ts)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.