@immediately-run/preauth-core 0.1.4 → 0.1.6

package/dist/capabilities.d.ts

@@ -1,6 +1,6 @@
 export type CapabilityKind = 'read' | 'action';
 export type CapabilityTier = 'baseline' | 'elevated' | 'first-party-only';
-export type Capability = 'theme:read' | 'theme:set' | 'auth:status' | 'auth:identity' | 'route:read' | 'formFactor:read' | 'mounts:read' | 'spaces:app' | 'spaces:user' | 'spaces:admin' | 'settings:app' | 'settings:fork' | 'settings:all' | 'contribute:self' | 'contribute:any' | 'contribute:direct' | 'editor:read' | 'editor:open' | 'editor:write' | 'editor:document' | 'editor:requestEdit' | 'vcs:read' | 'vcs:reset' | 'dnd:source' | 'catalog:read' | 'commands:read' | 'commands:run' | 'ipc' | 'task:invoke' | 'net:fetch' | 'secrets:add' | 'secrets:list' | 'secrets:revoke' | 'agent:session' | 'diagnostics:read' | 'llm:chat' | 'authoring:run';
+export type Capability = 'theme:read' | 'theme:set' | 'auth:status' | 'auth:identity' | 'route:read' | 'formFactor:read' | 'mounts:read' | 'mounts:registry' | 'spaces:app' | 'spaces:user' | 'spaces:admin' | 'settings:app' | 'settings:fork' | 'settings:all' | 'contribute:self' | 'contribute:any' | 'contribute:direct' | 'editor:read' | 'editor:open' | 'editor:write' | 'editor:document' | 'editor:requestEdit' | 'vcs:read' | 'vcs:reset' | 'dnd:source' | 'catalog:read' | 'commands:read' | 'commands:run' | 'ipc' | 'task:invoke' | 'net:fetch' | 'secrets:add' | 'secrets:list' | 'secrets:revoke' | 'agent:session' | 'diagnostics:read' | 'llm:chat' | 'authoring:run';
 export interface CapabilityDef {
     kind: CapabilityKind;
     tier: CapabilityTier;
@@ -31,11 +31,12 @@ export interface CapabilityDef {
     maximallyExplicit?: boolean;
 }
 export declare const CAPABILITIES: Record<Capability, CapabilityDef>;
-/** The current registry/vocabulary version (§5.11). Bumped to 1.4.0 with the
- *  `authoring:run` capability (the kernel authoring services — CLIENT_SERVICES §6,
- *  R3-107), mirroring capabilities.json. (1.3.0 added the provider-agnostic
- *  `llm:chat` slot; 1.2.0 added the per-user settings-space capabilities.) */
-export declare const REGISTRY_VERSION = "1.4.0";
+/** The current registry/vocabulary version (§5.11). Bumped to 1.5.0 with the
+ *  first-party-only `mounts:registry` capability (the PRINCIPALS §9 B2 Session-lens
+ *  mount oracle — R3-95), mirroring capabilities.json. (1.4.0 added `authoring:run`;
+ *  1.3.0 added the provider-agnostic `llm:chat` slot; 1.2.0 added the per-user
+ *  settings-space capabilities.) */
+export declare const REGISTRY_VERSION = "1.5.0";
 /** Is `cap` a known host-core capability? (Closed vocabulary — §5.12.) */
 export declare function isKnownCapability(cap: string): cap is Capability;
 export declare function tierOf(cap: Capability): CapabilityTier;

package/dist/capabilities.js

@@ -25,6 +25,20 @@ exports.CAPABILITIES = {
     'route:read': { kind: 'read', tier: 'baseline', since: '1.0.0' },
     'formFactor:read': { kind: 'read', tier: 'baseline', since: '1.0.0' },
     'mounts:read': { kind: 'read', tier: 'baseline', since: '1.0.0' },
+    // Enumerate the session's mounts BEYOND the app's own — the Session-lens
+    // "App | Session" superset (PRINCIPALS_SPEC §9 B2 / §8.9.1 / D-PRIN-4). Where
+    // `mounts:read` is a per-app filter (own mounts only, baseline), this is the
+    // cross-scope registry oracle: it reveals mounts the previewed app was never
+    // granted (the editor/agent session's own), so it is an activity oracle exactly
+    // like `settings:all`. **Permanently first-party-only:** a URL-loaded/previewed
+    // fork of the File Explorer may hold the App lens (`mounts:read`) but NEVER the
+    // Session lens — `buildConsent` refuses a first-party-only cap to a non-first-
+    // party binding regardless of consent, `overridePolicy` strips it on a repoint
+    // (D-PRIN-4 rejected both a forkable Session lens and a separate "session lens"
+    // capability: this IS the settled `mounts:registry`, a view selector over the
+    // mount registry, not a new power). Read kind — it gates the first-party
+    // `session-mounts` push channel (§8.3 view() projection).
+    'mounts:registry': { kind: 'read', tier: 'first-party-only', since: '1.5.0' },
     'spaces:app': { kind: 'action', tier: 'baseline', since: '1.0.0', parameterized: true },
     'spaces:user': { kind: 'action', tier: 'elevated', since: '1.0.0' },
     'spaces:admin': { kind: 'action', tier: 'elevated', since: '1.0.0' },
@@ -194,11 +208,12 @@ exports.CAPABILITIES = {
     // input-size). Not app-scoped: it confers no authority over other apps/mounts.
     'authoring:run': { kind: 'action', tier: 'baseline', since: '1.4.0' },
 };
-/** The current registry/vocabulary version (§5.11). Bumped to 1.4.0 with the
- *  `authoring:run` capability (the kernel authoring services — CLIENT_SERVICES §6,
- *  R3-107), mirroring capabilities.json. (1.3.0 added the provider-agnostic
- *  `llm:chat` slot; 1.2.0 added the per-user settings-space capabilities.) */
-exports.REGISTRY_VERSION = '1.4.0';
+/** The current registry/vocabulary version (§5.11). Bumped to 1.5.0 with the
+ *  first-party-only `mounts:registry` capability (the PRINCIPALS §9 B2 Session-lens
+ *  mount oracle — R3-95), mirroring capabilities.json. (1.4.0 added `authoring:run`;
+ *  1.3.0 added the provider-agnostic `llm:chat` slot; 1.2.0 added the per-user
+ *  settings-space capabilities.) */
+exports.REGISTRY_VERSION = '1.5.0';
 /** Is `cap` a known host-core capability? (Closed vocabulary — §5.12.) */
 function isKnownCapability(cap) {
     return Object.prototype.hasOwnProperty.call(exports.CAPABILITIES, cap);

package/dist/docLayout.d.ts

@@ -23,10 +23,6 @@ export declare const GRANT_EXPIRY_MS: number;
  *  RENAME-1). The stored Firestore path segment is a doc-ID, not a field literally
  *  named `principal`, so this rename is code-symbol-only — no data migration. */
 export declare const granteeId: (uid: string) => string;
-/** @deprecated use {@link granteeId}. Kept as an alias for the `userPrincipal →
- *  granteeId` migration (the SDK + site-main + backend RENAME-1 track); removed once
- *  consumers migrate. */
-export declare const userPrincipal: (uid: string) => string;
 /** Drop undefined values — Firestore rejects them. The two adapters historically
  *  each had their own copy of this; sharing it keeps the "omit absent optionals"
  *  rule identical on both sides. */

package/dist/docLayout.js

@@ -16,7 +16,7 @@
 // `.set()`/`.update()` is the only thing each adapter does itself. Drift is then
 // impossible without editing a helper both consume.
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.netFetchGrantFields = exports.mergeNetFetchHosts = exports.appSpaceGrantFields = exports.appKeyTouchFields = exports.appCountFields = exports.userCountFields = exports.ownerUserSpaceFields = exports.ownerMemberFields = exports.spaceDocFields = exports.appCountPath = exports.userCountPath = exports.appSpacePath = exports.appKeyPath = exports.userSpacePath = exports.memberPath = exports.spacePath = exports.defined = exports.userPrincipal = exports.granteeId = exports.GRANT_EXPIRY_MS = exports.grantKey = void 0;
+exports.netFetchGrantFields = exports.mergeNetFetchHosts = exports.appSpaceGrantFields = exports.appKeyTouchFields = exports.appCountFields = exports.userCountFields = exports.ownerUserSpaceFields = exports.ownerMemberFields = exports.spaceDocFields = exports.appCountPath = exports.userCountPath = exports.appSpacePath = exports.appKeyPath = exports.userSpacePath = exports.memberPath = exports.spacePath = exports.defined = exports.granteeId = exports.GRANT_EXPIRY_MS = exports.grantKey = void 0;
 /** Stable per-user identifier for a grant `(appKey, spaceId)`, used as the value
  *  of a delegated grant's `parentGrantId`. `::` is delimiter-safe: `appKey` uses
  *  `__` separators and a Firestore `spaceId` is alphanumeric. */
@@ -33,10 +33,6 @@ exports.GRANT_EXPIRY_MS = 90 * 24 * 60 * 60 * 1000;
  *  named `principal`, so this rename is code-symbol-only — no data migration. */
 const granteeId = (uid) => `user:${uid}`;
 exports.granteeId = granteeId;
-/** @deprecated use {@link granteeId}. Kept as an alias for the `userPrincipal →
- *  granteeId` migration (the SDK + site-main + backend RENAME-1 track); removed once
- *  consumers migrate. */
-exports.userPrincipal = exports.granteeId;
 /** Drop undefined values — Firestore rejects them. The two adapters historically
  *  each had their own copy of this; sharing it keeps the "omit absent optionals"
  *  rule identical on both sides. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@immediately-run/preauth-core",
-  "version": "0.1.4",
+  "version": "0.1.6",
   "description": "The shared §8.9 pre-auth target check + the single grant-mint path (mintConsentedGrants) + the capability vocabulary + the byte-faithful grant/space/net-fetch document layout. Consumed by site-main (browser Firestore) and the backend (admin Firestore) so there is ONE gate, ONE mint path, ONE wire layout.",
   "license": "UNLICENSED",
   "repository": {