Bug Description

The Feishu plugin reports a missing permission contact:contact.base:readonly and generates an authorization URL, but this scope does not exist on the Feishu Open Platform.

The correct scope should be contact:user.base:readonly, which is a valid Feishu permission for reading basic user contact information.

Steps to Reproduce

1. Configure a Feishu bot with OpenClaw
2. Send a message to the bot in a direct chat
3. System injects an error prompting admin to authorize contact:contact.base:readonly

Expected Behavior

The plugin should check for contact:user.base:readonly instead, or skip the check if already granted.

Actual Behavior

Every message triggers a system-injected error for contact:contact.base:readonly, a scope that does not exist in Feishu Open Platform. The authorization URL leads nowhere useful.

Evidence

• contact:contact.base:readonly is NOT listed in the Feishu Open Platform permission catalog
• contact:user.base:readonly IS a valid scope and is already granted (user level)
• contact:user.employee_id:readonly is also granted (tenant level)
• Checked via feishu_app_scopes: 404 scopes granted, none matching contact:contact.base:readonly