ci: create GitHub Release for OpenClaw local plugin publish

[Memtensor-AI]

背景

为了让 Doc Agent 通过 release.published 自动同步 OpenClaw 本地插件更新到 MemOS-Docs Plugin tab，本地插件发布 workflow 需要在 npm publish/tag 成功后创建规范 GitHub Release。

改动

• 新增 release_notes workflow_dispatch 输入，要求发布时填写可供 docs 同步消费的 Markdown changelog。
• 将本地插件新发版 tag 统一为 openclaw-local-plugin-v{version}。
• npm publish/tag 成功后自动创建 GitHub Release。
• Release 已存在时保持幂等，不重复覆盖。

不做什么

• 本 PR 不发布 npm 包。
• 本 PR 不创建产品 Release。
• 本 PR 不触发 MemOS-Docs 更新。
• CLI 和云插件后续单独处理。

验证

• 本地 YAML 解析通过。
• git diff --check 通过。

合并后，下一步会用 OpenClaw 本地插件做第一条完整链路验证：GitHub Release -> 106 Doc Agent -> docs PR -> auto merge -> pre -> 等待 360 秒 -> gray，且不触发 production。

[Memtensor-AI]

🤖 Open Code Review

Target: PR #2111
Task: 972ebf501a7a3139
Base: main
Head: docs-sync/openclaw-local-plugin-release

🔍 OpenCodeReview found 2 issue(s) in this PR.

---

1. .github/workflows/memos-local-plugin-publish.yml (L151-L153)

Inconsistent branding between release_tag and release_title/--title. The tag was renamed to openclaw-local-plugin-v* and the GitHub Release title uses "OpenClaw Local Plugin", but release_title (used for the git commit message and the PR title) still reads @memtensor/memos-local-plugin. This will produce a confusing mismatch: the tag is openclaw-local-plugin-v1.x, but the PR title says release: @memtensor/memos-local-plugin v1.x. Either revert the tag rename or update release_title to match the new branding.

💡 Suggested Change

Before:

          release_tag="openclaw-local-plugin-v${RELEASE_VERSION}"
          release_branch="release/${release_tag}"
          release_title="release: @memtensor/memos-local-plugin v${RELEASE_VERSION}"

After:

          release_tag="openclaw-local-plugin-v${RELEASE_VERSION}"
          release_branch="release/${release_tag}"
          release_title="release: OpenClaw Local Plugin v${RELEASE_VERSION}"

---

2. .github/workflows/memos-local-plugin-publish.yml (L139)

The inputs.release_notes value is multi-line Markdown that can contain colons, curly braces, and other YAML-special characters. Without explicit YAML quoting the expression is evaluated by GitHub's template engine before YAML parsing, which can break the YAML structure or silently truncate content when special characters appear. Wrap the expression in single quotes so the YAML parser treats the whole interpolated string as a scalar.

💡 Suggested Change

Before:

          RELEASE_NOTES: ${{ inputs.release_notes }}

After:

          RELEASE_NOTES: '${{ inputs.release_notes }}'

Generated by cloud-assistant via Open Code Review.

[Memtensor-AI]

✅ Automated Test Results: PASSED

All tests passed (1/1 executed). memos_github_open_source/smoke: 1/1. Duration: 1s

Branch: docs-sync/openclaw-local-plugin-release

[WeiminLee]

@Memtensor-AI Acknowledged the suggestions regarding release title branding and YAML quoting. These will be addressed in a follow-up cleanup PR to keep this one focused on enabling the Release creation flow. Merging to unblock the docs sync pipeline.

[WeiminLee]

OK