Skip to content

docs(extension): 明确文档内容域的网络与 Host 边界 #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xiaoland merged 1 commit into from
Sep 21, 2026
Merged

docs(extension): 明确文档内容域的网络与 Host 边界 #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion 20-product-tdd/extension-documentation-hosting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,11 @@ content within its management origin, and links to hosted sites sever opener acc
The serving topology must support root-relative static assets without rewriting the author's build.
When an author needs an absolute hostname during a build, tooling may reserve an opaque snapshot
address before computing the final content digest. An address can never be rebound to different
bytes. Concrete domain, DNS, TLS, and storage deployment choices remain Registry-owned.
bytes. DNS routing and TLS coverage may intentionally accept a wider hostname set than the
documentation address template. Registry must still admit only the exact host pattern generated by
that template; resolving through the same wildcard or completing TLS does not make another host a
documentation origin. Concrete domain, DNS, TLS, and storage deployment choices remain
Registry-owned.

## Release Lifecycle

Expand Down
Loading