#2482·cli

docs: align the Lark extension integration guide with the Feishu guide

Author: dajiaohuangCreated Aug 24, 2026Updated Sep 18, 2026
Labelsdomain/doc

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:

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.