Prepare WCPT private Tencent Lighthouse release candidate

[zjgulai]

---

title: WCPT Reconciliation Branch PR Body
date: 2026-07-06
status: review-ready
scope: reconciliation-branch, remote-review, tencent-lighthouse

Prepare WCPT Private Tencent Lighthouse Release Candidate

Summary

This branch reconciles the WCPT private-dashboard release work with origin/master, preserves the lightweight Tencent Lighthouse target, and adds local proof gates for runtime, Docker, PDF opt-in, deployment profile, branch handoff, and client bundle budget.

Facts

• Source branch: zjgulai:codex/reconcile-origin-master-20260705
• Source head: 1ae9dae225074338bbfe6a445d93b38777c47fd1
• Upstream base: wechat-article/wechat-article-exporter:master
• Local master head at review-pack time: 8f8c747c88bf4b65c080fb06f130c1277a6567f1
• origin/master head at review-pack time: 15b391bbf2d18ecd7e48b382e0d723fcfded92c1
• Local master -> source: 28 commits / 25 changed files
• origin/master -> source: 7 commits / 167 changed files
• Local master and origin/master are both ancestors of the source branch.
• Reconciliation source worktree is clean.
• Original master worktree remains dirty and must not be reset or merged without separate approval.
• Fork branch has been pushed for remote review.

Main Changes

• Reconciles private WCPT product changes with upstream origin/master.
• Keeps Tencent Lighthouse default profile lightweight: loopback Docker service, fs-backed Nitro KV, Open API default-off, LLM/provider calls default-off, PDF runtime default-off.
• Keeps PDF generation as an explicit opt-in runtime path with separate Docker build arguments and local smoke evidence.
• Adds branch handoff audit evidence so local master and origin/master ancestry are explicit.
• Adds client bundle budget audit and named lazy chunks for AG Grid / ExcelJS so large client chunks are classified and budgeted.
• Preserves DeepSeek/Kimi-style LLM work as default-off and server-only, with provider calls separated from production authorization.

Local Verification

• Loop 20: reconciliation merge verification recorded yarn install --frozen-lockfile --ignore-scripts --non-interactive, yarn test, yarn verify, docker compose config --quiet, git diff --check, and secret/public scan.
• Loop 21: local Nitro runtime smoke recorded root/dashboard, Open API default-off, worker metrics, browser screenshot, and PDF with explicit local Chrome.
• Loop 22: default lightweight Docker image and container smoke passed; default PDF runtime returns explicit 501 PDF_RUNTIME_UNAVAILABLE.
• Loop 23: PDF opt-in Docker image generated a real PDF locally, but remains non-default.
• Loop 24: lighthouse-default deployment profile and nginx handoff validation passed locally.
• Loop 25: reconciliation branch handoff audit reported readyForBranchReview=true.
• Loop 26: client bundle budget audit reported readyForLargeChunkCloseout=true and violationCount=0.
• Loop 27: integration route pack confirmed source branch cleanliness and ancestor relationships.
• Loop 33: fork branch push completed; remote branch SHA matches source head.

Risks / Review Focus

• Review deployment defaults carefully: PDF runtime is intentionally disabled by default for Tencent Lighthouse resource discipline.
• Review nuxt.config.ts, Dockerfile, docker-compose.yml, and deployment profile together; these files jointly define the private runtime contract.
• Review AG Grid / ExcelJS chunk budgets as explicit acceptance, not removal of heavy feature code.
• Review LLM routes and summary UI as default-off / authorization-gated; local live preflight is not production authorization.
• Review original master dirty-state separately before any local worktree update.

Explicit Boundaries

• branch_pushed_to_fork: true
• upstream_pr_requested: true
• merge_executed: false
• reset_executed: false
• deploy_attempted: false
• production_changed: false
• production_readonly_access: false
• provider_call: false
• live_send: false

Follow-up Gates Before Production

• Remote PR review and CI/readiness decision.
• Explicit review/decision for original master dirty-state preservation or cleanup.
• Refresh release/production-readiness packet after integration route selection.
• Production server read-only inventory after authorization.
• Runtime key injection after authorization.
• Deployment preflight and container restart after authorization.
• Production acceptance checks after deployment.