@immediately-run/preauth-core 0.1.3 → 0.1.5

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';
+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 interface CapabilityDef {
     kind: CapabilityKind;
     tier: CapabilityTier;
@@ -31,10 +31,11 @@ export interface CapabilityDef {
     maximallyExplicit?: boolean;
 }
 export declare const CAPABILITIES: Record<Capability, CapabilityDef>;
-/** The current registry/vocabulary version (§5.11). Bumped to 1.3.0 with the
- *  provider-agnostic `llm:chat` capability (the `llm.chat@1` slot), mirroring
- *  capabilities.json. (1.2.0 added the per-user settings-space capabilities.) */
-export declare const REGISTRY_VERSION = "1.3.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.) */
+export declare const REGISTRY_VERSION = "1.4.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

@@ -186,11 +186,19 @@ exports.CAPABILITIES = {
     // Elevated + app-scoped: a fork/previewed app EARNS it via lazy/manifest consent
     // (the fork-needs-more-caps story), recorded as a per-(user,appKey) §8.15 grant.
     'llm:chat': { kind: 'action', tier: 'elevated', since: '1.3.0', appScoped: true },
+    // Authoring services (CLIENT_SERVICES_SPEC §6, R3-107): typecheck/lint/format
+    // source via a kernel-owned same-origin worker (the in-browser coding agent's
+    // quality tools, LLM_AND_AGENTS §3.3). Baseline action — the worker only
+    // transforms data the app already holds and returns diagnostics, runs under host
+    // authority with nothing to confine (§3a), and is bounded per call (timeout +
+    // 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.3.0 with the
- *  provider-agnostic `llm:chat` capability (the `llm.chat@1` slot), mirroring
- *  capabilities.json. (1.2.0 added the per-user settings-space capabilities.) */
-exports.REGISTRY_VERSION = '1.3.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';
 /** 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.3",
+  "version": "0.1.5",
   "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": {