docs(vc): clarify meeting join gray release

[xu91102]

背景

vc +meeting-join 遇到 code 10012 / gray release scope 时，用户容易误以为是普通 scope、auth login 或应用可用范围配置问题。Issue #1788 需要明确这是 VC Agent 应用机器人入会能力的灰度/内测前置，并给出可行替代路径。

核心改动

• 在 vc +meeting-join shortcut description 中标出 code 10012 / gray release 的含义，方便 help/manifest 消费方发现。
• 在 lark-vc-agent 主 skill 和 +meeting-join reference 中补充灰度前置说明。
• 明确 10012 / gray release scope 不应通过重复 auth login 或普通 scope 排查处理。
• 给出旁听式替代路径：用户身份 +meeting-list-active 发现当前会议，再 +meeting-events 读取当前用户可见事件。
• 增加测试确保 +meeting-join description 持续暴露 gray release / 10012 提示。

验证

• go test ./shortcuts/vc -run 'TestMeetingJoinDescriptionMentionsGrayRelease|TestMeetingJoin_Validate|TestMeetingJoin_DryRun|TestMeetingJoin_Execute' -count=1: passed
• go test ./shortcuts/vc -count=1: passed
• node scripts/skill-format-check/index.js: passed
• go build -o ./lark-cli .: passed
• git diff --check: passed
• conflict marker scan: passed (no matches)

风险与回滚

低风险。主要是 help/skill 文档补充，唯一代码行为变化是 shortcut description 文案。若需要回滚，revert 本 PR 即可。

Fixes #1788

Summary by CodeRabbit

• Bug Fixes
  • Clarified the meeting-join shortcut description so users can better understand when join access may be unavailable in gray-release scenarios.
• Documentation
  • Added clearer guidance for handling meeting-join errors related to gray-release restrictions.
  • Included recommended fallback steps for read-only access when join permissions aren’t enabled.
• Tests
  • Added coverage to ensure the meeting-join description continues to mention the gray-release status and error code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: adc8ccce-d174-4898-a730-0f146b2b1d5b

📥 Commits

Reviewing files that changed from the base of the PR and between 74d8458 and 5d90796.

📒 Files selected for processing (4)

• shortcuts/vc/vc_meeting_join.go
• shortcuts/vc/vc_meeting_test.go
• skills/lark-vc-agent/SKILL.md
• skills/lark-vc-agent/references/lark-vc-agent-meeting-join.md

---

📝 Walkthrough

Walkthrough

This PR updates the VCMeetingJoin shortcut's description to explain that bot join failures with code 10012 relate to gray release scope for the VC Agent join capability. A corresponding test verifies the description text, and skill/reference documentation is updated with matching guidance and alternative workflows.

Changes

Gray Release Documentation for Meeting Join

Layer / File(s)	Summary
VCMeetingJoin description and test shortcuts/vc/vc_meeting_join.go, shortcuts/vc/vc_meeting_test.go	Description field updated to mention code 10012/gray release and VC Agent join capability; a new test asserts the description contains "gray release" and "10012".
SKILL.md gray release guidance skills/lark-vc-agent/SKILL.md	Adds explanations across the inner-test prompt, write-operation error troubleshooting, and app identity permission check sections for handling code 10012/gray release scope, including a user-identity read-only alternative.
Meeting-join reference doc updates skills/lark-vc-agent/references/lark-vc-agent-meeting-join.md	Adds a new "内测 / 灰度前置" subsection under core constraints and a new row in the common errors table describing code 10012/gray release scope handling.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• larksuite/cli#824: Introduced the VCMeetingJoin shortcut that this PR's description update directly modifies.
• larksuite/cli#1483: Also modifies VCMeetingJoin in shortcuts/vc/vc_meeting_join.go, changing AuthTypes to add bot support.

Suggested labels: documentation

Suggested reviewers: zhaoleibd, hugang-lark

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR clarifies gray-release meaning and fallback docs, but it doesn't state how a self-built app should request access or whether support/self-service is required.	Add the access request path for gray release approval, including any self-service, ticket, or support process, and document it in the join help/docs.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately describes the main change about meeting-join gray release documentation.
Description check	✅ Passed	The description covers summary, changes, verification, and related issue context, so it is mostly complete.
Out of Scope Changes check	✅ Passed	All changes stay within the gray-release clarification scope and related test coverage.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🚀 PR Preview Install Guide

🧰 CLI update

npm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@5d90796f68fa896acfe4cd56c24094e947931d47

🧩 Skill update

npx skills add xu91102/cli#docs/vc-meeting-join-gray-release -y -g

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}