@happyvertical/smrt-profiles 0.40.13 → 0.40.15

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.
Files changed (5) hide show
  1. package/README.md +2 -2
  2. package/dist/index.js +1 -1
  3. package/dist/manifest.json +2 -2
  4. package/dist/smrt-knowledge.json +4 -4
  5. package/package.json +6 -6
package/README.md CHANGED
@@ -155,12 +155,12 @@ lookup behavior and is not suitable for identity linking. Only the explicit
155
155
  deploy-time backfill scans the Profile table and records readiness; guarded
156
156
  runtime identity lookups use the indexed key and validate returned candidates.
157
157
  `createProfileFromOidc()` requires a transaction-capable database. Pass the
158
- root database, which must expose `beginTransaction`, and SMRT owns the
158
+ root database, which must expose `beginTransaction`, and s-m-r-t owns the
159
159
  transaction; an already transaction-bound handle is supported through a
160
160
  savepoint. Paths that perform canonical email lookup or reservation require
161
161
  `_smrt_backfills` to exist first. Provisioning never attempts tracker DDL on
162
162
  a caller-owned transaction; for those paths, if the table is absent, pass the
163
- root database so SMRT can initialize it outside the transaction. Exact
163
+ root database so s-m-r-t can initialize it outside the transaction. Exact
164
164
  issuer/subject reuse skips the email-key readiness-marker lookup, but root
165
165
  coordination still initializes the shared tracker table. Caller-owned exact
166
166
  reuse does not consult the tracker and therefore does not require that table.