[Luhaozhu]

Summary

Update the deterministic Community Edition tree with the current runtime, UI, and build changes. Requests continue through the native MCP session layer, blocking database operations run in worker threads, and conversation and automation views show current execution state.

• Carry native MCP 2.3 sessions, HTTP readiness checks, durable automation ownership and delivery, and model reasoning event handling into CE.
• Move blocking database work out of async request handlers and derive connection pools and worker limits from a shared thread budget.
• Refresh tool activity, elapsed time, compaction, streaming state, and automation run polling.
• Reorganize Docker build inputs under feature directories and remove the retired customer-example dependency from the full frontend build.
• Align release regressions with the current self-service MCP interface and a single application lifespan.
• Preserve CE route, model, licensing, and branding boundaries.

Compared with public main, this contains 2,758 changed files (98,013 insertions and 89,713 deletions), largely backend module/test moves. Enterprise implementations, internal documents, evaluation datasets, credentials, and build artifacts are excluded.

Validation

• Deterministic CE required-file, forbidden-artifact, binary allowlist, branding, and license gates passed.
• CE import, OpenAPI, ORM, and foreign-key boundary contract passed.
• CE release/runtime/sandbox regression selection: 72 passed.
• CE frontend production build passed with Node 22.
• Full-edition integration validation: 207 backend tests passed.
• Public index whitespace check passed.
• Full-tree lint remains at its existing baseline: 245 errors and 22 warnings on both development and product branches; it is not reported as passing.
• Existing CI results belong to the previous PR head; this update triggers fresh checks.

Upgrade notes

This includes CE migrations ce_0031 through ce_0033 for automation ownership, queued runs, and normalized delivery targets. Back up the database before upgrading. Update references to moved Docker Compose overlays when upgrading an existing installation. Desktop users need a rebuilt package to receive bundled frontend and runtime changes.