chore: baseline V8.10.0-dev.1 with v8_workflows type-mapping fix and trade-pro spec

- SiteForge Enterprise V8.10.0-dev.1 upstream source (210 tests)
- Fix: v8_workflows._mapped_input now reads both 类型/分类 columns so WXR
  imports keep post/product types instead of collapsing to page
- Docs: trade-pro theme port spec (R3) and implementation plan

Co-Authored-By: Claude Code <noreply@anthropic.com>

scripts/init_config.py

@@ -0,0 +1,23 @@
+"""Generate a local .env using only Docker's Python image (no host Python needed)."""
+import os
+import secrets
+from pathlib import Path
+
+root=Path(__file__).resolve().parent.parent
+config=root/'.env'
+if config.exists():
+    print('已存在 .env：为了防止覆盖现有密码和密钥，本次不做修改。')
+    raise SystemExit(0)
+password=secrets.token_urlsafe(24)
+secret=secrets.token_urlsafe(48)
+pg_password=secrets.token_urlsafe(30)
+deploy_secret=secrets.token_urlsafe(48)
+config.write_text(f'''# SiteForge Factory 8.10.0-dev.1 - 不要上传至代码仓库\nSITEFORGE_PORT=8787\nSITEFORGE_ADMIN_PASSWORD={password}\nSITEFORGE_SESSION_SECRET={secret}\nSITEFORGE_COOKIE_SECURE=false\nSITEFORGE_DOMAIN=siteforge.example.com\nSITEFORGE_PG_USER=siteforge\nSITEFORGE_PG_PASSWORD={pg_password}\nSITEFORGE_PG_DB=siteforge\nSITEFORGE_DEPLOY_SECRET={deploy_secret}\n# Remote deployment target: configure HTTPS URLs and corresponding secrets manually.\nSITEFORGE_DEPLOY_STAGING_URL=\nSITEFORGE_DEPLOY_STAGING_SECRET=\nSITEFORGE_DEPLOY_PRODUCTION_URL=\nSITEFORGE_DEPLOY_PRODUCTION_SECRET=\n''', encoding='utf-8')
+try:os.chmod(config,0o600)
+except OSError:pass
+print('SiteForge 已生成 .env 配置。')
+print('首次登录管理员密码：'+password)
+print('请将密码保存在安全的位置，忘记后可编辑 .env 的密码并重启容器。')
+print('SQLite 单机启动：docker compose up -d --build')
+print('PostgreSQL / Redis 企业测试：docker compose -f compose.enterprise.yaml up -d --build')
+print('发布 Agent 应安装在独立机器，经 HTTPS 反向代理并限制访问 IP。')