@cosmicdrift/kumiko-bundled-features 0.351.0 → 0.353.0

package/src/renderer-simple/changes.json

@@ -1,4 +1,10 @@
 [
+  {
+    "version": "0.352.0",
+    "type": "improvement",
+    "title": "Badge, stages track and chips for the simple mail renderer",
+    "detail": "Use badge, { stages } and { chips } in the template variables; the notification RenderResponse carries the matching plain text in text."
+  },
   {
     "version": "0.344.0",
     "type": "improvement",

package/src/seo/changes.json

@@ -1,4 +1,9 @@
 [
+  {
+    "version": "0.353.0",
+    "type": "fix",
+    "title": "sitemap.xml and llms.txt answer 429 when the managed-pages read is rate limited instead of omitting the pages"
+  },
   {
     "version": "0.147.3",
     "type": "fix",

package/src/tenant/changes.json

@@ -1,4 +1,11 @@
 [
+  {
+    "version": "0.353.0",
+    "type": "breaking",
+    "title": "Tenant names are encrypted under the tenant record and crypto-shredded when the tenant is destroyed",
+    "detail": "Tenant names are PII encrypted under the tenant record and crypto-shredded on tenant destroy\n`tenant.name` is now `personal: { of: \"id\" }`, so it is stored as `kumiko-pii:` ciphertext in events and in `read_tenants`. Signup no longer writes the email into the tenant name; it uses the generated tenant key. The tenant destroy job erases the tenant record key and purges the tenant's search documents. The tenant queries (`me`, memberships, tenant-directory, user list, cap-overview, tenants-missing-profile) decrypt the name, and the tenant list sorts by `key` because encrypted names are not sortable.",
+    "migration": "After the bump run the PII backfill (backfillEventPiiEncryption), then rebuild the read_tenants projection; the backfill only encrypts event payloads. Raw reads of read_tenants.name in apps now return ciphertext and must go through decryptStoredPii or the tenant query handlers. Tenants that were already destroyed (read_tenants.destroyed_at set) get the erased sentinel instead of a fresh record key."
+  },
   {
     "version": "0.341.0",
     "type": "improvement",

package/src/tenant-handover/changes.json

@@ -1,4 +1,10 @@
 [
+  {
+    "version": "0.353.0",
+    "type": "fix",
+    "title": "Tenant handover claims fail with transfer_graph_too_deep only when rows exist beyond the last allowed hop",
+    "detail": "Tenant handover only fails with `transfer_graph_too_deep` when rows really hang below the fifth hop, and failed workflow runs report the suspended step\nA claim used to fail whenever the last round's entity type had outgoing edges, even with no rows behind them, so a chain of exactly five hops with an unrestricted `parentRef` entity registered was rejected. `workflow.run-failed` carries the real `stepIndex` for the unsupported-suspension case instead of always 0."
+  },
   {
     "version": "0.321.0",
     "type": "improvement",

package/src/tier-engine/changes.json

@@ -1,4 +1,10 @@
 [
+  {
+    "version": "0.352.0",
+    "type": "improvement",
+    "title": "createTierOptionGate builds the availability rows and gates select options by tier on write",
+    "detail": "withTierOptionGate rejects a disallowed option with the lowest tier that allows it and lets an unchanged stored value pass on update."
+  },
   {
     "version": "0.278.0",
     "type": "breaking",

package/src/workflow-runner/changes.json

@@ -1,4 +1,9 @@
 [
+  {
+    "version": "0.353.0",
+    "type": "fix",
+    "title": "workflow.run-failed carries the real stepIndex when a run suspends in an unsupported step"
+  },
   {
     "version": "0.340.0",
     "type": "improvement",

package/dist/shared/has-where-rule.d.ts

@@ -1,2 +0,0 @@
-import type { OwnershipMap } from "@cosmicdrift/kumiko-framework/engine";
-export declare function hasWhereRule(map: OwnershipMap | undefined): boolean;

package/dist/shared/has-where-rule.js

@@ -1,10 +0,0 @@
-// `where`-rules are read-path only (buildOwnershipClause). The write path
-// decides in memory against the concrete row, so a where-rule there can only
-// ever deny — boot validation rejects the shape (fw#2626). Feature factories
-// that accept an `ownership` option reject it earlier, at build time, so the
-// author gets the option name in the message instead of an entity scope.
-export function hasWhereRule(map) {
-    if (!map)
-        return false;
-    return Object.values(map).some((rule) => rule !== "all" && rule.kind === "where");
-}