feat(feishu): 缺少日历（Calendar）API 支持

[hsuaaron]

背景

飞书扩展当前仅支持文档（Doc）、云盘（Drive）、Wiki、多维表格（Bitable）等功能，但缺少日历（Calendar）API 的支持。

使用场景

用户通过飞书分享日历事件邀请时，助手无法读取日历信息，导致：

1. 无法确认会议时间是否正确
2. 无法自动将会议添加到待办跟踪
3. 机器人无法代替用户响应日历邀请

建议

参考飞书开放平台日历 API（v4），实现以下能力：

核心接口

• GET /calendar/v4/calendars/primary — 获取主日历
• GET /calendar/v4/events — 读取日程列表
• GET /calendar/v4/events/{event_id} — 读取单个日程详情
• POST /calendar/v4/events — 创建日程（可选）

权限要求

• calendar:calendar:readonly
• calendar:event:readonly
• calendar:event:create（可选）

参考文档

飞书日历 API：https://open.feishu.cn/document/server-docs/calendar-v4/calendar-introduction

[clawsweeper]

Closing this as better suited for ClawHub/community plugin work after Codex automated review.

#55033 requests Feishu Calendar API tools. Current main does not implement calendar support, but the request is an optional service-specific workplace integration that fits the existing plugin/ClawHub path rather than OpenClaw core. The existing @openclaw/feishu plugin covers Feishu channel/doc/wiki/drive/bitable/permission surfaces, and current plugin docs/API support external tool plugins without a missing core seam.

Best possible solution:

Close this core issue as ClawHub scope. Keep the current @openclaw/feishu channel/doc/wiki/drive/bitable plugin as-is, and pursue Feishu Calendar read/create/respond tools as a separate ClawHub/npm plugin or skill unless a concrete missing OpenClaw plugin API seam is identified.

What I checked:

• Issue metadata has no protected maintainer signal: Provided GitHub context shows authorAssociation NONE, no labels, no comments, and no protected security/beta-blocker/release-blocker/maintainer label. (b565e6e96310)
• OpenClaw scope directs optional capabilities to plugins and ClawHub: VISION.md says core stays lean, optional capability should usually ship as plugins, external plugin work should be hosted outside the repo, and plugin promotion belongs in ClawHub. (VISION.md:54, b565e6e96310)
• Commercial service integrations are not current core-default scope: VISION.md lists commercial service integrations outside the model-provider category under work OpenClaw will not merge for now. (VISION.md:106, b565e6e96310)
• Existing Feishu plugin is already plugin-scoped and ClawHub/npm-published: The @openclaw/feishu package identifies itself as the Feishu/Lark channel plugin with doc/wiki/drive tools and has release metadata to publish to ClawHub and npm. (extensions/feishu/package.json:2, b565e6e96310)
• Current Feishu plugin registers no calendar tools: The Feishu bundled entry registers subagent hooks plus doc, chat, wiki, drive, permission, and bitable tools; there is no calendar registration path. (extensions/feishu/index.ts:73, b565e6e96310)
• Feishu tool config has no calendar category: The Feishu tool config type only includes doc, chat, wiki, drive, perm, and scopes, confirming calendar is not an existing configured tool surface. (extensions/feishu/src/types.ts:97, b565e6e96310)

So I’m closing this as a scope-fit item for the plugin/community path rather than keeping it open as an OpenClaw core request.

Codex Review notes: model gpt-5.5, reasoning high; reviewed against b565e6e96310.