@breadstone/archipel-mcp 0.0.33 → 0.0.35

package/data/guides/email-delivery.md

@@ -20,34 +20,75 @@ yarn add @breadstone/archipel-platform-mailing
 
 ## Choose a Delivery Strategy
 
-`platform-mailing` supports multiple email providers. You select the strategy via environment variables — no code changes required to switch providers.
+`platform-mailing` supports multiple email providers via **subpath exports**. Each delivery strategy is a separate entry point — only the provider you import is bundled (tree-shakeable).
 
-| Strategy     | Value for `MAIL_DELIVERY_STRATEGY` | When to use                          |
-| ------------ | ---------------------------------- | ------------------------------------ |
-| **SMTP**     | `smtp`                             | Any SMTP server (self-hosted, relay) |
-| **Postmark** | `postmark`                         | Postmark transactional email         |
-| **Resend**   | `resend`                           | Resend API                           |
-| **SendGrid** | `sendgrid`                         | Twilio SendGrid                      |
-| **Mailgun**  | `mailgun`                          | Mailgun API                          |
-| **Log**      | `log`                              | Development only — logs to console   |
+| Strategy     | Subpath Import                                              | When to use                          |
+| ------------ | ----------------------------------------------------------- | ------------------------------------ |
+| **SMTP**     | `@breadstone/archipel-platform-mailing/delivering/smtp`     | Any SMTP server (self-hosted, relay) |
+| **Postmark** | `@breadstone/archipel-platform-mailing/delivering/postmark` | Postmark transactional email         |
+| **Resend**   | `@breadstone/archipel-platform-mailing/delivering/resend`   | Resend API                           |
+| **SendGrid** | `@breadstone/archipel-platform-mailing/delivering/sendgrid` | Twilio SendGrid                      |
+| **Mailgun**  | `@breadstone/archipel-platform-mailing/delivering/mailgun`  | Mailgun API                          |
+| **Log**      | `@breadstone/archipel-platform-mailing/delivering/logger`   | Development only — logs to console   |
+
+The strategy is selected at **compile time** by passing the concrete class to `MailModule.register()`. No environment variable is needed for strategy selection.
 
 ---
 
 ## Module Registration
 
-`MailModule` is a global module. Register it once in your root module:
+`MailModule` requires explicit registration via `MailModule.register()`. You select the delivery strategy and template-fetch strategy at compile time by passing the concrete class:
 
 ```typescript
 import { Module } from '@nestjs/common';
 import { MailModule } from '@breadstone/archipel-platform-mailing';
+import { ResendDeliveryStrategy } from '@breadstone/archipel-platform-mailing/delivering/resend';
+import { FileTemplateFetchStrategy } from '@breadstone/archipel-platform-mailing/templating/file';
 
 @Module({
-  imports: [MailModule],
+  imports: [
+    MailModule.register({
+      deliveryStrategy: ResendDeliveryStrategy,
+      templateFetchStrategy: FileTemplateFetchStrategy,
+      templateNames: ['AuthRegister', 'AuthVerify', 'AuthForgotPassword'],
+    }),
+  ],
 })
 export class AppModule {}
 ```
 
-The module reads all configuration from environment variables. No `register()` call is needed.
+### Options
+
+| Option                       | Type                                | Default                         | Description                                                                 |
+| ---------------------------- | ----------------------------------- | ------------------------------- | --------------------------------------------------------------------------- |
+| `deliveryStrategy`           | `Type<DeliveryStrategyBase>`        | *required*                      | Concrete delivery strategy class                                            |
+| `templateFetchStrategy`      | `Type<TemplateFetchStrategyBase>`   | *required*                      | Concrete template-fetch strategy class                                      |
+| `templateNames`              | `ReadonlyArray<string>`             | `[]`                            | Template names to load (for `FileTemplateFetchStrategy`)                    |
+| `configEntries`              | `ReadonlyArray<IConfigRegistryEntry>` | `PLATFORM_MAILING_CONFIG_ENTRIES` | Provider-specific config entries                                          |
+| `templateRepositoryProvider` | `Provider<IMailTemplateRepository>` | —                               | Required when using `DatabaseTemplateFetchStrategy`                          |
+| `isGlobal`                   | `boolean`                           | `true`                          | Whether to register the module globally                                     |
+
+---
+
+## Package Structure & Tree-Shaking
+
+`platform-mailing` uses **multi-entry-point subpath exports**. The main entry point exports only core contracts, services, and base classes. Each provider (delivery strategy or template strategy) is a **separate subpath** that you import independently:
+
+```
+@breadstone/archipel-platform-mailing                    → Core (MailService, MailModule, ports, models, errors)
+@breadstone/archipel-platform-mailing/delivering/smtp     → SmtpDeliveryStrategy + SMTP_CONFIG_ENTRIES
+@breadstone/archipel-platform-mailing/delivering/resend   → ResendDeliveryStrategy + RESEND_CONFIG_ENTRIES
+@breadstone/archipel-platform-mailing/delivering/postmark → PostmarkDeliveryStrategy + POSTMARK_CONFIG_ENTRIES
+@breadstone/archipel-platform-mailing/delivering/sendgrid → SendGridDeliveryStrategy + SENDGRID_CONFIG_ENTRIES
+@breadstone/archipel-platform-mailing/delivering/mailgun  → MailgunDeliveryStrategy + MAILGUN_CONFIG_ENTRIES
+@breadstone/archipel-platform-mailing/delivering/logger   → LogDeliveryStrategy
+@breadstone/archipel-platform-mailing/templating/file     → FileTemplateFetchStrategy
+@breadstone/archipel-platform-mailing/templating/blob     → BlobTemplateFetchStrategy
+@breadstone/archipel-platform-mailing/templating/database → DatabaseTemplateFetchStrategy
+@breadstone/archipel-platform-mailing/health              → MailHealthIndicator
+```
+
+This ensures that importing the core package does **not** pull in provider-specific SDKs (e.g., `nodemailer`, `resend`, `@sendgrid/mail`). Only the subpath you import triggers a dependency on the corresponding SDK.
 
 ---
 
@@ -56,13 +97,14 @@ The module reads all configuration from environment variables. No `register()` c
 ### Core Variables
 
 ```env
-MAIL_DELIVERY_STRATEGY=resend
-MAIL_TEMPLATE_STRATEGY=file
 MAIL_TEMPLATE_ENGINE_FORMAT=html
-MAIL_FROM_ADDRESS=noreply@yourapp.com
-MAIL_FROM_NAME=YourApp
+MAIL_SENDER_EMAIL=noreply@yourapp.com
 ```
 
+::: info Strategy Selection
+The delivery strategy and template-fetch strategy are no longer configured via environment variables. They are selected at compile time by passing the class to `MailModule.register()`. The `MAIL_DELIVERY_STRATEGY` and `MAIL_TEMPLATE_STRATEGY` environment variables have been removed.
+:::
+
 ### Provider-Specific Variables
 
 #### SMTP
@@ -102,14 +144,15 @@ MAIL_MAILGUN_DOMAIN=mg.yourapp.com
 
 ### Template Strategies
 
-Templates can be loaded from the filesystem or from blob storage:
+Templates can be loaded from the filesystem, from blob storage, or from a database — each via a dedicated **subpath export**:
 
-| Strategy | Value for `MAIL_TEMPLATE_STRATEGY` | Description                                 |
-| -------- | ---------------------------------- | ------------------------------------------- |
-| **File** | `file`                             | Load templates from a local directory       |
-| **Blob** | `blob`                             | Load templates from `platform-blob-storage` |
+| Strategy     | Subpath Import                                            | Description                                     |
+| ------------ | --------------------------------------------------------- | ----------------------------------------------- |
+| **File**     | `@breadstone/archipel-platform-mailing/templating/file`     | Load templates from a local directory           |
+| **Blob**     | `@breadstone/archipel-platform-mailing/templating/blob`     | Load templates from `platform-blob-storage`     |
+| **Database** | `@breadstone/archipel-platform-mailing/templating/database` | Load templates from a database via repository   |
 
-For file-based templates, place your `.html` or `.txt` files in the configured template directory.
+Select the strategy by passing the class to `MailModule.register({ templateFetchStrategy: ... })`. For file-based templates, place your `.html` or `.txt` files in the configured template directory.
 
 ---
 
@@ -269,9 +312,10 @@ Map `MailDeliveryError` to an appropriate HTTP response in your global exception
 
 ## Development Tips
 
-- Use `MAIL_DELIVERY_STRATEGY=log` during local development to see email content in the console without sending real emails.
-- Use the **blob** template strategy when templates are shared across multiple services or managed by a CMS.
+- Use `LogDeliveryStrategy` during local development to see email content in the console without sending real emails.
+- Use the **blob** or **database** template strategy when templates are shared across multiple services or managed by a CMS.
 - Template variables use the format defined by the template engine. Place templates in a well-organized directory structure (e.g., `templates/mail/welcome.html`).
+- Only import the delivery/templating subpath you actually need — this keeps your bundle lean and avoids unnecessary peer dependency requirements.
 
 ---
 

package/data/guides/email-templates.md

@@ -14,20 +14,26 @@ This guide explains how to create email templates for `platform-mailing` and reg
 
 ## How It Works
 
-`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.
+`platform-mailing` does **not** ship ready-made template files. It defines a list of known template **names** and loads the actual content through a **template-fetch strategy** at startup. Each strategy is available as a dedicated subpath export:
+
+| Strategy     | Subpath Import                                              | Description                                    |
+| ------------ | ----------------------------------------------------------- | ---------------------------------------------- |
+| **File**     | `@breadstone/archipel-platform-mailing/templating/file`     | Load from local filesystem via `ResourceManager` |
+| **Blob**     | `@breadstone/archipel-platform-mailing/templating/blob`     | Load from blob storage via `BlobService`         |
+| **Database** | `@breadstone/archipel-platform-mailing/templating/database` | Load from database via `IMailTemplateRepository`  |
 
 ```mermaid
 flowchart LR
   MailService["MailService<br/>sendTemplate()"] --> MailTemplateEngine["MailTemplateEngine<br/>compileTemplate()"]
-  MailTemplateEngine --> ResourceManager["ResourceManager<br/>tryLoadAsync()"]
+  MailTemplateEngine --> TemplateFetchStrategy["TemplateFetchStrategy<br/>(file / blob / database)"]
   MailTemplateEngine --> ContentTemplateEngine["ContentTemplateEngine<br/>variable interpolation"]
-  ResourceManager --> FileResourceStrategy[FileResourceStrategy]
-  ResourceManager --> BlobResourceStrategy[BlobResourceStrategy]
-  ResourceManager --> EmbeddedResourceStrategy[EmbeddedResourceStrategy]
+  TemplateFetchStrategy --> FileTemplateFetchStrategy[FileTemplateFetchStrategy]
+  TemplateFetchStrategy --> BlobTemplateFetchStrategy[BlobTemplateFetchStrategy]
+  TemplateFetchStrategy --> DatabaseTemplateFetchStrategy[DatabaseTemplateFetchStrategy]
 ```
 
 1. `MailService.sendTemplate()` passes the template name and context variables to `MailTemplateEngine`.
-2. `MailTemplateEngine` looks up the pre-loaded template content by name and format (`.html` or `.txt`).
+2. `MailTemplateEngine` delegates to the configured `TemplateFetchStrategy` (file, blob, or database) to load the template content.
 3. `ContentTemplateEngine` from `platform-core` interpolates `{{placeholders}}` with the provided context.
 4. The compiled string is handed to the configured delivery strategy (SMTP, Resend, Postmark, etc.).
 
@@ -55,16 +61,16 @@ The strategy loads `AuthRegister.html`, `AuthRegister.txt`, `AuthVerify.html`, e
 
 Templates use a Handlebars-style syntax powered by `ContentTemplateEngine`:
 
-| Syntax                                         | Description                       |
-| ---------------------------------------------- | --------------------------------- |
-| `<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    |
+| 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    |
 
 ### Example: `AuthVerify.html`
 
@@ -76,14 +82,14 @@ Templates use a Handlebars-style syntax powered by `ContentTemplateEngine`:
   <title>Verify your email</title>
 </head>
 <body>
-  <h1>Hello, &#123;&#123;userName&#125;&#125;!</h1>
+  <h1>Hello, {{userName}}!</h1>
   <p>Please verify your email address by clicking the link below:</p>
   <p>
-    <a href="&#123;&#123;verificationUrl&#125;&#125;">Verify Email</a>
+    <a href="{{verificationUrl}}">Verify Email</a>
   </p>
-  &#123;&#123;#if expiresInHours&#125;&#125;
-  <p>This link expires in &#123;&#123;expiresInHours&#125;&#125; hours.</p>
-  &#123;&#123;/if&#125;&#125;
+  {{#if expiresInHours}}
+  <p>This link expires in {{expiresInHours}} hours.</p>
+  {{/if}}
   <p>If you did not create an account, you can safely ignore this email.</p>
 </body>
 </html>
@@ -92,13 +98,13 @@ Templates use a Handlebars-style syntax powered by `ContentTemplateEngine`:
 ### Example: `AuthVerify.txt`
 
 ```text
-Hello, &#123;&#123;userName&#125;&#125;!
+Hello, {{userName}}!
 
 Please verify your email address by visiting the following link:
 
-&#123;&#123;verificationUrl&#125;&#125;
+{{verificationUrl}}
 
-&#123;&#123;#if expiresInHours&#125;&#125;This link expires in &#123;&#123;expiresInHours&#125;&#125; hours.&#123;&#123;/if&#125;&#125;
+{{#if expiresInHours}}This link expires in {{expiresInHours}} hours.{{/if}}
 
 If you did not create an account, you can safely ignore this email.
 ```
@@ -146,6 +152,7 @@ import { Module } from '@nestjs/common';
 import { join } from 'node:path';
 import { ResourceModule, FileResourceStrategy } from '@breadstone/archipel-platform-resources';
 import { MailModule } from '@breadstone/archipel-platform-mailing';
+import { FileTemplateFetchStrategy } from '@breadstone/archipel-platform-mailing/templating/file';
 
 @Module({
   imports: [
@@ -159,21 +166,25 @@ import { MailModule } from '@breadstone/archipel-platform-mailing';
         }),
       ],
     }),
-    MailModule,
+    MailModule.register({
+      deliveryStrategy: ResendDeliveryStrategy,
+      templateFetchStrategy: FileTemplateFetchStrategy,
+      templateNames: ['AuthRegister', 'AuthVerify', 'AuthForgotPassword', 'AppointmentInvitation', 'AppointmentUpdate'],
+    }),
   ],
 })
 export class AppModule {}
 ```
 
-Set the environment variable to use the file strategy:
-
-```env
-MAIL_TEMPLATE_STRATEGY=file
-```
+The template names are passed directly to `MailModule.register()` via the `templateNames` option. `FileTemplateFetchStrategy` uses these names to load the corresponding `.html` and `.txt` files from `ResourceManager`.
 
 ### Blob-Based Templates
 
-For templates managed via a CMS or shared across multiple services, use `BlobTemplateFetchStrategy`. Upload a manifest file (`templates/templates.json`) and the template files to your blob storage:
+For templates managed via a CMS or shared across multiple services, use `BlobTemplateFetchStrategy` from the `templating/blob` subpath. Upload a manifest file (`templates/templates.json`) and the template files to your blob storage:
+
+```typescript
+import { BlobTemplateFetchStrategy } from '@breadstone/archipel-platform-mailing/templating/blob';
+```
 
 **`templates/templates.json`**
 ```json
@@ -186,13 +197,42 @@ For templates managed via a CMS or shared across multiple services, use `BlobTem
 ]
 ```
 
-Set the environment variable:
+The `BlobTemplateFetchStrategy` downloads the manifest, then fetches each listed file from blob storage via `BlobService` from `platform-blob-storage`. Select this strategy by passing it to `MailModule.register()`:
+
+```typescript
+import { MailModule } from '@breadstone/archipel-platform-mailing';
+import { BlobTemplateFetchStrategy } from '@breadstone/archipel-platform-mailing/templating/blob';
+
+MailModule.register({
+  deliveryStrategy: ResendDeliveryStrategy,
+  templateFetchStrategy: BlobTemplateFetchStrategy,
+})
+```
+
+### Database-Based Templates
 
-```env
-MAIL_TEMPLATE_STRATEGY=blob
+For templates stored in a database (e.g., managed via an admin panel), use `DatabaseTemplateFetchStrategy` from the `templating/database` subpath:
+
+```typescript
+import { DatabaseTemplateFetchStrategy } from '@breadstone/archipel-platform-mailing/templating/database';
 ```
 
-The `BlobTemplateFetchStrategy` downloads the manifest, then fetches each listed file from blob storage via `BlobService` from `platform-blob-storage`.
+This strategy loads templates through the `IMailTemplateRepository` port. You must provide an adapter implementation that fetches template records from your database:
+
+```typescript
+import { DatabaseTemplateFetchStrategy } from '@breadstone/archipel-platform-mailing/templating/database';
+import { IMailTemplateRepository, MAIL_TEMPLATE_REPOSITORY_TOKEN } from '@breadstone/archipel-platform-mailing';
+import { MailModule } from '@breadstone/archipel-platform-mailing';
+
+MailModule.register({
+  deliveryStrategy: SmtpDeliveryStrategy,
+  templateFetchStrategy: DatabaseTemplateFetchStrategy,
+  templateRepositoryProvider: {
+    provide: MAIL_TEMPLATE_REPOSITORY_TOKEN,
+    useClass: PrismaMailTemplateRepository,
+  },
+})
+```
 
 ---
 
@@ -284,19 +324,21 @@ To diagnose, enable `debug: true` in `ResourceModule.forRoot()`. This logs every
   - AuthVerify.txt (text/plain, 320 B) → /app/dist/assets/AuthVerify.txt
 ```
 
-Also check that `MAIL_TEMPLATE_STRATEGY` is set correctly (`file` or `blob`).
+Also check that your `MailModule.register()` call passes the correct `templateFetchStrategy` class (`FileTemplateFetchStrategy`, `BlobTemplateFetchStrategy`, or `DatabaseTemplateFetchStrategy`).
 
 ---
 
 ## Checklist
 
 - [ ] Template files created for all required template names (`.html` and/or `.txt`)
-- [ ] `ResourceModule.forRoot()` registered with base paths including your template directory
-- [ ] `MAIL_TEMPLATE_STRATEGY` set to `file` or `blob`
+- [ ] `ResourceModule.forRoot()` registered with base paths including your template directory (for `file` strategy)
+- [ ] `MailModule.register()` called with the correct `templateFetchStrategy` class
+- [ ] `templateNames` passed to `MailModule.register()` (for `FileTemplateFetchStrategy`)
 - [ ] `MAIL_TEMPLATE_ENGINE_FORMAT` set to `html` or `txt`
 - [ ] Placeholders in templates match the keys passed in `templateParams`
 - [ ] App-level overrides listed **before** library asset paths in `basePaths`
 - [ ] `debug: true` used during development to verify template availability
+- [ ] Only the needed templating subpath is imported (tree-shaking)
 
 ---
 

package/data/packages/platform-feature-flags/api/Class.AzureFeatureFlagReader.md

@@ -5,7 +5,7 @@ editUrl: false
 ---
 # Class: AzureFeatureFlagReader
 
-Defined in: azure/AzureFeatureFlagReader.ts:36
+Defined in: [azure/AzureFeatureFlagReader.ts:36](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L36)
 
 Azure App Configuration implementation of the [FeatureFlagReaderPort](Class.FeatureFlagReaderPort).
 Uses `@azure/app-configuration-provider` for connecting to Azure App Configuration
@@ -28,7 +28,7 @@ and `@microsoft/feature-management` for evaluating feature flags.
 new AzureFeatureFlagReader(configService): AzureFeatureFlagReader;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:49
+Defined in: [azure/AzureFeatureFlagReader.ts:49](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L49)
 
 #### Parameters
 
@@ -52,7 +52,7 @@ Defined in: azure/AzureFeatureFlagReader.ts:49
 getAllFlags(_context?): Promise<readonly IFeatureFlagEvaluation[]>;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:167
+Defined in: [azure/AzureFeatureFlagReader.ts:167](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L167)
 
 Returns all known feature flags with their current evaluation.
 
@@ -83,7 +83,7 @@ getVariant<T>(
 _context?): Promise<T>;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:146
+Defined in: [azure/AzureFeatureFlagReader.ts:146](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L146)
 
 Returns the variant value of a feature flag for multivariate flags and A/B testing.
 
@@ -119,7 +119,7 @@ The variant value of the feature flag.
 isEnabled(key, _context?): Promise<boolean>;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:131
+Defined in: [azure/AzureFeatureFlagReader.ts:131](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L131)
 
 Evaluates whether a feature flag is enabled.
 
@@ -148,7 +148,7 @@ Evaluates whether a feature flag is enabled.
 onModuleDestroy(): void;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:123
+Defined in: [azure/AzureFeatureFlagReader.ts:123](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L123)
 
 Cleans up the refresh interval on module destruction.
 
@@ -170,7 +170,7 @@ OnModuleDestroy.onModuleDestroy
 onModuleInit(): Promise<void>;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:63
+Defined in: [azure/AzureFeatureFlagReader.ts:63](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L63)
 
 Initializes the Azure App Configuration connection and feature manager.
 
@@ -192,7 +192,7 @@ OnModuleInit.onModuleInit
 ping(): Promise<boolean>;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:207
+Defined in: [azure/AzureFeatureFlagReader.ts:207](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L207)
 
 Lightweight connectivity check for the feature flag provider.
 Override in adapters to perform a real API call.
@@ -216,7 +216,7 @@ Defaults to `true` if not overridden.
 refresh(): Promise<void>;
 ```
 
-Defined in: azure/AzureFeatureFlagReader.ts:193
+Defined in: [azure/AzureFeatureFlagReader.ts:193](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagReader.ts#L193)
 
 Refreshes the flag state from the remote provider.
 Implementations should reload configuration from the upstream source.

package/data/packages/platform-feature-flags/api/Class.AzureFeatureFlagWriter.md

@@ -5,7 +5,7 @@ editUrl: false
 ---
 # Class: AzureFeatureFlagWriter
 
-Defined in: azure/AzureFeatureFlagWriter.ts:28
+Defined in: [azure/AzureFeatureFlagWriter.ts:28](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L28)
 
 Azure App Configuration implementation of the [FeatureFlagWriterPort](Class.FeatureFlagWriterPort).
 Uses `@azure/app-configuration` (`AppConfigurationClient`) for CRUD operations
@@ -27,7 +27,7 @@ on feature flags stored in Azure App Configuration.
 new AzureFeatureFlagWriter(configService): AzureFeatureFlagWriter;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:39
+Defined in: [azure/AzureFeatureFlagWriter.ts:39](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L39)
 
 #### Parameters
 
@@ -51,7 +51,7 @@ Defined in: azure/AzureFeatureFlagWriter.ts:39
 createFlag(definition): Promise<void>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:150
+Defined in: [azure/AzureFeatureFlagWriter.ts:150](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L150)
 
 Creates a new feature flag.
 
@@ -81,7 +81,7 @@ If the flag already exists or creation fails.
 deleteFlag(key): Promise<void>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:218
+Defined in: [azure/AzureFeatureFlagWriter.ts:218](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L218)
 
 Deletes a feature flag.
 
@@ -113,7 +113,7 @@ getFlag(key): Promise<
 | undefined>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:81
+Defined in: [azure/AzureFeatureFlagWriter.ts:81](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L81)
 
 Returns a single feature flag definition by key.
 
@@ -143,7 +143,7 @@ The flag definition, or `undefined` if not found.
 listFlags(): Promise<readonly IFeatureFlagDefinition[]>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:115
+Defined in: [azure/AzureFeatureFlagWriter.ts:115](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L115)
 
 Returns all feature flag definitions managed by the provider.
 
@@ -165,7 +165,7 @@ Array of flag definitions.
 onModuleInit(): Promise<void>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:53
+Defined in: [azure/AzureFeatureFlagWriter.ts:53](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L53)
 
 Initializes the Azure App Configuration management client.
 
@@ -187,7 +187,7 @@ OnModuleInit.onModuleInit
 ping(): Promise<boolean>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:237
+Defined in: [azure/AzureFeatureFlagWriter.ts:237](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L237)
 
 Lightweight connectivity check for the writer provider.
 Defaults to `true` if not overridden.
@@ -210,7 +210,7 @@ Defaults to `true` if not overridden.
 updateFlag(key, updates): Promise<void>;
 ```
 
-Defined in: azure/AzureFeatureFlagWriter.ts:177
+Defined in: [azure/AzureFeatureFlagWriter.ts:177](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/azure/AzureFeatureFlagWriter.ts#L177)
 
 Updates an existing feature flag.
 Only the fields present in the partial definition are updated.

package/data/packages/platform-feature-flags/api/Class.FeatureFlagError.md

@@ -5,7 +5,7 @@ editUrl: false
 ---
 # Class: FeatureFlagError
 
-Defined in: errors/FeatureFlagError.ts:6
+Defined in: [errors/FeatureFlagError.ts:6](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/errors/FeatureFlagError.ts#L6)
 
 Domain error thrown when a feature flag operation fails.
 
@@ -24,7 +24,7 @@ new FeatureFlagError(
    cause?): FeatureFlagError;
 ```
 
-Defined in: errors/FeatureFlagError.ts:16
+Defined in: [errors/FeatureFlagError.ts:16](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/errors/FeatureFlagError.ts#L16)
 
 #### Parameters
 
@@ -52,7 +52,7 @@ Error.constructor
 readonly code: "FEATURE_FLAG" = 'FEATURE_FLAG';
 ```
 
-Defined in: errors/FeatureFlagError.ts:9
+Defined in: [errors/FeatureFlagError.ts:9](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/errors/FeatureFlagError.ts#L9)
 
 ***
 
@@ -62,4 +62,4 @@ Defined in: errors/FeatureFlagError.ts:9
 readonly provider: string;
 ```
 
-Defined in: errors/FeatureFlagError.ts:10
+Defined in: [errors/FeatureFlagError.ts:10](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/errors/FeatureFlagError.ts#L10)

package/data/packages/platform-feature-flags/api/Class.FeatureFlagGuard.md

@@ -5,7 +5,7 @@ editUrl: false
 ---
 # Class: FeatureFlagGuard
 
-Defined in: guards/FeatureFlagGuard.ts:17
+Defined in: [guards/FeatureFlagGuard.ts:17](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/guards/FeatureFlagGuard.ts#L17)
 
 Guard that checks if a feature flag is enabled before allowing access to a route.
 Use the [FeatureFlag](Function.FeatureFlag) decorator to specify which flag to check.
@@ -22,7 +22,7 @@ Use the [FeatureFlag](Function.FeatureFlag) decorator to specify which flag to c
 new FeatureFlagGuard(featureFlagReader, reflector): FeatureFlagGuard;
 ```
 
-Defined in: guards/FeatureFlagGuard.ts:35
+Defined in: [guards/FeatureFlagGuard.ts:35](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/guards/FeatureFlagGuard.ts#L35)
 
 Constructs a new instance of the `FeatureFlagGuard` class.
 
@@ -45,7 +45,7 @@ Constructs a new instance of the `FeatureFlagGuard` class.
 canActivate(context): Promise<boolean>;
 ```
 
-Defined in: guards/FeatureFlagGuard.ts:51
+Defined in: [guards/FeatureFlagGuard.ts:51](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/guards/FeatureFlagGuard.ts#L51)
 
 Determines whether the guarded feature flag is enabled.
 

package/data/packages/platform-feature-flags/api/Class.FeatureFlagModule.md

@@ -5,7 +5,7 @@ editUrl: false
 ---
 # Class: FeatureFlagModule
 
-Defined in: FeatureFlagModule.ts:21
+Defined in: [FeatureFlagModule.ts:21](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/FeatureFlagModule.ts#L21)
 
 NestJS module providing feature flag infrastructure.
 Exposes a configurable feature flag reader and a route guard.
@@ -32,7 +32,7 @@ new FeatureFlagModule(): FeatureFlagModule;
 static register(options): DynamicModule;
 ```
 
-Defined in: FeatureFlagModule.ts:31
+Defined in: [FeatureFlagModule.ts:31](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/FeatureFlagModule.ts#L31)
 
 Configures the module with the specified options.
 

package/data/packages/platform-feature-flags/api/Class.FeatureFlagReaderPort.md

@@ -5,7 +5,7 @@ editUrl: false
 ---
 # Abstract Class: FeatureFlagReaderPort
 
-Defined in: contracts/FeatureFlagReaderPort.ts:15
+Defined in: [contracts/FeatureFlagReaderPort.ts:15](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/contracts/FeatureFlagReaderPort.ts#L15)
 
 Abstract port for feature flag reader operations.
 Each provider (Azure App Configuration, Vercel Edge Config) must implement this contract
@@ -36,7 +36,7 @@ new FeatureFlagReaderPort(): FeatureFlagReaderPort;
 abstract getAllFlags(context?): Promise<readonly IFeatureFlagEvaluation[]>;
 ```
 
-Defined in: contracts/FeatureFlagReaderPort.ts:46
+Defined in: [contracts/FeatureFlagReaderPort.ts:46](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/contracts/FeatureFlagReaderPort.ts#L46)
 
 Returns all known feature flags with their current evaluation.
 
@@ -63,7 +63,7 @@ abstract getVariant<T>(
 context?): Promise<T>;
 ```
 
-Defined in: contracts/FeatureFlagReaderPort.ts:37
+Defined in: [contracts/FeatureFlagReaderPort.ts:37](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/contracts/FeatureFlagReaderPort.ts#L37)
 
 Returns the variant value of a feature flag for multivariate flags and A/B testing.
 
@@ -95,7 +95,7 @@ The variant value of the feature flag.
 abstract isEnabled(key, context?): Promise<boolean>;
 ```
 
-Defined in: contracts/FeatureFlagReaderPort.ts:26
+Defined in: [contracts/FeatureFlagReaderPort.ts:26](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/contracts/FeatureFlagReaderPort.ts#L26)
 
 Evaluates whether a feature flag is enabled.
 
@@ -120,7 +120,7 @@ Evaluates whether a feature flag is enabled.
 ping(): Promise<boolean>;
 ```
 
-Defined in: contracts/FeatureFlagReaderPort.ts:64
+Defined in: [contracts/FeatureFlagReaderPort.ts:64](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/contracts/FeatureFlagReaderPort.ts#L64)
 
 Lightweight connectivity check for the feature flag provider.
 Override in adapters to perform a real API call.
@@ -140,7 +140,7 @@ Defaults to `true` if not overridden.
 abstract refresh(): Promise<void>;
 ```
 
-Defined in: contracts/FeatureFlagReaderPort.ts:54
+Defined in: [contracts/FeatureFlagReaderPort.ts:54](https://github.com/RueDeRennes/archipel/blob/main/libs/platform-feature-flags/src/contracts/FeatureFlagReaderPort.ts#L54)
 
 Refreshes the flag state from the remote provider.
 Implementations should reload configuration from the upstream source.