PR #74219: fix(plugin-sdk): restore feishu compatibility facades

• Repository: openclaw/openclaw
• Author: SymbolStar
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74219

Description (problem / solution / changelog)

Summary

Restores the openclaw/plugin-sdk/feishu (and helper feishu-setup, feishu-conversation) subpath facades that were removed in 1e3ce10e2.

Root Cause

The published @openclaw/[email protected] imports from openclaw/plugin-sdk/feishu, which was removed in the refactor(plugin-sdk): remove unused reserved helper exports commit. After upgrading to [email protected], the import fails at runtime:

TypeError: (0 , _feishu.createScopedPairingAccess) is not a function

This is the same class of regression as #73685 (Discord facade removal).

Changes

• src/plugin-sdk/feishu.ts — Restored facade with all exports needed by @openclaw/[email protected], including:
  • createScopedPairingAccess (from ./pairing-access.js)
  • issuePairingChallenge (from ../pairing/pairing-challenge.js)
  • createTypingCallbacks (from ../channels/typing.js)
  • splitOnboardingEntries (alias for splitSetupEntries)
  • ChannelOnboardingAdapter / ChannelOnboardingDmPolicy (type aliases for renamed types)
• src/plugin-sdk/feishu-setup.ts — Restored lazy facade loader for feishu setup wizard
• src/plugin-sdk/feishu-conversation.ts — Restored lazy facade loader for feishu conversation/thread binding helpers
• scripts/lib/plugin-sdk-entrypoints.json — Added feishu entry
• src/plugin-sdk/entrypoints.ts — Added feishu to supportedBundledFacadeSdkEntrypoints
• package.json — Synced exports map via sync-plugin-sdk-exports.mjs

Fixes #74138

Changed files

• package.json (modified, +4/-0)
• scripts/lib/plugin-sdk-entrypoints.json (modified, +1/-0)
• src/plugin-sdk/entrypoints.ts (modified, +1/-0)
• src/plugin-sdk/feishu-conversation.ts (added, +109/-0)
• src/plugin-sdk/feishu-setup.ts (added, +25/-0)
• src/plugin-sdk/feishu.ts (added, +157/-0)

PR #74223: plugin-sdk: restore Feishu pairing facade

• Repository: openclaw/openclaw
• Author: sahilsatralkar
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74223

Description (problem / solution / changelog)

Summary

Describe the problem and fix in 2–5 bullets:

If this PR fixes a plugin beta-release blocker, title it fix(<plugin-id>): beta blocker - <summary> and link the matching Beta blocker: <plugin-name> - <summary> issue labeled beta-blocker. Contributors cannot label PRs, so the title is the PR-side signal for maintainers and automation.

• Problem: npm-installed legacy Feishu plugins could import openclaw/plugin-sdk/feishu, but the host no longer exported that subpath.
• Why it matters: affected Feishu/Lark installs failed during module linking before pairing or startup could run.
• What changed: restored a scoped Feishu compatibility SDK facade, added it to SDK export wiring, updated API baseline/docs, and added a regression contract test for the legacy export surface.
• What did NOT change (scope boundary): no Feishu runtime behavior, config format, pairing storage, auth flow, or network behavior changed.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #74138
• Related #
• This PR fixes a bug or regression

Root Cause (if applicable)

For bug fixes or regressions, explain why this happened, not just what changed. Otherwise write N/A. If the cause is unclear, write Unknown.

• Root cause: Feishu’s historical package used a Feishu-specific SDK subpath, but later SDK export cleanup removed openclaw/plugin-sdk/feishu without leaving a compatibility facade.
• Missing detection / guardrail: SDK contract tests did not cover the published Feishu package’s legacy named imports from that subpath.
• Contributing context (if known): newer bundled Feishu code had moved to focused SDK subpaths, so local/current tests missed older npm-installed package compatibility.

Regression Test Plan (if applicable)

For bug fixes or regressions, name the smallest reliable test coverage that should catch this. Otherwise write N/A.

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
  • Target test or file: src/plugins/contracts/plugin-sdk-subpaths.test.ts
  • Scenario the test should lock in: openclaw/plugin-sdk/feishu remains importable and exposes the legacy runtime names used by published Feishu packages.
  • Why this is the smallest reliable guardrail: it validates the public SDK subpath contract directly without needing to boot a full Feishu channel runtime.
  • Existing test that already covers this (if any): none before this PR.
  • If no new test is added, why not: N/A

User-visible / Behavior Changes

Users with older npm-installed Feishu/Lark plugin packages can start the plugin again after upgrading the host.

Diagram (if applicable)

N/A.

Security Impact (required)

• New permissions/capabilities? (Yes/No) No
• Secrets/tokens handling changed? (Yes/No) No
• New/changed network calls? (Yes/No) No
• Command/tool execution surface changed? (Yes/No) No
• Data access scope changed? (Yes/No) No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS
• Runtime/container: local repo with pnpm
• Model/provider: N/A
• Integration/channel (if any): Feishu/Lark
• Relevant config (redacted): N/A

Steps

1. Install or run a legacy Feishu package that imports from openclaw/plugin-sdk/feishu.
2. Start the host with that plugin available.
3. Import/link the Feishu runtime.

Expected

• The Feishu SDK subpath resolves and exposes the legacy named exports required by the published plugin package.

Actual

• Before this PR, openclaw/plugin-sdk/feishu was missing or too narrow, causing ESM import/ link failures.

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios:
  • pnpm test -- src/plugins/contracts/plugin-sdk-subpaths.test.ts -t "Feishu pairing compatibility"
  • pnpm test -- src/plugins/contracts/plugin-sdk-subpaths.test.ts
  • pnpm plugin-sdk:api:check
  • pnpm build
  • pnpm check:changed
  • pnpm dlx codex review --base origin/main
• Edge cases checked: the compatibility facade includes the broader legacy Feishu named export set, not only createScopedPairingAccess.
• What you did not verify: live Feishu/Lark API traffic with real credentials.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? (Yes/No) Yes
• Config/env changes? (Yes/No) No
• Migration needed? (Yes/No) No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

• Risk: the restored Feishu facade could accidentally become a new general-purpose SDK surface.
  • Mitigation: the file is documented as a legacy compatibility facade, scoped to historical Feishu package imports, and covered by a focused contract test.

Built with Codex

Changed files

• docs/.generated/plugin-sdk-api-baseline.sha256 (modified, +2/-2)
• docs/plugins/sdk-migration.md (modified, +6/-4)
• docs/plugins/sdk-subpaths.md (modified, +1/-0)
• package.json (modified, +4/-0)
• scripts/lib/plugin-sdk-entrypoints.json (modified, +1/-0)
• src/plugin-sdk/entrypoints.ts (modified, +1/-0)
• src/plugin-sdk/feishu.ts (added, +121/-0)
• src/plugins/contracts/plugin-sdk-subpaths.test.ts (modified, +60/-0)