runtime: export the disable door's dependent-validation-rule verdict for host doors, so a host that removes a package another way answers the same 409 #31067

repo:cloud#3 · hotlong · session_01Q4EjjRhUZjdy8VXs6Kkur2
Ruled: maintainer 「平台开放检查，cloud 接上（推荐）」 (repo:cloud#3 seat session, 2026-11-07)

Filing gate: maintainer ruling on a gap measured by the objectstack#31001 dev. Platform gaps go to the platform (「平台的问题应该在平台处理」, objectstack#30765).

维护者速读

平台的「停用包」接口会在别的包有生效的校验规则读到被停用字段时拒绝停用（#30825），避免之后这个对象所有写入都失败。cloud 控制面还有一个「按安装停用」和卸载的接口，它把包直接从环境里拿掉，不经过这道检查。平台的判定是模块私有的，cloud 没法调用，只能自己再写一份，而规则要求只写一份。所以请平台把判定和提示语开放出来，cloud 随后接上。

Readings (objectstack main)

• readDisableDependentRules (packages/runtime/src/domains/packages.ts) is module-private. The sentence disableDependentRulesMessage("Package '<id>' cannot be disabled", dependents) is composed inline at the door.
• Consumer: cloud packages/service-cloud/src/routes/environment-crud/packages.ts. Its disable arm (PATCH …/cloud/environments/:id/packages/:pkgId/disable) and the soft-disable uninstall drop the package from the environment's artifact with no scan. On the cloud#31001 rig this left every write on the object refused 400 VALIDATION_FAILED.

Expected

• A public, pure verdict over a registry, or a kernel service read, that returns the dependent rules plus the message builder. The door itself consumes it, so there is still one spelling of the scan and the sentence.

Acceptance

• The door's behaviour is unchanged (existing fix(runtime)!: the package disable door refuses while an enabled package's validation rule reads a field the package adds #30825 tests green).
• A unit test of the exported verdict.
• The export is on the package entry.

Consumer card: objectstack-ai/cloud (filed alongside).

Suggested-grade: p2.