@immediately-run/preauth-core 0.1.10 → 0.1.12

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' | '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 type Capability = 'theme:read' | 'theme:set' | 'auth:status' | 'auth:identity' | 'route:read' | 'formFactor:read' | 'chrome: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' | 'analytics:emit';
 export interface CapabilityDef {
     kind: CapabilityKind;
     tier: CapabilityTier;
@@ -31,12 +31,13 @@ export interface CapabilityDef {
     maximallyExplicit?: boolean;
 }
 export declare const CAPABILITIES: Record<Capability, CapabilityDef>;
-/** 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";
+/** The current registry/vocabulary version (§5.11). Bumped to 1.7.0 with the baseline
+ *  state read `chrome:read` (PRESENT_MODE_CHROME_SPEC §6 — R3-191), mirroring
+ *  capabilities.json. (1.6.0 added the elevated, app-scoped, parameterized
+ *  `analytics:emit`; 1.5.0 added the first-party-only `mounts:registry`; 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.7.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

@@ -208,13 +208,48 @@ exports.CAPABILITIES = {
     // 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' },
+    // APP_ANALYTICS_SPEC §2 (R3-350): emit an app's OWN usage analytics through the
+    // platform's pipeline, against a vocabulary the app declares in its manifest.
+    //
+    // **ELEVATED + appScoped, and NOT baseline.** The earlier spec draft wrote
+    // "baseline, consented", which is not a tier and not a thing: `baseline` IS the
+    // floor — `buildConsent` short-circuits `tier === 'baseline'` before generating any
+    // consent line, and a previewed frame is seeded with the baseline set directly. At
+    // baseline this would hand EVERY app on the platform an unconsented, unrevocable,
+    // un-journalled egress capability. CAPABILITY_REFERENCE had already closed the
+    // question: "'App-scoped' is NOT a fourth tier. It is a consent-path annotation on
+    // the elevated tier."
+    //
+    // **Parameterized**, because the grant is not "may emit" but "may emit THIS
+    // vocabulary": §2.1 hashes the manifest-declared vocabulary into the grant, and a
+    // changed hash invalidates it. `appKey` carries no ref, so without that binding a
+    // publisher could observe their aggregates and then ship an alphabet tuned to encode
+    // what they now want to read, under a grant the user gave for a different one.
+    'analytics:emit': { kind: 'action', tier: 'elevated', since: '1.6.0', parameterized: true, appScoped: true },
+    // PRESENT_MODE_CHROME_SPEC §6 (R-PMC-17, R3-191): read the host's own present-mode
+    // chrome state — whether the platform menu/sheet is open over the app, and which
+    // edge the reveal tab sits on — so a platform-aware app MAY pause an animation
+    // while it is dimmed, or keep its corner clear of the tab.
+    //
+    // **BASELINE, alongside `formFactor:read`.** Both are reads of the HOST's own UI
+    // state, not of anything app-foreign: the app already knows it is being displayed,
+    // and "chrome is currently over you" discloses nothing about the user, other apps,
+    // the filesystem, or the network. There is no `chrome:set` counterpart — an app
+    // cannot operate platform chrome, only observe it, so this cannot become an
+    // authority-escalation path.
+    //
+    // R-PMC-18 is the reason it can be baseline without a consent line at all: no
+    // platform behavior may depend on an app consuming this channel, so an app that
+    // never reads it is indistinguishable from one that does.
+    'chrome:read': { kind: 'read', tier: 'baseline', since: '1.7.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';
+/** The current registry/vocabulary version (§5.11). Bumped to 1.7.0 with the baseline
+ *  state read `chrome:read` (PRESENT_MODE_CHROME_SPEC §6 — R3-191), mirroring
+ *  capabilities.json. (1.6.0 added the elevated, app-scoped, parameterized
+ *  `analytics:emit`; 1.5.0 added the first-party-only `mounts:registry`; 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.7.0';
 /** Is `cap` a known host-core capability? (Closed vocabulary — §5.12.) */
 function isKnownCapability(cap) {
     return Object.prototype.hasOwnProperty.call(exports.CAPABILITIES, cap);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@immediately-run/preauth-core",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "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": {