@singi-labs/sifa-sdk 0.19.55 → 0.19.57

package/dist/verification-providers-7il3kPQS.d.ts

@@ -0,0 +1,158 @@
+import { z } from 'zod';
+
+/**
+ * Grapheme-aware refinement matching the AT Protocol lexicon `maxGraphemes`
+ * constraint. JS strings are sequences of UTF-16 code units, but lexicon
+ * `maxGraphemes` counts user-perceived characters (grapheme clusters), so
+ * emoji sequences, regional indicators, ZWJ joins, and combining marks all
+ * count as one unit each. We use `Intl.Segmenter` to enforce this correctly.
+ */
+declare function maxGraphemes(max: number): (value: string) => boolean;
+/** Decentralized identifier, AT Protocol `format: did`. */
+declare const didSchema: z.ZodString;
+/** RFC 3339 datetime with timezone offset, AT Protocol `format: datetime`. */
+declare const datetimeSchema: z.ZodString;
+/**
+ * Freeform calendar date for user-facing profile dates (start/end, issued,
+ * completed, awarded, published, etc.). Accepts a bare year, year-month,
+ * year-month-day, or a full datetime (so a legacy record's RFC-3339 date maps
+ * through on backfill without loss). NOT strict `datetime` -- users typically
+ * remember only month/year, and LinkedIn-importer writes carry partial dates,
+ * so the lexicons document these as freeform `YYYY-MM` / `YYYY-MM-DD`. Record
+ * metadata like `createdAt` stays on `datetimeSchema`.
+ */
+declare const partialDateSchema: z.ZodString;
+/** Generic AT-URI, AT Protocol `format: at-uri`. */
+declare const atUriSchema: z.ZodString;
+/** Content identifier, AT Protocol `format: cid`. Loose validation -- accepts CIDv0 and CIDv1. */
+declare const cidSchema: z.ZodString;
+/** BCP 47 language tag, AT Protocol `format: language`. */
+declare const languageTagSchema: z.ZodString;
+/** Generic URI, AT Protocol `format: uri`. */
+declare const uriSchema: z.ZodString;
+/**
+ * StrongRef shape from `com.atproto.repo.strongRef` -- pins a record by both
+ * AT-URI (identity) and CID (version).
+ */
+declare const strongRefSchema: z.ZodObject<{
+    uri: z.ZodString;
+    cid: z.ZodString;
+}, z.core.$strip>;
+/**
+ * Reference to an `id.sifa.profile.skill` record by AT-URI. Mirrors
+ * `id.sifa.defs#skillRef`, which carries no CID at all: skills are mutable
+ * records in the same user's repo, so the reference resolves live and tracks
+ * edits to the target.
+ */
+declare const skillRefSchema: z.ZodObject<{
+    uri: z.ZodString;
+}, z.core.$strip>;
+/**
+ * Reference to a record by AT-URI, with an optional CID. Mirrors
+ * `id.sifa.defs#externalRecordRef`. Unlike a strongRef the CID is optional:
+ * consumers resolve the AT-URI live so the reference tracks edits to the
+ * target, and the CID is a best-effort integrity hint only.
+ */
+declare const externalRecordRefSchema: z.ZodObject<{
+    uri: z.ZodString;
+    cid: z.ZodOptional<z.ZodString>;
+}, z.core.$strip>;
+/**
+ * Shared reference to an organization or person named by a record. Mirrors
+ * `id.sifa.defs#agentRef`. `name` is a point-in-time snapshot label captured
+ * when the record was saved; `did` and `entityRef` are the durable identity and
+ * should be resolved live. `name` is required so an empty object cannot validate
+ * as a no-op. `.passthrough()` (not `.strict()`): external apps may emit fields a
+ * newer schema will define, and dropping them on a round-trip would silently
+ * lose data.
+ */
+declare const agentRefSchema: z.ZodObject<{
+    name: z.ZodString;
+    did: z.ZodOptional<z.ZodString>;
+    entityRef: z.ZodOptional<z.ZodString>;
+}, z.core.$loose>;
+type AgentRef = z.infer<typeof agentRefSchema>;
+/**
+ * Self-labels shape from `com.atproto.label.defs#selfLabels`. Modelled
+ * permissively because clients rarely construct this directly; the AppView
+ * handles label validation.
+ */
+declare const selfLabelsSchema: z.ZodObject<{
+    $type: z.ZodOptional<z.ZodLiteral<"com.atproto.label.defs#selfLabels">>;
+    values: z.ZodArray<z.ZodObject<{
+        val: z.ZodString;
+    }, z.core.$strip>>;
+}, z.core.$strip>;
+
+/**
+ * Verification providers -- the trust roots Sifa recognizes for AT Protocol
+ * `app.bsky.graph.verification` records.
+ *
+ * Framing (see decisions/2026-07-13-third-party-verification-providers.md, D4):
+ * a verification checkmark is ONE low-tier trust layer, not Sifa's headline.
+ * Most of what it certifies is "this account is who they claim to be" -- useful,
+ * and worth carrying because it's an already-recognized network signal, but low
+ * value on its own. It sits among Sifa's other trust signals and never becomes a
+ * score or a gate. This registry only decides which issuers Sifa displays and
+ * with what provenance.
+ *
+ * Data-only: badge colors and icons are consumer concerns (React DOM on web,
+ * React Native on mobile), same split as {@link PLATFORM_LABELS}. Consumers map
+ * a provider id to a token/color.
+ */
+type VerificationProviderId = 'bluesky' | 'mu';
+/** How Sifa learns about a provider's verifications. */
+type VerificationSource = 'bluesky-api' | 'firehose';
+interface VerificationProvider {
+    id: VerificationProviderId;
+    /** Human label for the badge popover, e.g. "Bluesky", "mu (Eurosky)". */
+    label: string;
+    /**
+     * Primary-display priority (D1): when an account holds verifications from
+     * multiple providers, the lowest number wins the single inline badge and the
+     * rest move into the popover. Must be unique across providers.
+     */
+    priority: number;
+    /**
+     * - `bluesky-api`: sourced from Bluesky's public-API `verifiedStatus`. Bluesky
+     *   maintains its own trusted-verifier set, so Sifa keeps no local DID list.
+     * - `firehose`: sourced from the Jetstream, gated on {@link verifierDids}.
+     */
+    source: VerificationSource;
+    /**
+     * Trusted verifier DIDs for firehose-sourced providers. A verification record
+     * counts only if its ISSUER DID is in this list. Empty for `bluesky-api`
+     * providers (Bluesky's AppView owns that decision). DIDs, not handles: a handle
+     * takeover must never confer verifier status.
+     */
+    verifierDids: readonly string[];
+}
+/**
+ * A verification held by an account, as surfaced to the UI. `issuerDid` is
+ * present for firehose-sourced providers and absent for `bluesky-api`.
+ */
+interface AccountVerification {
+    provider: VerificationProviderId;
+    verifiedAt?: string | null;
+    issuerDid?: string | null;
+}
+declare const VERIFICATION_PROVIDERS: Record<VerificationProviderId, VerificationProvider>;
+declare function isKnownVerificationProvider(id: string): id is VerificationProviderId;
+declare function getVerificationProvider(id: string): VerificationProvider | undefined;
+/**
+ * The firehose issuer gate: given the DID that authored an
+ * `app.bsky.graph.verification` record, return the provider it verifies for, or
+ * `null` if the issuer is not a recognized firehose verifier. API-sourced
+ * providers (Bluesky) are never matched here -- their verifications do not enter
+ * through the firehose, so a self-issued record cannot resolve to them.
+ */
+declare function resolveVerifierProvider(issuerDid: string): VerificationProviderId | null;
+/**
+ * D1 primary-provider selection: from all verifications an account holds, pick
+ * the one whose provider has the highest priority (lowest `priority` number) for
+ * the single inline badge. The rest belong in the popover. Verifications from
+ * unknown providers are ignored. Returns `null` when nothing is displayable.
+ */
+declare function primaryVerification(verifications: readonly AccountVerification[]): AccountVerification | null;
+
+export { type AgentRef as A, VERIFICATION_PROVIDERS as V, type AccountVerification as a, type VerificationProvider as b, type VerificationProviderId as c, type VerificationSource as d, agentRefSchema as e, atUriSchema as f, cidSchema as g, datetimeSchema as h, didSchema as i, externalRecordRefSchema as j, getVerificationProvider as k, isKnownVerificationProvider as l, languageTagSchema as m, maxGraphemes as n, primaryVerification as o, partialDateSchema as p, skillRefSchema as q, resolveVerifierProvider as r, selfLabelsSchema as s, strongRefSchema as t, uriSchema as u };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@singi-labs/sifa-sdk",
-  "version": "0.19.55",
+  "version": "0.19.57",
   "description": "Sifa SDK — public client library for the Sifa AppView on AT Protocol. Shared by sifa-web and sifa-app.",
   "license": "MIT",
   "type": "module",

package/dist/shared-v0vl5hov.d.cts

@@ -1,87 +0,0 @@
-import { z } from 'zod';
-
-/**
- * Grapheme-aware refinement matching the AT Protocol lexicon `maxGraphemes`
- * constraint. JS strings are sequences of UTF-16 code units, but lexicon
- * `maxGraphemes` counts user-perceived characters (grapheme clusters), so
- * emoji sequences, regional indicators, ZWJ joins, and combining marks all
- * count as one unit each. We use `Intl.Segmenter` to enforce this correctly.
- */
-declare function maxGraphemes(max: number): (value: string) => boolean;
-/** Decentralized identifier, AT Protocol `format: did`. */
-declare const didSchema: z.ZodString;
-/** RFC 3339 datetime with timezone offset, AT Protocol `format: datetime`. */
-declare const datetimeSchema: z.ZodString;
-/**
- * Freeform calendar date for user-facing profile dates (start/end, issued,
- * completed, awarded, published, etc.). Accepts a bare year, year-month,
- * year-month-day, or a full datetime (so a legacy record's RFC-3339 date maps
- * through on backfill without loss). NOT strict `datetime` -- users typically
- * remember only month/year, and LinkedIn-importer writes carry partial dates,
- * so the lexicons document these as freeform `YYYY-MM` / `YYYY-MM-DD`. Record
- * metadata like `createdAt` stays on `datetimeSchema`.
- */
-declare const partialDateSchema: z.ZodString;
-/** Generic AT-URI, AT Protocol `format: at-uri`. */
-declare const atUriSchema: z.ZodString;
-/** Content identifier, AT Protocol `format: cid`. Loose validation -- accepts CIDv0 and CIDv1. */
-declare const cidSchema: z.ZodString;
-/** BCP 47 language tag, AT Protocol `format: language`. */
-declare const languageTagSchema: z.ZodString;
-/** Generic URI, AT Protocol `format: uri`. */
-declare const uriSchema: z.ZodString;
-/**
- * StrongRef shape from `com.atproto.repo.strongRef` -- pins a record by both
- * AT-URI (identity) and CID (version).
- */
-declare const strongRefSchema: z.ZodObject<{
-    uri: z.ZodString;
-    cid: z.ZodString;
-}, z.core.$strip>;
-/**
- * Reference to an `id.sifa.profile.skill` record by AT-URI. Mirrors
- * `id.sifa.defs#skillRef`, which carries no CID at all: skills are mutable
- * records in the same user's repo, so the reference resolves live and tracks
- * edits to the target.
- */
-declare const skillRefSchema: z.ZodObject<{
-    uri: z.ZodString;
-}, z.core.$strip>;
-/**
- * Reference to a record by AT-URI, with an optional CID. Mirrors
- * `id.sifa.defs#externalRecordRef`. Unlike a strongRef the CID is optional:
- * consumers resolve the AT-URI live so the reference tracks edits to the
- * target, and the CID is a best-effort integrity hint only.
- */
-declare const externalRecordRefSchema: z.ZodObject<{
-    uri: z.ZodString;
-    cid: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-/**
- * Shared reference to an organization or person named by a record. Mirrors
- * `id.sifa.defs#agentRef`. `name` is a point-in-time snapshot label captured
- * when the record was saved; `did` and `entityRef` are the durable identity and
- * should be resolved live. `name` is required so an empty object cannot validate
- * as a no-op. `.passthrough()` (not `.strict()`): external apps may emit fields a
- * newer schema will define, and dropping them on a round-trip would silently
- * lose data.
- */
-declare const agentRefSchema: z.ZodObject<{
-    name: z.ZodString;
-    did: z.ZodOptional<z.ZodString>;
-    entityRef: z.ZodOptional<z.ZodString>;
-}, z.core.$loose>;
-type AgentRef = z.infer<typeof agentRefSchema>;
-/**
- * Self-labels shape from `com.atproto.label.defs#selfLabels`. Modelled
- * permissively because clients rarely construct this directly; the AppView
- * handles label validation.
- */
-declare const selfLabelsSchema: z.ZodObject<{
-    $type: z.ZodOptional<z.ZodLiteral<"com.atproto.label.defs#selfLabels">>;
-    values: z.ZodArray<z.ZodObject<{
-        val: z.ZodString;
-    }, z.core.$strip>>;
-}, z.core.$strip>;
-
-export { type AgentRef as A, agentRefSchema as a, atUriSchema as b, cidSchema as c, datetimeSchema as d, didSchema as e, externalRecordRefSchema as f, skillRefSchema as g, strongRefSchema as h, languageTagSchema as l, maxGraphemes as m, partialDateSchema as p, selfLabelsSchema as s, uriSchema as u };

package/dist/shared-v0vl5hov.d.ts

@@ -1,87 +0,0 @@
-import { z } from 'zod';
-
-/**
- * Grapheme-aware refinement matching the AT Protocol lexicon `maxGraphemes`
- * constraint. JS strings are sequences of UTF-16 code units, but lexicon
- * `maxGraphemes` counts user-perceived characters (grapheme clusters), so
- * emoji sequences, regional indicators, ZWJ joins, and combining marks all
- * count as one unit each. We use `Intl.Segmenter` to enforce this correctly.
- */
-declare function maxGraphemes(max: number): (value: string) => boolean;
-/** Decentralized identifier, AT Protocol `format: did`. */
-declare const didSchema: z.ZodString;
-/** RFC 3339 datetime with timezone offset, AT Protocol `format: datetime`. */
-declare const datetimeSchema: z.ZodString;
-/**
- * Freeform calendar date for user-facing profile dates (start/end, issued,
- * completed, awarded, published, etc.). Accepts a bare year, year-month,
- * year-month-day, or a full datetime (so a legacy record's RFC-3339 date maps
- * through on backfill without loss). NOT strict `datetime` -- users typically
- * remember only month/year, and LinkedIn-importer writes carry partial dates,
- * so the lexicons document these as freeform `YYYY-MM` / `YYYY-MM-DD`. Record
- * metadata like `createdAt` stays on `datetimeSchema`.
- */
-declare const partialDateSchema: z.ZodString;
-/** Generic AT-URI, AT Protocol `format: at-uri`. */
-declare const atUriSchema: z.ZodString;
-/** Content identifier, AT Protocol `format: cid`. Loose validation -- accepts CIDv0 and CIDv1. */
-declare const cidSchema: z.ZodString;
-/** BCP 47 language tag, AT Protocol `format: language`. */
-declare const languageTagSchema: z.ZodString;
-/** Generic URI, AT Protocol `format: uri`. */
-declare const uriSchema: z.ZodString;
-/**
- * StrongRef shape from `com.atproto.repo.strongRef` -- pins a record by both
- * AT-URI (identity) and CID (version).
- */
-declare const strongRefSchema: z.ZodObject<{
-    uri: z.ZodString;
-    cid: z.ZodString;
-}, z.core.$strip>;
-/**
- * Reference to an `id.sifa.profile.skill` record by AT-URI. Mirrors
- * `id.sifa.defs#skillRef`, which carries no CID at all: skills are mutable
- * records in the same user's repo, so the reference resolves live and tracks
- * edits to the target.
- */
-declare const skillRefSchema: z.ZodObject<{
-    uri: z.ZodString;
-}, z.core.$strip>;
-/**
- * Reference to a record by AT-URI, with an optional CID. Mirrors
- * `id.sifa.defs#externalRecordRef`. Unlike a strongRef the CID is optional:
- * consumers resolve the AT-URI live so the reference tracks edits to the
- * target, and the CID is a best-effort integrity hint only.
- */
-declare const externalRecordRefSchema: z.ZodObject<{
-    uri: z.ZodString;
-    cid: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-/**
- * Shared reference to an organization or person named by a record. Mirrors
- * `id.sifa.defs#agentRef`. `name` is a point-in-time snapshot label captured
- * when the record was saved; `did` and `entityRef` are the durable identity and
- * should be resolved live. `name` is required so an empty object cannot validate
- * as a no-op. `.passthrough()` (not `.strict()`): external apps may emit fields a
- * newer schema will define, and dropping them on a round-trip would silently
- * lose data.
- */
-declare const agentRefSchema: z.ZodObject<{
-    name: z.ZodString;
-    did: z.ZodOptional<z.ZodString>;
-    entityRef: z.ZodOptional<z.ZodString>;
-}, z.core.$loose>;
-type AgentRef = z.infer<typeof agentRefSchema>;
-/**
- * Self-labels shape from `com.atproto.label.defs#selfLabels`. Modelled
- * permissively because clients rarely construct this directly; the AppView
- * handles label validation.
- */
-declare const selfLabelsSchema: z.ZodObject<{
-    $type: z.ZodOptional<z.ZodLiteral<"com.atproto.label.defs#selfLabels">>;
-    values: z.ZodArray<z.ZodObject<{
-        val: z.ZodString;
-    }, z.core.$strip>>;
-}, z.core.$strip>;
-
-export { type AgentRef as A, agentRefSchema as a, atUriSchema as b, cidSchema as c, datetimeSchema as d, didSchema as e, externalRecordRefSchema as f, skillRefSchema as g, strongRefSchema as h, languageTagSchema as l, maxGraphemes as m, partialDateSchema as p, selfLabelsSchema as s, uriSchema as u };