feat: reconcile GLS registry into runtime manifest v2

product-source/hololake-native-desktop/docs/GLS-NATIVE-RUNTIME-IMPLEMENTATION-PLAN-20260817.md

@@ -25,7 +25,7 @@
 REPO-012 的 `gls/` 树中另有 75 个唯一编号 `.hdlp` 源。协议注册表、`GLS-ENTRY`、`SOURCE-MANIFEST`、架构目录和 routing 映射并未收敛为一份可执行注册真相：
 
 - 注册表唯一编号：52
-- 草案依赖涉及唯一编号：63
+- 草案依赖涉及唯一编号：57
 - 草案引用但未进入该注册表的依赖：19
 - 草案引用但没有可直接定位的编号 `.hdlp` 正本：24
 - 编号 `.hdlp` 存在但没有进入该协议注册表：31
@@ -217,11 +217,8 @@ protocol_decision_receipt:
 
 ## 8. 当前 HoloLake 分支的承接关系
 
-当前 `d6b1290` 已完成 75 份编号协议的确定性发现登记，并为 `GLS-0250 / 0253 / 0262 / 0263` 建立首批原生适配器。下一步不继续盲目增加适配器，而是：
+`d6b1290` 完成了 75 份编号协议的确定性发现登记，并为 `GLS-0250 / 0253 / 0262 / 0263` 建立首批原生适配器。P0 随后已把运行清单升级为 v2：四份登记源分别固化摘要，75 份协议全部取得登记解释，旧依赖与显式运行依赖分离，三组旧环只进入审计面而不能进入执行图。
 
-1. 先把发现登记升级为 P0 的权威对账清单；
-2. 给依赖边加类型并拆除三组运行环；
-3. 实现 P1 的 GLP schema、统一裁决 API 和持久回执；
-4. 再按 P2–P7 逐层扩大运行集合。
+下一步是实现 P1 的 GLP schema、统一裁决 API 和持久回执，再按 P2–P7 逐层扩大运行集合。旧依赖边只有经权威修订为明确的类型边后才可离开审计面。
 
 这保证“已注册”不会被误报为“系统正在运行”，也保证每次新增执行协议都有可重复编译、明确守卫和真实回执。

product-source/hololake-native-desktop/docs/adr/0006-compiled-gls-protocol-runtime.md

@@ -9,7 +9,9 @@ REPO-012 contains dozens of numbered GLS protocol sources. Human-readable source
 
 ## Decision
 
-Compile the current numbered GLS sources into a deterministic registry pinned to an exact REPO-012 commit. Every selected source records its stable GLS number, path and SHA-256. Duplicate historical source locations are resolved by a deterministic source preference, while alternate-source counts remain visible.
+Compile the current numbered GLS sources into a deterministic v2 runtime manifest pinned to an exact REPO-012 commit. Every selected source records its stable GLS number, path and SHA-256. Duplicate historical source locations are resolved by a deterministic source preference, while alternate-source counts remain visible. The compiler also reconciles the protocol registry, GLS entry, source manifest, architecture catalog and routing references, preserving their independent source hashes and rejecting registration conflicts.
+
+Legacy `depends` arrays are not silently interpreted as runtime edges. They remain `LEGACY_UNTYPED_REFERENCE` audit edges and block new activation until their meaning is classified. Only dependencies declared by an explicit executable projection enter the runtime graph as `RUNTIME_REQUIRES`; that graph must be acyclic and dependency-closed.
 
 An executable projection requires an explicit native adapter, event kinds, dependency list and fail-closed behavior. The compiler rejects missing executable dependencies and dependency cycles. The native runtime revalidates schema, source commit, counts, hashes, adapters and dependency closure before returning a protocol set to an organ.