arcane-os 0.24.0 → 0.24.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.24.1
+
+- Add a mail CLI parameter table with command scope, purpose, and defaults.
+  Explain the difference between `--app`, `X-Mail-App`, `--report-stdin`, and
+  the nonsecret `--report-key` used for intentional same-message retries.
+- Remove redundant default-profile configuration and the alternate-account
+  placeholder from the main mail example. Align the CLI reference with the
+  shared configuration and credential files while preserving named-profile APIs.
+- Clarify when subscription headers are required, how ordinary delivery failures
+  retain their existing report, and the separate browser callback and verification
+  service paths that can create feedback. Runtime behavior is unchanged.
+
 ## 0.24.0
 
 - Read nonsecret mail settings from `arcane.config.json.mail` and provider keys

package/README.md

@@ -19,7 +19,7 @@ version-locked SDK runtime, while an integrated Arcane checkout uses its live
 `arcane/` runtime. Both profiles preserve the same app URLs, theme, packaging,
 event, cancellation, and browser run contracts.
 
-This checkout defines the `0.24.0` SDK contract. Applications pin one exact npm
+This checkout defines the `0.24.1` SDK contract. Applications pin one exact npm
 version and lockfile; registry state is deliberately not baked into application
 artifacts.
 

package/docs/reference/cli.md

@@ -812,10 +812,13 @@ npm exec -- arcane repo status
 
 ## `arcane mail`
 
-### Resend credential profiles
+### Configuration and provider credentials
 
-The mail commands read `.arcane.env.json` from the invocation directory on Windows,
-Linux, and macOS. The credential subcommands select one profile in that file:
+Mail reads nonsecret settings from `arcane.config.json.mail` and the Resend key
+from `.arcane.env.json.mail.apiKey` in the invocation directory on Windows,
+Linux, and macOS. See [Mail CLI parameters](mail.md#mail-cli-parameters) for the
+complete parameter, configuration-field, default, and precedence reference.
+The credential subcommands manage the provider key:
 
 ```text
 arcane mail key set [profile] [--secret-stdin]
@@ -826,26 +829,43 @@ arcane mail key delete [profile]
 `key set` reads the Resend API key from a hidden terminal prompt. The
 `--secret-stdin` form is for deliberately redirected non-interactive input and
 rejects a TTY before reading. The key is written to `.arcane.env.json` and is never
-accepted in argv or returned in status output. The optional profile defaults
-to `mail`, which selects top-level `RESEND_API_KEY`. Any other exact profile
-selects `MAIL_PROFILES[profile].RESEND_API_KEY`, with no default-key fallback.
+accepted in argv or returned in status output. The optional credential-command
+profile defaults to `mail`, independently of the send/serve configuration.
 
-The minimal file is:
+The minimal `.arcane.env.json` is:
 
 ```json
 {
-  "RESEND_API_KEY": ""
+  "mail": {
+    "apiKey": ""
+  }
 }
 ```
 
 Fill in the key before starting mail, and add `.arcane.env.json` to the project's
-`.gitignore`; the SDK repository already ignores it. Set and delete preserve
-the file's other settings and profiles. Status returns the selected profile,
+`.gitignore`; the SDK repository already ignores it. Keep nonsecret listener
+settings, including certificate file paths, in `arcane.config.json.mail`.
+
+Named profiles remain an optional CLI/toolchain compatibility feature for
+selecting another stored Resend key. An exact name selects
+`mail.profiles[name].apiKey`; the name is independent of incoming application
+names, domains, and subscription keys. One server process uses one selected
+Resend key for all its requests. An absent named key never falls back to the
+default account. Existing root `RESEND_API_KEY` and
+`MAIL_PROFILES[name].RESEND_API_KEY` remain fallbacks when the corresponding
+nested key property is absent. A nested property containing null or an empty
+string means the selected key is absent and takes precedence over a legacy key.
+
+Set and delete preserve the file's other settings and profile containers. New
+keys are written to the nested mail member. Existing legacy keys are updated
+in place unless the selected nested key property exists; delete removes both
+representations of only the selected key. Status returns the selected profile,
 `provider:'resend'`, `storage:'.arcane.env.json'`, and `exists`. Delete returns
 `exists:false` for both a removed and an already-absent credential.
 
-Programmatic `createToolchain().mail(...)` resolves the configuration directory
-from `cwd ?? workspaceRoot ?? process.cwd()`. This uses ordinary Node file
+Programmatic `createToolchain().mail(...)` resolves both files from the directory
+selected by `cwd ?? workspaceRoot ?? process.cwd()`, with no upward search.
+This uses ordinary Node file
 access rather than platform-specific credential processes. An Android host
 supplies a compatible Node runtime and an accessible configuration directory.
 Existing Windows Credential Manager records remain untouched; the JSON reader
@@ -854,11 +874,13 @@ populate or depend on process environment variables for this key.
 
 The SDK's installation directory does not affect this location. With an SDK
 under `my-site/arcane-os-sdk/`, run the command from `my-site/` and keep
-`my-site/.arcane.env.json` alongside that directory. Existing deployments using
+`my-site/arcane.config.json` and `my-site/.arcane.env.json` alongside that
+directory. Existing deployments using
 SDK 0.22.1 or earlier must rename `.env.json` to `.arcane.env.json` while
 preserving its contents; the loader reads only the new name.
 
-Missing files or missing/empty selected keys stop `send` and `serve` with the
+Each file is an optional configuration source. Missing or empty selected keys
+stop `send` and `serve` with the
 configuration path and exact JSON setting to fill in. Invalid JSON and file
 access failures remain observable without printing credential content.
 
@@ -890,11 +912,16 @@ shape:
 
 The CLI forwards the complete provider fields, including template requests.
 Resend owns their accepted shape. The adapter removes the application-only
-`type` field and applies `--from` when supplied; otherwise the report or provider
-template supplies the sender. Direct CLI sending has
-no configured fallback recipients. The Resend credential comes only from the
-selected `.arcane.env.json` profile; omitting `--profile` selects `mail`. Neither the
-key nor report content is accepted through argv or process environment variables.
+`type` field and applies the shared sender from `--from` or `mail.from` when
+supplied; otherwise the report or provider template supplies the sender. Direct
+CLI sending has no configured fallback recipients and requires no listener TLS
+paths. It consumes the configured provider timeout and retry guidance.
+
+The Resend credential comes from the selected `.arcane.env.json` entry.
+An explicit `--profile` overrides `arcane.config.json.mail.profile`; omitting
+both selects the default `mail.apiKey`, with the legacy fallback described
+above. Neither the key nor report content is accepted through argv or process
+environment variables.
 
 The caller owns the nonempty `--report-key`, which is forwarded unchanged.
 Reuse the same key only with the same
@@ -918,22 +945,28 @@ loss after the attempt begins is ambiguous because Resend may have accepted it.
 arcane mail serve [--profile <profile>] [--from <verified-sender>] [--app <label>] [--origin <exact-origin>] [--allow-to <addresses>] [--host 0.0.0.0] [--port 4433] [--request-timeout <ms>]
 ```
 
-The selected `.arcane.env.json` profile supplies only the server-side Resend API key;
-omitting `--profile` selects `mail`.
+The selected `.arcane.env.json` entry supplies only the server-side Resend API
+key. An explicit `--profile` overrides `arcane.config.json.mail.profile`;
+omitting both selects the default key.
 
-Add the listener's certificate configuration at the top level of the same file:
+Add the listener's certificate paths to `arcane.config.json`:
 
 ```json
 {
-  "RESEND_API_KEY": "",
-  "MAIL_TLS_CERT_PATH": ".arcane/mail/fullchain.pem",
-  "MAIL_TLS_KEY_PATH": ".arcane/mail/private-key.pem"
+  "mail": {
+    "certPath": ".arcane/mail/fullchain.pem",
+    "keyPath": ".arcane/mail/private-key.pem"
+  }
 }
 ```
 
 Supply an existing PEM certificate chain and its private key. Paths resolve
-relative to `.arcane.env.json`, or may be absolute. They are shared across provider
-profiles. Missing TLS settings name the fields to fill in before a listener
+relative to the selected configuration directory, or may be absolute. They
+belong to the listener regardless of the provider key selected. Legacy root
+`MAIL_TLS_CERT_PATH` and `MAIL_TLS_KEY_PATH` in `.arcane.env.json` remain
+fallbacks for omitted config paths. Explicit programmatic `certPath` and
+`keyPath` options override those files. Missing TLS settings name the fields
+to fill in before a listener
 opens; the TLS owner reports PEM file errors. Keep private-key material outside
 tracked source. The SDK repository already ignores `.arcane/` and `.arcane.env.json`.
 
@@ -949,7 +982,7 @@ server; the incoming request's `X-Mail-App` identifies the application for
 subscription verification. The HTTP authentication contract pairs that
 application with `Authorization: Bearer <subscription_key>`.
 
-Subscription verification is disabled for this initial service setup. The
+Subscription verification is disabled when no callback is configured. The
 programmatic `createToolchain().mail({action: 'serve', ...})` path accepts
 `verifySubscription({appName, subscriptionKey, signal})`; supplying that callback
 enables verification before each provider attempt. It must resolve to `true`
@@ -958,16 +991,27 @@ failure receives retryable 503; cancellation stops verification before sending.
 The callback connects the actual TWiN Stripe endpoint when its contract is
 ready. There is no guessed URL, response schema, or command-line endpoint flag.
 
-The listener defaults to `0.0.0.0`; `--host` selects another bind host. Browser
-mail defaults to `/v1/mail` on the current domain. `--origin` is optional and
-selects an explicit CORS allowlist when supplied. `--allow-to` optionally
-supplies a comma-separated recipient allowlist. CLI parsing preserves supplied
-address spelling and repeated entries. Programmatic `errorTo` selects fallback
-recipients for error reports; when omitted, the selected `allowTo` list supplies
-that fallback. `--request-timeout`
-adds a caller-selected provider-attempt timeout from 1 through 2147483647
-milliseconds, the Node timer range. When it is omitted, the SDK adds no
-provider timeout.
+The listener defaults to `0.0.0.0:4433`; `mail.host` and `mail.port` configure
+the listener, and explicit `--host` and `--port` override them. Browser mail
+defaults to `/v1/mail` on the current domain. `mail.origins` supplies an exact
+origin array; `--origin` replaces it with one origin. Repeated `--origin`
+options keep the last value. An absent or empty list selects the current
+request authority. Other Origins receive `403 mail_origin_not_allowed`;
+requests without an Origin continue normally. This CORS configuration does
+not filter client IPs or give loopback special treatment.
+
+`mail.recipientAllowlist` supplies the recipient list; `--allow-to` replaces it
+with a comma-separated list. CLI parsing preserves supplied address spelling
+and repeated entries. Programmatic `errorTo` or `mail.errorRecipients` selects
+fallback recipients for error reports. When neither is supplied, the effective
+recipient allowlist supplies that fallback; an explicit empty array supplies
+none. The [Mail CLI parameters](mail.md#mail-cli-parameters) reference also
+documents programmatic aliases and list-replacement precedence.
+
+`--request-timeout` overrides `mail.providerTimeoutMs` and accepts 1 through
+2147483647 milliseconds, the Node timer range. An absent effective timeout
+adds no provider deadline; programmatic/configured null also selects no
+deadline. `mail.bodyTimeoutMs` selects the optional request-body deadline.
 
 After binding, `server.ready` reports lifecycle fields such as
 protocol, optional app label, bind address, port, URL, and `callerAuthentication`

package/docs/reference/mail.md

@@ -272,6 +272,40 @@ committed acceptance result.
 
 ## Operate the CLI and gateway
 
+### Mail CLI parameters
+
+`mail serve` starts the shared mail server. `mail send` makes one direct Resend
+request. `mail key set|status|delete` manages the provider credential.
+
+| Parameter | Command | What it does | When omitted |
+| --- | --- | --- | --- |
+| `--app <label>` | `mail serve` | Supplies a fallback application label for server events. An incoming `X-Mail-App` supplies the request's label. This option does not choose a Stripe account or limit which apps may send mail. | Uses `mail.appId` when configured; otherwise adds no fallback label. |
+| `--from <sender>` | `mail serve`, `mail send` | Overrides the sender, for example `"Dragon Dispatch <dispatch@example.com>"`. On the server, the override applies to every report. Resend must accept that sender. | Uses `mail.from` when configured, then the report's `from` or provider template default. |
+| `--report-stdin` | `mail send` | Reads one complete UTF-8 report JSON object from redirected standard input, including recipients, subject, body, and other provider fields. | Required; the command reports a usage error. |
+| `--report-key <id>` | `mail send` | Identifies one intended email and is forwarded unchanged as Resend's `Idempotency-Key`. Use a new value for a new email; reuse the value and unchanged report for an intentional retry. It is not a credential. | Required; the command reports a usage error. |
+| `--host <address>` | `mail serve` | Selects the listener bind address. `0.0.0.0` accepts connections through all IPv4 interfaces. | Uses `mail.host`, then `0.0.0.0`. |
+| `--port <number>` | `mail serve` | Selects the HTTPS listener port. Explicit `0` asks the operating system for an available port. | Uses `mail.port`, then `4433`. |
+| `--origin <origin>` | `mail serve` | Replaces the configured CORS origins with one exact browser origin, including scheme and any nondefault port. Use the JSON `origins` array for multiple origins; repeated flags keep only the last value. | Uses `mail.origins`; an absent or empty list uses the current request authority. Requests without an `Origin` header continue normally. |
+| `--allow-to <addresses>` | `mail serve` | Replaces the recipient allowlist with a comma-separated list. Applies to `to`, `cc`, and `bcc`, and supplies error-report fallback recipients unless `mail.errorRecipients` is configured separately. | Uses `mail.recipientAllowlist`; an absent or empty list leaves recipients unrestricted. |
+| `--request-timeout <ms>` | `mail serve`, `mail send` | Sets the deadline for one Resend request, in milliseconds. A timeout after sending begins leaves delivery uncertain; it does not schedule a retry. | Uses `mail.providerTimeoutMs`; absent or null adds no provider deadline. |
+| `--profile <name>` | `mail serve`, `mail send` | Selects an alternate saved Resend credential for this invocation. One listener uses that selected provider key for all callers. | Uses `mail.profile` if configured, otherwise the normal `mail.apiKey`. The single-key setup needs no profile setting. |
+| `[profile]` | `mail key set\|status\|delete` | Optional positional name of the credential to manage; it is not a flag. | Manages the normal `mail.apiKey`, independently of `mail.profile`. |
+| `--secret-stdin` | `mail key set` | Reads the Resend API key from deliberately redirected standard input instead of the hidden terminal prompt. | Prompts with hidden input. Machine-output mode requires redirected input. |
+| `--output human\|json\|ndjson` | All mail commands | Selects readable console output, one JSON result, or newline-delimited JSON events. | Uses `human`. |
+| `--help` | CLI | Displays CLI help instead of running the mail operation. | Runs the requested operation. |
+| `--version` | CLI | Displays the SDK version instead of running the mail operation. | Runs the requested operation. |
+
+There is no `--report` flag. `--report-stdin` supplies the message;
+`--report-key` identifies that same message across attempts. Browser `Mail.send()`
+generates and retains its report key automatically.
+
+Mail reads configuration from the directory in which the command runs;
+`--workspace` does not relocate these mail files. Mail HTTPS uses `mail.certPath`
+and `mail.keyPath` in JSON. The `--cert`, `--key`, `--https`, and `--http-port`
+flags belong to browser `dev`/`run`, and `--http` belongs to `dev`.
+
+### Mail configuration
+
 Keep app-supplied SDK settings under named capability members, starting with
 `mail`. Put the nonsecret mail settings in `arcane.config.json` in the directory
 from which the command runs:
@@ -285,7 +319,6 @@ from which the command runs:
       "https://dragons.example",
       "https://www.dragons.example"
     ],
-    "profile": "mail",
     "certPath": "certificates/fullchain.pem",
     "keyPath": "certificates/private-key.pem"
   }
@@ -333,24 +366,16 @@ injected providers, `fetchImpl`, `onEvent`, `requestIdFactory`,
 runtime inputs, not JSON settings. Reports and their idempotency keys remain
 inputs to each send operation.
 
-The default credential profile `mail` selects `.arcane.env.json.mail.apiKey`.
-Other profile names select exact entries in `.arcane.env.json.mail.profiles`:
-
-```json
-{
-  "mail": {
-    "apiKey": "",
-    "profiles": {
-      "another-provider-account": {
-        "apiKey": ""
-      }
-    }
-  }
-}
-```
+The single-key configuration above needs no `profile` or `profiles` member.
+Omitting the selection uses `.arcane.env.json.mail.apiKey`; multiple apps and
+domains can share that provider key.
 
-An absent named profile does not fall back to the default key. The profile
-selects Resend provider credentials; it is separate from the incoming
+For callers that already select an alternate credential, named-profile support
+remains available: `--profile <name>` or `mail.profile` selects
+`.arcane.env.json.mail.profiles[name].apiKey`. An absent named profile does not
+fall back to the default key. Selection happens once when send or serve starts;
+it does not map incoming apps or domains to different provider accounts.
+The profile selects Resend provider credentials, separately from the incoming
 application name and subscriber key. Existing top-level `RESEND_API_KEY` and
 `MAIL_PROFILES[profile].RESEND_API_KEY` remain supported. A nested selected
 `apiKey` takes precedence when the property exists, including null or an empty
@@ -449,8 +474,8 @@ arcane mail send --from "Arcane <verified@example.com>" --report-key <stable-id>
 The redirected UTF-8 JSON object is read completely. Its fields and values
 are retained; the Resend adapter removes the SDK's `type` routing field,
 uses `from` when configured (otherwise the report or provider template supplies
-the sender), and applies configured error-recipient fallback
-when applicable. Resend evaluates its own required provider fields. Message
+the sender). Direct sending supplies no fallback recipients. Resend evaluates
+its own required provider fields. Message
 content is not accepted in argv. Programmatic results and observer events
 preserve the complete report, provider request, provider response, and error detail while
 never exposing either credential.
@@ -579,6 +604,12 @@ key, and `signal` follows the request lifecycle. These control fields stay
 separate from the mail report and Resend payload. The verifier runs for each
 POST request before any provider attempt; results are not cached.
 
+`X-Mail-App` identifies the originating app so the verifier can select that
+app's subscription account, such as the appropriate Stripe account for `BOSS`
+or `TWiN`. It is separate from the gateway's optional `--app` event label.
+The missing-header and Bearer errors below apply only when `verifySubscription`
+is configured. Ordinary `mail serve` does not require either header.
+
 | Configured-verifier outcome | Gateway response |
 | --- | --- |
 | Missing or empty `X-Mail-App` | `400 mail_invalid_headers` |
@@ -602,6 +633,32 @@ CLI startup output says `Subscription verification: disabled` or
 `Subscription verification: configured`. Structured `server.ready` output
 includes the corresponding `callerAuthentication` value.
 
+## Error reports and retries
+
+An incoming report with `type: 'error'` is an email supplied by its caller.
+The gateway's `errorRecipients` setting only supplies fallback recipients for
+that report when its `to` array is empty. A gateway or provider failure returns
+an HTTP error and diagnostic events; it does not generate another error email.
+Gateway event-handler failures are written to the console. Each POST and each
+direct CLI send performs at most one provider attempt, with no automatic server retry.
+
+The browser outbox retains the same report and key after a retryable delivery
+failure. Each drain attempts each eligible record once; a later startup,
+connectivity event, or explicit drain can retry it. Browser `Errors` notification
+failure retains the same pending occurrence and logs a warning without scheduling
+itself again.
+
+A separate browser callback path can feed back into error reporting: a mail-event
+subscriber that repeatedly throws can reach global error capture, create another
+error report, and trigger another mail event. Subscriber failures cannot change
+an already committed mail result, though global capture can report them as new
+errors. This is a source-level possibility, not evidence of a deployed loop.
+
+For a verification service that sends its own emails, its host integration must
+also avoid the circular request path `mail -> verify subscription -> send mail ->
+verify subscription`. The SDK supplies a callback for verification; it does not
+choose that service's caller flow or enable it in ordinary CLI startup.
+
 ## Gateway request lifecycle
 
 The gateway uses the published `node-http-server` instance lifecycle. Its raw

package/docs/reviews/mail-server-purpose-review.md

@@ -480,7 +480,7 @@ files. Their explicit precedence and credential compatibility rules are in the
 | `readMailConfiguration` | Y/Y/N | Keep the cohesive configuration at the SDK owner. Send/serve read each required file once, in parallel when both are needed. A send with an injected credential reader skips the unused secrets file; incoming HTTP requests use the resolved configuration without file reads. Other capability settings stay untouched. |
 | CLI's early default host, port, and send/serve profile values | Y/Y/Y | Remove premature default assignment. The same defaults remain after file configuration resolves, while explicit CLI values retain priority. Assigning defaults before reading JSON would conceal the deployment's chosen settings. |
 | `origins` string array and list replacement | Y/Y/N | Keep one exact list for multiple caller domains. Explicit options replace the file list, including empty arrays. Existing `origin`, `allowTo`, `errorTo`, and `requestTimeout` aliases remain compatible and win over their canonical programmatic names when both are supplied. No normalization or list-merging helper is needed. |
-| Root provider-key, named-profile, and TLS compatibility | Y/Y/N | Preserve live deployments using `RESEND_API_KEY`, `MAIL_PROFILES`, `MAIL_TLS_CERT_PATH`, and `MAIL_TLS_KEY_PATH`. Nested selected key presence takes priority even when null or empty. Named profiles never select a different account's default key. |
+| Root provider-key, named-profile, and TLS compatibility | Y/Y/N | Preserve supported inputs using `RESEND_API_KEY`, `MAIL_PROFILES`, `MAIL_TLS_CERT_PATH`, and `MAIL_TLS_KEY_PATH`. Nested selected key presence takes priority even when null or empty. Named profiles never select a different account's default key. Named-profile deployment use is unverified; the retained behavior is a compatibility contract. |
 | Key set/status/delete operations | Y/Y/N | Preserve credential management and secret-free status. New keys use the nested member; existing legacy keys are updated in place unless a nested key exists. Delete removes both selected representations to prevent an old credential reappearing, preserving other keys, settings, and profile containers. Key commands still default to `mail` independently of the serving profile. |
 | Send configuration | Y/Y/N | Use the same profile, sender, provider-timeout, and retry-guidance settings for direct sending. A send needs provider authority and its report, so listener certificates remain a serve-only prerequisite. Reports and idempotency keys remain per-operation inputs. |
 | Explicit runtime dependencies and callbacks | Y/Y/N | Preserve `readCredential`, provider injection, observation, cancellation, and subscription callbacks as programmatic inputs. A function or signal is not JSON configuration. The portable browser mail import retains its existing dependency boundary. |
@@ -507,3 +507,37 @@ adaptation. Local tests, checks, server launches, live mail sends, and platform
 execution were not performed by this documentation author. Selected package
 verification and publication outcomes belong to the release owner's delivery
 record.
+
+## Parameter examples and error-report path clarification
+
+The ordinary shared mail server needs one Resend key. Its current-domain
+behavior, origin list, and incoming application/subscription verification do
+not select among provider profiles. A named profile selects one stored key
+for an entire send or server invocation. Source inspection found named CLI and
+toolchain inputs plus synthetic tests; it did not establish a deployment that
+uses named mail profiles.
+
+| Method or action | Gates | Decision, callers, and concrete purpose |
+| --- | --- | --- |
+| Explicit default `profile: 'mail'` in setup examples | N/N/Y | Remove the redundant setting. Omission already selects the default key when no named configuration is supplied. CLI send/serve still honor an explicitly selected profile or `mail.profile`. |
+| Extra `another-provider-account` credential placeholder | N/N/Y | Remove it from ordinary setup. It adds an unused account choice to a one-key configuration. Existing optional named-profile behavior remains documented without presenting another account as a setup requirement. |
+| Named-profile CLI/toolchain capability and credential CRUD | Y/Y/N for compatibility | Retain the supported optional profile argument and exact named-key operations. Concrete application/deployment use is unverified. This is an account-selection contract, separate from removing redundant default arguments; its retention makes no claim that the nominal deployment needs it. |
+| Full CLI parameter explanation | Y/Y/N | Keep one canonical [Mail CLI parameters](../reference/mail.md#mail-cli-parameters) table. The CLI reference links to it and describes the current split configuration, selected values, defaults, aliases, and provider behavior without another competing table. |
+| Claim that mail errors can never produce an error-report loop | N/N/Y | Replace the absolute claim with the source-path qualification below. Ordinary server failures do not send another mail; a repeatedly failing browser event subscriber can produce new global error incidents during error-mail delivery. |
+
+The Node gateway reports ordinary request/provider failures through responses,
+observer results, or its console logger. Its error reporter does not call the
+mail sender. In the browser, `Errors` owns global `error` and
+`unhandledrejection` capture and sends error notifications through Mail. A
+failed notification remains pending with a warning rather than immediately
+creating another notification from that send failure.
+
+There is a separate conditional path: a subscriber that repeatedly throws
+while handling Mail events reaches the event authority's listener-failure
+reporter. In browsers with `reportError`, that failure can become a new global
+error incident. Sending that incident through Mail can invoke the same failing
+subscriber again. A loop therefore depends on that subscriber and the active
+global error handler; it is not an automatic server response to an ordinary
+mail failure. This is a static source-path finding, not an observed production
+incident or an executed reproduction. This documentation clarification changes
+no error, subscription, retry, or delivery behavior.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arcane-os",
-  "version": "0.24.0",
+  "version": "0.24.1",
   "description": "Arcane OS JavaScript SDK, project-local CLI, browser runtime, and repository-portable application packager.",
   "type": "module",
   "main": "./src/index.mjs",