@kya-os/consent 0.1.44 → 0.1.47

package/dist/mcp-app/inline.js.map

@@ -1 +1 @@
-{"version":3,"file":"inline.js","sourceRoot":"","sources":["../../src/mcp-app/inline.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,sEAAsE;AACtE,MAAM,CAAC,MAAM,oBAAoB,GAAW,ws/uBAAws/uB,CAAC;AAErv/uB,4CAA4C;AAC5C,MAAM,CAAC,MAAM,yBAAyB,GAAW,MAAM,CAAC"}
+{"version":3,"file":"inline.js","sourceRoot":"","sources":["../../src/mcp-app/inline.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,sEAAsE;AACtE,MAAM,CAAC,MAAM,oBAAoB,GAAW,m1mvBAAm1mvB,CAAC;AAEh4mvB,4CAA4C;AAC5C,MAAM,CAAC,MAAM,yBAAyB,GAAW,MAAM,CAAC"}

package/dist/resolution/credential-capabilities.d.ts

@@ -0,0 +1,38 @@
+import { type AuthMode } from "../types/modes.types.js";
+import type { Capability } from "../types/capabilities.types.js";
+export declare function shouldRenderCapabilityScreen(mode: AuthMode, capabilityCount: number): boolean;
+/**
+ * The credential path grants a fixed, all-or-nothing scope set (see the
+ * scopes constraint in handleApprove), so every capability starts selected —
+ * the rows themselves stay interactive, same as the consent-only path.
+ */
+export declare function shouldSelectAllCapabilities(mode: AuthMode): boolean;
+export declare function areCredentialsComplete(formData: Record<string, string>): boolean;
+/**
+ * Whether the legacy scope-selection checkboxes (`renderPermissions` /
+ * `<consent-permissions>`) should render as interactive. When a signed
+ * identity assertion is bound to the request, `handleApprove` always posts
+ * the full requested scope set - the assertion binds a hash of that full
+ * set, so a user-narrowed subset would fail the mint gate's hash check and
+ * 403 (see the comment on the `scopes` form-data append in mcp-consent.ts).
+ * Letting the user uncheck a scope that will be granted regardless is a
+ * consent-accuracy bug, so this path drops to display-only rows instead.
+ * Interactive narrowing returns once the deferred subset-binding follow-up
+ * ships.
+ */
+export declare function shouldRenderScopesInteractive(identityAssertion: string | undefined): boolean;
+/**
+ * Which capabilities count as selected. In disclosure mode every capability is
+ * granted, so all ids are returned; otherwise the operator's `defaultOn` seeds
+ * the initial selection.
+ */
+export declare function capabilityIdsFor(capabilities: Capability[], disclosureMode: boolean): string[];
+/**
+ * Identity of a seeding decision: the capability ids in order, plus the
+ * all-selected flag. Lit compares properties by reference, so a parent that
+ * rebuilds its capability array on every render would otherwise re-seed (and
+ * wipe the user's toggles) on every keystroke. Seeding is keyed on this value
+ * instead of array identity.
+ */
+export declare function capabilitySeedKey(capabilities: Capability[], allSelected: boolean): string;
+//# sourceMappingURL=credential-capabilities.d.ts.map

package/dist/resolution/credential-capabilities.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"credential-capabilities.d.ts","sourceRoot":"","sources":["../../src/resolution/credential-capabilities.ts"],"names":[],"mappings":"AAAA,OAAO,EAAc,KAAK,QAAQ,EAAE,MAAM,yBAAyB,CAAC;AACpE,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,gCAAgC,CAAC;AAYjE,wBAAgB,4BAA4B,CAC1C,IAAI,EAAE,QAAQ,EACd,eAAe,EAAE,MAAM,GACtB,OAAO,CAET;AAED;;;;GAIG;AACH,wBAAgB,2BAA2B,CAAC,IAAI,EAAE,QAAQ,GAAG,OAAO,CAEnE;AAED,wBAAgB,sBAAsB,CACpC,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAC/B,OAAO,CAKT;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,6BAA6B,CAC3C,iBAAiB,EAAE,MAAM,GAAG,SAAS,GACpC,OAAO,CAET;AAED;;;;GAIG;AACH,wBAAgB,gBAAgB,CAC9B,YAAY,EAAE,UAAU,EAAE,EAC1B,cAAc,EAAE,OAAO,GACtB,MAAM,EAAE,CAIV;AAED;;;;;;GAMG;AACH,wBAAgB,iBAAiB,CAC/B,YAAY,EAAE,UAAU,EAAE,EAC1B,WAAW,EAAE,OAAO,GACnB,MAAM,CAER"}

package/dist/resolution/credential-capabilities.js

@@ -0,0 +1,61 @@
+import { AUTH_MODES } from "../types/modes.types.js";
+/**
+ * Modes whose screen is replaced by the humanized capability layout. Credentials
+ * is included so the user sees what is being granted before signing in — on the
+ * anchor path the sign-in submit IS the approval, so there is no later screen.
+ */
+const CAPABILITY_SCREEN_MODES = [
+    AUTH_MODES.CONSENT_ONLY,
+    AUTH_MODES.CREDENTIALS,
+];
+export function shouldRenderCapabilityScreen(mode, capabilityCount) {
+    return capabilityCount > 0 && CAPABILITY_SCREEN_MODES.includes(mode);
+}
+/**
+ * The credential path grants a fixed, all-or-nothing scope set (see the
+ * scopes constraint in handleApprove), so every capability starts selected —
+ * the rows themselves stay interactive, same as the consent-only path.
+ */
+export function shouldSelectAllCapabilities(mode) {
+    return mode === AUTH_MODES.CREDENTIALS;
+}
+export function areCredentialsComplete(formData) {
+    return ((formData.username?.trim().length ?? 0) > 0 &&
+        (formData.password?.trim().length ?? 0) > 0);
+}
+/**
+ * Whether the legacy scope-selection checkboxes (`renderPermissions` /
+ * `<consent-permissions>`) should render as interactive. When a signed
+ * identity assertion is bound to the request, `handleApprove` always posts
+ * the full requested scope set - the assertion binds a hash of that full
+ * set, so a user-narrowed subset would fail the mint gate's hash check and
+ * 403 (see the comment on the `scopes` form-data append in mcp-consent.ts).
+ * Letting the user uncheck a scope that will be granted regardless is a
+ * consent-accuracy bug, so this path drops to display-only rows instead.
+ * Interactive narrowing returns once the deferred subset-binding follow-up
+ * ships.
+ */
+export function shouldRenderScopesInteractive(identityAssertion) {
+    return !identityAssertion;
+}
+/**
+ * Which capabilities count as selected. In disclosure mode every capability is
+ * granted, so all ids are returned; otherwise the operator's `defaultOn` seeds
+ * the initial selection.
+ */
+export function capabilityIdsFor(capabilities, disclosureMode) {
+    return capabilities
+        .filter((capability) => disclosureMode || capability.defaultOn)
+        .map((capability) => capability.id);
+}
+/**
+ * Identity of a seeding decision: the capability ids in order, plus the
+ * all-selected flag. Lit compares properties by reference, so a parent that
+ * rebuilds its capability array on every render would otherwise re-seed (and
+ * wipe the user's toggles) on every keystroke. Seeding is keyed on this value
+ * instead of array identity.
+ */
+export function capabilitySeedKey(capabilities, allSelected) {
+    return `${allSelected ? 1 : 0}:${capabilities.map((c) => c.id).join(" ")}`;
+}
+//# sourceMappingURL=credential-capabilities.js.map

package/dist/resolution/credential-capabilities.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"credential-capabilities.js","sourceRoot":"","sources":["../../src/resolution/credential-capabilities.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAiB,MAAM,yBAAyB,CAAC;AAGpE;;;;GAIG;AACH,MAAM,uBAAuB,GAAwB;IACnD,UAAU,CAAC,YAAY;IACvB,UAAU,CAAC,WAAW;CACvB,CAAC;AAEF,MAAM,UAAU,4BAA4B,CAC1C,IAAc,EACd,eAAuB;IAEvB,OAAO,eAAe,GAAG,CAAC,IAAI,uBAAuB,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC;AACvE,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,2BAA2B,CAAC,IAAc;IACxD,OAAO,IAAI,KAAK,UAAU,CAAC,WAAW,CAAC;AACzC,CAAC;AAED,MAAM,UAAU,sBAAsB,CACpC,QAAgC;IAEhC,OAAO,CACL,CAAC,QAAQ,CAAC,QAAQ,EAAE,IAAI,EAAE,CAAC,MAAM,IAAI,CAAC,CAAC,GAAG,CAAC;QAC3C,CAAC,QAAQ,CAAC,QAAQ,EAAE,IAAI,EAAE,CAAC,MAAM,IAAI,CAAC,CAAC,GAAG,CAAC,CAC5C,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,6BAA6B,CAC3C,iBAAqC;IAErC,OAAO,CAAC,iBAAiB,CAAC;AAC5B,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,gBAAgB,CAC9B,YAA0B,EAC1B,cAAuB;IAEvB,OAAO,YAAY;SAChB,MAAM,CAAC,CAAC,UAAU,EAAE,EAAE,CAAC,cAAc,IAAI,UAAU,CAAC,SAAS,CAAC;SAC9D,GAAG,CAAC,CAAC,UAAU,EAAE,EAAE,CAAC,UAAU,CAAC,EAAE,CAAC,CAAC;AACxC,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,iBAAiB,CAC/B,YAA0B,EAC1B,WAAoB;IAEpB,OAAO,GAAG,WAAW,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,YAAY,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC;AAC7E,CAAC"}

package/dist/security/identity-assertion.d.ts

@@ -0,0 +1,49 @@
+/**
+ * Identity Assertion Fragment Parsing
+ *
+ * Part of the consent-approve auth-gate fix
+ * (docs/superpowers/specs/2026-07-29-consent-approve-auth-gate-design.md §3.1).
+ * After credential/OAuth sign-in, the worker mints a grant-bound signed
+ * identity assertion and redirects the browser to the clickwrap consent
+ * screen carrying it in the URL **fragment**
+ * (`.../consent#identity_assertion=<token>`) rather than a query param.
+ * Fragments are never sent to the server — not in access logs, not in
+ * `Referer` — so this is the only way the assertion can be delivered without
+ * leaking it. That also means the server-rendered shell can never see it to
+ * pass it down as an attribute; the component must read `location.hash`
+ * itself once mounted in the browser.
+ *
+ * This module holds the pure parsing logic so it can be unit-tested in this
+ * package's node-environment vitest suite, which has no DOM and cannot mount
+ * the Lit component to exercise `location.hash` directly.
+ *
+ * @module @kya-os/consent/security/identity-assertion
+ */
+/**
+ * Parse the `identity_assertion` value out of a URL fragment.
+ *
+ * Accepts a raw `location.hash`-shaped string, with or without its leading
+ * `#`. Returns `undefined` when the key is absent, the value is empty, or
+ * the fragment is empty/nullish. Never throws.
+ *
+ * @param hash - The fragment string, e.g. `location.hash`
+ *   (`"#identity_assertion=abc"`)
+ * @returns The decoded assertion token, or `undefined` if not present
+ *
+ * @example
+ * ```typescript
+ * parseIdentityAssertionFromHash('#identity_assertion=abc123')
+ * // => 'abc123'
+ *
+ * parseIdentityAssertionFromHash('#a=1&identity_assertion=abc&b=2')
+ * // => 'abc'
+ *
+ * parseIdentityAssertionFromHash('#a=1&b=2')
+ * // => undefined
+ *
+ * parseIdentityAssertionFromHash('')
+ * // => undefined
+ * ```
+ */
+export declare function parseIdentityAssertionFromHash(hash: string | undefined | null): string | undefined;
+//# sourceMappingURL=identity-assertion.d.ts.map

package/dist/security/identity-assertion.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"identity-assertion.d.ts","sourceRoot":"","sources":["../../src/security/identity-assertion.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,8BAA8B,CAC5C,IAAI,EAAE,MAAM,GAAG,SAAS,GAAG,IAAI,GAC9B,MAAM,GAAG,SAAS,CAgBpB"}

package/dist/security/identity-assertion.js

@@ -0,0 +1,66 @@
+/**
+ * Identity Assertion Fragment Parsing
+ *
+ * Part of the consent-approve auth-gate fix
+ * (docs/superpowers/specs/2026-07-29-consent-approve-auth-gate-design.md §3.1).
+ * After credential/OAuth sign-in, the worker mints a grant-bound signed
+ * identity assertion and redirects the browser to the clickwrap consent
+ * screen carrying it in the URL **fragment**
+ * (`.../consent#identity_assertion=<token>`) rather than a query param.
+ * Fragments are never sent to the server — not in access logs, not in
+ * `Referer` — so this is the only way the assertion can be delivered without
+ * leaking it. That also means the server-rendered shell can never see it to
+ * pass it down as an attribute; the component must read `location.hash`
+ * itself once mounted in the browser.
+ *
+ * This module holds the pure parsing logic so it can be unit-tested in this
+ * package's node-environment vitest suite, which has no DOM and cannot mount
+ * the Lit component to exercise `location.hash` directly.
+ *
+ * @module @kya-os/consent/security/identity-assertion
+ */
+/**
+ * Parse the `identity_assertion` value out of a URL fragment.
+ *
+ * Accepts a raw `location.hash`-shaped string, with or without its leading
+ * `#`. Returns `undefined` when the key is absent, the value is empty, or
+ * the fragment is empty/nullish. Never throws.
+ *
+ * @param hash - The fragment string, e.g. `location.hash`
+ *   (`"#identity_assertion=abc"`)
+ * @returns The decoded assertion token, or `undefined` if not present
+ *
+ * @example
+ * ```typescript
+ * parseIdentityAssertionFromHash('#identity_assertion=abc123')
+ * // => 'abc123'
+ *
+ * parseIdentityAssertionFromHash('#a=1&identity_assertion=abc&b=2')
+ * // => 'abc'
+ *
+ * parseIdentityAssertionFromHash('#a=1&b=2')
+ * // => undefined
+ *
+ * parseIdentityAssertionFromHash('')
+ * // => undefined
+ * ```
+ */
+export function parseIdentityAssertionFromHash(hash) {
+    if (!hash)
+        return undefined;
+    const withoutLeadingHash = hash.startsWith("#") ? hash.slice(1) : hash;
+    if (!withoutLeadingHash)
+        return undefined;
+    try {
+        const params = new URLSearchParams(withoutLeadingHash);
+        const value = params.get("identity_assertion");
+        return value ? value : undefined;
+    }
+    catch {
+        // URLSearchParams is very lenient and does not throw in practice, but
+        // guard anyway - a parsing failure here must never crash the consent
+        // screen, it should just mean "no assertion found".
+        return undefined;
+    }
+}
+//# sourceMappingURL=identity-assertion.js.map

package/dist/security/identity-assertion.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"identity-assertion.js","sourceRoot":"","sources":["../../src/security/identity-assertion.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,MAAM,UAAU,8BAA8B,CAC5C,IAA+B;IAE/B,IAAI,CAAC,IAAI;QAAE,OAAO,SAAS,CAAC;IAE5B,MAAM,kBAAkB,GAAG,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;IACvE,IAAI,CAAC,kBAAkB;QAAE,OAAO,SAAS,CAAC;IAE1C,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,IAAI,eAAe,CAAC,kBAAkB,CAAC,CAAC;QACvD,MAAM,KAAK,GAAG,MAAM,CAAC,GAAG,CAAC,oBAAoB,CAAC,CAAC;QAC/C,OAAO,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,SAAS,CAAC;IACnC,CAAC;IAAC,MAAM,CAAC;QACP,sEAAsE;QACtE,qEAAqE;QACrE,oDAAoD;QACpD,OAAO,SAAS,CAAC;IACnB,CAAC;AACH,CAAC"}

package/dist/security/index.d.ts

@@ -7,4 +7,5 @@
  */
 export * from "./escape.js";
 export * from "./validators.js";
+export * from "./identity-assertion.js";
 //# sourceMappingURL=index.d.ts.map

package/dist/security/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/security/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,cAAc,aAAa,CAAC;AAC5B,cAAc,iBAAiB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/security/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,cAAc,aAAa,CAAC;AAC5B,cAAc,iBAAiB,CAAC;AAChC,cAAc,yBAAyB,CAAC"}

package/dist/security/index.js

@@ -7,4 +7,5 @@
  */
 export * from "./escape.js";
 export * from "./validators.js";
+export * from "./identity-assertion.js";
 //# sourceMappingURL=index.js.map

package/dist/security/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/security/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,cAAc,aAAa,CAAC;AAC5B,cAAc,iBAAiB,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/security/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,cAAc,aAAa,CAAC;AAC5B,cAAc,iBAAiB,CAAC;AAChC,cAAc,yBAAyB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kya-os/consent",
-  "version": "0.1.44",
+  "version": "0.1.47",
   "description": "Canonical consent page types, styles, and utilities for MCP-I and AgentShield",
   "type": "module",
   "main": "dist/index.js",