Some commands returns hardcoded `www.feishu.cn` instead of tenant-specific domain, howerver some commands don't

[meloalright]

These commands hardcode the result domain.

Command	URL returned
wiki +node-create	https://www.feishu.cn/wiki/...
drive +upload	https://www.feishu.cn/file/...
markdown +create	https://www.feishu.cn/file/...
docs +create (v1 fallback)	https://www.feishu.cn/docx/...

These commands know the correct tenant domain.

Command	URL returned
drive +create-folder	https://<tenant>.larkoffice.com/drive/folder/...
sheets +create	https://<tenant>.larkoffice.com/sheets/...
slides +create	https://<tenant>.larkoffice.com/slides/...
base +base-create	https://<tenant>.larkoffice.com/base/...

that is weird, and relative to #810

[jshaofa-ui]

Root Cause Analysis — Hardcoded www.feishu.cn Domain

Diagnosis

This is a domain inconsistency bug — some commands correctly resolve tenant-specific domains while others hardcode www.feishu.cn.

Affected Commands

Command	Broken URL	Expected URL
wiki +node-create	https://www.feishu.cn/wiki/...	https://<tenant>.larkoffice.com/wiki/...
drive +upload	https://www.feishu.cn/file/...	https://<tenant>.larkoffice.com/drive/...
markdown +create	https://www.feishu.cn/file/...	https://<tenant>.larkoffice.com/file/...
docs +create (v1)	https://www.feishu.cn/docx/...	https://<tenant>.larkoffice.com/docx/...

Working Commands (for reference)

drive +create-folder, sheets +create, slides +create, base +base-create — all correctly use tenant domain.

Root Cause

The working commands use a shared domain resolution utility that reads tenant context from CLI config or API response. The broken commands have hardcoded URL templates with www.feishu.cn, bypassing the resolver.

Proposed Fix

1. Create shared domain resolver (if not exists)

// src/utils/domain-resolver.ts
export function resolveBaseUrl(): string {
  const config = loadConfig();
  
  // From explicit tenant domain config
  if (config?.tenantDomain) {
    return `https://${config.tenantDomain}`;
  }
  
  // Derive from API base URL
  const apiBase = config?.apiBaseUrl || 'https://open.feishu.net';
  if (apiBase.includes('larksuite.com') || apiBase.includes('larkoffice.com')) {
    const tenant = config?.appTenantKey || 'open';
    return `https://${tenant}.larkoffice.com`;
  }
  
  return 'https://www.feishu.cn';
}

2. Fix each affected command

Replace hardcoded www.feishu.cn in URL construction with resolveBaseUrl():

• wiki +node-create → after node creation URL construction
• drive +upload → after file upload URL construction
• markdown +create → after markdown conversion URL construction
• docs +create v1 fallback → after doc creation URL construction

3. Add regression test

Ensure all shortcut commands that return URLs use the shared resolver.

Impact

• Multi-tenant Feishu/Lark users cannot use returned URLs directly
• Enterprise deployments with custom domains are affected
• Cross-region users (China vs International) get wrong domain
• Related to wiki +node-create returns URL with www.feishu.cn host but tenant uses my.feishu.cn #810 (same domain inconsistency theme)