kavachos 0.0.2 → 0.0.4

package/dist/types-_7hIICee.d.ts

@@ -1,52 +0,0 @@
-/**
- * Core types for the human auth adapter system.
- */
-/**
- * A resolved human user identity.  All fields except `id` are optional
- * because different providers expose different levels of profile data.
- */
-interface ResolvedUser {
-    /** Stable user ID (from the auth provider). */
-    id: string;
-    email?: string;
-    name?: string;
-    image?: string;
-    /** Any additional claims / metadata from the auth provider. */
-    metadata?: Record<string, unknown>;
-}
-/**
- * Plug KavachOS into an existing auth system by implementing this interface.
- *
- * Only `resolveUser` is required – it is called for every inbound request that
- * needs a human identity.  The optional helpers (`getUser`, `syncUser`) are
- * called by higher-level KavachOS flows when they need to fetch or persist user
- * data.
- */
-interface AuthAdapter {
-    /**
-     * Resolve a human user from an incoming HTTP `Request`.
-     *
-     * Inspect cookies, session tokens, `Authorization` headers, etc. and return
-     * the matching `ResolvedUser`.  Return `null` when the request carries no
-     * recognisable credential.
-     */
-    resolveUser(request: Request): Promise<ResolvedUser | null>;
-    /**
-     * Fetch a user by their ID from the auth provider.
-     *
-     * Used when KavachOS needs to verify that a user still exists (e.g. before
-     * creating an agent on their behalf).  Return `null` when the user is not
-     * found or has been deleted.
-     */
-    getUser?(userId: string): Promise<ResolvedUser | null>;
-    /**
-     * Persist / update user data from the auth provider into the KavachOS
-     * `kavach_users` table.
-     *
-     * Called after a successful `resolveUser` when user data should be kept in
-     * sync with an external provider.
-     */
-    syncUser?(user: ResolvedUser): Promise<void>;
-}
-
-export type { AuthAdapter as A, ResolvedUser as R };