fix(metadata-protocol): chunkedUpload 改用与 files 同一的可服务性判据(#5672)

同一 slot(file-storage)的两个词表键此前判据不同:files 走可服务性、
chunkedUpload 只看注册存在。后果有二:自声明 stub 的存储实现会被广告出
chunkedUpload: true —— 而该 builder 本就不给它广告 routes.storage;更要紧的
是 runtime dispatcher 对同一键答的是 hasFiles(可服务性),两个生产者会对同
一宿主的同一键给出相反答案 —— 正是本单要消除的方言。

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fxLGQdatPbBUvCgiVxg6D

Author: claude

packages/metadata-protocol/src/protocol.ts

@@ -2798,7 +2798,18 @@ export class ObjectStackProtocolImplementation implements
             cron: registeredServices.has('job'),
             search: registeredServices.has('search'),
             export: registeredServices.has('automation') || registeredServices.has('queue'),
-            chunkedUpload: registeredServices.has('file-storage'),
+            // [#5672] Serveability-gated, was presence-only. Two reasons, and
+            // the second is the binding one:
+            //   1. `declared === enforced` — a self-declared stub file-storage
+            //      mounts no HTTP surface, so this builder already withholds
+            //      `routes.storage` from it; advertising chunked upload anyway
+            //      promised an upload endpoint that cannot exist.
+            //   2. the runtime dispatcher answers this key `hasFiles`, i.e.
+            //      `isServiceServeable(filesSvc)`. Leaving this one on presence
+            //      would make the two producers give the SAME host opposite
+            //      answers for the SAME key — a new dialect inside the
+            //      vocabulary this issue exists to unify.
+            chunkedUpload: capabilityServed('file-storage'),
             // Atomic cross-object batch (#3298 / #1604 / ADR-0034 item 4): the
             // REST /batch endpoint runs its ops inside `engine.transaction()`,
             // which only opens a real (all-or-nothing) transaction when the