docs(deployment): keep the developer half (build the artifact, extend the image, CI publish, tenancy, seed repair) and hand production operation of ObjectOS Community to docs.objectos.ai's merged self-managed handbook #26688

Filing gate: ③ a task the maintainer directed — Sam, objectos project thread "Decide docs.objectos.ai content scope", 2026-10-27, verbatim: 「Enterprise 镜像部署；Community 生产自托管部署，是用 docker 吗？有什么区别吗？很多都应该合并吧」 · 「同意，立卡」.

维护者速读

ObjectOS Community（ghcr.io/objectstack-ai/objectstack）和 Enterprise（objectos-ee）是同一个运行时、同一套配置，自托管运维今天在两站各写一份：本仓 content/docs/deployment/self-hosting.mdx（5,129 词）等页写 Community，docs.objectos.ai 的 Deploy/Operate 写 Enterprise。维护者决定合并到 docs.objectos.ai，作为两版本共用的自托管手册（objectstack-ai/docs.objectos.ai#345）。本仓保留开发者半边：怎么 os build 出 artifact、扩展官方镜像、CI 里发布、租户模式、种子修复、publish & preview、Cloud Connection 的服务端；生产运行（Compose、K8s、反向代理、备份、升级、观测、排障）指向 docs.objectos.ai。

Governing text

• Brand split (cloud ADR-0085; this repository's LICENSING.md): ObjectStack = the developer brand, objectstack.ai/docs = protocol, SDK, CLI, kernel; ObjectOS Community is the runtime's product name and docs.objectos.ai is the product site for all three editions.
• AGENTS.md 〈Documentation Guardrails〉: content/docs/deployment/ is hand-written; references/ and releases/ are untouched by this card.
• docker/README.md already says "the full walkthrough lives in Self-Hosted Deployment"; after this card that sentence points at the product site for production and keeps the extend-the-image walkthrough here.

Done looks like

1. content/docs/deployment/self-hosting.mdx keeps: the artifact model, "extend the official image" Dockerfile, artifact-pinned boot (OS_ARTIFACT_URL), first-boot admin bootstrap and sign-up postures (framework-decided behaviour). It drops, with a one-line pointer each to docs.objectos.ai: Docker Compose with Postgres, Kubernetes, bare Node.js systemd, reverse proxy & TLS, scaling, go-live checklist.
2. deployment/backup-restore.mdx, troubleshooting.mdx, production-readiness.mdx: keep what only the framework decides (what os commands exist, exit codes, error catalog cross-links); operator runbook content moves to docs.objectos.ai (🔗 Broken links detected in documentation #345) and is linked.
3. deployment/index.mdx's two-clock table gains a third row: "Where the operator handbook is: docs.objectos.ai/docs/deploy (Community and Enterprise, one handbook)".
4. docker/README.md and content/docs/deployment/meta.json updated; lychee.toml link check green on the new cross-site links.
5. Dispatched after Deploy and Operate become one self-managed handbook for Community and Enterprise: each page written once, "Enterprise adds" sections for the private image and license, plus Licensing and Business Self-Managed vs Enterprise pages docs.objectos.ai#345 lands, so no production topic is undocumented in between.

Out of scope

deployment/cloud-connection.mdx (stays: it is the server half, docs.objectos.ai writes the account half), tenancy-modes, seed-tenancy-repair, publish-and-preview, install-modes, app-dependencies, validating-metadata, cli, environment-variables — all developer-side, unchanged.

Blocked-by: objectstack-ai/docs.objectos.ai#345