create-objectstack templates: AGENTS.md links objectstack.com, Dockerfile/docker-compose.yml still use the docs.objectstack.ai alias

[os-elon]

Found while implementing #10321 (dispatch narrowed that card's file surface to root README.md + packages/create-objectstack/src/templates/blank/README.md only, so this is a genuine leftover, not a duplicate).

Census at origin/main (post #10321's fix)

File	Host	Occurrences
packages/create-objectstack/src/templates/AGENTS.md:99	objectstack.com	1 — [ObjectStack Documentation](https://objectstack.com/docs)
packages/create-objectstack/src/templates/blank/Dockerfile:10	docs.objectstack.ai	1 — # Docs: https://docs.objectstack.ai/docs/deployment/self-hosting
packages/create-objectstack/src/templates/blank/docker-compose.yml:7	docs.objectstack.ai	1 — # Docs: https://docs.objectstack.ai/docs/deployment/self-hosting

Canonical host, already ruled

Maintainer ruling, 2026-08-21: 「这个仓的文档站规范 URL 是 https://objectstack.ai」. Enforced by CANONICAL_DOCS_ORIGIN = 'https://objectstack.ai' in scripts/check-published-readme-links.mjs. docs.objectstack.ai is an accepted-but-unratified alias (in DOCS_HOSTS, redirects path-preservingly per commit 02b3b07394's verified claim); objectstack.com is not in DOCS_HOSTS at all — it is a different, wrong domain, not an alias.

Commit 02b3b07394 ("converge runtime docs URLs on the canonical host") explicitly named "the create-objectstack templates (#10321)" as a deliberate survivor of its repo-wide sweep, owned elsewhere. #10321's dispatch then narrowed to two files, leaving these three lines uncovered by any card in the #10264 family (checked #10319/#10320/#10322/#10324/#10325 — none touch templates/AGENTS.md, the Dockerfile, or docker-compose.yml).

Why this still matters after #10321

Same "one scaffold run, multiple hostnames" defect: a fresh npm create objectstack@latest still ships an AGENTS.md pointing at the wrong domain (objectstack.com) alongside a README.md (fixed by #10321) now correctly pointing at objectstack.ai, plus a Dockerfile/docker-compose.yml pair still on the unratified docs.objectstack.ai alias.

Suggested landing

packages/create-objectstack/src/templates/AGENTS.md:99, packages/create-objectstack/src/templates/blank/Dockerfile:10, packages/create-objectstack/src/templates/blank/docker-compose.yml:7 — converge all three on https://objectstack.ai.

Filed by the os-dev seat working #10321; not fixed there because it fell outside that card's dispatched file surface.

[huangyiirene]

Concentration-round first-touch (triage seat, batch anchor for the scaffolded-text family: #10990, #10967, #11022, #11023 — labels flipped per-card, this comment carries the shared grading):

All four promoted finding → pm:queue, Task, domain:cli. Shared rationale: each is measured stale/wrong text that ships to a user's own project or terminal (scaffold output, --help examples, template files) — the highest-leverage doc surface the CLI has, and each card already names its exact lines, the settled wording/host to converge on, and its pin/test obligations. No judgement forks: the canonical host is ruled (2026-08-21), the self-contained-rewrite style is settled by #10324, the os projects→os environments swap is proven by #10927.

Per-card scope notes:

• create-objectstack templates: AGENTS.md links objectstack.com, Dockerfile/docker-compose.yml still use the docs.objectstack.ai alias #10990 — 3 lines, host convergence on https://objectstack.ai.
• packages/cli: environments/*.ts command source still names os projects in examples, class names, and docstrings — leaks into live --help output #10967 — the examples arrays + JSDoc are the deliverable (user-visible); class/test renames are optional riders, not blockers.
• create-objectstack: the blank template's README still cites ADR-0097 and "the ObjectStack framework repo" — the last two dead references in a scaffolded project #11022 — includes deleting the self-retiring EXCLUDED entry in starter-comments-self-contained.test.ts (part of the fix, not a follow-up); serial note: PR fix(create-objectstack): scaffolder "Next steps" names the pm it actually used #11013 touches the same README — land after it or merge across it.
• os init writes ADR identifiers into the user's project too — the same defect #10324 fixed in create-objectstack, in the other scaffolder #11023 — the two-sided pin shape ([finding] The two starter files a newcomer opens first cite ADR numbers, an issue number and a monorepo script that do not exist in their project #10324's test) applies to the rendered literals; hot-file note: packages/cli/src/commands/init.ts is the same file as queued A freshly scaffolded project still reports 4 unmet @better-auth/utils peers on its first install — the skew is not in the scaffold's peerDependencyRules #10931/[finding] Two scaffold paths render the same pnpm-workspace.yaml rule independently, and the drift between them is only ever noticed one incident at a time #10499 territory — fold-or-serial is the cli seat's five-gate answer at claim.

Family fold: all five gates plausibly pass for #10990+#11022 (+#10967); #11023 shares the init.ts hot file with a different family — the seat decides. Dispatch sizing: S each, mechanical.

---

Generated by Claude Code