Best possible solution:

Keep the resolver fix and regression test, add the missing changelog credit, then merge once normal maintainer checks pass.

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

Yes. Source inspection gives a high-confidence path: Telegram topic sessions produce a colon-containing conversation id, current Active Memory can pass that id as messageChannel, and bundled plugin dir-name validation rejects ':'.

Is this the best way to solve the issue?

Yes. Resolving this inside Active Memory by ignoring scoped conversation ids for runnable channel selection and falling back to messageProvider is the narrow maintainable fix; the remaining cleanup is changelog credit only.

Full review comments:

• [P3] Credit the contributor in the changelog entry — CHANGELOG.md:39
  OpenClaw changelog policy asks contributor-facing entries to include a human Thanks @... credit. This new user-facing fix entry currently has no credit despite known human contributors, so the release-note credit audit will need a follow-up.
  Confidence: 0.83

Overall correctness: patch is correct
Overall confidence: 0.86

Acceptance criteria:

• pnpm test extensions/active-memory/index.test.ts
• pnpm exec oxfmt --check --threads=1 extensions/active-memory/index.ts extensions/active-memory/index.test.ts
• git diff --check

What I checked:

• Current-main bug path: Current main normalizes ctx.channelId into explicitChannel and can pass it directly as runEmbeddedPiAgent messageChannel before provider fallback. (extensions/active-memory/index.ts:507, d0497d13d18e)
• Hook context separates provider from conversation target: Hook context returns the raw session conversation id as channelId while preserving messageProvider separately, so a topic conversation id can reach Active Memory as channelId. (src/plugins/hook-agent-context.ts:44, d0497d13d18e)
• Telegram topic id shape: Telegram topic conversations are encoded as ':topic:', matching the colon-containing id reported in [Bug]: active-memory fails in Telegram forum topic sessions with directory-name validation error #76704. (extensions/telegram/src/topic-conversation.ts:16, d0497d13d18e)
• Reported throw is source-backed: Bundled plugin dir-name validation rejects any dirName containing ':', so using a Telegram topic conversation id as messageChannel reaches the reported validation error. (src/plugins/public-surface-runtime.ts:49, d0497d13d18e)
• PR fix and regression coverage: The provided PR head introduces runnableExplicitChannel, falls back to messageProvider for scoped ids, and adds a Telegram forum-topic regression test around runEmbeddedPiAgent messageChannel. (extensions/active-memory/index.ts:506, 7d3e1cca27a2)
• Changelog credit gap: The PR adds a user-facing fix entry but omits the usual contributor Thanks attribution even though the PR and linked report identify human contributors. (CHANGELOG.md:39, 7d3e1cca27a2)

Likely related people:

• steipete: Current checkout history and blame for the Active Memory resolver, hook channel context, Telegram topic parser, and bundled public-surface validation point to Peter Steinberger's recent commits across the relevant paths. (role: introduced behavior / adjacent maintainer; confidence: medium; commits: 8c95664e5596, 9e56cfcc3588, 103b6d50a5b6; files: extensions/active-memory/index.ts, src/plugins/hook-agent-context.ts, extensions/telegram/src/topic-conversation.ts)

Remaining risk / open question:

• I did not run the new Active Memory test or observe CI in this read-only review.

Codex review notes: model gpt-5.5, reasoning high; reviewed against d0497d13d18e.