@webex/internal-plugin-call-ai-summary 3.12.0-next.59 → 3.12.0-next.60

package/docs/architecture.md

@@ -0,0 +1,287 @@
+---
+type: Architecture
+title: '@webex/internal-plugin-call-ai-summary architecture'
+description: Repository-wide boundaries, resources, interactions, dependencies, and cross-cutting architecture.
+tags: [architecture]
+---
+<!-- sdd-generated-metadata
+doc_kind: standing-doc
+generated_from: architecture@0.3.0
+generated_by: claude-code
+approved_by: "@riag"
+updated_at: 2026-09-23T14:03:22Z
+validation_status: pass
+-->
+
+# @webex/internal-plugin-call-ai-summary architecture
+
+Canonical repository-wide architecture. This document owns facts that span
+multiple services, packages, modules, applications, or repositories. Link to
+the owning service, module, feature, ADR, or native contract instead of
+duplicating owner-local detail.
+
+Related context: [specification registry](specs/README.md) ·
+[repository agent instructions](../AGENTS.md)
+
+## Applicability
+
+| Condition ID                         | Status | Evidence or reason | Owned section                       |
+| ------------------------------------ | ------ | ------------------ | ----------------------------------- |
+| `repo.owns_datastore`                | N/A    | The package persists nothing; all content is fetched per call from Pragya and AI Bridge. `src/ai-summary.ts` | Repository data and schema          |
+| `repo.holds_client_state`            | N/A    | The WebexPlugin.extend object holds no session state between calls. `src/ai-summary.ts` | Client state model                  |
+| `repo.components_interact`           | N/A    | Single module; interaction with upstream services is covered by Interaction and execution flows. `src/` | Dependency and interaction topology |
+| `repo.domain_data_across_components` | N/A    | One module owns all domain data in this package. `src/types.ts` | Object and data ownership           |
+| `repo.caches_data`                   | N/A    | No cache layer exists in the source. `src/ai-summary.ts` | Caching catalog                     |
+| `repo.observability_convention`      | Applicable | Every public method logs failures through this.logger.error before rethrowing. `src/ai-summary.ts` | Observability patterns              |
+| `repo.deploys_to_infra`              | N/A    | Published library; no deployment surface or infrastructure. `package.json` | Runtime and infrastructure          |
+| `repo.shared_base_libs`              | Applicable | Inherits WebexPlugin, request handling, and the auth interceptor from @webex/webex-core. `package.json` | Shared and base libraries           |
+| `repo.is_monorepo`                   | N/A    | The SDD root is one package; the surrounding monorepo is out of this scope. `package.json` | Package map and dependencies        |
+| `repo.multi_platform`                | Applicable | Supports both browser and Node.js environments. `package.json` | Platform matrix                     |
+| `repo.published_package`             | Applicable | Published to npm via the deploy:npm script. `package.json` | Release and versioning              |
+| `repo.embedded_in_host`              | Applicable | Registers into a host Webex SDK instance as webex.internal.aisummary. `src/index.ts` | Host integration and theming        |
+| `repo.exposes_commands_or_artifacts` | Applicable | Publishes a build artifact to dist/ and exposes documented yarn commands. `package.json` | Commands and generated artifacts    |
+| `repo.cross_repo_deps_material`      | Applicable | Behavior depends on the externally owned Pragya, AI Bridge, Janus, and KMS services. `src/constants.ts` | Cross-repository topology           |
+| `repo.security_arch_warranted`       | Applicable | All content is KMS-encrypted and every call is token-authenticated. `src/ai-summary.ts` | Security architecture               |
+
+## Design overview
+
+The Webex JS SDK will provide AI-generated call summary retrieval capabilities through a new **`internal-plugin-call-ai-summary`** internal plugin. This document describes the architecture for retrieving AI-generated notes, action items, and transcripts from completed calls.
+
+AI summary content is discovered through a two-step lookup: **Janus** (call history) provides container IDs, and **Pragya** (AI container service) resolves those IDs into content URLs and an encryption key.
+
+The package pursues these goals:
+
+- Resolve AI summary container IDs from Janus call history via Pragya
+- Retrieve AI-generated notes (full notes) for a call
+- Retrieve AI-generated action items for a call
+- Retrieve transcript download URLs for a call
+- Handle encrypted content decryption via KMS
+- Maintain consistency with existing Webex JS SDK internal plugin patterns
+- Provide type-safe interfaces for all operations
+- Support both browser and Node.js environments
+
+The following are explicitly out of scope:
+
+- Start/stop AI assistant during active calls (handled by Pragya start/stop APIs, out of scope)
+- Generate or regenerate summaries (backend-managed during/after calls)
+- Provide real-time in-call AI responses
+- Handle recording storage or deletion
+- Implement feedback UI components
+
+Operation depends on two prerequisites:
+
+1. Janus API already returns `extensionPayload.callingContainerIds` in the response
+2. Testing environment with AI-enabled calls that generate summaries
+
+The decisions that shape this structure are recorded in
+[ADR-0001](adr/0001-flatten-container-response-and-prefer-single-request-summary.md).
+
+## Resource inventory and responsibilities
+
+| Component | Responsibility |
+| --------- | -------------- |
+| `internal-plugin-call-ai-summary` | Internal plugin; resolves Pragya containers, fetches and decrypts summary content |
+| `internal-plugin-encryption` | KMS integration for decrypting AI-generated content using `encryptionKeyUrl` |
+| `http-core` | HTTP transport; adds authorization headers, handles retries |
+| Pragya Service | Container metadata; provides content URLs and encryption key |
+| Summary Content Endpoints | Serve encrypted AI-generated content (notes, action items, transcripts) |
+
+Only the first component is owned by this repository. Its source is `src/` and its canonical
+specification is [`src/docs/README.md`](../src/docs/README.md); it is owned by the Webex JS SDK Team.
+The encryption plugin and HTTP transport are sibling workspace packages, and the Pragya and summary
+content services are externally owned.
+
+## Interaction and execution flows
+
+AI summary content is discovered in three steps.
+
+**Step 1: Get container IDs from Janus call history**
+
+The Janus `UserSession` response includes an `extensionPayload` field containing container IDs for AI artifacts related to a call:
+
+The `extensionPayload.callingContainerIds` field is already present in the Janus API response but is not yet in the SDK's `UserSession` type definition, so consumers read it from the raw session payload. The exact session shape is owned by the Janus call-history type declaration rather than restated here.
+
+**Step 2: Resolve container IDs via Pragya**
+
+For each `containerId`, call the Pragya container API at `GET https://{pragya-host}/pragya/api/v1/containers/{containerId}`. The raw Pragya response nests summary URLs under `summaryData.data`. The plugin's `getContainer()` method flattens this so consumers can access `summaryData.summaryUrl` directly; the exact response body is owned by `src/types.ts`.
+
+**Step 3: Fetch summary content from the URLs**
+
+The `summaryData` object provides direct, region-correct URLs to each content type. The plugin fetches content from these URLs and decrypts it using the `encryptionKeyUrl` returned alongside them.
+
+```mermaid
+flowchart LR
+  Client[Client application] -->|getCallHistoryData| Janus[Janus call history]
+  Janus -->|extensionPayload.callingContainerIds| Client
+  Client -->|getContainer| Plugin[internal-plugin-call-ai-summary]
+  Plugin -->|GET containers/id| Pragya[Pragya service]
+  Pragya -->|summaryData URLs + encryptionKeyUrl| Plugin
+  Plugin -->|GET summaryUrl / notesUrl / actionItemsUrl / transcriptUrl| Bridge[AI Bridge content endpoints]
+  Bridge -->|encrypted content| Plugin
+  Plugin -->|decryptText| KMS[internal-plugin-encryption + KMS]
+  KMS -->|plaintext| Plugin
+  Plugin -->|decrypted summary| Client
+```
+
+The component architecture places the client application above the SDK, the plugin beside the
+encryption plugin and HTTP transport inside `webex.internal`, and the Pragya and summary-content
+services outside the SDK boundary. The end-to-end retrieval flow runs call history, then container
+resolution, then content fetch and decryption, in that order.
+
+| From | To | Interaction or transport | Purpose | Failure or compatibility behavior |
+| ---- | -- | ------------------------ | ------- | --------------------------------- |
+| Client | Janus | HTTPS call | Get call history and container IDs | Owned by the call-history plugin |
+| Plugin | Pragya | `webex.request` with `service: 'pragya'` | Resolve container metadata, content URLs, and encryption key | 401/403/404 normalized by `_handleError`; see the module spec |
+| Plugin | AI Bridge | `webex.request` with an absolute `uri` | Fetch encrypted note, short note, action items, and transcript | 404 becomes `Summary content not available or expired` |
+| Plugin | `internal-plugin-encryption` | In-process call to `decryptText` | Decrypt every `aiGeneratedContent` field | Rejection propagates through `_handleError` |
+
+Get-container, get-notes and get-action-items each follow the same shape: validate input, issue one
+request, then decrypt. Per-method sequence detail and failure branches are owned by
+[the module specification](../src/docs/README.md).
+
+## Dependency topology
+
+Internal workspace dependencies, both declared `workspace:*` in `package.json` and both consumed by
+`src/`:
+
+| Package | Purpose |
+| ------- | ------- |
+| `@webex/webex-core` | Plugin infrastructure (`WebexPlugin`, `registerInternalPlugin`) |
+| `@webex/internal-plugin-encryption` | Content decryption via `decryptText()` |
+
+External service dependencies. A `webex-core` request rejection or a `decryptText` rejection
+propagates to the caller through `_handleError`:
+
+| Service | Purpose | Discovery |
+| ------- | ------- | --------- |
+| **Janus** | Call history; provides `extensionPayload.callingContainerIds` | U2C: `serviceName: "janus"` |
+| **Pragya** | Container metadata; provides content URLs and encryption key | U2C: `serviceName: "pragya"` |
+| **Summary Content Endpoints** | Serve encrypted AI-generated content | Direct URLs from Pragya response |
+| **KMS** | Encryption key management | Via `encryptionKeyUrl` from Pragya |
+
+Pragya is discoverable via U2C as `serviceName: "pragya"` (validated: e.g., load-us resolves to `https://pragya-loada.ciscospark.com/pragya/api/v1`). There are no dependency cycles: the package is
+a leaf consumer of `webex-core` and the encryption plugin. Exact versions stay in `package.json`.
+
+## Public and consumer surfaces
+
+| Surface | Type | Owner | Consumers | Compatibility policy | Source |
+| ------- | ---- | ----- | --------- | -------------------- | ------ |
+| `aisummary-sdk` | SDK | `src/` | Webex SDK consumers via `webex.internal.aisummary` | Internal plugin; does not strictly adhere to semantic versioning | `src/ai-summary.ts` |
+| `aisummary-package-entry` | SDK | `src/` | Anything importing the package | Internal; import performs registration | `src/index.ts` |
+| `aisummary-types` | SDK | `src/` | TypeScript consumers | Internal; shipped as declarations with the package | `src/types.ts` |
+| `pragya-containers-http` | API | Pragya service team | `src/` | Externally owned; consumed, not published here | External: Webex service catalog pragya. `src/constants.ts` |
+| `ai-bridge-content-http` | API | AI Bridge service team | `src/` | Externally owned; URLs supplied at runtime by PragyaSummaryData | `src/types.ts` |
+| `webex-encryption-sdk` | SDK | Webex JS SDK Team | `src/` | Workspace peer; decryptText contract from @webex/internal-plugin-encryption | `package.json` |
+
+No repository-owned HTTP API exists, so no OpenAPI document is selected. See
+`.sdd/manifest.json` `contract_catalog` for the authoritative registry.
+
+## Cross-cutting architecture
+
+### Security
+
+- Trust boundaries and identity flow: all API calls (Pragya and content URLs) require a valid user bearer token, and the token is automatically attached by the SDK's HTTP layer.
+- Sensitive surfaces and data classes: AI-generated call content — notes, short notes, action items, and transcripts — is personal meeting content and is never logged in plaintext.
+- Encryption and secret boundaries: all AI-generated content is encrypted at rest with KMS, `encryptionKeyUrl` from Pragya container is the decryption key, and HTTPS required for all API calls.
+
+### Observability and operations
+
+- Logging and correlation: every public method catches failures and calls `this.logger.error` with a `AISummary->{method} failed` label before rethrowing a normalized error.
+- Metrics, traces, and audit signals: none are emitted by this package; the host SDK owns transport-level telemetry.
+- Ownership and operational entry points: Webex JS SDK Team; upstream availability is owned by the Pragya and AI Bridge service teams.
+
+### Quality attributes
+
+The package is an SDK, so its measurable boundaries are footprint and compatibility rather than
+service SLOs: it adds two workspace dependencies and no transitive runtime services, supports both
+browser and Node.js environments, and holds no state between calls. Content latency is dominated by
+the upstream Pragya and AI Bridge calls plus per-field KMS decryption, which runs concurrently
+through `Promise.all` for snippet collections.
+
+## Observability patterns
+
+| Signal | Convention or required fields | Propagation or naming rule | Primary evidence |
+| ------ | ----------------------------- | -------------------------- | ---------------- |
+| Logs | `this.logger.error` with the error and relevant identifiers | `AISummary->{methodName} failed` | `src/ai-summary.ts` |
+| Metrics | None emitted by this package | N/A | `src/ai-summary.ts` |
+| Traces | None emitted by this package | N/A | `src/ai-summary.ts` |
+| Audit | None emitted by this package; access control is enforced upstream | N/A | `src/ai-summary.ts` |
+
+## Shared and base libraries
+
+| Library | Inherited responsibility | Consumers | Version floor | Compatibility rule |
+| ------- | ------------------------ | --------- | ------------- | ------------------ |
+| `@webex/webex-core` | Base plugin class, request handling, auth interceptor | `src/` | `workspace:*` | Follows the monorepo's synchronized workspace version |
+| `@webex/internal-plugin-encryption` | KMS decryption via `decryptText` | `src/` | `workspace:*` | Follows the monorepo's synchronized workspace version |
+
+## Platform matrix
+
+| Platform | Shared versus platform-specific boundary | Entry or build | Support and compatibility constraints |
+| -------- | ---------------------------------------- | -------------- | ------------------------------------- |
+| Browser | Fully shared; no platform-specific source | `dist/index.js` via `yarn build` | Requires a registered device and Mercury connection for KMS |
+| Node.js | Fully shared; no platform-specific source | `dist/index.js` via `yarn build` | `engines.node >=16` per `package.json` |
+
+## Release and versioning
+
+| Artifact | Publish target | Versioning rule | Deprecation window | Changelog or migration obligation |
+| -------- | -------------- | --------------- | ------------------ | --------------------------------- |
+| `@webex/internal-plugin-call-ai-summary` | npm via `yarn deploy:npm` | Internal plugin; does not strictly adhere to semantic versioning | None declared | Monorepo release tooling owns changelog generation |
+
+## Host integration and theming
+
+| Host or integration | Mount or entry contract | Required providers or peers | Theming and accessibility constraints |
+| ------------------- | ----------------------- | --------------------------- | ------------------------------------- |
+| Webex JS SDK instance | `registerInternalPlugin('aisummary', ...)` on import; reachable at `webex.internal.aisummary` | An authenticated SDK instance with a registered device, plus `@webex/internal-plugin-encryption` | N/A — no UI surface |
+
+## Commands and generated artifacts
+
+| Command or artifact | Owner | Inputs | Output or side effect | Compatibility boundary |
+| ------------------- | ----- | ------ | --------------------- | ---------------------- |
+| `yarn build` | `src/` | `src/**/*.ts` | Compiled JS, type declarations, and maps in `dist/` | `main` entry point `dist/index.js` |
+| `yarn test:style` | `src/` | `src/**/*` | ESLint report | Repository lint configuration |
+| `yarn test:unit` | `src/` | Unit test sources | Jest run | No test sources exist yet; see the module spec |
+
+## Cross-repository topology
+
+| Repository or external system | Relationship | Exchanged contract or artifact | Owner | Sequencing constraint |
+| ----------------------------- | ------------ | ------------------------------ | ----- | --------------------- |
+| Janus | Consumes | `extensionPayload.callingContainerIds` from call history | Janus service team | Must run before container resolution |
+| Pragya | Consumes | Container metadata, content URLs, `encryptionKeyUrl` | Pragya service team | Must run before any content fetch |
+| AI Bridge | Consumes | Encrypted note, short note, action items, transcript | AI Bridge service team | Requires URLs from Pragya |
+| KMS | Consumes | Decryption keys addressed by `encryptionKeyUrl` | KMS service team | Requires device registration and Mercury |
+
+## Security architecture
+
+Authentication, authorization, and content protection are enforced across three boundaries. Only call participants or authorized users can access containers and summaries; org-level AI features must be enabled; and per-call consent means the AI assistant must have been enabled during the call. The package itself enforces none of these — it presents the user's bearer token and surfaces upstream 401/403 responses as normalized errors.
+
+All AI-generated content is encrypted using KMS (Key Management Service). The **Encryption Key** is the `encryptionKeyUrl` from the Pragya container response (format: `kms://kms-{region}.wbx2.com/keys/{key-id}`); the **Encrypted Fields** are `aiGeneratedContent` in notes and action item snippets; and **Decryption** uses `@webex/internal-plugin-encryption` via `decryptText()`. The SDK uses the existing `@webex/internal-plugin-encryption` plugin rather than implementing key handling locally.
+
+This is the same pattern used by existing plugins — the **AI Assistant Plugin** (`internal-plugin-ai-assistant/src/utils.ts`) and the **Task Plugin** (`internal-plugin-task/src/helpers/decrypt.helper.js`) both call `decryptText` with a key URL and ciphertext. The exact call shape is owned by `src/ai-summary.ts`.
+
+```mermaid
+flowchart LR
+  Principal[Webex user] -->|bearer token| Boundary[SDK auth interceptor]
+  Boundary --> Pragya[Pragya container ACL]
+  Pragya -->|encryptionKeyUrl| KMS[KMS key authority]
+  KMS -->|decrypted content| Protected[AI-generated call content]
+```
+
+## Domain language
+
+| Term | Repository-specific meaning | Authoritative source |
+| ---- | --------------------------- | -------------------- |
+| Container | A Pragya-owned record grouping the AI artifacts for one call, addressed by `containerId` | `src/types.ts` |
+| Pragya | The AI container service that resolves container IDs into content URLs and an encryption key | `src/constants.ts` |
+| AI Bridge | The service behind `summaryUrl`, `notesUrl`, `actionItemsUrl`, and `transcriptUrl` that serves encrypted content | `src/types.ts` |
+| Janus | The call-history service that surfaces `extensionPayload.callingContainerIds` | External |
+| Note / short note | The long and condensed AI-generated summaries of a call | `src/types.ts` |
+| Snippet | One action item or one timed transcript segment | `src/types.ts` |
+
+## References and maintenance
+
+- Decisions: [adr/](adr/)
+- Instantiated specifications and routing: [specs/README.md](specs/README.md)
+- Repository rules and patterns: [module specification](../src/docs/README.md)
+- Update this document in the same change that alters repository boundaries,
+  resource ownership, cross-resource interaction, or cross-cutting
+  architecture.

package/docs/getting-started.md

@@ -0,0 +1,147 @@
+---
+type: Getting Started
+title: Getting started
+description: Local setup, build, run, and test routing for @webex/internal-plugin-call-ai-summary.
+tags: [onboarding]
+---
+<!-- sdd-generated-metadata
+doc_kind: standing-doc
+generated_from: getting-started@0.3.0
+generated_by: claude-code
+approved_by: "@riag"
+updated_at: 2026-09-23T14:03:22Z
+validation_status: pass
+-->
+
+# Getting started
+
+Onboarding for **@webex/internal-plugin-call-ai-summary**.
+
+## Prerequisites
+
+| Tool or access                         | Version or requirement |
+| -------------------------------------- | ---------------------- |
+| Node.js                                | `>=16` per `package.json` |
+| Yarn (berry, workspace protocol)       | As pinned by the monorepo |
+| An authenticated Webex SDK instance with a registered device | Required |
+| `@webex/internal-plugin-encryption` (pulled in automatically as a dependency) | Workspace dependency |
+| A valid Pragya container ID (obtained from Janus call history `extensionPayload.callingContainerIds`) | Required for any live call |
+
+## Install
+
+This plugin is part of the Webex JS SDK monorepo. It self-registers when imported — no changes to `packages/webex` are needed.
+
+```bash
+yarn install   # From the SDK monorepo root
+```
+
+To use in a consuming application:
+
+```js
+// Importing the plugin auto-registers it on webex.internal.aisummary
+import '@webex/internal-plugin-call-ai-summary';
+```
+
+## Build
+
+```bash
+cd packages/@webex/internal-plugin-call-ai-summary
+yarn build
+```
+
+## Run
+
+This package is a library, not a runnable application. It becomes active when a consuming
+application imports it, exposing `webex.internal.aisummary`. To exercise it directly, use the manual
+scripts in the Tests section below.
+
+## Tests
+
+```bash
+yarn test:unit
+```
+
+Use the table as the repository-level test router. List only tiers that
+actually exist; behavioral intent belongs in the owning module specifications and exact
+cases remain in the repository's native test sources.
+
+| Tier         | Command              | Test location | Framework   | External dependencies               |
+| ------------ | -------------------- | ------------- | ----------- | ----------------------------------- |
+| Unit         | `yarn test:unit`     | `test/unit/spec/` | Jest via `@webex/jest-config-legacy` | None |
+| Manual       | `node src/manual-pragya-api-test.js` | `src/manual-pragya-api-test.js` | Plain Node script | Live Webex token |
+| Manual       | `node src/manual-integration-test.js` | `src/manual-integration-test.js` | Plain Node script | Live Webex token and container ID |
+
+- Coverage or quality gate: none. The repository owner verified on 2026-09-23 that no coverage gate applies to this package; no threshold exists in this package, in `@webex/jest-config-legacy`, or in any repository-level Sonar configuration.
+- Enforcement source: none found.
+- Test environment or QA dependencies: the manual scripts require live Pragya and AI Bridge access.
+
+The unit tier runs 38 tests from `test/unit/spec/ai-summary.ts`, with upstream wire fixtures in
+`test/unit/fixture/responses.ts`. Jest collects `test/unit/**` excluding `lib` and `fixture`, so new
+fixture files belong under `fixture/`.
+
+The suite needs only `engines.node >=16`; it is verified on Node 24.10 as well as the monorepo's
+pinned 22.14, so `nvm` is not required to run it.
+
+### Manual verification scripts
+
+Two manual test scripts are provided in `src/`. Both scripts require a valid Webex access token. Set `WEBEX_TOKEN` and optionally `CONTAINER_ID` as environment variables, or update the placeholders inside the scripts.
+
+`manual-pragya-api-test.js` validates the Pragya container response structure (34 checks).
+
+```bash
+cd packages/@webex/internal-plugin-call-ai-summary
+node src/manual-pragya-api-test.js
+```
+
+Provide the token as `WEBEX_TOKEN='<token>'` on the same line.
+
+A manual integration test is provided for verifying against live APIs. `manual-integration-test.js` tests the full end-to-end flow using the SDK service catalog:
+
+1. Device registration (WDM) to populate the service catalog
+2. `getContainer` via plugin (resolves `service: 'pragya'` from the catalog)
+3. `getSummary` via plugin (fetches + decrypts note, short note, and action items via KMS)
+4. `getTranscriptUrl` via plugin
+5. Transcript content fetch
+
+```bash
+cd packages/@webex/internal-plugin-call-ai-summary
+node src/manual-integration-test.js
+```
+
+Provide a fresh token and container ID as `WEBEX_TOKEN='<token>' CONTAINER_ID='<id>'` on the same line.
+
+This script registers a device (WDM), resolves the Pragya service via the SDK service catalog, fetches the container, decrypts summary content, and prints the results.
+
+## Configuration and secrets
+
+- Required configuration: none. `src/config.ts` declares an empty `aisummary` namespace.
+- Secret source: a Webex access token supplied at runtime by the host application, or `WEBEX_TOKEN` for the manual scripts.
+- Package or artifact access: the monorepo's configured npm registry.
+- Required neighboring repositories or workspace layout: the `webex-js-sdk` monorepo, because dependencies use the `workspace:*` protocol.
+- Platform, simulator, device, or SDK setup: a registered Webex device is required before any decryption can succeed.
+- Never commit credentials or copy production secrets into a local config.
+
+## Development
+
+```bash
+cd packages/@webex/internal-plugin-call-ai-summary
+yarn build        # Build
+yarn test:style   # Lint
+yarn test:unit    # Unit tests
+yarn test         # All checks
+```
+
+## First-run verification
+
+1. Run `yarn build` from the package directory.
+2. Check that `dist/index.js` and its type declarations are produced.
+3. Run `yarn test:style`.
+
+Expected result: the build emits `dist/` output and ESLint reports no errors.
+
+## Next steps
+
+- [Repository architecture](architecture.md)
+- [Module specification](../src/docs/README.md)
+- [Specification registry](specs/README.md)
+- [Documentation index](index.md)

package/docs/index.md

@@ -0,0 +1,53 @@
+---
+okf_version: '0.1'
+---
+<!-- sdd-generated-metadata
+doc_kind: standing-doc
+generated_from: docs-index@0.3.0
+generated_by: claude-code
+approved_by: "@riag"
+updated_at: 2026-09-23T14:03:22Z
+validation_status: pass
+-->
+
+# @webex/internal-plugin-call-ai-summary documentation
+
+Internal Webex JS SDK plugin for retrieving AI-generated call summaries, notes, action items, and transcripts from completed calls.
+
+This plugin resolves AI summary containers via the **Pragya** service and fetches encrypted summary content from URLs returned by Pragya. All content is decrypted through the Webex KMS encryption plugin before it reaches the caller.
+
+**Discovery flow:**
+
+1. **Janus** (call history) returns `extensionPayload.callingContainerIds` per call session
+2. **Pragya** resolves a container ID into metadata including content URLs and encryption key
+3. **Plugin** fetches content from those URLs and decrypts using `@webex/internal-plugin-encryption`
+
+## Start here
+
+- [Getting started](getting-started.md)
+- [Repository architecture](architecture.md)
+- [Module specification](../src/docs/README.md)
+
+This package is a published SDK plugin, not a deployable service, so no service specification or
+OpenAPI document is generated. See `.sdd/manifest.json` `layout.artifact_decisions` for the
+recorded reasoning.
+
+## Decisions
+
+- [adr/](adr/) — architectural decision records
+
+## Specifications and contracts
+
+- [architecture.md](architecture.md) — canonical repository-wide architecture
+- [specs/README.md](specs/README.md) — manifest-backed module and contract registry
+- `src/docs/README.md` — the owning specification beside the module's code
+- [adr/](adr/) — concrete architectural decisions; blank ADR templates remain under `.sdd/`
+
+Use the manifest-linked native source for exact contract details. The published SDK surface is owned
+by `src/index.ts` and `src/types.ts`; the Pragya and AI Bridge HTTP surfaces are externally owned and
+are registered in `.sdd/manifest.json` `contract_catalog` rather than copied into Markdown.
+
+## Related repository resources
+
+- `README.md` — the npm-facing package readme, including the full end-to-end usage example
+- `src/manual-pragya-api-test.js` and `src/manual-integration-test.js` — manual verification scripts

package/docs/specs/README.md

@@ -0,0 +1,83 @@
+---
+type: Reference
+title: Specification registry
+description: Canonical specification registry and change-routing guide.
+tags: [specifications, registry]
+---
+<!-- sdd-generated-metadata
+doc_kind: standing-doc
+generated_from: spec-index@0.3.0
+generated_by: claude-code
+approved_by: "@riag"
+updated_at: 2026-09-23T14:03:22Z
+validation_status: pass
+-->
+
+# Specification registry
+
+Use this page to find the canonical repository architecture and every
+instantiated service and module specification plus native contract. Keep technical facts
+in one owning document and use this page only for navigation, ownership,
+status, and change/test routing.
+
+Start with the [repository architecture](../architecture.md). This package contains no deployable
+service, so no service specification is generated.
+
+## Document roles
+
+| Document                                            | Canonical ownership                                                                                          |
+| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| [Repository architecture](../architecture.md)       | Repository boundaries, resource inventory, interactions, dependency topology, and cross-cutting architecture |
+| Module specifications                                | Stable behavior and design at each manifest-routed `<module-path>/docs/README.md`                              |
+| [ADR](../adr/)                                      | A durable decision, its deciders, rationale, consequences, and supersession lineage                          |
+
+## Instantiated specification registry
+
+| Resource   | Role                       | Canonical path         | Owner          | Status                                  | Last verified |
+| ---------- | -------------------------- | ---------------------- | -------------- | --------------------------------------- | ------------- |
+| Repository | Architecture               | `docs/architecture.md` | Webex JS SDK Team | Active                               | 2026-09-23    |
+| AI call summary plugin | Module         | `src/docs/README.md`   | Webex JS SDK Team | Active                               | 2026-09-23    |
+| ADR-0001   | Contract                   | `docs/adr/0001-flatten-container-response-and-prefer-single-request-summary.md` | Webex JS SDK Team | Active | 2026-09-23 |
+
+### Module registry
+
+One row per module in `.sdd/manifest.json`, which stays authoritative; this table is its
+human-readable mirror and the reconciliation surface for `scripts/check_spec_index.py`.
+
+| Module | Responsibility | Manifest coverage state | Start here |
+| --- | --- | --- | --- |
+| `src/` | Resolve Pragya containers and return decrypted AI call summary, notes, action items, and transcript content | Specced | `src/docs/README.md` |
+
+Coverage state is mirrored from `.sdd/manifest.json`. Generator-side field measurement is complete:
+the module is `Specced` at 100% public-surface coverage, assessed 2026-09-23, with independent
+validation reporting no drift. Behavior is verified by 38 unit tests in
+`test/unit/spec/ai-summary.ts`, covering every documented requirement including plugin registration.
+
+## Change and verification routing
+
+| Change affects                                          | Load and update                                                                   | Verification route                               |
+| ------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------ |
+| Repository boundaries or cross-cutting architecture     | `docs/architecture.md` and applicable ADRs                                        | Repository test routing and affected owner specs |
+| A stable code, package, or component boundary           | `src/docs/README.md`                                                              | Module tests plus affected contracts             |
+| A public API, event, command, package, or file contract | The owning architecture/module section plus the native definition                 | Compatibility and contract tests                 |
+| The published SDK surface or its types                  | `src/docs/README.md` Public surface plus `src/index.ts` and `src/types.ts`        | Compatibility checks; no automated tests exist yet |
+
+## Module and contract registration
+
+The module specification is generated directly at the exact `modules[].canonical_spec` path recorded
+in `.sdd/manifest.json`, which is `src/docs/README.md`.
+
+Six contracts are registered in `.sdd/manifest.json` `contract_catalog`:
+
+| Contract ID | Publication | Native source |
+| ----------- | ----------- | ------------- |
+| `aisummary-sdk` | internal | `src/ai-summary.ts` |
+| `aisummary-package-entry` | internal | `src/index.ts` |
+| `aisummary-types` | internal | `src/types.ts` |
+| `pragya-containers-http` | published, externally owned | External: Webex service catalog pragya. `src/constants.ts` |
+| `ai-bridge-content-http` | published, externally owned | URLs supplied at runtime by PragyaSummaryData. `src/types.ts` |
+| `webex-encryption-sdk` | internal | Workspace package @webex/internal-plugin-encryption. `package.json` |
+
+No repository-owned HTTP surface exists, so no `api-specs/openapi.yaml` is selected. The published
+SDK surface retains its ecosystem-native TypeScript declarations as the contract source. This page
+provides navigation and ownership rather than a copied contract.

package/package.json

@@ -40,8 +40,8 @@
     "build:src": "webex-legacy-tools build -dest \"./dist\" -src \"./src\" -js -ts -maps",
     "deploy:npm": "yarn npm publish",
     "test": "yarn test:style && yarn test:unit",
-    "test:style": "eslint ./src/**/*.*",
+    "test:style": "eslint ./src/**/*.{ts,js}",
     "test:unit": "webex-legacy-tools test --unit --runner jest"
   },
-  "version": "3.12.0-next.59"
+  "version": "3.12.0-next.60"
 }