feat(cc): add AI summaries across Contact Center widgets

.github/workflows/deploy.yml

@@ -132,6 +132,10 @@ jobs:
         run: |
           echo "npmAuthToken: ${{ env.token }}" >> ~/.yarnrc.yml
 
+      - name: Assert Publishable Package Boundary
+        if: steps.check-changes.outputs.has_changes == 'true'
+        run: node tooling/src/publish.js assert-publishable
+
       - name: Sync and Increment Package Versions
         id: increment
         if: steps.check-changes.outputs.has_changes == 'true'

.gitignore

@@ -22,6 +22,9 @@ yarn-error.log*
 .node_repl_history
 reports/
 .generated/
+.worktrees/
+vendor/
+!vendor/
 
 #IDEs
 .project
@@ -39,6 +42,9 @@ reports/
 
 #Local stuff
 *.json
+!prog-mini-js.config.json
+!playwright/visual/ai-summary-harness.json
+!playwright/tsconfig.ai-summary.json
 !docs/changelog/logs/*.json
 !.sdd/manifest.json
 .env*
@@ -54,3 +60,16 @@ node_modules/
 # Playwright reports
 **/test-results/
 **/playwright-report
+
+# Artificer runtime and local requirement/UX inputs
+.matrix/
+.prog/
+requirementVersion/
+.ccwidgets/
+
+# The implementation DAG is an Artificer design deliverable, not runtime state.
+!design/default/implementation_dag.json
+
+# Reviewed AI-summary admission artifacts.
+!design/default/sdk_package_lock.json
+!vendor/contact-center-cc-summaries.tgz

ai-docs/ARCHITECTURE.md

@@ -57,6 +57,53 @@ subscribes to store observables → user action (e.g. set state, accept task) 
 → SDK responds and/or emits an event → store updates observables in `runInAction()` → observing widgets
 re-render. Grounded in `packages/contact-center/store/src/store.ts` and `storeEventsWrapper.ts`.
 
+**AI Summary visual evidence:** `playwright/visual/ai-summary-harness.json` binds the
+accepted UX source/state IDs to the existing Playwright project, sample-app
+production-component mount, observable assertions, and 2x capture geometry.
+`playwright/Utils/aiSummaryUtils.ts` runs browser assertions and writes raw
+PNG/DOM/comparison records under `.matrix/results/prog-mini-js/ux-visual/<phase>/`.
+These records do not assert visual fidelity; the prog-mini-js visual task must
+inspect the target/render pairs and publish a separate attempt-bound handoff.
+The deterministic host owns browser startup and cleanup. Do not turn a
+machine-generated comparison score into a claim of model image inspection.
+
+**UX seal revalidation:** `tooling/src/ai-summary-sdk-lock.js seal-ux` independently
+reopens and hashes the admitted target files on every call. If an existing seal
+matches the complete validated evidence and authority metadata, it preserves the
+original lock-file bytes and `ux.sealedAt`; repeated DAG acceptance must not make
+visual receipts stale merely by refreshing a timestamp. Missing, symlinked, or
+changed inputs and mismatched sealed metadata fail closed without replacing the
+receipt. A genuinely changed authority requires an explicit admission repair,
+not an automatic reseal during acceptance. Regression coverage lives in
+`tooling/tests/ai-summary-sdk-lock.test.js`.
+
+**Local UX provenance:** `tooling/src/verify-ai-summary-release.js` checks the
+harness descriptor, active visual plan/receipts, and archived JSON evidence.
+The exact `figma_mcp_policy: "forbidden"` and `mcp_policy: "forbidden"` declarations
+are prohibitions, not evidence of MCP use. Explicit use/transport/tool records
+and remote Figma references remain rejected; ambiguous MCP policies fail closed.
+Local scene-graph node/file IDs and evidence filenames alone do not establish
+remote acquisition. Provenance failures identify the repository-relative file
+and JSON field, without printing evidence values or remote credentials.
+Regression coverage lives in `tooling/tests/verify-ai-summary-release.test.js`.
+
+**AI summary SDK validation:** initiating/post-call requests resolve `Promise<AISummary>`;
+receiver content uses `task:midCallSummaryReceived` and capability updates use
+`task:featureEnablement` on the matching Task. The packed runtime and its extracted declarations
+are checked together, including a TypeScript compiler probe explicitly mapped to the candidate.
+Legacy seals cannot skip runtime validation or omit required source/build provenance. The combined
+lock verification also packs and inspects all six AI-summary workspace boundaries in an isolated
+child environment. See [`ai-summary.md`](../ai-summary.md) for the exact API and current sealed-package defect.
+
+**Release evidence binding:** release manifests are nonempty, hash every named file, and match live
+Git changes since an ancestor `baseCommit`. Verification runs on the requirement's promotion branch.
+Each gate names a repository-contained receipt with an explicit passing status, matching file hash,
+and matching HEAD. The D8b gate also binds the packaging receipt hash; actual tarball file lists must
+match that receipt. Executable provenance scanning inspects calls rather than matching explanatory
+comments, regular expressions, or test source strings. Privacy scanning permits raw-error variables
+used for normalization while rejecting their use as arguments to known logging sinks. These checks
+do not turn unexecuted browser/visual or failed SDK checks into passing release evidence.
+
 ## Dependencies
 | Dependency | Type (internal / external / peer) | How used | Failure / version handling |
 |---|---|---|---|

ai-docs/CONTRACTS.md

@@ -25,6 +25,9 @@ The aggregator package `@webex/cc-widgets` re-exports every widget plus the `sto
 | cc-widgets.store | `@webex/cc-store` | `store` | MobX singleton (`Store.getInstance()`); `init(options: InitParams, setupEventListeners): Promise<void>`; sole SDK access point via `store.cc.*` | stable semver | `packages/contact-center/store/ai-docs/store-spec.md` | `packages/contact-center/store/src/index.ts:1,4` |
 | store.host-init.enableWxBetterTogether | `@webex/cc-store` | `webexConfig.cc.enableWxBetterTogether` → `store.enableWxBetterTogether` | Host init boolean (default `false`), set **before** `store.init()`: read from `webexConfig.cc` on `{ webexConfig, access_token }` init or `webex.config.cc` on `{ webex }` init; read-only observable after init (Phase 1: re-init to change). Gates wxApp Mute/Keypad visibility and wxApp mute seed; SDK owns mute/DTMF API routing. | stable semver; renaming or removing the init key or store getter is breaking | `packages/contact-center/store/ai-docs/store-spec.md` (`STORE-R-030`); `packages/contact-center/task/ai-docs/task-spec.md` (WXCC-6026) | `packages/contact-center/store/src/store.ts`, `packages/contact-center/store/src/store.types.ts` (`WebexCcInitConfig`) |
 | store.types | `@webex/cc-store` | Existing queue/entry-point request, response, and entity type re-exports plus `TaskUIControls` | TypeScript exports describing the SDK-backed domain surface; established entity rows and Task destination controls pass through without a widget destination abstraction | stable semver; SDK-shaped types track SDK | `@webex/contact-center` types (`node_modules/@webex/contact-center/dist/types/index.d.ts`) (SDK source); `packages/contact-center/store/ai-docs/store-spec.md` | `packages/contact-center/store/src/store.types.ts` |
+| cc-components.CallControlComponent | `@webex/cc-components` | `CallControlComponent` (`CallControlComponentProps`) | React presentation component for call controls. Public props include optional `aiSummary?: CallControlAISummaryProps`, `sendMidCallSummaryBeforeAction(actionType, expectedRevision): Promise<{outcome: 'sent' \| 'failed' \| 'blocked' \| 'stale'}>` through that prop, and `wrapupCall(wrapupReason, wrapupId): Promise<WrapupCompletionResult>`. `handleTargetSelect` waits for the mid-call summary Promise to settle before invoking `consultCall`/`transferCall` once. `handleWrapupCall` resolves a `WrapupCompletionResult` and catches callback throws/rejections into `{wrapup: 'failed'}`. | stable semver; optional `aiSummary` is additive, but the `wrapupCall` migration from synchronous `void` to `Promise<WrapupCompletionResult>` is breaking for typed consumers | `packages/contact-center/cc-components/ai-docs/cc-components-spec.md` (`CC-COMPONENTS-R-006`) | `packages/contact-center/cc-components/src/components/task/task.types.ts`, `packages/contact-center/cc-components/src/components/task/CallControl/call-control.tsx`, `packages/contact-center/cc-components/src/components/task/CallControl/call-control.utils.ts` |
+| cc-components.AIAssistantComponent | `@webex/cc-components` | `AIAssistantComponent` (`AIAssistantComponentProps`, `AIAssistantReceiverSummary`, `AdaptiveCardRendererProps`) | AI Assistant panel chrome, Real-time Assist transcript/actions, and props-only receiving-agent `View summary` branch with display-only card rendering, receiver copy, and feedback callbacks | stable semver; receiver branch prop shape is a public type surface | `packages/contact-center/cc-components/ai-docs/cc-components-spec.md` (`CC-COMPONENTS-R-020`, `CC-COMPONENTS-R-021`) | `packages/contact-center/cc-components/src/components/AIAssistant/ai-assistant.types.ts` |
+| cc-components.AISummary | `@webex/cc-components` | `AISummary`, `AISummaryProps`, `AI_SUMMARY_MESSAGES`, `COPIED_FEEDBACK_MS`, `MID_CALL_SECTION_DEFINITIONS`, `POST_CALL_SECTION_DEFINITIONS`, `POST_CALL_DISPLAY_SECTION_ORDER`, `projectPostCallDisplaySections` | SDK-free shared AI summary surface for mid-call initiator, mid-call receiver, and post-call wrap-up modes; exposes exact copy constants, ordered section key/label definitions, and post-call section projection used by components and tests | stable semver; adding optional props/values is additive, narrowing `AISummaryProps` modes/callback result types is breaking | `packages/contact-center/cc-components/ai-docs/cc-components-spec.md` (`CC-COMPONENTS-R-002`, `CC-COMPONENTS-R-022`) | `packages/contact-center/cc-components/src/components/AISummary/index.ts` |
 | cc-components.consult-transfer-lists | `@webex/cc-components` | `CallControl` consult/transfer fetch props plus `action`, `availableDestinations`, and optional list-item `presence` | `FetchPaginatedList<ContactServiceQueue>` / `FetchPaginatedList<EntryPointRecord>` and the SDK-ordered destination array from `TaskUIControls`; UI preserves list/category order, passes buddy availability to Momentum Avatar as semantic presence, shows `AddressBookEntry.number` and `EntryPointRecord.number` subtitles, and may only apply host hide overrides | stable semver; entity and control types track store/SDK contracts; optional presentation prop is additive | `packages/contact-center/cc-components/ai-docs/cc-components-spec.md`; `ai-docs/features/consult-transfer-list-policy/spec/feature-spec.md` | `packages/contact-center/cc-components/src/components/task/task.types.ts` |
 | cc-components.TelephonyActionToast | `@webex/cc-components` | `TelephonyActionToast` (`TelephonyActionToastProps`) | wxApp thick-client telephony error toast (Momentum `Toast` `variant="error"`); consumed by `@webex/cc-task` CallControl / CallControlCAD wrappers | widget-internal / monorepo cross-package only; not a host-facing `@webex/cc-widgets` surface | `packages/contact-center/cc-components/ai-docs/cc-components-spec.md` | `packages/contact-center/cc-components/src/components/task/TelephonyActionToast/telephony-action-toast.tsx` |
 | cc-components.WxAppOfferActionError | `@webex/cc-components` | `WxAppOfferActionError` (`WxAppOfferActionErrorProps`) | Inline wxApp offer-action error as red text below Accept/Decline; store-backed per `interactionId` | widget-internal / monorepo cross-package only; not a host-facing `@webex/cc-widgets` surface | `packages/contact-center/cc-components/ai-docs/cc-components-spec.md` | `packages/contact-center/cc-components/src/components/task/WxAppOfferActionError/wxapp-offer-action-error.tsx` |
@@ -44,7 +47,17 @@ The aggregator package `@webex/cc-widgets` re-exports every widget plus the `sto
 | `@r2wc/react-to-web-component` | Wraps React widgets as custom elements (`packages/contact-center/cc-widgets/src/wc.ts:1`) | r2wc docs | Bundled with `cc-widgets` | N/A | per `package.json` |
 
 ## Compatibility & Deprecation Policy
-- **Breaking-change rule:** Semver. A breaking change requires a major version bump. The breaking surface is: the named **package exports** above, the **custom-element tag names** (`widget-cc-*` in `packages/contact-center/cc-widgets/src/wc.ts:68-78`), and the **declared widget event/callback prop names**. Renaming/removing any of these, or changing a callback signature, is breaking. Adding a new widget, export, or optional prop is additive (minor).
+
+The sealed AI summary SDK contract is documented in [`ai-summary.md`](../ai-summary.md).
+Initiating mid-call and post-call results resolve `Promise<AISummary>` from the Task request methods.
+Receiving-agent content arrives on `TASK_EVENTS.TASK_MID_CALL_SUMMARY_RECEIVED`
+(`task:midCallSummaryReceived`); capability changes arrive on `TASK_EVENTS.TASK_FEATURE_ENABLEMENT`
+(`task:featureEnablement`). The store owns subscriptions and response sends. The previous
+three summary-event names and separate event-payload type exports are not part of this SDK.
+`tooling/src/ai-summary-sdk-lock.js verify-sdk` always validates extracted candidate declarations
+and runs the packed runtime suite, including legacy seals without a recorded harness marker.
+Admission does not silently convert a failed probe into a successful receipt.
+- **Breaking-change rule:** Semver. A breaking change requires a major version bump. The breaking surface is: the named **package exports** above, the **custom-element tag names** (`widget-cc-*` in `packages/contact-center/cc-widgets/src/wc.ts:68-78`, `component-cc-*` in `packages/contact-center/cc-components/src/wc.ts`), and the **declared widget/component event/callback prop names**. Renaming/removing any of these, narrowing a callback signature, or changing a required callback return type is breaking; `CallControlComponentProps.wrapupCall` changing from synchronous `void` to `Promise<WrapupCompletionResult>` is such a breaking migration. Adding a new widget, export, or optional prop is additive (minor).
 - **Deprecation:** Releases are cut by `semantic-release` (`package.json`, `.releaserc`); commit type drives the version bump (`fix` → patch, `feat` → minor, breaking footer → major). Deprecated surfaces are kept for at least one minor release with a JSDoc `@deprecated` note before removal in a major.
 
 ## Maintenance