From c51d5e1a7451865e290ff1be55657e76b06ae2a9 Mon Sep 17 00:00:00 2001 From: Lan_zhijiang Date: Mon, 21 Sep 2026 20:44:04 +0800 Subject: [PATCH] =?UTF-8?q?docs(extension):=20=E6=98=8E=E7=A1=AE=E5=86=85?= =?UTF-8?q?=E5=AE=B9=E5=9F=9F=20Host=20=E5=87=86=E5=85=A5=E8=BE=B9?= =?UTF-8?q?=E7=95=8C?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 20-product-tdd/extension-documentation-hosting.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/20-product-tdd/extension-documentation-hosting.md b/20-product-tdd/extension-documentation-hosting.md index 5d0e926..e8a3fc0 100644 --- a/20-product-tdd/extension-documentation-hosting.md +++ b/20-product-tdd/extension-documentation-hosting.md @@ -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