chore(deps): bump lark-cli 1.0.66 → 1.0.68

[ddpie]

这个 PR 做什么

把 lark-cli 版本锁定从 1.0.66 升到 1.0.68，按项目 bump runbook（docs/skills/bump-lark-cli.md）完整走了一遍：重抽 scope 映射、重建 allowlist、按上游 diff 增量重适配变更的 skill。

上游有什么变化

1.0.68 相对 1.0.66 的实质新增是两个邮件命令：

• +message-modify（lark_mail_message_modify）——改标签 / 读未读状态 / 移动文件夹，支持批量
• +message-trash（lark_mail_message_trash）——软删除到垃圾箱，高危写操作，需 _confirm=true

两者都是 user scope（mail:user_mailbox.message:modify、mail:user_mailbox.folder:read），无 bot-only scope 引入。其余是 7 个 domain 的文档 / workflow 描述更新。

改动分布

• docker/Dockerfile：pin 1.0.66 → 1.0.68
• docker/shortcut-scopes.json：新增上述两个 mail 快捷 + 版本号
• docker/rawapi-scopes.json：版本号同步（内容无变化）
• docker/skills/：重适配 7 个上游有变更的 domain——apps、doc、drive、mail、slides、vc-agent、wiki。新增 3 个文件：mail 的 message-modify / message-trash 两个 reference、slides 的 slides_chart_demo.xml
• 无需变更：scope-allowlist.ts（新 scope 已被现有 allowlist 覆盖）、config/oauth-scopes.json（tier1 全覆盖）、CDK snapshot（asset hash 不含版本 pin）

Summary by CodeRabbit

• New Features

  • Added mail message modification and soft-delete capabilities.
  • Added Drive file sorting guidance and expanded knowledge-organization workflows.
  • Added support for inserting local Mermaid, SVG, and PlantUML assets into whiteboards.
  • Expanded presentation chart examples and native chart planning guidance.
  • Improved meeting-event pagination, output formats, and chat/reaction forwarding.

• Bug Fixes

  • Updated environment selection guidance for single- and multi-environment applications.
  • Clarified wiki token handling and mail watch output defaults.

• Documentation

  • Strengthened confirmation and safety requirements for Drive deletion and public sharing.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates the pinned Lark CLI and regenerated shortcut metadata, then revises operational guidance for application environments, Drive, Mail, Slides, video-conference events, documents, and wiki workflows.

Changes

CLI metadata

Layer / File(s)	Summary
CLI version and shortcut scopes docker/Dockerfile, docker/rawapi-scopes.json, docker/shortcut-scopes.json	Updates the CLI version metadata and adds Mail message modification and trash shortcuts.

Application and document guidance

Layer / File(s)	Summary
Application environment rules docker/skills/lark-apps/references/*	Documents server-selected dev/online environments and single-environment validation.
Document whiteboard file paths docker/skills/lark-doc/references/*	Documents local Mermaid, SVG, and PlantUML path references expanded by the CLI.

Drive and wiki workflows

Layer / File(s)	Summary
Drive routing and operations docker/skills/lark-drive/SKILL.md, docker/skills/lark-drive/references/lark-drive-{delete,files-list,inspect,permission-guide,push}.md	Updates routing, pagination, inspection, deletion confirmation, public permissions, and upload error handling.
Knowledge organization workflow docker/skills/lark-drive/references/lark-drive-workflow*.md	Registers knowledge_organize and clarifies its protocol, runtime state, and execution states.
Wiki workflow entry points docker/skills/lark-wiki/SKILL.md, docker/skills/lark-wiki/references/lark-wiki-node-get.md	Routes knowledge organization through the workflow registry and adjusts raw token handling.

Mail shortcut guidance

Layer / File(s)	Summary
Mail modify and trash contracts docker/skills/lark-mail/references/lark-mail-message-{modify,trash}.md	Defines shortcut parameters, validation, batching, confirmation, failure handling, and output behavior.
Mail workflow integration docker/skills/lark-mail/SKILL.md, docker/skills/lark-mail/references/lark-mail-{forward,reply,reply-all}.md	Replaces batch API examples with direct modification and trash shortcuts.
Mail event output format docker/skills/lark-mail/references/lark-mail-watch.md	Changes the default watch format to data and documents NDJSON variants.

Slides chart contracts

Layer / File(s)	Summary
Chart planning and generation contract docker/skills/lark-slides/references/{asset-planning,planning-layer}.md	Adds chart contracts, fallback rules, data-source requirements, and native chart generation constraints.
Chart and whiteboard routing docker/skills/lark-slides/references/{lark-slides-whiteboard,slides_xml_schema_definition,xml-schema-quick-ref}.md	Clarifies native chart selection and non-native SVG/Mermaid routing.
Chart XML examples and schema references docker/skills/lark-slides/references/{slides_chart_demo.xml,xml-format-guide.md}	Replaces the chart demo and adds a complete combo chart XML example.

Video conference event guidance

Layer / File(s)	Summary
Meeting event contract and pagination docker/skills/lark-vc-agent/SKILL.md, docker/skills/lark-vc-agent/references/lark-vc-agent-meeting-events.md	Documents structured event fields, output formats, pagination, and fresh event reads.
Meeting chat forwarding and errors docker/skills/lark-vc-agent/references/*	Documents reaction forwarding, identity visibility, recipient handling, and meeting-ended errors.

Estimated code review effort: 4 (Complex) | ~60 minutes

Possibly related PRs

• ddpie/lark-mcp-on-agentcore#57: Updates the same CLI version and scope metadata.
• ddpie/lark-mcp-on-agentcore#64: Touches the same knowledge-organization workflow documentation.
• ddpie/lark-mcp-on-agentcore#88: Updates the same CLI pinning and generated scope artifacts.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: bumping lark-cli from 1.0.66 to 1.0.68.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-lark-cli-1.0.68

---

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.}

[coderabbitai]

Actionable comments posted: 12

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docker/skills/lark-drive/references/lark-drive-workflow-knowledge-organize.md (1)

91-121: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Include all required shared Artifact Contract fields.

The shared contract in docker/skills/lark-drive/references/lark-drive-workflow.md requires workflow_id, facts, unsupported_checks, and execution_results, but this workflow’s runtime-state table omits them while claiming to extend that contract. An agent following this table could lose evidence, unsupported-check results, or execution results during a run.

Add the inherited fields explicitly, or state unambiguously that the table is additive and link to the complete shared field set.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docker/skills/lark-drive/references/lark-drive-workflow-knowledge-organize.md`
around lines 91 - 121, Update the runtime-state table describing the shared
Artifact Contract to explicitly include workflow_id, facts, unsupported_checks,
and execution_results, or clearly state that the table is additive and
references the complete field set in the shared contract. Ensure agents preserve
these inherited fields throughout the workflow run alongside the existing
fields.

🧹 Nitpick comments (1)

docker/skills/lark-slides/references/lark-slides-whiteboard.md (1)

64-71: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Do not permit “simple SVG rectangles/lines” as the fallback.

For unsupported data visuals, this wording allows the bare shapes prohibited by the later quality rules and can produce charts without axes, labels, or meaningful segmentation. Require a semantically complete SVG fallback instead.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-slides/references/lark-slides-whiteboard.md` around lines
64 - 71, Replace the “simple SVG rectangles/lines” fallback in the non-native
chart routing table with a requirement for a semantically complete SVG
visualization, including appropriate axes, labels, legends, and meaningful data
segmentation; retain Mermaid as the preferred path for Doubao, Seed, and Other
models when applicable.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docker/skills/lark-apps/references/lark-apps-db.md`:
- Line 157: Revise the guidance around environment detection and write
operations: do not recommend an explicit dev write as a probe. In the documented
workflow, first use a read-only environment/status check or dry_run=true to
determine available environments, then require an explicit environment value
before any import or audit-setting write, including online operations.

In `@docker/skills/lark-drive/references/lark-drive-files-list.md`:
- Around line 78-79: Update the guidance in the page_size recommendation to
downgrade only when the service explicitly rejects page_size; do not treat
generic parameter errors as sufficient. For errors involving folder_token,
page_token, order_by, direction, or other fields, correct or rediscover the
offending field instead of retrying with a smaller page_size.

In `@docker/skills/lark-drive/references/lark-drive-permission-guide.md`:
- Around line 13-24: 公开权限执行门槛需覆盖所有实际影响暴露范围的字段，而不仅是
link_share_entity。更新“公开范围”确认要求，明确列出并验证 link_share_entity 与 data.external_access
的用户选择及映射关系；仅在目标资源、各字段取值和执行意图均得到本轮明确确认后，才允许使用 _confirm=true。

In `@docker/skills/lark-drive/SKILL.md`:
- Line 160: Make the native API discovery prerequisite consistent in the Drive
skill documentation. Update the examples around the “高频原生命令” section and the
`files-list` guidance so every direct `lark_invoke` call is preceded by
`lark_discover`, or explicitly document that `lark_get_skill(domain="drive",
section="files-list")` supersedes discovery. Apply the same clarification to the
additional examples referenced by the review.

In `@docker/skills/lark-mail/references/lark-mail-message-modify.md`:
- Around line 9-14: Add a language identifier, such as bash or text, to the
Markdown code fence containing the lark_mail_message_modify examples.

In `@docker/skills/lark-mail/references/lark-mail-message-trash.md`:
- Around line 11-14: The command code fence in the lark mail trash documentation
lacks a language identifier. Update the fence containing the
lark_mail_message_trash examples to specify bash or text.
- Around line 5-7: The lark-mail trash documentation should reflect the
authorization exception: state that `_confirm=true` is always required to
execute deletion, while a separate user confirmation of the deletion preview is
required only when no recent user request explicitly specifies both the target
and deletion action. Update the guidance near the high-risk-write instructions.

In `@docker/skills/lark-slides/references/slides_chart_demo.xml`:
- Line 1: Update the footer page numbers across all slide elements so the total
reflects the actual 11-slide presentation: change every `/ 12` denominator to `/
11` and ensure the sequence runs consistently from `01 / 11` through `11 / 11`,
including the footer in the slide containing the `02 / 12` text.
- Line 1: Populate every self-closing whiteboard in the scatter, bubble,
word-cloud, funnel, and Pareto sections with a valid child visualization.
Replace each <whiteboard> in the relevant chart slides with an appropriate <svg>
or <mermaid> payload containing complete illustrative data and shapes, ensuring
each whiteboard has exactly one supported child so it renders correctly.

In `@docker/skills/lark-slides/references/xml-format-guide.md`:
- Line 266: Update the chart coverage sentence near the `slides_chart_demo.xml`
reference to match the actual demo contents: remove “瀑布” from the listed
whiteboard SVG examples, unless a corresponding waterfall example is added to
that file.

In `@docker/skills/lark-vc-agent/references/lark-vc-agent-meeting-events.md`:
- Around line 105-109: Update the `format="json"` contract description to
include the top-level `warnings` field alongside `meeting`, `identity`,
`events`, `has_more`, and `page_token`, ensuring consumers preserve permission
and partial-result warnings.
- Line 187: Add a language identifier to the fenced code block in the
meeting-events documentation, using text or bash as appropriate, so it complies
with Markdownlint MD040.

---

Outside diff comments:
In
`@docker/skills/lark-drive/references/lark-drive-workflow-knowledge-organize.md`:
- Around line 91-121: Update the runtime-state table describing the shared
Artifact Contract to explicitly include workflow_id, facts, unsupported_checks,
and execution_results, or clearly state that the table is additive and
references the complete field set in the shared contract. Ensure agents preserve
these inherited fields throughout the workflow run alongside the existing
fields.

---

Nitpick comments:
In `@docker/skills/lark-slides/references/lark-slides-whiteboard.md`:
- Around line 64-71: Replace the “simple SVG rectangles/lines” fallback in the
non-native chart routing table with a requirement for a semantically complete
SVG visualization, including appropriate axes, labels, legends, and meaningful
data segmentation; retain Mermaid as the preferred path for Doubao, Seed, and
Other models when applicable.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 637c41b3-45ad-4254-a800-607103930815

📥 Commits

Reviewing files that changed from the base of the PR and between 626c856 and eb09715.

📒 Files selected for processing (34)

• docker/Dockerfile
• docker/rawapi-scopes.json
• docker/shortcut-scopes.json
• docker/skills/lark-apps/references/lark-apps-db-execute.md
• docker/skills/lark-apps/references/lark-apps-db.md
• docker/skills/lark-doc/references/lark-doc-whiteboard.md
• docker/skills/lark-doc/references/lark-doc-xml.md
• docker/skills/lark-drive/SKILL.md
• docker/skills/lark-drive/references/lark-drive-delete.md
• docker/skills/lark-drive/references/lark-drive-files-list.md
• docker/skills/lark-drive/references/lark-drive-inspect.md
• docker/skills/lark-drive/references/lark-drive-permission-guide.md
• docker/skills/lark-drive/references/lark-drive-push.md
• docker/skills/lark-drive/references/lark-drive-workflow-knowledge-organize.md
• docker/skills/lark-drive/references/lark-drive-workflow.md
• docker/skills/lark-mail/SKILL.md
• docker/skills/lark-mail/references/lark-mail-forward.md
• docker/skills/lark-mail/references/lark-mail-message-modify.md
• docker/skills/lark-mail/references/lark-mail-message-trash.md
• docker/skills/lark-mail/references/lark-mail-reply-all.md
• docker/skills/lark-mail/references/lark-mail-reply.md
• docker/skills/lark-mail/references/lark-mail-watch.md
• docker/skills/lark-slides/references/asset-planning.md
• docker/skills/lark-slides/references/lark-slides-whiteboard.md
• docker/skills/lark-slides/references/planning-layer.md
• docker/skills/lark-slides/references/slides_chart_demo.xml
• docker/skills/lark-slides/references/slides_xml_schema_definition.xml
• docker/skills/lark-slides/references/xml-format-guide.md
• docker/skills/lark-slides/references/xml-schema-quick-ref.md
• docker/skills/lark-vc-agent/SKILL.md
• docker/skills/lark-vc-agent/references/lark-vc-agent-meeting-events.md
• docker/skills/lark-vc-agent/references/lark-vc-agent-meeting-list-active.md
• docker/skills/lark-wiki/SKILL.md
• docker/skills/lark-wiki/references/lark-wiki-node-get.md

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Do not use a write operation as the environment probe.

On multi-environment applications, explicit environment="dev" writes execute against the development database; only single-environment applications reject them. The current wording can therefore mutate data before the environment is known. Use a read-only environment/status check or dry_run=true, then require an explicit environment before performing the write.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-apps/references/lark-apps-db.md` at line 157, Revise the
guidance around environment detection and write operations: do not recommend an
explicit dev write as a probe. In the documented workflow, first use a read-only
environment/status check or dry_run=true to determine available environments,
then require an explicit environment value before any import or audit-setting
write, including online operations.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Only downgrade page_size for page-size validation errors.

The rule currently treats any “parameter error” as a reason to lower page_size; errors in folder_token, page_token, order_by, or direction will not be fixed by that retry. Limit the fallback to an explicit page_size rejection; otherwise repair or rediscover the offending field.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-drive/references/lark-drive-files-list.md` around lines 78
- 79, Update the guidance in the page_size recommendation to downgrade only when
the service explicitly rejects page_size; do not treat generic parameter errors
as sufficient. For errors involving folder_token, page_token, order_by,
direction, or other fields, correct or rediscover the offending field instead of
retrying with a smaller page_size.

[coderabbitai]

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Confirm every field that controls exposure, not only link_share_entity.

The downstream command also sets data.external_access (lark-drive-workflow-permission-governance-commands.md:87), but this gate describes organization/internet and read/edit choices as link_share_entity values alone. That can leave external_access at an unintended default or map the requested access level incorrectly. Require explicit confirmation and mapping for all effective public-permission fields before _confirm=true.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-drive/references/lark-drive-permission-guide.md` around
lines 13 - 24, 公开权限执行门槛需覆盖所有实际影响暴露范围的字段，而不仅是
link_share_entity。更新“公开范围”确认要求，明确列出并验证 link_share_entity 与 data.external_access
的用户选择及映射关系；仅在目标资源、各字段取值和执行意图均得到本轮明确确认后，才允许使用 _confirm=true。

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Make the native-API discovery prerequisite consistent.

Line 158 requires lark_discover before every native API call, but these new examples invoke lark_invoke directly; lark-drive-files-list.md:79 also makes discovery conditional. Add the discovery step or explicitly state that lark_get_skill supersedes it.

Also applies to: 202-207

🧰 Tools

🪛 SkillSpector (2.3.7)

[warning] 51: [MP2] Context Window Stuffing: Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.

Remediation: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.

(Memory Poisoning (MP2))

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-drive/SKILL.md` at line 160, Make the native API discovery
prerequisite consistent in the Drive skill documentation. Update the examples
around the “高频原生命令” section and the `files-list` guidance so every direct
`lark_invoke` call is preceded by `lark_discover`, or explicitly document that
`lark_get_skill(domain="drive", section="files-list")` supersedes discovery.
Apply the same clarification to the additional examples referenced by the
review.

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a language identifier to the command fence.

This fence triggers MD040; use a suitable identifier such as bash or text.

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 9-9: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-mail/references/lark-mail-message-modify.md` around lines
9 - 14, Add a language identifier, such as bash or text, to the Markdown code
fence containing the lark_mail_message_modify examples.

Source: Linters/SAST tools

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a language identifier to the command fence.

This fence triggers MD040; use bash or text.

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 11-11: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-mail/references/lark-mail-message-trash.md` around lines
11 - 14, The command code fence in the lark mail trash documentation lacks a
language identifier. Update the fence containing the lark_mail_message_trash
examples to specify bash or text.

Source: Linters/SAST tools

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Fix the slide-count footer.

The presentation contains 11 <slide> elements, but the footers use / 12 and stop at 11 / 12, producing inconsistent page numbering.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-slides/references/slides_chart_demo.xml` at line 1, Update
the footer page numbers across all slide elements so the total reflects the
actual 11-slide presentation: change every `/ 12` denominator to `/ 11` and
ensure the sequence runs consistently from `01 / 11` through `11 / 11`,
including the footer in the slide containing the `02 / 12` text.

---

🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift

Populate the non-native whiteboards; self-closing elements are invalid and render blank.

The scatter, bubble, word-cloud, funnel, and Pareto regions contain <whiteboard .../> with neither <svg> nor <mermaid>. The schema requires one child, so this reference presentation is incomplete and cannot demonstrate those visuals.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-slides/references/slides_chart_demo.xml` at line 1,
Populate every self-closing whiteboard in the scatter, bubble, word-cloud,
funnel, and Pareto sections with a valid child visualization. Replace each
<whiteboard> in the relevant chart slides with an appropriate <svg> or <mermaid>
payload containing complete illustrative data and shapes, ensuring each
whiteboard has exactly one supported child so it renders correctly.

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Keep the demo coverage claim accurate.

slides_chart_demo.xml does not contain a waterfall example. Remove “瀑布” from this sentence or add the missing example so the documentation matches the referenced file.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-slides/references/xml-format-guide.md` at line 266, Update
the chart coverage sentence near the `slides_chart_demo.xml` reference to match
the actual demo contents: remove “瀑布” from the listed whiteboard SVG examples,
unless a corresponding waterfall example is added to that file.

[coderabbitai]

🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Include warnings in the JSON contract.

This format description omits warnings, while SKILL.md Lines 70-71 and this file’s response table include it as a top-level field. Consumers following this contract may silently discard permission or partial-result warnings.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-vc-agent/references/lark-vc-agent-meeting-events.md`
around lines 105 - 109, Update the `format="json"` contract description to
include the top-level `warnings` field alongside `meeting`, `identity`,
`events`, `has_more`, and `page_token`, ensuring consumers preserve permission
and partial-result warnings.

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a language tag to the fenced example.

The code fence triggers Markdownlint MD040; mark it as text or bash.

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 187-187: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker/skills/lark-vc-agent/references/lark-vc-agent-meeting-events.md` at
line 187, Add a language identifier to the fenced code block in the
meeting-events documentation, using text or bash as appropriate, so it complies
with Markdownlint MD040.

Source: Linters/SAST tools