@ascendenceai/cortena-extensions-e2e-kit 0.1.0

package/dist/locators.d.ts

@@ -0,0 +1,210 @@
+/**
+ * Every selector the kit uses, in one file.
+ *
+ * This is the seam the whole package exists for. Six extensions writing their
+ * own layer-3 suites means six copies of "how do I find the sidebar", and the
+ * copies drift on the one layer that is supposed to prove the fleet looks the
+ * same. Here the shell is found once; a renamed `data-slot` in cortena-ui
+ * breaks every adopter's suite in this file rather than in six of them.
+ *
+ * ## Why `data-slot` and not a role or a test id
+ *
+ * `data-slot` is cortena-ui's own attribute, written by the component for its
+ * own styling. It is therefore load-bearing: it cannot be deleted as "test
+ * scaffolding" by somebody who does not run the suite, which is exactly what
+ * happens to a `data-testid` that only a Playwright file reads. Roles and
+ * accessible names are used where the component's contract IS the role — the
+ * avatar menu's items, the agent composer — because those are what a person
+ * uses and what a screen reader announces.
+ *
+ * ## DESIGN-119
+ *
+ * DESIGN-119 changes how sign-in and the signed-out state are mounted: today
+ * an extension may draw its own login form (Tasks does, with an organisation
+ * step cortena-ui's `LoginScreen` has no equivalent of), and afterwards the
+ * frame composition mounts the shared screen. Everything under `signIn` below
+ * is therefore written twice — the shared `data-slot`s first, the extension's
+ * own form as the fallback — and `SIGN_IN` is the only export that moves when
+ * DESIGN-119 lands. Nothing outside this file names a sign-in element.
+ */
+/** The cortena-ui version these selectors were read out of. */
+export declare const CORTENA_UI = "1.13.0";
+/**
+ * `AppShell` — cortena-ui/src/components/app-shell.tsx.
+ *
+ * `NAV_DRAWER_ID` is exported by the package as `cortena-nav-drawer` and
+ * `HELP_PANEL_ID` as `cortena-help-panel`; both are written here as the ids
+ * they are, because a Playwright file cannot import a React module.
+ */
+export declare const SHELL: {
+    readonly root: string;
+    readonly header: string;
+    readonly brand: string;
+    readonly brandSquare: string;
+    /**
+     * The registered mark. `data-mark` carries the mark's id, or the literal
+     * `fallback` when nothing is registered for the extension — which renders an
+     * initial rather than an empty box, and is worth failing on.
+     */
+    readonly brandMark: string;
+    readonly markAttribute: "data-mark";
+    readonly brandName: string;
+    readonly navToggle: string;
+    readonly nav: string;
+    readonly navList: string;
+    readonly navItem: string;
+    /** One row by the id the extension gave it: `[data-nav-item="my-tasks"]`. */
+    readonly navItemById: (id: string) => string;
+    /** The row a screen reader hears as the current page, not the one that merely looks lit. */
+    readonly navItemCurrent: "[data-slot=\"app-shell-nav-item\"][aria-current=\"page\"]";
+    readonly navGroupLabel: string;
+    readonly navDrawer: "#cortena-nav-drawer";
+    readonly navDrawerClose: string;
+    readonly navScrim: string;
+    readonly main: string;
+    readonly avatarTrigger: string;
+    /** The avatar menu's rows carry `data-item`: profile, settings, logout, and the extension's own. */
+    readonly menuItem: (id: string) => string;
+    /** `BottomRightCluster` — theme, help, and the agent pill stacked above them. */
+    readonly cluster: string;
+    readonly clusterRow: string;
+    readonly clusterAgent: string;
+    readonly themeToggle: string;
+    readonly helpButton: string;
+    /**
+     * The shell's own help region — `<aside id="cortena-help-panel">`. Not
+     * `[data-slot="help-panel"]`: that is cortena-ui's markdown `HelpPanel`, and
+     * an extension whose functional document is HTML renders a frame inside this
+     * aside instead (Tasks does). The aside is the part every adopter has.
+     */
+    readonly helpPanel: string;
+    readonly helpPanelById: "#cortena-help-panel";
+};
+/**
+ * `AgentChatPopup` and `AgentChat` — cortena-ui/src/components/agent-chat-popup.tsx
+ * and agent-chat.tsx, reached through the `cortena-ui/agent-chat` entry.
+ */
+export declare const AGENT: {
+    readonly pill: string;
+    readonly pillUnread: string;
+    readonly panel: string;
+    readonly collapse: string;
+    readonly expand: string;
+    readonly chat: string;
+    readonly scroll: string;
+    readonly input: string;
+    readonly send: string;
+    readonly stop: string;
+    readonly turn: string;
+    readonly message: string;
+    readonly userMessage: "[data-slot=\"agent-chat-message\"][data-role=\"user\"]";
+    readonly assistantMessage: "[data-slot=\"agent-chat-message\"][data-role=\"assistant\"]";
+    readonly errorMessage: "[data-slot=\"agent-chat-message\"][data-role=\"error\"]";
+    readonly streaming: string;
+    readonly streamingText: string;
+    /** The A2UI block the protocol requires the pop-up to be able to draw (§19, P-25). */
+    readonly a2ui: string;
+    readonly toolCard: string;
+    readonly newSession: string;
+    readonly sessionsTrigger: string;
+    readonly session: string;
+    readonly empty: string;
+};
+/**
+ * `SessionGuard`'s expiry dialog — §10.4, rule P-37. The kit does not drive
+ * session expiry (it needs the idle policy shortened, which is an extension's
+ * own switch), but `signIn` has to be able to tell "signed out" from "broken".
+ */
+export declare const SESSION: {
+    readonly dialog: string;
+    readonly countdown: string;
+    readonly continue: string;
+    readonly logout: string;
+};
+/**
+ * Sign-in. **This is the block DESIGN-119 moves.**
+ *
+ * `shared` is cortena-ui's `AuthScreen`/`LoginScreen` composition, which is
+ * what an extension will mount once DESIGN-119 lands. `own` is the form an
+ * extension draws itself today — labelled controls and a submit button, which
+ * is all that can be assumed of a form nobody shared. `signIn()` prefers the
+ * shared slots and falls back to the labels, so an extension that has already
+ * adopted the shared screen and one that has not both sign in through the same
+ * call, and the fallback deletes itself when the last extension migrates.
+ */
+export declare const SIGN_IN: {
+    readonly shared: {
+        readonly screen: string;
+        readonly card: string;
+        readonly title: string;
+        readonly brandName: string;
+        readonly form: string;
+        readonly submit: string;
+        readonly error: string;
+        /** The "You were signed out" notice §10.4.1 asks for. */
+        readonly signedOut: string;
+        readonly returnTo: string;
+        readonly providers: string;
+    };
+    /**
+     * The extension's own form, by accessible name. Deliberately not a
+     * `data-slot`: an extension's own markup has none to promise.
+     */
+    readonly own: {
+        readonly orgLabel: RegExp;
+        readonly orgSubmit: RegExp;
+        readonly emailLabel: RegExp;
+        readonly passwordLabel: RegExp;
+        readonly submit: RegExp;
+    };
+};
+/**
+ * The MCP consent page — the one screen in the six that no extension renders.
+ * It is cortena-auth's hosted page, so there is no cortena-ui slot to key on
+ * and no version of this repository can promise one. It is located by what a
+ * consent page *is*: a form naming the client, listing the scopes, with an
+ * allow and a deny. `ConsentScreen`'s slots are tried first for the day
+ * cortena-auth adopts it.
+ */
+export declare const CONSENT: {
+    readonly screen: string;
+    readonly scopes: string;
+    readonly scope: string;
+    readonly actions: string;
+    /** The form-shaped fallback, which is what is actually there today. */
+    readonly byForm: {
+        readonly allow: RegExp;
+        readonly deny: RegExp;
+        /** cortena-auth's own list of what is being asked for. */
+        readonly scopeList: ".scope-list";
+        /** The organisation picker, when the user is a member of more than one. */
+        readonly orgPick: ".org-pick";
+    };
+    /**
+     * cortena-auth's own sign-in, which the authorisation request lands on
+     * before it will show a consent page — and which asks for the organisation
+     * first, exactly as an extension's own login does.
+     */
+    readonly signIn: {
+        readonly org: RegExp;
+        readonly orgSubmit: RegExp;
+        readonly email: RegExp;
+        readonly password: RegExp;
+        readonly submit: RegExp;
+    };
+};
+/**
+ * The theme contract, from cortena-ui's `useCortenaTheme`.
+ *
+ * cortena-design drives dark mode off `data-theme` on `<html>` and falls back
+ * to `prefers-color-scheme` when the attribute is absent — so "the OS path" is
+ * literally the absence of the attribute, and a suite that only ever writes it
+ * never tests the fallback the majority of first visits take.
+ */
+export declare const THEME: {
+    readonly attribute: "data-theme";
+    readonly storageKey: "cortena.theme";
+    /** The toggle publishes both the stored choice and what is painted. */
+    readonly choiceAttribute: "data-theme-choice";
+    readonly resolvedAttribute: "data-theme-resolved";
+};

package/dist/locators.js

@@ -0,0 +1,212 @@
+/**
+ * Every selector the kit uses, in one file.
+ *
+ * This is the seam the whole package exists for. Six extensions writing their
+ * own layer-3 suites means six copies of "how do I find the sidebar", and the
+ * copies drift on the one layer that is supposed to prove the fleet looks the
+ * same. Here the shell is found once; a renamed `data-slot` in cortena-ui
+ * breaks every adopter's suite in this file rather than in six of them.
+ *
+ * ## Why `data-slot` and not a role or a test id
+ *
+ * `data-slot` is cortena-ui's own attribute, written by the component for its
+ * own styling. It is therefore load-bearing: it cannot be deleted as "test
+ * scaffolding" by somebody who does not run the suite, which is exactly what
+ * happens to a `data-testid` that only a Playwright file reads. Roles and
+ * accessible names are used where the component's contract IS the role — the
+ * avatar menu's items, the agent composer — because those are what a person
+ * uses and what a screen reader announces.
+ *
+ * ## DESIGN-119
+ *
+ * DESIGN-119 changes how sign-in and the signed-out state are mounted: today
+ * an extension may draw its own login form (Tasks does, with an organisation
+ * step cortena-ui's `LoginScreen` has no equivalent of), and afterwards the
+ * frame composition mounts the shared screen. Everything under `signIn` below
+ * is therefore written twice — the shared `data-slot`s first, the extension's
+ * own form as the fallback — and `SIGN_IN` is the only export that moves when
+ * DESIGN-119 lands. Nothing outside this file names a sign-in element.
+ */
+/** The cortena-ui version these selectors were read out of. */
+export const CORTENA_UI = '1.13.0';
+const slot = (name) => `[data-slot="${name}"]`;
+/**
+ * `AppShell` — cortena-ui/src/components/app-shell.tsx.
+ *
+ * `NAV_DRAWER_ID` is exported by the package as `cortena-nav-drawer` and
+ * `HELP_PANEL_ID` as `cortena-help-panel`; both are written here as the ids
+ * they are, because a Playwright file cannot import a React module.
+ */
+export const SHELL = {
+    root: slot('app-shell'),
+    header: slot('app-shell-header'),
+    brand: slot('app-shell-brand'),
+    brandSquare: slot('app-shell-brand-square'),
+    /**
+     * The registered mark. `data-mark` carries the mark's id, or the literal
+     * `fallback` when nothing is registered for the extension — which renders an
+     * initial rather than an empty box, and is worth failing on.
+     */
+    brandMark: slot('brand-mark'),
+    markAttribute: 'data-mark',
+    brandName: slot('app-shell-brand-name'),
+    navToggle: slot('app-shell-nav-toggle'),
+    nav: slot('app-shell-nav'),
+    navList: slot('app-shell-nav-list'),
+    navItem: slot('app-shell-nav-item'),
+    /** One row by the id the extension gave it: `[data-nav-item="my-tasks"]`. */
+    navItemById: (id) => `[data-nav-item="${id}"]`,
+    /** The row a screen reader hears as the current page, not the one that merely looks lit. */
+    navItemCurrent: '[data-slot="app-shell-nav-item"][aria-current="page"]',
+    navGroupLabel: slot('app-shell-nav-group-label'),
+    navDrawer: '#cortena-nav-drawer',
+    navDrawerClose: slot('app-shell-nav-drawer-close'),
+    navScrim: slot('app-shell-nav-scrim'),
+    main: slot('app-shell-main'),
+    avatarTrigger: slot('app-shell-avatar-trigger'),
+    /** The avatar menu's rows carry `data-item`: profile, settings, logout, and the extension's own. */
+    menuItem: (id) => `[data-item="${id}"]`,
+    /** `BottomRightCluster` — theme, help, and the agent pill stacked above them. */
+    cluster: slot('bottom-right-cluster'),
+    clusterRow: slot('bottom-right-cluster-row'),
+    clusterAgent: slot('bottom-right-cluster-agent'),
+    themeToggle: slot('theme-toggle'),
+    helpButton: slot('help-button'),
+    /**
+     * The shell's own help region — `<aside id="cortena-help-panel">`. Not
+     * `[data-slot="help-panel"]`: that is cortena-ui's markdown `HelpPanel`, and
+     * an extension whose functional document is HTML renders a frame inside this
+     * aside instead (Tasks does). The aside is the part every adopter has.
+     */
+    helpPanel: slot('app-shell-help-panel'),
+    helpPanelById: '#cortena-help-panel',
+};
+/**
+ * `AgentChatPopup` and `AgentChat` — cortena-ui/src/components/agent-chat-popup.tsx
+ * and agent-chat.tsx, reached through the `cortena-ui/agent-chat` entry.
+ */
+export const AGENT = {
+    pill: slot('agent-chat-pill'),
+    pillUnread: slot('agent-chat-pill-unread'),
+    panel: slot('agent-chat-panel'),
+    collapse: slot('agent-chat-collapse'),
+    expand: slot('agent-chat-expand'),
+    chat: slot('agent-chat'),
+    scroll: slot('agent-chat-scroll'),
+    input: slot('agent-chat-input'),
+    send: slot('agent-chat-send'),
+    stop: slot('agent-chat-stop'),
+    turn: slot('agent-chat-turn'),
+    message: slot('agent-chat-message'),
+    userMessage: '[data-slot="agent-chat-message"][data-role="user"]',
+    assistantMessage: '[data-slot="agent-chat-message"][data-role="assistant"]',
+    errorMessage: '[data-slot="agent-chat-message"][data-role="error"]',
+    streaming: slot('agent-chat-streaming'),
+    streamingText: slot('agent-chat-streaming-text'),
+    /** The A2UI block the protocol requires the pop-up to be able to draw (§19, P-25). */
+    a2ui: slot('agent-chat-a2ui'),
+    toolCard: slot('agent-tool-card'),
+    newSession: slot('agent-chat-new-session'),
+    sessionsTrigger: slot('agent-chat-sessions-trigger'),
+    session: slot('agent-chat-session'),
+    empty: slot('agent-chat-empty'),
+};
+/**
+ * `SessionGuard`'s expiry dialog — §10.4, rule P-37. The kit does not drive
+ * session expiry (it needs the idle policy shortened, which is an extension's
+ * own switch), but `signIn` has to be able to tell "signed out" from "broken".
+ */
+export const SESSION = {
+    dialog: slot('session-expiry-dialog'),
+    countdown: slot('session-expiry-countdown'),
+    continue: slot('session-expiry-continue'),
+    logout: slot('session-expiry-logout'),
+};
+/**
+ * Sign-in. **This is the block DESIGN-119 moves.**
+ *
+ * `shared` is cortena-ui's `AuthScreen`/`LoginScreen` composition, which is
+ * what an extension will mount once DESIGN-119 lands. `own` is the form an
+ * extension draws itself today — labelled controls and a submit button, which
+ * is all that can be assumed of a form nobody shared. `signIn()` prefers the
+ * shared slots and falls back to the labels, so an extension that has already
+ * adopted the shared screen and one that has not both sign in through the same
+ * call, and the fallback deletes itself when the last extension migrates.
+ */
+export const SIGN_IN = {
+    shared: {
+        screen: slot('auth-screen'),
+        card: slot('auth-screen-card'),
+        title: slot('auth-screen-title'),
+        brandName: slot('auth-screen-brand-name'),
+        form: slot('login-screen-form'),
+        submit: slot('login-screen-submit'),
+        error: slot('login-screen-error'),
+        /** The "You were signed out" notice §10.4.1 asks for. */
+        signedOut: slot('login-screen-signed-out'),
+        returnTo: slot('login-screen-return-to'),
+        providers: slot('login-screen-providers'),
+    },
+    /**
+     * The extension's own form, by accessible name. Deliberately not a
+     * `data-slot`: an extension's own markup has none to promise.
+     */
+    own: {
+        orgLabel: /organi[sz]ation/i,
+        orgSubmit: /^continue$/i,
+        emailLabel: /^e-?mail$/i,
+        passwordLabel: /^password$/i,
+        submit: /^sign in$/i,
+    },
+};
+/**
+ * The MCP consent page — the one screen in the six that no extension renders.
+ * It is cortena-auth's hosted page, so there is no cortena-ui slot to key on
+ * and no version of this repository can promise one. It is located by what a
+ * consent page *is*: a form naming the client, listing the scopes, with an
+ * allow and a deny. `ConsentScreen`'s slots are tried first for the day
+ * cortena-auth adopts it.
+ */
+export const CONSENT = {
+    screen: slot('consent-screen'),
+    scopes: slot('consent-screen-scopes'),
+    scope: slot('consent-scope'),
+    actions: slot('consent-screen-actions'),
+    /** The form-shaped fallback, which is what is actually there today. */
+    byForm: {
+        allow: /^(allow|authori[sz]e|approve|continue)$/i,
+        deny: /^(deny|cancel|reject)$/i,
+        /** cortena-auth's own list of what is being asked for. */
+        scopeList: '.scope-list',
+        /** The organisation picker, when the user is a member of more than one. */
+        orgPick: '.org-pick',
+    },
+    /**
+     * cortena-auth's own sign-in, which the authorisation request lands on
+     * before it will show a consent page — and which asks for the organisation
+     * first, exactly as an extension's own login does.
+     */
+    signIn: {
+        org: /organi[sz]ation/i,
+        orgSubmit: /^continue$/i,
+        email: /^e-?mail$/i,
+        password: /^password$/i,
+        submit: /^sign in$/i,
+    },
+};
+/**
+ * The theme contract, from cortena-ui's `useCortenaTheme`.
+ *
+ * cortena-design drives dark mode off `data-theme` on `<html>` and falls back
+ * to `prefers-color-scheme` when the attribute is absent — so "the OS path" is
+ * literally the absence of the attribute, and a suite that only ever writes it
+ * never tests the fallback the majority of first visits take.
+ */
+export const THEME = {
+    attribute: 'data-theme',
+    storageKey: 'cortena.theme',
+    /** The toggle publishes both the stored choice and what is painted. */
+    choiceAttribute: 'data-theme-choice',
+    resolvedAttribute: 'data-theme-resolved',
+};
+//# sourceMappingURL=locators.js.map

package/dist/locators.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"locators.js","sourceRoot":"","sources":["../src/locators.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,+DAA+D;AAC/D,MAAM,CAAC,MAAM,UAAU,GAAG,QAAQ,CAAC;AAEnC,MAAM,IAAI,GAAG,CAAC,IAAY,EAAU,EAAE,CAAC,eAAe,IAAI,IAAI,CAAC;AAE/D;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG;IACnB,IAAI,EAAE,IAAI,CAAC,WAAW,CAAC;IACvB,MAAM,EAAE,IAAI,CAAC,kBAAkB,CAAC;IAChC,KAAK,EAAE,IAAI,CAAC,iBAAiB,CAAC;IAC9B,WAAW,EAAE,IAAI,CAAC,wBAAwB,CAAC;IAC3C;;;;OAIG;IACH,SAAS,EAAE,IAAI,CAAC,YAAY,CAAC;IAC7B,aAAa,EAAE,WAAW;IAC1B,SAAS,EAAE,IAAI,CAAC,sBAAsB,CAAC;IACvC,SAAS,EAAE,IAAI,CAAC,sBAAsB,CAAC;IACvC,GAAG,EAAE,IAAI,CAAC,eAAe,CAAC;IAC1B,OAAO,EAAE,IAAI,CAAC,oBAAoB,CAAC;IACnC,OAAO,EAAE,IAAI,CAAC,oBAAoB,CAAC;IACnC,6EAA6E;IAC7E,WAAW,EAAE,CAAC,EAAU,EAAU,EAAE,CAAC,mBAAmB,EAAE,IAAI;IAC9D,4FAA4F;IAC5F,cAAc,EAAE,uDAAuD;IACvE,aAAa,EAAE,IAAI,CAAC,2BAA2B,CAAC;IAChD,SAAS,EAAE,qBAAqB;IAChC,cAAc,EAAE,IAAI,CAAC,4BAA4B,CAAC;IAClD,QAAQ,EAAE,IAAI,CAAC,qBAAqB,CAAC;IACrC,IAAI,EAAE,IAAI,CAAC,gBAAgB,CAAC;IAC5B,aAAa,EAAE,IAAI,CAAC,0BAA0B,CAAC;IAC/C,oGAAoG;IACpG,QAAQ,EAAE,CAAC,EAAU,EAAU,EAAE,CAAC,eAAe,EAAE,IAAI;IACvD,iFAAiF;IACjF,OAAO,EAAE,IAAI,CAAC,sBAAsB,CAAC;IACrC,UAAU,EAAE,IAAI,CAAC,0BAA0B,CAAC;IAC5C,YAAY,EAAE,IAAI,CAAC,4BAA4B,CAAC;IAChD,WAAW,EAAE,IAAI,CAAC,cAAc,CAAC;IACjC,UAAU,EAAE,IAAI,CAAC,aAAa,CAAC;IAC/B;;;;;OAKG;IACH,SAAS,EAAE,IAAI,CAAC,sBAAsB,CAAC;IACvC,aAAa,EAAE,qBAAqB;CAC5B,CAAC;AAEX;;;GAGG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG;IACnB,IAAI,EAAE,IAAI,CAAC,iBAAiB,CAAC;IAC7B,UAAU,EAAE,IAAI,CAAC,wBAAwB,CAAC;IAC1C,KAAK,EAAE,IAAI,CAAC,kBAAkB,CAAC;IAC/B,QAAQ,EAAE,IAAI,CAAC,qBAAqB,CAAC;IACrC,MAAM,EAAE,IAAI,CAAC,mBAAmB,CAAC;IACjC,IAAI,EAAE,IAAI,CAAC,YAAY,CAAC;IACxB,MAAM,EAAE,IAAI,CAAC,mBAAmB,CAAC;IACjC,KAAK,EAAE,IAAI,CAAC,kBAAkB,CAAC;IAC/B,IAAI,EAAE,IAAI,CAAC,iBAAiB,CAAC;IAC7B,IAAI,EAAE,IAAI,CAAC,iBAAiB,CAAC;IAC7B,IAAI,EAAE,IAAI,CAAC,iBAAiB,CAAC;IAC7B,OAAO,EAAE,IAAI,CAAC,oBAAoB,CAAC;IACnC,WAAW,EAAE,oDAAoD;IACjE,gBAAgB,EAAE,yDAAyD;IAC3E,YAAY,EAAE,qDAAqD;IACnE,SAAS,EAAE,IAAI,CAAC,sBAAsB,CAAC;IACvC,aAAa,EAAE,IAAI,CAAC,2BAA2B,CAAC;IAChD,sFAAsF;IACtF,IAAI,EAAE,IAAI,CAAC,iBAAiB,CAAC;IAC7B,QAAQ,EAAE,IAAI,CAAC,iBAAiB,CAAC;IACjC,UAAU,EAAE,IAAI,CAAC,wBAAwB,CAAC;IAC1C,eAAe,EAAE,IAAI,CAAC,6BAA6B,CAAC;IACpD,OAAO,EAAE,IAAI,CAAC,oBAAoB,CAAC;IACnC,KAAK,EAAE,IAAI,CAAC,kBAAkB,CAAC;CACvB,CAAC;AAEX;;;;GAIG;AACH,MAAM,CAAC,MAAM,OAAO,GAAG;IACrB,MAAM,EAAE,IAAI,CAAC,uBAAuB,CAAC;IACrC,SAAS,EAAE,IAAI,CAAC,0BAA0B,CAAC;IAC3C,QAAQ,EAAE,IAAI,CAAC,yBAAyB,CAAC;IACzC,MAAM,EAAE,IAAI,CAAC,uBAAuB,CAAC;CAC7B,CAAC;AAEX;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,OAAO,GAAG;IACrB,MAAM,EAAE;QACN,MAAM,EAAE,IAAI,CAAC,aAAa,CAAC;QAC3B,IAAI,EAAE,IAAI,CAAC,kBAAkB,CAAC;QAC9B,KAAK,EAAE,IAAI,CAAC,mBAAmB,CAAC;QAChC,SAAS,EAAE,IAAI,CAAC,wBAAwB,CAAC;QACzC,IAAI,EAAE,IAAI,CAAC,mBAAmB,CAAC;QAC/B,MAAM,EAAE,IAAI,CAAC,qBAAqB,CAAC;QACnC,KAAK,EAAE,IAAI,CAAC,oBAAoB,CAAC;QACjC,yDAAyD;QACzD,SAAS,EAAE,IAAI,CAAC,yBAAyB,CAAC;QAC1C,QAAQ,EAAE,IAAI,CAAC,wBAAwB,CAAC;QACxC,SAAS,EAAE,IAAI,CAAC,wBAAwB,CAAC;KAC1C;IACD;;;OAGG;IACH,GAAG,EAAE;QACH,QAAQ,EAAE,kBAAkB;QAC5B,SAAS,EAAE,aAAa;QACxB,UAAU,EAAE,YAAY;QACxB,aAAa,EAAE,aAAa;QAC5B,MAAM,EAAE,YAAY;KACrB;CACO,CAAC;AAEX;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,OAAO,GAAG;IACrB,MAAM,EAAE,IAAI,CAAC,gBAAgB,CAAC;IAC9B,MAAM,EAAE,IAAI,CAAC,uBAAuB,CAAC;IACrC,KAAK,EAAE,IAAI,CAAC,eAAe,CAAC;IAC5B,OAAO,EAAE,IAAI,CAAC,wBAAwB,CAAC;IACvC,uEAAuE;IACvE,MAAM,EAAE;QACN,KAAK,EAAE,0CAA0C;QACjD,IAAI,EAAE,yBAAyB;QAC/B,0DAA0D;QAC1D,SAAS,EAAE,aAAa;QACxB,2EAA2E;QAC3E,OAAO,EAAE,WAAW;KACrB;IACD;;;;OAIG;IACH,MAAM,EAAE;QACN,GAAG,EAAE,kBAAkB;QACvB,SAAS,EAAE,aAAa;QACxB,KAAK,EAAE,YAAY;QACnB,QAAQ,EAAE,aAAa;QACvB,MAAM,EAAE,YAAY;KACrB;CACO,CAAC;AAEX;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG;IACnB,SAAS,EAAE,YAAY;IACvB,UAAU,EAAE,eAAe;IAC3B,uEAAuE;IACvE,eAAe,EAAE,mBAAmB;IACpC,iBAAiB,EAAE,qBAAqB;CAChC,CAAC"}

package/dist/protocol/suite.d.ts

@@ -0,0 +1,31 @@
+import { type ProtocolSuiteOptions } from './types.js';
+/**
+ * The six end-to-end checks §23.4 requires, written once.
+ *
+ * HOW-TO §23.4 layer 3 names the same six things for every extension, none of
+ * which exist until something is deployed and none of which a unit test can
+ * see: the login page, the extension inside the CortenaWeb frame, the MCP
+ * consent page, the agent pop-up, UI state, and shell chrome. Written per
+ * extension that is six copies of the same fixtures and six ways of finding
+ * the sidebar — and drift on the one layer that is supposed to prove the fleet
+ * looks the same. Here it is a config file per extension, and a renamed
+ * `data-slot` fails every adopter's suite in `locators.ts` rather than in six
+ * places.
+ *
+ *   // extensions/<name>/e2e/protocol.spec.ts
+ *   defineProtocolSuite({
+ *     host: 'https://test.<name>.ascendenceai.com',
+ *     listRoute: '/things',
+ *     filter: { param: 'status', value: 'open' },
+ *     detail: { open, urlPattern, close },
+ *     agentSlug: '<name>',
+ *     helpTopic: 'Things',
+ *     expects: { brandName: 'Things', navItems: [...], listHeading: /things/i, agentPrompt: '...' },
+ *     cases: { login, embedded, consent, popup, listState, shell },
+ *   });
+ *
+ * Both themes are the two Playwright projects `protocolConfig()` defines, so
+ * every one of the six runs twice and the run's variant is read off the project
+ * name by the Assure reporter. `retries: 0`, because a flaky test is a defect.
+ */
+export declare function defineProtocolSuite(options: ProtocolSuiteOptions): void;

package/dist/protocol/suite.js

@@ -0,0 +1,196 @@
+import { expect, test } from '@playwright/test';
+import { assureAnnotation, isAssureAnnotation, } from '@ascendenceai/cortena-extensions-assure-reporters/annotations';
+import { consent } from '../fixtures/consent.js';
+import { embedded, expectTokenStrippedFromUrl, postHostTheme } from '../fixtures/embedded.js';
+import { listState } from '../fixtures/list-state.js';
+import { popup, expectSessionResumes } from '../fixtures/popup.js';
+import { expectShellChrome, shell } from '../fixtures/shell.js';
+import { isSignInScreen, organisationStep, signIn } from '../fixtures/sign-in.js';
+import { expectTheme, theme, themeFromProjectName } from '../fixtures/theme.js';
+import { SHELL } from '../locators.js';
+import { readCredentials } from '../env.js';
+import { PROTOCOL_CASE_KEYS } from './types.js';
+/**
+ * The six end-to-end checks §23.4 requires, written once.
+ *
+ * HOW-TO §23.4 layer 3 names the same six things for every extension, none of
+ * which exist until something is deployed and none of which a unit test can
+ * see: the login page, the extension inside the CortenaWeb frame, the MCP
+ * consent page, the agent pop-up, UI state, and shell chrome. Written per
+ * extension that is six copies of the same fixtures and six ways of finding
+ * the sidebar — and drift on the one layer that is supposed to prove the fleet
+ * looks the same. Here it is a config file per extension, and a renamed
+ * `data-slot` fails every adopter's suite in `locators.ts` rather than in six
+ * places.
+ *
+ *   // extensions/<name>/e2e/protocol.spec.ts
+ *   defineProtocolSuite({
+ *     host: 'https://test.<name>.ascendenceai.com',
+ *     listRoute: '/things',
+ *     filter: { param: 'status', value: 'open' },
+ *     detail: { open, urlPattern, close },
+ *     agentSlug: '<name>',
+ *     helpTopic: 'Things',
+ *     expects: { brandName: 'Things', navItems: [...], listHeading: /things/i, agentPrompt: '...' },
+ *     cases: { login, embedded, consent, popup, listState, shell },
+ *   });
+ *
+ * Both themes are the two Playwright projects `protocolConfig()` defines, so
+ * every one of the six runs twice and the run's variant is read off the project
+ * name by the Assure reporter. `retries: 0`, because a flaky test is a defect.
+ */
+export function defineProtocolSuite(options) {
+    assertCases(options);
+    const { expects, listRoute, agentSlug } = options;
+    test.describe('protocol (§23.4, P-36)', () => {
+        /*
+         * The theme is applied before every navigation, not inside the specs: the
+         * stored choice is read before the first paint, so a spec that sets it
+         * after `goto` has proved a re-render and nothing else.
+         */
+        test.beforeEach(async ({ page }, testInfo) => {
+            await theme(page, themeFromProjectName(testInfo.project.name));
+        });
+        test('the login page asks for the organisation and signs a person in', { annotation: [assureAnnotation(options.cases.login)] }, async ({ page }, testInfo) => {
+            const credentials = readCredentials();
+            test.skip(!credentials.email || !credentials.password, 'CORTENA_E2E_USER_EMAIL and CORTENA_E2E_USER_PASSWORD are needed: a token proves the '
+                + 'handoff, only the form proves a person can sign in.');
+            await page.goto('/');
+            /*
+             * Signed out, the app must *be* a sign-in screen rather than an empty
+             * shell or a spinner. §10.4.1: whatever happened, the user lands
+             * somewhere that says what to do next.
+             */
+            expect(await isSignInScreen(page), 'a signed-out visit must land on the sign-in screen').toBe(true);
+            await expectTheme(page, themeFromProjectName(testInfo.project.name));
+            // The organisation step decides *how* this org signs in before it asks
+            // for anything — password, Google, or both (P-08). `signIn` walks it
+            // again from the top, which is the flow a person actually takes.
+            await organisationStep(page, credentials.orgId);
+            await signIn(page, { useForm: true, credentials, route: '/' });
+            await expect(shell(page).root).toBeVisible();
+        });
+        test('a token-only launch renders the extension, not the login page', { annotation: [assureAnnotation(options.cases.embedded)] }, async ({ page }, testInfo) => {
+            const mode = themeFromProjectName(testInfo.project.name);
+            await embedded(page, { route: listRoute });
+            await expectTokenStrippedFromUrl(page);
+            await expectListRendered(page, expects.listHeading);
+            /*
+             * The host owns the theme in the frame: CortenaWeb posts it in on load
+             * and on every change, and the extension applies the *mode* it implies.
+             *
+             * The **opposite** mode first, and that is the whole assertion. The
+             * page already carries `mode` from `beforeEach`, so posting `mode` and
+             * asserting `mode` is a tautology — delete cortena-ui's `cortena-theme`
+             * listener entirely and it still passes. Posting the opposite means the
+             * attribute can only change if the message was received, and posting
+             * back leaves the page in the theme the project is named for.
+             */
+            const opposite = mode === 'dark' ? 'light' : 'dark';
+            await postHostTheme(page, opposite);
+            await postHostTheme(page, mode);
+        });
+        test('the MCP consent page names the resource and can be refused', { annotation: [assureAnnotation(options.cases.consent)] }, async ({ page }) => {
+            await consent(page, {
+                host: options.host,
+                scopes: expects.consentScopes,
+                // A client registered by hand, when an environment forbids dynamic
+                // registration. Absent, one is registered the way an MCP client does.
+                clientId: process.env.CORTENA_E2E_MCP_CLIENT_ID?.trim() || undefined,
+            });
+        });
+        test('the agent pop-up opens, streams a turn, resumes it after a reload and draws A2UI', { annotation: [assureAnnotation(options.cases.popup)] }, async ({ page }) => {
+            await embedded(page, { route: listRoute });
+            const chat = popup(page);
+            await chat.open();
+            await chat.ask(expects.agentPrompt);
+            await expect(chat.assistantMessages.first()).toBeVisible();
+            // The block of A2UI, which is the half of P-25 that says the agent can
+            // answer with a screen rather than with a paragraph about one.
+            const a2uiPrompt = expects.a2uiPrompt;
+            if (a2uiPrompt) {
+                await chat.ask(a2uiPrompt);
+                await expect(chat.a2ui.or(chat.toolCards).first()).toBeVisible();
+            }
+            // The session is the server's, not this tab's.
+            await expectSessionResumes(page, expects.agentPrompt);
+        });
+        test('the list keeps its filter through the detail, Back, reload and a new tab', { annotation: [assureAnnotation(options.cases.listState)] }, async ({ page }) => {
+            // Signed in first, so the five navigations below are the list's own and
+            // not a redirect to the login screen five times.
+            await embedded(page, { route: listRoute });
+            await expectListRendered(page, expects.listHeading);
+            await listState(page, {
+                route: listRoute,
+                filter: options.filter,
+                detail: options.detail,
+            });
+        });
+        test('the shell puts the mark top-left, Settings under the avatar, theme then help bottom-right', { annotation: [assureAnnotation(options.cases.shell)] }, async ({ page }, testInfo) => {
+            const mode = themeFromProjectName(testInfo.project.name);
+            await embedded(page, { route: listRoute });
+            await expectShellChrome(page, expects);
+            await expectTheme(page, mode);
+            /*
+             * §10.1 and §19.1: the mark id, the extension id and the AgentTemplate
+             * slug are **one value**. `data-mark` reads `fallback` when nothing is
+             * registered for that id, which renders an initial in a box — so this
+             * catches both a mark nobody registered and a slug that drifted from
+             * the id the shell was given.
+             */
+            await expect(shell(page).brandMark).toHaveAttribute(SHELL.markAttribute, agentSlug);
+            // The help panel answers from the extension's own functional document
+            // (§13, P-13) — not a hand-written copy that drifts.
+            const s = shell(page);
+            await s.openHelp();
+            await expect(s.helpPanel).toContainText(options.helpTopic);
+            await page.keyboard.press('Escape');
+            // The drawer is the same navigation below the breakpoint, with a focus
+            // trap and a way out. A sidebar that simply disappears on a phone is
+            // the failure this catches.
+            await s.openNavDrawer();
+            await expect(s.navDrawer.locator(SHELL.navItem).first()).toBeVisible();
+            await s.navDrawerClose.click();
+            await expect(s.navDrawer).toHaveCount(0);
+            /*
+             * The other way into the same theme, in a second page of the same
+             * context. `data-theme` absent means cortena-design falls back to
+             * `prefers-color-scheme`, and a suite that only ever writes the
+             * attribute never exercises the path a first-time visitor takes — so
+             * an extension can be correct in dark mode only for people who once
+             * pressed the toggle. It is a second page rather than a seventh spec
+             * because it is the same claim about the same screen.
+             */
+            const osPage = await page.context().newPage();
+            try {
+                await theme(osPage, mode, { path: 'os' });
+                await embedded(osPage, { route: listRoute });
+                await expectTheme(osPage, mode, 'os');
+            }
+            finally {
+                await osPage.close();
+            }
+        });
+    });
+}
+/** The list route rendered, by the name a person reads rather than a test id. */
+async function expectListRendered(page, heading) {
+    await expect(page.getByRole('heading', { name: heading }).first()).toBeVisible();
+}
+/**
+ * Six cases, all six present and all six real.
+ *
+ * A missing one used to be a spec that ran and recorded nothing, which is the
+ * exact shape of failure the Assure reporters exist to prevent: a green
+ * pipeline over an empty record.
+ */
+function assertCases(options) {
+    const missing = PROTOCOL_CASE_KEYS.filter((key) => !isAssureAnnotation(options.cases?.[key]));
+    if (missing.length) {
+        throw new Error(`defineProtocolSuite: the cases ${missing.join(', ')} are missing or are not assureCase() `
+            + 'literals. Write all six out in this file — assure-sync-cases parses the literal without '
+            + 'running the test and never looks inside node_modules, so a case built in the kit is a '
+            + 'case the catalogue never hears about. Copy them from the kit README.');
+    }
+}
+//# sourceMappingURL=suite.js.map