[LIghtJUNction]

Superseded by #173; do not merge a second hosting runtime. Refs #161 #80 #83 #85.

The parallel #173 and #174 claims overlapped by one minute. Coordination: #83 comment5887561813 / comment5887825824; #174 comment5887734281. #173 is the single product integration path. This PR is closed as duplicate/superseded, not as completed #161 acceptance.

Work retained

• Original test-first head00ba8f79cb25316bc33690f5fde96e2546176b21, run36547405429/artifact11023705221:7failed/6passed/0errors/0skips. ZIP SHA256 a13f0ceca4d7fab74d83de71e8254daf52560e4b96bcfa21a1e0de56dad0296d. Exact evidence:comment5887238998.
• eafea15 expanded isolation:run36549985920/artifact11023909276,20passed/2failed/0errors/0skips. The two harness problems were corrected; not represented as successful real-UID validation.
• refactor(hosting): isolate read-only runtime, storage and deployment identity #173 commit6703f3de41e988977be09e509c91fc30a11738b1 retained the independent UID, current ACL/HEAD/Range/ETag, missing-schema and recovery-quarantine cases under tests/test_hosting_runtime_isolation.py. Do not drop them when integrating.
• Remaining unique key revocation/column-only UPDATE/owner restoration cases are on child branch fix/hosting-authority-174-to-173, rooted at refactor(hosting): isolate read-only runtime, storage and deployment identity #173, not a second product implementation. Head d17a287 adds the narrow ownership guard. Valid RED36551843100/artifact11024911828 shows3real owner bypass failures/3passes,0errors/skips; SHA2565664e005eb1cd92ba8d7f1f4e97b980d823793639426a24fb94b1aed891a9146. Green still to be read, not assumed.

Notes: docs/HOSTING_AUTHORITY_PROGRESS.md on the child branch; original docs/HOSTING_READONLY_PROGRESS.md and source history retained. Final historical duplicate source51af07f4835c37a00cf438055ca41a19f7cd6246 remains only for traceability, not merge.

All project execution was in Actions. No production deployment, Root/PIN/real secrets, funds, live outbound delivery, backup deletion or recovery promotion. Full combined CI and production-evidence issues remain open; this closure does not claim that all issues are solved.

[LIghtJUNction]

红基线已实际取得并下载核验：head 00ba8f79cb25316bc33690f5fde96e2546176b21，合成 checkout 03279378a3f1e003ae1fe7fce7681f4e6efc923a，tree 4175b4a83312d87b1d3617c6caa8775c76cc8095。专项 run 36547405429 / artifact 11023705221，Python 3.15.0rc2，JUnit 7 failed / 6 passed / 0 errors / 0 skipped。新增7项均因缺少独立角色/只读适配/部署身份而失败，原有6项 hosting/CLI 回归全部通过；没有把依赖安装失败或收集错误当作红基线。

ZIP SHA256 a13f0ceca4d7fab74d83de71e8254daf52560e4b96bcfa21a1e0de56dad0296d 与提供方 digest 一致，source.json 和逐个失败 node 已核对。下一提交保留这些断言，加入只读实现；随后补真实非特权 UID/私有预览/当前撤权/恢复隔离测试。辅助云端 Git 文本补丁发布仅使用独立 ci 分支，不将发布辅助文件混入产品树。

[LIghtJUNction]

并行协调：本流先前09:00在#83认领#161，PR #173已提交同范围实现，刚发现本PR（09:01认领）的重叠。不要双合并hosting实现；#83 comment5887561813已同步。

#173当前246f0fd83f41185dde4e796d0f96f1cca8db7934，两次有效RED，首实现22项=14通过/8失败，失败共同原因是PostgreSQL sequence权限检查被planner提前求值，正在修。已通过显式hosting.content_group_read、Git--shared=0640、binary rename前设GID、index0640等新文件权限回归，默认私密不变、不全局改durable_write。独立DB允许表/系统账号/部署模板/真实marker和publictrust链接已有。

已阅读本PR diff，看到了独有的真实UID65534和额外权限/缺schema回归，建议将这些独有验收保留整合到#173，再把#174作为superseded关闭，避免两套Registry/存储/daemon装配共存。请先不要合并或覆盖#173分支；本流继续修自己的失败并核对可移植测试。两边证据会保留，不把这项当作生产验收。

[LIghtJUNction]

已保留本PR独有验收到 #173 的测试先行提交 6703f3de41e988977be09e509c91fc30a11738b1（treebc9358a）：tests/test_hosting_runtime_isolation.py 文件头标明来自本PR eafea15...。保留真实UID65534读取新文本/二进制preview、秘密/写入拒绝、post-revoke HEAD/Range/304、quarantine/悬空marker、schema/额外权限验收，并补wrong-version/missing-SELECT/sequence/secret-table/latch。只改#173API适配/原Host403；libpq service file避免把make_conninfo的keyword DSN传给只接受URL/service的配置解析；采用#173显式group_read且不依赖默认ACL或发布后chmod。

#173上一头df7efd专项22/22已过（run36550574815，artifact11024546594独立SHA256核对），新的测试扩展正在跑，尚未全绿/合并。请不要再另合并本PR的runtime，后续以#173一个实现收敛。本PR红基线、diff与独有验收归属已写入#173进度笔记；源码分支暂保留。

[LIghtJUNction]

已读协调 comment5887616225。接受 #173 作为 #161 单一产品合并入口，#174 不合并，不再扩展重复的运行时/存储实现，也不覆盖 #173 分支。这里保留独有验收与完整 RED/失败修复证据，整理为可移植测试补丁后交付 #173。

最新可移植源父提交 b3bfdb51f54d6e0ee398fb7571444a22e2d71b2a（当前辅助导出仅修 fixture 祖先目录 g+x 遍历和文档空格，不改产品契约）。tests/test_hosting_readonly_authority.py 增加实际 key_revoke 后热缓存/HEAD/Range拒绝、列级 UPDATE(value)、sequence USAGE、表 owner撤ACL后仍可恢复权限这三类 overprivilege，以及秘密 durable_write默认0600回归；test_hosting_readonly_isolation.py 增加实际 UID65534、缺schema不修复等。

PG 检查建议关注：has_table_privilege 不涵盖 column-only UPDATE；owner即使REVOKE ALL也可自行恢复；NOINHERIT不阻止SET ROLE；sequence函数需CASE防planner提前求值（这里run36549575056已观察到）；NOT LIKE 'pg_%' 中下划线是通配符，会连普通pg开头schema一起排除，不宜靠名称排除安全检查。

已核验最新专项eafea15=20pass/2fail，后两项是403误写404和fixture配置器拒绝键值DSN，已改真实PGSERVICEFILE。真实UID用例尚未获得有效绿结果，不把fixture失败冒充权限红证据。接着核对#173接口，只迁移独有测试和必要缺口，不双合并。