docs: align the Lark extension integration guide with the Feishu guide
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.3k
- Forks
- 1.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 105
Description
Checked state
Checked on 2026-08-24 against repository main at 35bd5ecfcd84c8e457323a1bcf9453ba600c0270.
The root READMEs advertise six extension points for enterprise embedding: credentials, transport, restriction, audit, wrapping, and lifecycle hooks. The repository implements and documents all six under extension/.
Problem
The two official public integration guides currently diverge substantially:
- Lark: https://open.larksuite.com/document/uAjLw4CM/ukTMukTMukTM/lark-cli-integration/integration
- Feishu: https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/lark-cli-integration/integration
Their Markdown endpoints are also available by appending .md.
At the checked time:
- The Lark Markdown page had 393 lines, was written primarily in Chinese, and documented only credential and transport extension points.
- The Feishu Markdown page had 894 lines and documented all six extension points, including restrict, audit, wrap, and lifecycle hooks.
All four HTML/Markdown URLs returned HTTP 200, so this is content drift rather than an outage.
Expected behavior
The Lark guide should be an English, feature-complete counterpart to the Feishu guide and match the capabilities advertised in the English README.
Impact
International integrators following the official Lark documentation cannot discover the restriction, audit, wrapping, or lifecycle contracts even though the repository exposes them.
Duplicate check
I searched open and closed issues, all PR states, and recent repository history for the integration page plus audit, restrict, and Lark documentation terms; no existing report was found.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the Lark and Feishu Markdown endpoints, then read the root READMEs and the six extension areas under extension/. Identify the documented credentials, transport, restriction, audit, wrapping, and lifecycle contracts, and use the Feishu guide as the completeness reference. Done means the Lark guide is an English counterpart covering all six capabilities.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100