Deferred half of the Option-A ruling on objectstack-ai/cloud#1685 (2026-08-28). Today HotCRM builds against published spec 17.1.0, whose toolchain still EMITS the retired allowRestore/allowPurge defaults into every permission entry; the artifacts boot only because of the retired-defaulted-key tolerance (objectstack#12845). When the maintainer cuts the next spec release: verify BY TARBALL CONTENT that it carries the retirement (grep the dist for the #12497 tombstones and the absence of allowRestore.*default), bump the dependency, rebuild, and verify the artifact emits NEITHER key — at which point HotCRM no longer leans on the tolerance at all. Not urgent (the tolerance is a permanent class rule, not a window); this card exists so the hygiene isn't lost. Origin: the release-gap incident measured on cloud#1685/cloud#1672.
Deferred half of the Option-A ruling on objectstack-ai/cloud#1685 (2026-08-28). Today HotCRM builds against published spec 17.1.0, whose toolchain still EMITS the retired
allowRestore/allowPurgedefaults into every permission entry; the artifacts boot only because of the retired-defaulted-key tolerance (objectstack#12845). When the maintainer cuts the next spec release: verify BY TARBALL CONTENT that it carries the retirement (grep the dist for the #12497 tombstones and the absence ofallowRestore.*default), bump the dependency, rebuild, and verify the artifact emits NEITHER key — at which point HotCRM no longer leans on the tolerance at all. Not urgent (the tolerance is a permanent class rule, not a window); this card exists so the hygiene isn't lost. Origin: the release-gap incident measured on cloud#1685/cloud#1672.