@voltro/protocol 0.41.0 → 0.43.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/jwt.d.ts CHANGED
@@ -286,7 +286,7 @@ declare const Subject: Schema.Union<[Schema.Struct<{
286
286
  * Set when this caller PRESENTED a credential and it was rejected — an
287
287
  * expired token above all. Absent when they presented none.
288
288
  *
289
- * The two are the same Subject and must not be the same ANSWER. A consumer
289
+ * The two are the same Subject and must not be the same ANSWER. A deployment
290
290
  * measured the cost: a user's tab outlived their IdP's token lifetime, the
291
291
  * strategy logged `supabase jwt expired`, the caller fell through to
292
292
  * anonymous, and the guard then refused with `missing required scope
package/dist/rest.d.ts CHANGED
@@ -176,7 +176,7 @@ declare interface GuardSpec<Input = unknown> {
176
176
  * in its own tables (a `teamMembers` row, say) registers its own tuple source
177
177
  * rather than copying data across; see `policyGuardResolver.ts`.
178
178
  *
179
- * That paragraph is here because its absence cost a consumer their access
179
+ * That paragraph is here because its absence cost a deployment their access
180
180
  * gate. This comment used to describe the resolver as "a future ReBAC /
181
181
  * `accessPolicy()` resolver" — written before the ReBAC path shipped and
182
182
  * never updated. They read the type, quoted the sentence, concluded there was
@@ -653,7 +653,7 @@ declare interface QueryCacheConfig {
653
653
  *
654
654
  * `'tenant'` exists because the other two were the only options and neither
655
655
  * fits an org-wide figure: `subject` recomputes it per person, and `global`
656
- * is not a cache but a cross-tenant leak. A consumer reported computing the
656
+ * is not a cache but a cross-tenant leak. A deployment reported computing the
657
657
  * same nine-table statistic up to 18 times for 18 employees rather than take
658
658
  * the second option, which was the correct call.
659
659
  *
@@ -897,7 +897,7 @@ declare const Subject: Schema.Union<[Schema.Struct<{
897
897
  * Set when this caller PRESENTED a credential and it was rejected — an
898
898
  * expired token above all. Absent when they presented none.
899
899
  *
900
- * The two are the same Subject and must not be the same ANSWER. A consumer
900
+ * The two are the same Subject and must not be the same ANSWER. A deployment
901
901
  * measured the cost: a user's tab outlived their IdP's token lifetime, the
902
902
  * strategy logged `supabase jwt expired`, the caller fell through to
903
903
  * anonymous, and the guard then refused with `missing required scope
package/dist/session.d.ts CHANGED
@@ -284,7 +284,7 @@ declare const Subject: Schema.Union<[Schema.Struct<{
284
284
  * Set when this caller PRESENTED a credential and it was rejected — an
285
285
  * expired token above all. Absent when they presented none.
286
286
  *
287
- * The two are the same Subject and must not be the same ANSWER. A consumer
287
+ * The two are the same Subject and must not be the same ANSWER. A deployment
288
288
  * measured the cost: a user's tab outlived their IdP's token lifetime, the
289
289
  * strategy logged `supabase jwt expired`, the caller fell through to
290
290
  * anonymous, and the guard then refused with `missing required scope
@@ -330,7 +330,7 @@ declare const SubjectIdentity: Schema.Union<[Schema.Struct<{
330
330
  * Set when this caller PRESENTED a credential and it was rejected — an
331
331
  * expired token above all. Absent when they presented none.
332
332
  *
333
- * The two are the same Subject and must not be the same ANSWER. A consumer
333
+ * The two are the same Subject and must not be the same ANSWER. A deployment
334
334
  * measured the cost: a user's tab outlived their IdP's token lifetime, the
335
335
  * strategy logged `supabase jwt expired`, the caller fell through to
336
336
  * anonymous, and the guard then refused with `missing required scope
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@voltro/protocol",
3
- "version": "0.41.0",
3
+ "version": "0.43.0",
4
4
  "description": "The Voltro wire + plugin contract — defineQuery/Mutation/Action/Stream, definePlugin, sessions / JWT / API-keys, and the RPC protocol.",
5
5
  "keywords": [
6
6
  "voltro",
@@ -54,8 +54,8 @@
54
54
  },
55
55
  "dependencies": {
56
56
  "@effect/sql": "^0.52.0",
57
- "@voltro/database": "0.41.0",
58
- "@voltro/logger": "0.41.0",
57
+ "@voltro/database": "0.43.0",
58
+ "@voltro/logger": "0.43.0",
59
59
  "jose": "^6.2.8"
60
60
  },
61
61
  "peerDependencies": {