@webex/contact-center 3.12.0-next.9 → 3.12.0-next.90

package/ai-docs/adr/0001-spec-source-policy.md

@@ -0,0 +1,55 @@
+# ADR-0001 — Migrate legacy Contact Center AI docs into canonical SDD specs
+
+| Field | Value |
+|---|---|
+| Status | Accepted |
+| Date | 2026-07-07 |
+| Deciders | Package maintainer / user |
+| Supersedes / Superseded by | none |
+
+## Context
+
+The Contact Center package already contained module-local `AGENTS.md`, `ARCHITECTURE.md`, pattern, and workflow documents before canonical SDD specifications were introduced. Those files contain useful intent and examples, but allowing them to remain co-equal with the generated `*-spec.md` files would make documentation routing ambiguous and could preserve statements that have drifted from `src/**` and `test/**`.
+
+The source inventory and canonical targets are recorded in `packages/@webex/contact-center/.sdd/manifest.json`. Code and tests remain the behavioral referee for every migrated statement.
+
+## Decision
+
+Use the `migrate-existing` source policy.
+
+- Preserve relevant legacy content by meaning in the canonical SDD specification for each module.
+- Treat manifest-routed legacy documents as reference-only migration sources, not canonical specifications.
+- Route agents through `.sdd/manifest.json` and `ai-docs/SPEC_INDEX.md` to the canonical target.
+- Retain legacy files with a banner pointing to their canonical target; if documentation conflicts with code or tests, code and tests win.
+
+The SDD route replaces the former package-local workflow, classification summary, specification-summary gate, and service-routing tables with one sequence: read package `AGENTS.md`, select the owning spec through `SPEC_INDEX.md`, verify requirements against source/tests, obtain approval for the affected files/contracts, update code and its owning spec together, and run generator-side conformance plus independent semantic validation before staging.
+
+| Module | Canonical target |
+|---|---|
+| `src` | `ai-docs/contact-center-spec.md` |
+| `src/metrics` | `src/metrics/ai-docs/metrics-spec.md` |
+| `src/services` | `src/services/ai-docs/services-spec.md` |
+| `src/services/agent` | `src/services/agent/ai-docs/agent-spec.md` |
+| `src/services/config` | `src/services/config/ai-docs/config-spec.md` |
+| `src/services/core` | `src/services/core/ai-docs/core-spec.md` |
+| `src/services/task` | `src/services/task/ai-docs/task-spec.md` |
+| `src/services/task/state-machine` | `src/services/task/state-machine/ai-docs/task-state-machine-spec.md` |
+| `src/utils` | `src/utils/ai-docs/utils-spec.md` |
+
+## Alternatives Considered
+
+| Alternative | Pros | Cons | Why rejected |
+|---|---|---|---|
+| Keep legacy and SDD docs separate and co-equal | No migration work | Agents must choose between competing authorities; drift remains likely | Does not establish deterministic routing |
+| Reconcile every legacy document in place | Preserves familiar paths | Keeps multiple canonical shapes and complicates validation | The package needs one template-compatible SDD surface |
+| Delete legacy documents after migration | Removes ambiguity | Loses useful historical examples and context | Reference material remains valuable when clearly marked noncanonical |
+
+## Consequences
+
+- **Positive:** Each module has one machine-routed canonical specification and a durable, reviewable policy record.
+- **Negative / cost:** Retained legacy documents require reference-only banners and must not be updated as independent authorities.
+- **Agents must:** Read the manifest and `SPEC_INDEX.md`, open the canonical `*-spec.md`, and cross-check behavior against source and tests.
+
+## Revisit When
+
+- A module is promoted from `Partial` to `Specced`, a canonical target is relocated, or a legacy file is proposed for removal.

package/ai-docs/adr/README.md

@@ -0,0 +1,8 @@
+# Architecture Decision Records
+
+Use this append-only directory for durable decisions that constrain future Contact Center SDK work.
+
+- One decision per `NNNN-short-title.md` file.
+- Accepted ADRs are immutable; supersede them with a new ADR.
+- Record Context, Decision, Alternatives Considered, Consequences, and Revisit When.
+- Link ADRs from the affected module specs and `ARCHITECTURE.md`.

package/ai-docs/adr/_adr-template.md

@@ -0,0 +1,31 @@
+# ADR-NNNN — Short decision title
+
+| Field | Value |
+|---|---|
+| Status | Proposed |
+| Date | YYYY-MM-DD |
+| Deciders | roles |
+| Supersedes / Superseded by | none |
+
+## Context
+
+State the code-grounded forces and evidence paths.
+
+## Decision
+
+State the directive.
+
+## Alternatives Considered
+
+| Alternative | Pros | Cons | Why rejected |
+|---|---|---|---|
+
+## Consequences
+
+- **Positive:**
+- **Negative / cost:**
+- **Agents must:**
+
+## Revisit When
+
+- Define a measurable reconsideration trigger.

package/ai-docs/contact-center-spec.md

@@ -0,0 +1,341 @@
+# Contact Center — SPEC
+
+> Start here → root [`AGENTS.md`](../AGENTS.md) · router [`SPEC_INDEX.md`](SPEC_INDEX.md) · system [`ARCHITECTURE.md`](ARCHITECTURE.md). This is the module's canonical specification.
+
+## Metadata
+
+| Field | Value |
+|---|---|
+| Module id | `contact-center` |
+| Source path(s) | `src` |
+| Doc kind | Module spec |
+| Coverage score | Partial (manifest-authoritative); 15/15 required document fields present |
+| Generated from | `module-spec` @ SDLC template library `0.2.1` |
+| generated_by / approved_by / updated_at | Codex generator / developer-approved follow-up review remediation / 2026-07-21 |
+| Validation status | Follow-up validation passed (independent Claude fallback, 2026-07-21); 1 existing test-coverage gap; coverage remains Partial |
+
+## Evidence Rules
+Every requirement cites stable source and test file paths. Code/tests are the behavioral referee; routed source text supplies explicit intent and rationale. Missing or contradictory evidence blocks promotion.
+
+## Source Material Register
+| Source material | Scope | Decision | Detail location or disposition |
+|---|---|---|---|
+| Reviewed prior module guides and architecture material | overview / architecture / API / tests | used and code-checked | Content is placed by meaning throughout this specification; exact routing remains in the manifest. |
+
+## Overview
+Contact Center is one of nine confirmed Contact Center SDK modules. Own the published Webex Contact Center SDK plugin surface, registration lifecycle, public method delegation, and application-facing event routing. Existing reviewed documentation is migrated by meaning and code/tests remain the behavioral referee.
+
+The `@webex/contact-center` package is a Webex SDK plugin that provides a TypeScript/JavaScript API for building Contact Center agent applications. It enables:
+
+- **Agent Session Management**: Register, login, logout, state changes
+
+- **Task Handling**: Inbound/outbound calls, chat, transfers, conferences
+
+- **Real-time Events**: WebSocket-based notifications for agent and task events
+
+- **Browser-based Calling**: WebRTC integration for browser softphone
+
+- **Metrics & Diagnostics**: Built-in telemetry and log upload
+
+## Purpose / Responsibility
+Own the published Webex Contact Center SDK plugin surface, registration lifecycle, public method delegation, and application-facing event routing.
+
+## Stack
+TypeScript 5.4, WebexPlugin, Node EventEmitter, WebSocket/WebRTC integrations, Jest 27, Yarn 3.4.1.
+
+## Folder / Package Structure
+```text
+src/
+├── index.ts                         package exports and plugin registration
+├── cc.ts                            ContactCenter façade and lifecycle orchestration
+├── types.ts                         package-level public contracts
+├── metrics/                         telemetry manager and taxonomy
+├── services/                        transport, agent, config, data, and calling collaborators
+│   ├── UserPreference.ts            user-preference CRUD REST client
+│   └── task/                        task objects, manager, media implementations, state machine
+└── utils/PageCache.ts               shared pagination cache
+```
+
+## Key Files (source of truth)
+| File | Holds |
+|---|---|
+| `src/index.ts` | Authoritative Contact Center implementation or contract source. |
+| `src/cc.ts` | Authoritative Contact Center implementation or contract source. |
+| `src/types.ts` | Authoritative Contact Center implementation or contract source. |
+| `src/constants.ts` | Authoritative Contact Center implementation or contract source. |
+| `src/config.ts` | Authoritative Contact Center implementation or contract source. |
+| `src/services/UserPreference.ts` | User-preference CRUD implementation exposed through `cc.userPreference`. |
+| `src/services/task/dialer.ts` | Preview-campaign AQM request implementations. |
+| `src/services/task/types.ts` | `PreviewContactPayload`, `TaskResponse`, and task contract types. |
+
+## Public Surface
+| Contract ID | Type | Surface | Purpose | Compatibility / deprecation | Schema / detail link | Root index |
+|---|---|---|---|---|---|---|
+| `contact-center.surface` | SDK / event / internal API | Published `@webex/contact-center` exports and the `ContactCenter` (`cc`) WebexPlugin API. | Stable module consumption boundary. | Additive changes by default; breaking package exports require a major-version transition. | `src/index.ts` | `CONTRACTS.md` |
+| `contact-center.user-preference` | SDK data API | Exported `UserPreference`, `cc.userPreference`, and user-preference request/response types. | Read and mutate user preferences through authenticated REST operations. | Additive public API; removals or signature changes are breaking. | `src/services/UserPreference.ts`, `src/services/config/types.ts` | `CONTRACTS.md` |
+| `contact-center.preview-campaign` | SDK task API | `acceptPreviewContact`, `skipPreviewContact`, `removePreviewContact`. | Resolve campaign preview reservations through typed AQM operations. | Additive public API; removals or signature changes are breaking. | `src/cc.ts`, `src/services/task/dialer.ts`, `src/services/task/types.ts` | `CONTRACTS.md` |
+
+Compatibility notes:
+- Do not remove or reinterpret exported symbols/events without a documented consumer migration.
+
+## Requires (dependencies)
+- Webex SDK host/plugin lifecycle
+- Contact Center REST and WebSocket backends
+- Services, TaskManager, MetricsManager, WebCallingService, UserPreference, and data-service modules
+
+## Requirements
+| ID | WHAT | WHY | Source Evidence | Test / Example Evidence | Assumptions / Gaps | Confidence |
+|---|---|---|---|---|---|---|
+| CONTACT_CENTER-R-001 | Construct the service graph once after the host Webex SDK emits READY, before `register()` is invoked. | Collaborators require initialized host request, logger, and plugin configuration state. | `src/cc.ts` | `test/unit/spec/cc.ts` | None; source and test evidence rechecked during the 2026-07-09 remediation; independent document revalidation pending. | PRESENT |
+| CONTACT_CENTER-R-002 | `register()` must attach connection/message listeners, connect the primary WebSocket, and return the fetched Profile or rethrow a logged failure. | Applications need an explicit readiness boundary and must never observe a synthetic successful registration. | `src/cc.ts` | `test/unit/spec/cc.ts` | None; source and test evidence rechecked during the 2026-07-09 remediation; independent document revalidation pending. | PRESENT |
+| CONTACT_CENTER-R-003 | Delegate agent, task, data, user-preference, preview-campaign, AI-assistant, calling, and telemetry behavior to their owning collaborators while preserving typed package methods and events. Before preview delegation, reject disabled skip/remove actions from task campaign flags. | A stable façade keeps consumer compatibility while specialized modules retain transport and lifecycle ownership; campaign controls must prevent prohibited backend operations. | `src/cc.ts`, `src/services/UserPreference.ts`, `src/services/task/dialer.ts` | `test/unit/spec/cc.ts`, `test/unit/spec/services/UserPreference.ts`, `test/unit/spec/services/task/dialer.ts` | Public preview delegation is covered; the `campaignPreviewSkipDisabled` and `campaignPreviewRemoveDisabled` early-exit guards lack direct unit coverage. Independent review identified this gap on 2026-07-15. | PRESENT |
+| CONTACT_CENTER-R-004 | `deregister()` must remove registered listeners, stop applicable host/calling resources, close primary and RTD WebSockets, clear agent configuration, and surface cleanup failures. | Listener or connection leaks create duplicate events and stale authenticated sessions in long-lived hosts. | `src/cc.ts` | `test/unit/spec/cc.ts` | None; source and test evidence rechecked during the 2026-07-09 remediation; independent document revalidation pending. | PRESENT |
+| CONTACT_CENTER-R-005 | On `connectionLost`, ContactCenter must own recovery policy and invoke private `silentRelogin()` only when automated relogin is allowed. | ConnectionService reports transport state; only ContactCenter has agent profile and policy context for authentication recovery. | `src/cc.ts` | `test/unit/spec/cc.ts` | None; source and test evidence rechecked during the 2026-07-09 remediation; independent document revalidation pending. | PRESENT |
+
+## Design Overview
+`ContactCenter` is the package façade and lifecycle owner. Its constructor waits for the host Webex SDK `READY` event, validates plugin configuration, initializes `WebexRequest`, obtains the singleton `Services` graph, and constructs calling, AI-assistant, metrics, task-management, `UserPreference`, and data-service collaborators. `register()` is deliberately narrower: it attaches runtime listeners and establishes the primary Contact Center WebSocket subscription.
+
+Direct data/configuration and user-preference operations return authenticated REST responses. Enabled agent/task AQM operations, including preview-campaign accept/skip/remove, send authenticated HTTP requests but resolve or reject only after a matching WebSocket notification. Before delegating preview skip/remove, ContactCenter checks the task's campaign-disable flags and throws locally when the corresponding flag is `'true'`. TaskManager converts backend task events into Task instances and typed state-machine events. ContactCenter maps package-facing events through WebexPlugin `trigger` or its internal EventEmitter according to the published contract.
+
+Durable agent, task, and configuration records remain remote-system owned. The package owns only in-memory profile/task/listener/cache/connection state.
+
+## Data Flow
+```mermaid
+flowchart TD
+  Host[Host Webex SDK READY] --> Validate[Validate plugin config]
+  Validate --> WR[Initialize WebexRequest]
+  WR --> Services[Services singleton: agent/config/contact/dialer + primary/RTD WebSockets]
+  Services --> Collaborators[Create WebCalling, ApiAIAssistant, Metrics, TaskManager, UserPreference, data services]
+  Collaborators --> Register[Application calls register]
+  Register --> Listeners[Attach connection and message listeners]
+  Listeners --> Connect[Subscribe/connect primary WebSocket]
+  Connect --> Profile[Fetch/return Profile]
+  Profile --> App[Application invokes typed cc methods]
+  App --> Direct[Direct REST data/config]
+  App --> AQM[AQM HTTP initiation]
+  AQM --> WS[Correlated WebSocket completion]
+  Direct --> App
+  WS --> App
+```
+
+## Sequence Diagram(s)
+Sequence coverage:
+
+| Operation group | Diagram | Failure / recovery coverage |
+|---|---|---|
+| READY-time bootstrap | Bootstrap | Invalid configuration or collaborator initialization rejects readiness-dependent use. |
+| Registration | Register | Connection/subscription failure is logged, metrics record failure, logs upload, and the error is rethrown. |
+| Deregistration | Deregister | Cleanup failure is measured, logged, and rethrown; no synthetic success. |
+| Connection recovery | Recovery | ConnectionService emits state; ContactCenter chooses silent relogin or preserves failure state. |
+
+### Bootstrap
+
+```mermaid
+sequenceDiagram
+  participant Host as Host Webex SDK
+  participant CC as ContactCenter
+  participant S as Services
+  participant TM as TaskManager
+  Host-->>CC: READY
+  CC->>CC: validatePluginConfig()
+  alt configuration valid
+    CC->>CC: WebexRequest.getInstance(webex)
+    CC->>S: Services.getInstance(webex, connectionConfig)
+    CC->>CC: create WebCallingService + ApiAIAssistant + MetricsManager
+    CC->>TM: getTaskManager(aiAssistant, contact, calling, primaryWS, rtdWS)
+    CC->>CC: create EntryPoint + AddressBook + Queue; initialize LoggerProxy
+  else invalid configuration or initialization failure
+    CC-->>Host: readiness-dependent use rejects
+  end
+```
+
+### Register
+
+```mermaid
+sequenceDiagram
+  participant App
+  participant CC as ContactCenter
+  participant WS as Primary WebSocketManager
+  participant Cfg as AgentConfigService
+  participant Agent as Services.agent
+  participant Metrics
+  App->>CC: register()
+  CC->>CC: setupEventListeners(); listen for WS messages
+  CC->>Metrics: time register success/failure
+  CC->>WS: initWebSocket({body, resource: SUBSCRIBE_API})
+  WS-->>CC: Welcome data containing agentId
+  CC->>Cfg: getAgentConfig(orgId, agentId)
+  alt profile fetched
+    Cfg-->>CC: Profile
+    CC->>CC: set TaskManager/config/AI flags
+    opt applicable AI feature enabled
+      CC->>CC: start RTD WebSocket; log but contain RTD failure
+    end
+    opt browser calling applicable
+      CC->>CC: mercury.connect(); log but contain failure
+    end
+    opt allowAutomatedRelogin
+      CC->>Agent: reload()
+      Agent-->>CC: relogin result, AGENT_NOT_FOUND, or error
+    end
+    CC->>Metrics: track registration success
+    CC-->>App: Profile
+  else primary subscription/profile/relogin failure
+    CC->>Metrics: track registration failure
+    CC->>CC: uploadLogs(correlationId)
+    CC-->>App: throw error
+  end
+```
+
+### Deregister
+
+```mermaid
+sequenceDiagram
+  participant App
+  participant CC as ContactCenter
+  participant Host as Mercury/device
+  participant WS as Primary + RTD WebSockets
+  App->>CC: deregister()
+  CC->>CC: remove TaskManager/message/connection listeners
+  opt browser calling resources active
+    CC->>Host: disconnect Mercury; unregister device
+  end
+  CC->>WS: close(false, reason)
+  CC->>CC: agentConfig = null
+  alt cleanup succeeds
+    CC-->>App: void
+  else cleanup fails
+    CC-->>App: throw error
+  end
+```
+
+### Recovery
+
+```mermaid
+sequenceDiagram
+  participant CS as ConnectionService
+  participant CC as ContactCenter
+  participant Agent as Services.agent
+  CS-->>CC: connectionLost(details)
+  CC->>CC: handleConnectionLost(details)
+  alt allowAutomatedRelogin
+    CC->>CC: silentRelogin()
+    CC->>Agent: reload()
+    alt relogin succeeds
+      Agent-->>CC: relogin result; update agent config/device state
+    else AGENT_NOT_FOUND
+      Agent-->>CC: handled silently
+    else other failure
+      Agent--xCC: throw detailed error
+    end
+  else disabled
+    CC->>CC: make no relogin call; retain reported transport state
+  end
+```
+
+## Class / Component Relationships
+```mermaid
+classDiagram
+  class ContactCenter
+  class Services
+  class WebexRequest
+  class MetricsManager
+  class TaskManager
+  class WebCallingService
+  class ApiAIAssistant
+  class EntryPoint
+  class AddressBook
+  class Queue
+  ContactCenter --> WebexRequest : initializes/uses for log upload
+  ContactCenter --> Services : agent/config/contact/dialer + WebSockets
+  ContactCenter --> MetricsManager : timings and tracking
+  ContactCenter --> TaskManager : task lifecycle/events
+  ContactCenter --> WebCallingService : browser calling
+  ContactCenter --> ApiAIAssistant : transcript/suggestion API
+  ContactCenter --> EntryPoint
+  ContactCenter --> AddressBook
+  ContactCenter --> Queue
+  TaskManager --> ApiAIAssistant
+  TaskManager --> WebCallingService
+```
+
+## Use Cases
+- **UC-1 Host bootstrap:** after host READY, initialize the complete collaborator graph exactly once. Evidence: `src/cc.ts`, `test/unit/spec/cc.ts`.
+- **UC-2 Register:** attach listeners and establish the primary WebSocket subscription before returning Profile. Evidence: `src/cc.ts`, `test/unit/spec/cc.ts`.
+- **UC-3 Delegate SDK operations:** validate/map public inputs, call the owning collaborator, track metrics, and return or emit typed results. Evidence: `src/cc.ts`, `src/index.ts`, `test/unit/spec/cc.ts`.
+- **UC-4 Recover connection:** consume ConnectionService state and conditionally reload the agent session through ContactCenter policy. Evidence: `src/cc.ts`, `test/unit/spec/cc.ts`.
+- **UC-5 Deregister:** remove the same listener identities, shut down applicable host/WebSocket resources, and clear in-memory profile state. Evidence: `src/cc.ts`, `test/unit/spec/cc.ts`.
+
+## State Model
+ContactCenter retains in-memory `agentConfig`, collaborator references, event listeners, task collections through TaskManager, and connection/recovery state. Remote Webex services remain authoritative for agent, task, and organization data. Registration establishes runtime connectivity but does not imply station login; deregistration tears down SDK resources but does not itself perform station logout.
+
+## Business Rules & Invariants
+- Collaborators are initialized after host READY and before their use; `register()` must not be documented as their constructor boundary. Evidence: `src/cc.ts`.
+- AQM promises complete only from correlated WebSocket success/failure or timeout, not from HTTP acknowledgement. Evidence: `src/services/core/aqm-reqs.ts`.
+- `skipPreviewContact` checks `campaignPreviewSkipDisabled` and `removePreviewContact` checks `campaignPreviewRemoveDisabled` on the matching task. When the applicable value is `'true'`, ContactCenter throws before initiating an HTTP or WebSocket-correlated AQM operation; `acceptPreviewContact` has no equivalent pre-guard. Evidence: `src/cc.ts`.
+- ContactCenter owns automated relogin policy; ConnectionService owns transport-state detection/emission. Evidence: `src/cc.ts`, `src/services/core/websocket/connection-service.ts`.
+- Deregistration does not station-logout the agent. Evidence: `src/cc.ts`.
+- Published methods/types/events remain semver-sensitive through `src/index.ts`.
+
+## Concurrency & Reactive Flow
+READY initialization, REST promises, AQM WebSocket correlation, TaskManager events, calling events, and connection timers execute asynchronously. Listener cleanup must use the registered function identity. Message listeners are independent: AqmReqs correlates pending requests, ContactCenter maps package events, TaskManager owns task lifecycle, and ConnectionService tracks liveness/reconnect state.
+
+## State Machine
+```mermaid
+stateDiagram-v2
+  [*] --> AwaitingHostReady
+  AwaitingHostReady --> Initialized: host READY + collaborators created
+  Initialized --> Registering: register()
+  Registering --> Registered: WebSocket/profile success
+  Registering --> Initialized: registration failure
+  Registered --> Recovering: connectionLost
+  Recovering --> Registered: reconnect/relogin succeeds
+  Recovering --> Registered: relogin disabled; transport state reported
+  Registered --> Deregistering: deregister()
+  Deregistering --> Initialized: listeners/resources cleared
+  Deregistering --> Registered: cleanup throws before completion
+```
+
+## Protocol / Wire Format
+Authenticated REST initiates direct data/config operations and AQM agent/task operations. For AQM, the HTTP response is acknowledgement only; `notifSuccess.bind`/`notifFail.bind` match WebSocket payloads that settle the promise. The primary WebSocket carries Contact Center notifications; the RTD WebSocket carries transcript/suggestion traffic. Payload and event names are owned by `src/types.ts`, `src/services/config/types.ts`, `src/services/agent/types.ts`, and `src/services/task/types.ts`.
+
+## Error Handling & Failure Modes
+| Condition | Signal (error/code/result) | Caller recovery |
+|---|---|---|
+| Dependency rejection | Typed/rethrown error or failure event | Inspect structured details, preserve tracking id, and retry only when the operation is safe. |
+| Timeout or missing async completion | Timeout/recovery state | Follow the module-specific recovery path; never synthesize success. |
+
+## Pitfalls
+- READY-time construction and `register()` are different lifecycle boundaries; moving collaborator creation into `register()` can duplicate listeners and use uninitialized host services.
+- AQM HTTP responses are acknowledgements, not operation completion; only a correlated WebSocket notification or timeout settles the operation.
+- Listener cleanup must use the same bound function identities registered during setup or repeated register/deregister cycles will leak handlers.
+
+## Module Do's / Don'ts
+- DO construct the collaborator graph only after host READY and keep registration focused on listeners, subscription, and profile retrieval.
+- DO route agent recovery decisions through ContactCenter because it owns profile/config policy.
+- DON'T synthesize successful register/deregister results after a dependency or cleanup failure.
+- DON'T let transport services call `silentRelogin()` directly.
+
+## Export Stability
+The npm export/type-declaration surface is semver-sensitive. Additive optional types are compatible; removals, renames, or semantic changes require a major-version migration and changelog entry.
+
+## Host Integration & Theming
+The module registers as `cc` through the Webex SDK plugin system and depends on host-provided Webex credentials, configuration, request routing, and lifecycle events. It renders no UI and defines no theme contract.
+
+## Key Design Trade-off
+- A single plugin surface centralizes compatibility and event routing, while specialized modules retain implementation ownership; this costs careful bootstrap and cleanup ordering.
+
+## Test-Case Strategy (module)
+`test/unit/spec/cc.ts` is the characterization baseline. Cover READY-time construction, registration success/failure, listener identity, public method delegation, WebSocket event mapping, preview-campaign operations (including disabled skip/remove pre-guards), automated-relogin enabled/disabled branches, browser-calling conditions, and deregistration cleanup/error paths. Use `test/unit/spec/services/UserPreference.ts` for user-preference CRUD and `test/unit/spec/services/task/dialer.ts` for preview AQM request contracts. Preserve the package-wide 85% branch/function/line/statement threshold.
+
+| Requirement | Existing evidence | Required revalidation |
+|---|---|---|
+| CONTACT_CENTER-R-001 | `test/unit/spec/cc.ts` | READY-time ownership and initialization order |
+| CONTACT_CENTER-R-002 | `test/unit/spec/cc.ts` | register success/failure and log-upload path |
+| CONTACT_CENTER-R-003 | `test/unit/spec/cc.ts`, `test/unit/spec/services/UserPreference.ts`, `test/unit/spec/services/task/dialer.ts` | Add direct tests proving disabled skip/remove flags throw before dialer invocation; revalidate typed delegation, user-preference CRUD, preview-campaign AQM operations, and event routing. |
+| CONTACT_CENTER-R-004 | `test/unit/spec/cc.ts` | listener/resource cleanup and error propagation |
+| CONTACT_CENTER-R-005 | `test/unit/spec/cc.ts` | relogin policy ownership |
+
+## Traceability
+- Repo architecture: `ARCHITECTURE.md` · Registry: `SPEC_INDEX.md`
+- Coverage state and contracts baseline: `../.sdd/manifest.json`

package/ai-docs/features/generated-spec-conformance-fidelity-remediation/spec/feature-spec.md

@@ -0,0 +1,117 @@
+# Feature Spec — Generated Spec Conformance and Fidelity Remediation
+
+> Start here → package root [`AGENTS.md`](../../../../AGENTS.md) · router [`SPEC_INDEX.md`](../../../SPEC_INDEX.md) · system [`ARCHITECTURE.md`](../../../ARCHITECTURE.md). This is a documentation-only protected-spec delta. It authorizes canonical documentation corrections but no runtime, test, or manifest change.
+
+## Metadata
+
+| Field | Value |
+|---|---|
+| Feature / ticket key | `CC-SDD-CONFORMANCE-FIDELITY-20260709` |
+| Title | Generated module-spec conformance and source-fidelity remediation |
+| Status | applied; generator-side source fidelity, conformance, and coverage pass; independent validation pending |
+| Change class | documentation-only MODIFIED conformance and fidelity correction |
+| created_by / approved_by / date | Codex generator / developer / 2026-07-09 |
+| Generated from | `feature-spec` @ SDLC template library `0.2.1` |
+
+## Problem & Goal
+
+The prior deterministic conformance pass checked section presence but did not verify that sequence-inventory rows mapped to actual operation-specific diagrams, that migrated diagrams appeared in the canonical section selected by meaning, or that every required section remained concrete after migration. A read-only brownfield audit found cross-module structural and source-fidelity gaps despite clean semantic validation metadata.
+
+The goal is to make all nine module specs satisfy the full module-spec output contract while preserving current source behavior and routed legacy detail.
+
+## Scope
+
+In scope:
+
+- Repair sequence inventories, diagram placement, operation coverage, and error/timeout/retry/recovery branches.
+- Correct Task AQM completion semantics and Utils cache-key scope semantics from current source.
+- Add complete requirement-to-test mappings.
+- Replace generic pitfalls and module conventions with code-grounded module-specific content.
+- Remove stale validation-pending text and superseded local-doc routing artifacts.
+- Normalize mechanically fragmented tables without dropping rows.
+- Reconcile diagram dispositions in source-fidelity inventories and rerun generator-side gates.
+
+Out of scope:
+
+- Runtime source or test changes.
+- Public API, event, behavior, transport, timeout, or compatibility changes.
+- `.sdd/manifest.json` edits or coverage-status promotion.
+- Independent validator acceptance on the generator runtime.
+
+## Requirements
+
+| ID | WHAT | WHY | Acceptance | State |
+|---|---|---|---|---|
+| REMEDIATION-R-001 | Every Sequence Diagram(s) inventory must map each distinct operation group to an actual titled diagram or an explicitly justified shared diagram. | A table that advertises uncovered flows is not actionable documentation. | Coverage rows and diagrams agree; distinct failure/state outcomes are diagrammed. | Approved |
+| REMEDIATION-R-002 | Migrated flow, sequence, class, and state diagrams must appear in the canonical section selected by meaning and remain one-for-one unless code requires a recorded correction. | Source fidelity cannot be satisfied by retaining valid detail only in superseded documents. | Diagram inventory targets/statuses and canonical placement agree. | Approved |
+| REMEDIATION-R-003 | Every module test strategy must map every requirement ID to concrete test files and an explicit remaining gap. | Prose-only testing guidance cannot prove requirement coverage. | Nine complete requirement-to-test matrices. | Approved |
+| REMEDIATION-R-004 | Pitfalls and module conventions must name module-specific failure modes, ownership boundaries, constants, events, or lifecycle constraints. | Generic boilerplate is not evidence-backed maintenance guidance. | No repeated generic ownership/raw-string boilerplate remains. | Approved |
+| REMEDIATION-R-005 | Correct Task AQM and Utils cache-key descriptions to current source behavior. | The existing Task diagram treats HTTP acknowledgement as completion, and Utils overstates `orgId` as the only runtime scope key. | AQM resolves on matched WebSocket completion; cache scope records `orgId` or `bookId` by consumer. | Approved |
+| REMEDIATION-R-006 | Remove stale validation-pending cells and legacy “this file”/superseded-doc navigation from canonical specs. | Canonical docs must describe their current status and route readers to canonical surfaces. | Metadata and requirement gap cells agree; no module-local legacy doc is presented as canonical. | Approved |
+| REMEDIATION-R-007 | Preserve all current table rows while consolidating repeated one-row table fragments. | Mechanical migration fragmentation harms reviewability and can conceal omissions. | Repeated adjacent identical table headers are consolidated without data loss. | Approved |
+
+## MODIFIED Requirements
+
+### MOD-001 — Contact Center
+
+Name and map its four lifecycle sequence diagrams, add the bootstrap rejection branch, complete concrete pitfalls/conventions, and retain its full requirement-to-test matrix.
+
+### MOD-002 — Metrics
+
+Preserve the two legacy sequences, add explicit disabled/submission-error coverage, complete the test matrix, and normalize event/taxonomy tables.
+
+### MOD-003 — Services
+
+Add the missing direct-REST sequence, use the three-column sequence inventory, complete the test matrix, and remove copied legacy-file identity text.
+
+### MOD-004 — Agent
+
+Restore code-supported station-login, state-change, WebSocket-event, and relogin detail; add logout/buddy coverage; correct legacy diagram dispositions; and complete the test matrix.
+
+### MOD-005 — Config
+
+Keep the corrected ten-result profile aggregation, add pagination coverage, complete the test matrix, and normalize API/type tables.
+
+### MOD-006 — Core
+
+Add authenticated REST coverage, diagram duplicate-pending/offline retry behavior, identify private helpers as internal, correct diagram dispositions, and complete the test matrix.
+
+### MOD-007 — Task
+
+Move legacy sequences from Data Flow to Sequence Diagram(s), correct AQM completion, add all five operation-group diagrams, and complete the test matrix.
+
+### MOD-008 — Task state machine
+
+Add group-specific sequences for offer/assignment, hold/resume, consult, conference/transfer, wrapup/termination, and hydration; preserve exact state diagrams; complete the test matrix.
+
+### MOD-009 — Utils
+
+Describe the caller-supplied cache scope accurately, add lookup/store and clear sequences with backend failure behavior, correct legacy diagram disposition, and complete the test matrix.
+
+### MOD-010 — Cross-module audit state
+
+Refresh source-fidelity dispositions, conformance evidence, validation metadata/gap wording, local navigation, and decision logs without modifying the manifest.
+
+## Acceptance Criteria
+
+- All nine specs pass template/profile/heading/link/placeholder checks.
+- Every sequence inventory maps to actual diagrams with applicable failure/recovery behavior.
+- No sequence diagram remains in Task Data Flow.
+- Task AQM diagrams distinguish HTTP acknowledgement from WebSocket settlement.
+- Utils documents the real consumer scope (`orgId` for EntryPoint/Queue; `bookId` for AddressBook).
+- Every requirement ID appears in its module's test-strategy matrix.
+- No runtime/test file changes and manifest hash remains unchanged.
+- Generator-side source-fidelity and conformance pass before independent validator handoff.
+
+## Change Log
+
+| Date | Change | By | Why |
+|---|---|---|---|
+| 2026-07-09 | Created and approved MOD-001 through MOD-010 | Codex + developer | Repair all-module brownfield conformance and source-fidelity gaps found by read-only audit |
+| 2026-07-09 | Applied remediation and completed generator-side gates | Codex | 12/12 fidelity inventories, 9/9 module conformance, and 9/9 coverage pass; manifest unchanged |
+
+## References
+
+- Current behavior: `src/` and `test/`
+- Canonical routing: [`SPEC_INDEX.md`](../../../SPEC_INDEX.md)
+- Public contract index: [`CONTRACTS.md`](../../../CONTRACTS.md)