@breadstone/archipel-mcp 0.0.22 → 0.0.25

package/README.md

@@ -1,6 +1,6 @@
 # @breadstone/archipel-mcp
 
-MCP (Model Context Protocol) server that provides Archipel platform knowledge — documentation and query patterns — to AI development tools. The server acts as a structured knowledge provider: AI models combine this knowledge with the user's project context to generate framework-compliant code.
+MCP (Model Context Protocol) server that provides Archipel platform knowledge - documentation and query patterns - to AI development tools. The server acts as a structured knowledge provider: AI models combine this knowledge with the user's project context to generate framework-compliant code.
 
 ## Usage
 
@@ -40,30 +40,49 @@ npx @breadstone/archipel-mcp
 Returns the complete Archipel v1 query pattern: `IRepositoryQuery` interface, `query()` factory, `QueryResultType`, transactional queries, rules, and usage examples. When a `modelName` and `fields` array are provided, it generates tailored `findFirst`, `findMany`, and `count` query examples for that model.
 
 ```
-modelName?: string   — Prisma model name (e.g. "User")
-fields?: string[]    — Field names (e.g. ["id", "email", "name", "createdAt"])
+modelName?: string   - Prisma model name (e.g. "User")
+fields?: string[]    - Field names (e.g. ["id", "email", "name", "createdAt"])
 ```
 
 ## Architecture
 
 Plain Node.js MCP server using `@modelcontextprotocol/sdk`. No NestJS, no DI container.
 
-```
-main.ts                          ← CLI entry (stdio transport, tool registration)
-DocsLoader.ts                    ← Loads & indexes .docs/packages/ markdown files
-models/
-└── IPackageDoc.ts               ← Package documentation interface
-knowledge/
-└── queryPattern.ts              ← Query pattern knowledge content
+```mermaid
+flowchart TB
+  MainTs[main.ts\nCLI entry\nstdio transport + tool registration]
+  DocsLoader[DocsLoader.ts\nLoads and indexes .docs/packages]
+  GuidesLoader[GuidesLoader.ts\nLoads and indexes .docs/guides]
+  PatternsLoader[PatternsLoader.ts\nLoads and indexes .docs/patterns]
+
+  subgraph Models[models/]
+    IPackageDoc[IPackageDoc.ts\nPackage documentation interface]
+    IGuideDoc[IGuideDoc.ts\nGuide documentation interface]
+    IPatternDoc[IPatternDoc.ts\nPattern documentation interface]
+  end
+
+  subgraph Generators[generators/]
+    QueryGenerator[queryPatternGenerator.ts]
+    RepositoryGenerator[repositoryPatternGenerator.ts]
+    MappingGenerator[mappingPatternGenerator.ts]
+    ModuleGenerator[modulePatternGenerator.ts]
+  end
+
+  MainTs --> DocsLoader
+  MainTs --> GuidesLoader
+  MainTs --> PatternsLoader
+  DocsLoader --> IPackageDoc
+  GuidesLoader --> IGuideDoc
+  PatternsLoader --> IPatternDoc
 ```
 
 ### Documentation Resolution
 
 The server locates docs in this order:
 
-1. **Bundled data** — `<package>/data/packages/` (shipped with the npm package)
-2. **Workspace root** — `<cwd>/.docs/packages/` (monorepo development)
-3. **Relative fallback** — walks up from compiled source to find `.docs/packages/`
+1. **Bundled data** - `<package>/data/packages/` (shipped with the npm package)
+2. **Workspace root** - `<cwd>/.docs/packages/` (monorepo development)
+3. **Relative fallback** - walks up from compiled source to find `.docs/packages/`
 
 ## Development
 

package/data/guides/ai-text-generation.md

@@ -368,28 +368,20 @@ If an AI SDK provider package is not installed, the error message clearly states
 
 ## Architecture Overview
 
-```
-┌────────────────────────────────────┐
-│         IntelligenceModule         │
-│                                    │
-│  ┌──────────────────────────────┐  │
-│  │  IntelligenceTextGenerator   │──┼── generateText(prompt, options?)
-│  │  (ConfigService → provider)  │  │
-│  └──────────────────────────────┘  │
-│                                    │
-│  ┌──────────────────────────────┐  │
-│  │  IntelligenceCapability      │──┼── resolve(intent, context)
-│  │  Registry                    │  │   register(capability)
-│  └──────────────────────────────┘  │
-└────────────────────────────────────┘
-         │                │
-         ▼                ▼
-  ┌─────────────┐  ┌──────────────┐
-  │ Provider     │  │ Feature      │
-  │ Loaders      │  │ Capabilities │
-  │ (OpenAI,     │  │ (custom      │
-  │  Anthropic,  │  │  handlers)   │
-  │  Google,     │  │              │
-  │  Grok)       │  │              │
-  └─────────────┘  └──────────────┘
+```mermaid
+flowchart TB
+  subgraph IntelligenceModule[IntelligenceModule]
+    TextGenerator[IntelligenceTextGenerator\nConfigService -> provider]
+    CapabilityRegistry[IntelligenceCapability Registry]
+  end
+
+  GenerateText["generateText(prompt, options?)"]
+  ResolveCapability["resolve(intent, context)\nregister(capability)"]
+  ProviderLoaders[Provider Loaders\nOpenAI, Anthropic, Google, Grok]
+  FeatureCapabilities[Feature Capabilities\ncustom handlers]
+
+  TextGenerator --> GenerateText
+  CapabilityRegistry --> ResolveCapability
+  TextGenerator --> ProviderLoaders
+  CapabilityRegistry --> FeatureCapabilities
 ```

package/data/guides/caching.md

@@ -24,6 +24,39 @@ yarn add ioredis
 
 ---
 
+## Configuration
+
+### Core Variables
+
+```env
+CACHE_DEFAULT_TTL_MS=60000
+CACHE_MAX_ENTRIES=1000
+CACHE_STALE_WHILE_REVALIDATE=false
+```
+
+All core variables are optional. When omitted, each cache instance uses the values passed directly to its constructor options.
+
+### Redis Variables
+
+```env
+REDIS_URL=redis://localhost:6379
+REDIS_KEY_PREFIX=app:
+REDIS_TTL_SECONDS=300
+```
+
+`REDIS_URL` is required when using `RedisLayeredCache`. The other variables are optional.
+
+### Using Config Keys
+
+Import the typed config keys and pass them to your module registration:
+
+```typescript
+import { PLATFORM_CACHING_CONFIG_ENTRIES } from '@breadstone/archipel-platform-caching';
+import { REDIS_CONFIG_ENTRIES } from '@breadstone/archipel-platform-caching/redis';
+```
+
+---
+
 ## Concepts
 
 `platform-caching` provides a generic `ILayeredCache<TKey, TValue>` interface with two implementations:

package/data/guides/email-delivery.md

@@ -147,7 +147,33 @@ The `template` field is the template name (without extension). The `context` obj
 
 ---
 
-## Email Verification
+## SMTP Connection Verification
+
+`SmtpConnectionVerifier` verifies SMTP server connectivity and optionally sends a test email. It replaces the deprecated `MailVerificationService`.
+
+```typescript
+import { Injectable } from '@nestjs/common';
+import { SmtpConnectionVerifier } from '@breadstone/archipel-platform-mailing';
+
+@Injectable()
+export class HealthService {
+  constructor(private readonly _smtpVerifier: SmtpConnectionVerifier) {}
+
+  public async checkSmtpConnectivity(): Promise<boolean> {
+    return this._smtpVerifier.verifyConnection();
+  }
+
+  public async sendTestEmail(to: string): Promise<boolean> {
+    return this._smtpVerifier.sendTestEmail(to);
+  }
+}
+```
+
+## Email Verification (Deprecated)
+
+::: warning Deprecated
+`MailVerificationService` is deprecated. Use `SmtpConnectionVerifier` for SMTP connectivity checks.
+:::
 
 `MailVerificationService` provides a complete email verification flow:
 

package/data/guides/email-templates.md

@@ -16,16 +16,14 @@ This guide explains how to create email templates for `platform-mailing` and reg
 
 `platform-mailing` does **not** ship ready-made template files. It defines a list of known template **names** and loads the actual content through `ResourceManager` at startup.
 
-```
-┌──────────────┐     ┌─────────────────────────┐     ┌──────────────────┐
-│ MailService   │────▶│ MailTemplateEngine       │────▶│ ResourceManager  │
-│ sendTemplate()│     │ compileTemplate()        │     │ tryLoadAsync()   │
-└──────────────┘     └─────────────────────────┘     └──────────────────┘
-                              │                              │
-                              ▼                              ▼
-                     ContentTemplateEngine          FileResourceStrategy
-                     (variable interpolation)       BlobResourceStrategy
-                                                    EmbeddedResourceStrategy
+```mermaid
+flowchart LR
+  MailService["MailService<br/>sendTemplate()"] --> MailTemplateEngine["MailTemplateEngine<br/>compileTemplate()"]
+  MailTemplateEngine --> ResourceManager["ResourceManager<br/>tryLoadAsync()"]
+  MailTemplateEngine --> ContentTemplateEngine["ContentTemplateEngine<br/>variable interpolation"]
+  ResourceManager --> FileResourceStrategy[FileResourceStrategy]
+  ResourceManager --> BlobResourceStrategy[BlobResourceStrategy]
+  ResourceManager --> EmbeddedResourceStrategy[EmbeddedResourceStrategy]
 ```
 
 1. `MailService.sendTemplate()` passes the template name and context variables to `MailTemplateEngine`.
@@ -59,18 +57,18 @@ Templates use a Handlebars-style syntax powered by `ContentTemplateEngine`:
 
 | Syntax                                         | Description                       |
 | ---------------------------------------------- | --------------------------------- |
-| `{{variableName}}`                             | Simple variable substitution      |
-| `{{#if condition}}...{{/if}}`                  | Conditional block                 |
-| `{{#if condition}}...{{else}}...{{/if}}`       | Conditional with else             |
-| `{{#unless condition}}...{{/unless}}`          | Negative conditional              |
-| `{{#each items}}...{{/each}}`                  | Loop over array                   |
-| `{{#with object}}...{{/with}}`                 | Context switching                 |
-| `{{@index}}`, `{{@first}}`, `{{@last}}`        | Loop metadata inside `#each`      |
-| `{{nested.property}}`                          | Dot notation for nested values    |
+| `<code>&#123;&#123;variableName&#125;&#125;</code>`                             | Simple variable substitution      |
+| `<code>&#123;&#123;#if condition&#125;&#125;...&#123;&#123;/if&#125;&#125;</code>`                  | Conditional block                 |
+| `<code>&#123;&#123;#if condition&#125;&#125;...&#123;&#123;else&#125;&#125;...&#123;&#123;/if&#125;&#125;</code>`       | Conditional with else             |
+| `<code>&#123;&#123;#unless condition&#125;&#125;...&#123;&#123;/unless&#125;&#125;</code>`          | Negative conditional              |
+| `<code>&#123;&#123;#each items&#125;&#125;...&#123;&#123;/each&#125;&#125;</code>`                  | Loop over array                   |
+| `<code>&#123;&#123;#with object&#125;&#125;...&#123;&#123;/with&#125;&#125;</code>`                 | Context switching                 |
+| `<code>&#123;&#123;@index&#125;&#125;</code>`, `<code>&#123;&#123;@first&#125;&#125;</code>`, `<code>&#123;&#123;@last&#125;&#125;</code>`        | Loop metadata inside `#each`      |
+| `<code>&#123;&#123;nested.property&#125;&#125;</code>`                          | Dot notation for nested values    |
 
 ### Example: `AuthVerify.html`
 
-```html
+```text
 <!DOCTYPE html>
 <html>
 <head>
@@ -78,14 +76,14 @@ Templates use a Handlebars-style syntax powered by `ContentTemplateEngine`:
   <title>Verify your email</title>
 </head>
 <body>
-  <h1>Hello, {{userName}}!</h1>
+  <h1>Hello, &#123;&#123;userName&#125;&#125;!</h1>
   <p>Please verify your email address by clicking the link below:</p>
   <p>
-    <a href="{{verificationUrl}}">Verify Email</a>
+    <a href="&#123;&#123;verificationUrl&#125;&#125;">Verify Email</a>
   </p>
-  {{#if expiresInHours}}
-  <p>This link expires in {{expiresInHours}} hours.</p>
-  {{/if}}
+  &#123;&#123;#if expiresInHours&#125;&#125;
+  <p>This link expires in &#123;&#123;expiresInHours&#125;&#125; hours.</p>
+  &#123;&#123;/if&#125;&#125;
   <p>If you did not create an account, you can safely ignore this email.</p>
 </body>
 </html>
@@ -94,13 +92,13 @@ Templates use a Handlebars-style syntax powered by `ContentTemplateEngine`:
 ### Example: `AuthVerify.txt`
 
 ```text
-Hello, {{userName}}!
+Hello, &#123;&#123;userName&#125;&#125;!
 
 Please verify your email address by visiting the following link:
 
-{{verificationUrl}}
+&#123;&#123;verificationUrl&#125;&#125;
 
-{{#if expiresInHours}}This link expires in {{expiresInHours}} hours.{{/if}}
+&#123;&#123;#if expiresInHours&#125;&#125;This link expires in &#123;&#123;expiresInHours&#125;&#125; hours.&#123;&#123;/if&#125;&#125;
 
 If you did not create an account, you can safely ignore this email.
 ```
@@ -117,18 +115,30 @@ When the format is `html`, `MailTemplateEngine` automatically **escapes all cont
 
 Place your template files in your application's assets directory and register the path with `ResourceModule`:
 
-```
-my-app/
-├── src/
-│   ├── assets/
-│   │   ├── AuthRegister.html
-│   │   ├── AuthRegister.txt
-│   │   ├── AuthVerify.html
-│   │   ├── AuthVerify.txt
-│   │   ├── AuthForgotPassword.html
-│   │   ├── AppointmentInvitation.html
-│   │   └── AppointmentUpdate.html
-│   └── app.module.ts
+```mermaid
+flowchart TB
+  Root[my-app/]
+  Src[src/]
+  Assets[assets/]
+  AppModule[app.module.ts]
+  AuthRegisterHtml[AuthRegister.html]
+  AuthRegisterTxt[AuthRegister.txt]
+  AuthVerifyHtml[AuthVerify.html]
+  AuthVerifyTxt[AuthVerify.txt]
+  AuthForgotPasswordHtml[AuthForgotPassword.html]
+  AppointmentInvitationHtml[AppointmentInvitation.html]
+  AppointmentUpdateHtml[AppointmentUpdate.html]
+
+  Root --> Src
+  Src --> Assets
+  Src --> AppModule
+  Assets --> AuthRegisterHtml
+  Assets --> AuthRegisterTxt
+  Assets --> AuthVerifyHtml
+  Assets --> AuthVerifyTxt
+  Assets --> AuthForgotPasswordHtml
+  Assets --> AppointmentInvitationHtml
+  Assets --> AppointmentUpdateHtml
 ```
 
 ```typescript

package/data/guides/esigning-integration.md

@@ -56,11 +56,17 @@ export class AppModule {}
 
 ## Configuration
 
-```env
-ESIGNING_API_BASE_URL=https://demo.docusign.net/restapi
-ESIGNING_API_KEY=your-api-key
-ESIGNING_WEBHOOK_SECRET=your-webhook-secret
-```
+Each provider requires its own set of environment variables. See the [platform-esigning package docs](../packages/platform-esigning/) for the full table per provider.
+
+### Provider Environment Variables (Summary)
+
+| Provider       | Key Variables                                                                                      |
+| -------------- | -------------------------------------------------------------------------------------------------- |
+| **DocuSign**   | `DOCUSIGN_INTEGRATION_KEY`, `DOCUSIGN_SECRET_KEY`, `DOCUSIGN_ACCOUNT_ID`, `DOCUSIGN_BASE_URL`     |
+| **Adobe Sign** | `ADOBE_SIGN_INTEGRATION_KEY`, `ADOBE_SIGN_CLIENT_SECRET`, `ADOBE_SIGN_BASE_URL`, `ADOBE_SIGN_WEBHOOK_CLIENT_ID` (required) |
+| **Dropbox Sign** | `DROPBOX_SIGN_API_KEY`, `DROPBOX_SIGN_CLIENT_ID`                                               |
+
+> **Breaking change:** `ADOBE_SIGN_WEBHOOK_CLIENT_ID` is now **required** for Adobe Sign webhook verification.
 
 ---
 

package/data/guides/health-indicators.md

@@ -0,0 +1,220 @@
+---
+title: Health Indicators
+description: Integrate health checks from all Archipel platform libraries using the unified health indicator architecture.
+order: 10
+---
+
+# Health Indicators
+
+Every Archipel platform library ships an optional **health indicator** as a separate `/health` subpath export. Health indicators implement the `IHealthIndicator` interface from `platform-health` and can be registered with the `HealthModule` to build a unified `/health` endpoint for your application.
+
+## Architecture
+
+```mermaid
+flowchart LR
+  subgraph App
+    HealthController --> HealthOrchestrator
+  end
+
+  subgraph platform-health
+    HealthOrchestrator
+  end
+
+  subgraph Indicators
+    DatabaseHealthIndicator
+    BlobHealthIndicator
+    MailHealthIndicator
+    CachingHealthIndicator
+    QueueHealthIndicator
+    PaymentHealthIndicator
+    EsigningHealthIndicator
+    IntelligenceHealthIndicator
+    AnalyticsHealthIndicator
+    TelemetryHealthIndicator
+    AuthenticationHealthIndicator
+    McpHealthIndicator
+  end
+
+  HealthOrchestrator --> Indicators
+```
+
+The `HealthOrchestrator` aggregates all registered `IHealthIndicator` instances and returns a combined result. Each indicator reports its own key and status independently.
+
+## Prerequisites
+
+- `@breadstone/archipel-platform-health` installed
+- `@nestjs/terminus` installed (peer dependency)
+
+## IHealthIndicator Interface
+
+Every health indicator implements this contract:
+
+```typescript
+interface IHealthIndicator {
+  /** Unique key identifying this indicator in the health response. */
+  readonly key: string;
+
+  /** Run the health check and return a Terminus HealthIndicatorResult. */
+  check(): HealthIndicatorResult | Promise<HealthIndicatorResult>;
+}
+```
+
+## Available Indicators
+
+All 12 platform libraries provide a health indicator via their `/health` subpath:
+
+| Library | Subpath Import | Class | Key | Check Behavior |
+| ------- | -------------- | ----- | --- | -------------- |
+| `platform-database` | `@breadstone/archipel-platform-database/health` | `DatabaseHealthIndicator` | `database` | Prisma `SELECT 1` ping |
+| `platform-blob-storage` | `@breadstone/archipel-platform-blob-storage/health` | `BlobHealthIndicator` | `blob` | HTTP ping to blob URL (or `disabled` if unconfigured) |
+| `platform-mailing` | `@breadstone/archipel-platform-mailing/health` | `MailHealthIndicator` | `mail` | Validates mail host, user, and port config |
+| `platform-caching` | `@breadstone/archipel-platform-caching/health` | `CachingHealthIndicator` | `caching` | Always `up` |
+| `platform-queue` | `@breadstone/archipel-platform-queue/health` | `QueueHealthIndicator` | `queue` | Always `up` |
+| `platform-payments` | `@breadstone/archipel-platform-payments/health` | `PaymentHealthIndicator` | `payment` | Calls `PaymentClientPort.ping()` to verify provider connectivity |
+| `platform-esigning` | `@breadstone/archipel-platform-esigning/health` | `EsigningHealthIndicator` | `esigning` | Calls `EsigningClientPort.ping()` to verify provider connectivity, reports `providerId` |
+| `platform-intelligence` | `@breadstone/archipel-platform-intelligence/health` | `IntelligenceHealthIndicator` | `intelligence` | Checks `list().length > 0` on the capability registry, reports count |
+| `platform-analytics` | `@breadstone/archipel-platform-analytics/health` | `AnalyticsHealthIndicator` | `analytics` | Calls `AnalyticsClientPort.ping()` to verify provider readiness |
+| `platform-telemetry` | `@breadstone/archipel-platform-telemetry/health` | `TelemetryHealthIndicator` | `telemetry` | Checks `OtelSdkHolder.isInitialized` for SDK presence |
+| `platform-authentication` | `@breadstone/archipel-platform-authentication/health` | `AuthenticationHealthIndicator` | `authentication` | Always `up` |
+| `platform-mcp` | `@breadstone/archipel-platform-mcp/health` | `McpHealthIndicator` | `mcp` | Checks tool/resource/prompt registry counts, reports breakdown |
+
+### Indicator Categories
+
+**Active checks** — perform a real probe:
+- `DatabaseHealthIndicator` — executes a SQL ping
+- `BlobHealthIndicator` — sends an HTTP request to the blob URL
+- `MailHealthIndicator` — validates configuration values
+- `PaymentHealthIndicator` — calls `PaymentClientPort.ping()` (adapters can override for real API calls)
+- `EsigningHealthIndicator` — calls `EsigningClientPort.ping()` (adapters can override for real API calls)
+- `AnalyticsHealthIndicator` — calls `AnalyticsClientPort.ping()` (adapters can override for SDK readiness checks)
+
+**State checks** — inspect in-memory state (zero-cost, no I/O):
+- `IntelligenceHealthIndicator` — verifies at least one capability is registered
+- `TelemetryHealthIndicator` — checks whether the OpenTelemetry SDK has been initialized
+- `McpHealthIndicator` — verifies at least one tool/resource/prompt handler is registered
+
+**Stub checks** — always report `up`:
+- `CachingHealthIndicator`, `QueueHealthIndicator`, `AuthenticationHealthIndicator`
+
+## Quick Start
+
+### 1. Register Indicators
+
+Use `HealthModule.withIndicators()` to register the indicators you need:
+
+```typescript
+import { Module } from '@nestjs/common';
+import { HealthModule } from '@breadstone/archipel-platform-health';
+import { DatabaseHealthIndicator } from '@breadstone/archipel-platform-database/health';
+import { MailHealthIndicator } from '@breadstone/archipel-platform-mailing/health';
+import { PaymentHealthIndicator } from '@breadstone/archipel-platform-payments/health';
+import { CachingHealthIndicator } from '@breadstone/archipel-platform-caching/health';
+
+@Module({
+  imports: [
+    // ... your feature modules
+    HealthModule.withIndicators([
+      DatabaseHealthIndicator,
+      MailHealthIndicator,
+      PaymentHealthIndicator,
+      CachingHealthIndicator,
+    ]),
+  ],
+})
+export class AppModule {}
+```
+
+### 2. Expose a Health Endpoint
+
+The `HealthOrchestrator` runs all registered indicators and returns an aggregated result:
+
+```typescript
+import { Controller, Get } from '@nestjs/common';
+import { HealthOrchestrator } from '@breadstone/archipel-platform-health';
+
+@Controller('health')
+export class HealthController {
+  constructor(private readonly _health: HealthOrchestrator) {}
+
+  @Get()
+  public async check() {
+    return this._health.check();
+  }
+}
+```
+
+### 3. Example Response
+
+```json
+{
+  "status": "ok",
+  "details": {
+    "database": { "status": "up" },
+    "mail": { "status": "up" },
+    "payment": { "status": "up" },
+    "caching": { "status": "up" },
+    "intelligence": { "status": "up", "registeredCapabilities": 3 },
+    "mcp": { "status": "up", "tools": 5, "resources": 2, "prompts": 1 },
+    "telemetry": { "status": "up", "sdkInitialized": true }
+  }
+}
+```
+
+When a provider is not registered (e.g., no `PaymentClientPort` injected), the indicator reports:
+
+```json
+{
+  "payment": { "status": "up", "disabled": true }
+}
+```
+
+When a ping fails, the indicator reports `down` with error details:
+
+```json
+{
+  "payment": { "status": "down", "error": "ECONNREFUSED" }
+}
+```
+
+## Writing a Custom Indicator
+
+Implement `IHealthIndicator` to create a health check for your own services:
+
+```typescript
+import { Injectable } from '@nestjs/common';
+import { IHealthIndicator } from '@breadstone/archipel-platform-health';
+import type { HealthIndicatorResult } from '@nestjs/terminus';
+
+@Injectable()
+export class SearchHealthIndicator implements IHealthIndicator {
+  public readonly key = 'search';
+
+  public check(): HealthIndicatorResult<'search'> {
+    return { search: { status: 'up' } };
+  }
+}
+```
+
+Register it alongside built-in indicators:
+
+```typescript
+HealthModule.withIndicators([
+  DatabaseHealthIndicator,
+  SearchHealthIndicator,
+]);
+```
+
+## Tree-Shaking
+
+Health indicators are **not** included in the main library entry point. They are exported from a separate `/health` subpath, so they are fully tree-shakeable. If you don't import the health subpath, the indicator code and its `@nestjs/terminus` peer dependency are never bundled.
+
+## Peer Dependencies
+
+Each health indicator requires these optional peer dependencies:
+
+| Package | Notes |
+| ------- | ----- |
+| `@breadstone/archipel-platform-health` | `IHealthIndicator` interface and `HealthModule` |
+| `@nestjs/terminus` | `HealthIndicatorResult` type |
+
+Both are listed as optional peer dependencies in each library's `package.json`.

package/data/guides/index.md

@@ -52,6 +52,8 @@ Practical guides for working with Archipel packages in your NestJS application.
 | [Telemetry & Observability](./telemetry-and-observability)   | OpenTelemetry metrics, distributed tracing, and structured logging.                   |
 | [Analytics & Error Tracking](./analytics-and-error-tracking) | Capture errors and user context with Sentry, AppInsights, or Datadog.                 |
 | [Caching](./caching)                                         | In-memory LRU and Redis layered caches with TTL, stale-while-revalidate, and metrics. |
+| [Queue Infrastructure](./queue-infrastructure)               | In-memory FIFO, BullMQ (Redis), and Azure Service Bus job queues.                     |
+| [Health Indicators](./health-indicators)                     | Integrate health checks from all platform libraries using the unified health architecture. |
 
 ## AI & Extensibility