Group of 2 Under the hood
No documentation found
Tool and HIPAA compliance settings gain a stricter hardBlockUnder enforcement tier beyond the existing deny list
What
- Several HIPAA compliance settings (Memory sync, Projects, Team onboarding, Peer messaging) now carry a
hardBlockUnder: ["hipaa"]property alongside the existingdeniedUnder, marking a stricter enforcement tier separate from ordinary denial. - A new lookup table is built by collecting each tool's
hardBlockUnderconfiguration, pairing each named threshold with the tool it applies to. The related deny-on-cache-miss list was also simplified to be built directly from each tool's configuration instead of a fixed base list plus filtering.
Why This adds a stricter "hard block" enforcement level on top of the existing deny mechanism, letting specific settings and tools be blocked outright under certain compliance thresholds (like HIPAA) rather than just denied through the normal path.
Names in the bundlehardBlockUnder
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What practical difference a hard block has from denial (e.g. whether it can be overridden) is not stated.