@fluojs/discord 1.0.1 → 1.0.3

package/README.ko.md

@@ -95,6 +95,7 @@ DiscordModule.forRootAsync({
 Behavioral contract 메모:
 
 - `DiscordService.send(...)`는 전달 전에 `defaultThreadId`를 해석합니다.
+- `DiscordService.sendMany(...)`는 `DiscordMessage[]`를 직접 순차 전송하는 batch API이며 `continueOnError`를 지원합니다. 이는 multi-recipient `@fluojs/notifications` dispatch shortcut이 아닙니다.
 - 서비스는 모듈 bootstrap 시 transport를 초기화하고, factory가 소유한 리소스만 애플리케이션 shutdown 시 닫습니다.
 - send는 bootstrap이 transport를 `ready`로 표시한 뒤에만 허용됩니다. bootstrap 전, startup 중, bootstrap 실패 후, shutdown 중, shutdown 후 시도는 전달 전에 거부됩니다.
 - 서비스가 shutdown 중이거나 이미 stopped 상태라면 cached transport를 재사용하지 않고 send를 거부합니다.
@@ -144,7 +145,7 @@ Behavioral contract 메모:
 - 하나의 notification dispatch는 정확히 하나의 Discord thread 경로로 매핑됩니다. `payload.threadId` 또는 `recipients`의 단일 항목을 사용해야 합니다.
 - `payload.threadId`가 없으면 `DiscordService.sendNotification(...)`는 첫 번째 `recipients` 항목을 사용하고, 그것도 없으면 `defaultThreadId`로 폴백합니다.
 - notification metadata는 payload metadata, dispatch metadata, template/subject marker를 합쳐 구성됩니다. `template`은 renderer가 구성된 경우에만 렌더링됩니다.
-- 여러 Discord thread로 fan-out이 필요하다면 하나의 multi-recipient dispatch 대신 `sendMany(...)`를 사용해야 합니다.
+- 여러 Discord thread로 fan-out이 필요한 notification workflow라면 thread별 concrete Discord message를 만들어 `DiscordService.sendMany(...)`로 보내거나 별도 notification dispatch를 실행해야 합니다. 하나의 notification dispatch는 multi-recipient fan-out을 암묵적으로 확장하지 않습니다.
 
 ### 명시적 fetch 주입을 사용하는 webhook-first 전달
 
@@ -185,7 +186,10 @@ Discord 패키지는 의도적으로 다음을 **포함하지 않습니다**:
 
 ### 핵심
 
+- `Discord`
 - `DiscordModule.forRoot(options)` / `DiscordModule.forRootAsync(options)`
+- `DiscordModuleOptions`
+- `DiscordAsyncModuleOptions`
 - `DiscordService`
 - `DiscordChannel`
 - `DISCORD`
@@ -197,11 +201,11 @@ Discord 패키지는 의도적으로 다음을 **포함하지 않습니다**:
 
 - `DiscordMessage`
 - `NormalizedDiscordMessage`
-- `DiscordAsyncModuleOptions`
 - `DiscordWebhookTransportOptions`
 - `DiscordFetchLike`
 - `DiscordFetchResponse`
 - `DiscordSendResult`
+- `DiscordSendOptions`
 - `DiscordSendManyOptions`
 - `DiscordSendBatchResult`
 - `DiscordSendFailure`
@@ -213,7 +217,9 @@ Discord 패키지는 의도적으로 다음을 **포함하지 않습니다**:
 - `DiscordEmbed`
 - `DiscordPoll`
 - `DiscordTransport`
+- `DiscordTransportContext`
 - `DiscordTransportFactory`
+- `DiscordTransportReceipt`
 - `DiscordTemplateRenderInput`
 - `DiscordTemplateRenderResult`
 - `DiscordTemplateRenderer`
@@ -223,6 +229,8 @@ Discord 패키지는 의도적으로 다음을 **포함하지 않습니다**:
 
 - `createDiscordPlatformStatusSnapshot(...)`
 - `DiscordLifecycleState`
+- `DiscordPlatformStatusSnapshot`
+- `DiscordStatusAdapterInput`
 - `DiscordConfigurationError`
 - `DiscordMessageValidationError`
 - `DiscordTransportError`

package/README.md

@@ -95,6 +95,7 @@ DiscordModule.forRootAsync({
 Behavioral contract notes:
 
 - `DiscordService.send(...)` resolves `defaultThreadId` before delivery.
+- `DiscordService.sendMany(...)` is a direct `DiscordMessage[]` batch API that sends messages sequentially and supports `continueOnError`; it is not a multi-recipient `@fluojs/notifications` dispatch shortcut.
 - The service initializes the configured transport during module bootstrap and closes factory-owned resources during application shutdown.
 - Sends are accepted only after bootstrap marks the transport `ready`; attempts before bootstrap, during startup, after failed bootstrap, while shutting down, or after shutdown are rejected before delivery.
 - Sends attempted while the service is shutting down or already stopped are rejected before reusing the cached transport.
@@ -144,7 +145,7 @@ Behavioral contract notes:
 - One notification dispatch maps to exactly one Discord thread route. Use `payload.threadId` or a single entry in `recipients`.
 - If `payload.threadId` is omitted, `DiscordService.sendNotification(...)` uses the first `recipients` entry or falls back to `defaultThreadId`.
 - Notification metadata is merged from payload metadata, dispatch metadata, and template/subject markers. `template` is rendered only when a renderer is configured.
-- If a notification needs fan-out across multiple Discord threads, call `sendMany(...)` instead of one multi-recipient dispatch.
+- If a notification workflow needs fan-out across multiple Discord threads, create one concrete Discord message per thread with `DiscordService.sendMany(...)` or issue separate notification dispatches; a single notification dispatch never expands multi-recipient fan-out implicitly.
 
 ### Webhook-first delivery with explicit fetch injection
 
@@ -185,7 +186,10 @@ These limitations are part of the package contract so runtime choice, provider c
 
 ### Core
 
+- `Discord`
 - `DiscordModule.forRoot(options)` / `DiscordModule.forRootAsync(options)`
+- `DiscordModuleOptions`
+- `DiscordAsyncModuleOptions`
 - `DiscordService`
 - `DiscordChannel`
 - `DISCORD`
@@ -197,11 +201,11 @@ Compose applications through `DiscordModule` and integrate notifications through
 
 - `DiscordMessage`
 - `NormalizedDiscordMessage`
-- `DiscordAsyncModuleOptions`
 - `DiscordWebhookTransportOptions`
 - `DiscordFetchLike`
 - `DiscordFetchResponse`
 - `DiscordSendResult`
+- `DiscordSendOptions`
 - `DiscordSendManyOptions`
 - `DiscordSendBatchResult`
 - `DiscordSendFailure`
@@ -213,7 +217,9 @@ Compose applications through `DiscordModule` and integrate notifications through
 - `DiscordEmbed`
 - `DiscordPoll`
 - `DiscordTransport`
+- `DiscordTransportContext`
 - `DiscordTransportFactory`
+- `DiscordTransportReceipt`
 - `DiscordTemplateRenderInput`
 - `DiscordTemplateRenderResult`
 - `DiscordTemplateRenderer`
@@ -223,6 +229,8 @@ Compose applications through `DiscordModule` and integrate notifications through
 
 - `createDiscordPlatformStatusSnapshot(...)`
 - `DiscordLifecycleState`
+- `DiscordPlatformStatusSnapshot`
+- `DiscordStatusAdapterInput`
 - `DiscordConfigurationError`
 - `DiscordMessageValidationError`
 - `DiscordTransportError`

package/package.json

@@ -9,7 +9,7 @@
     "portable",
     "fetch"
   ],
-  "version": "1.0.1",
+  "version": "1.0.3",
   "private": false,
   "license": "MIT",
   "repository": {
@@ -36,10 +36,10 @@
     "dist"
   ],
   "dependencies": {
-    "@fluojs/core": "^1.0.1",
-    "@fluojs/di": "^1.0.1",
-    "@fluojs/notifications": "^1.0.0",
-    "@fluojs/runtime": "^1.0.1"
+    "@fluojs/core": "^1.0.3",
+    "@fluojs/notifications": "^1.0.1",
+    "@fluojs/runtime": "^1.1.1",
+    "@fluojs/di": "^1.0.3"
   },
   "devDependencies": {
     "vitest": "^3.2.4"