SuavePlan/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated skills

Browse Source
This commit is contained in:
admin
2026-06-09 21:06:27 +01:00
parent db1ce43ee1
commit 427a5bd919
1283 changed files with 24684 additions and 2313 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
plugins/document-navigator/docs/communication/messaging/discord-client/README.md
View File

@@ -97,4 +97,3 @@ new DiscordBotClient({
|--------|------|--------|
| `discord_client.request.total` | Counter | `kind`, `method`, `outcome`, `status` |
| `discord_client.request.duration_ms` | Histogram | `kind`, `method`, `outcome` |

1
plugins/document-navigator/docs/communication/messaging/imessage-adapter/README.md
View File

@@ -117,4 +117,3 @@ to bind subsequent records to the chosen provider.
Server-tier (Bun on macOS). The `bun:sqlite` import is reached via
`createRequire(import.meta.url)` so the static module graph never
attempts to resolve the specifier on a non-Bun runner.

2
plugins/document-navigator/docs/communication/messaging/imessage-adapter/src/watcher/imessage-watcher.md
View File

@@ -95,7 +95,7 @@ const parsed = await watcher.poll({ signal: controller.signal });
The legacy `on/off` API delegates straight to the typed `EventBus`,
which keeps the two surfaces in lockstep — there is no separate
listener registry. The cursor advances inside the row loop *before*
listener registry. The cursor advances inside the row loop _before_
filters apply, so filtered rows are not re-fetched next tick. The
scheduler-vs-explicit-poll error policy is asymmetric on purpose: a
caller invoking `poll({ signal })` directly wants the error; the

1
plugins/document-navigator/docs/communication/messaging/notification-channel/README.md
View File

@@ -114,4 +114,3 @@ The 11-code `defineCodes("NOTIFICATION_CHANNEL", […])` registry preserves lite
## License
MIT

1
plugins/document-navigator/docs/communication/messaging/slack-client/README.md
View File

@@ -84,4 +84,3 @@ Four instruments under meter `@suaveplan/slack-client@0.1.0`:
## License
MIT

1
plugins/document-navigator/docs/communication/messaging/sms-providers/README.md
View File

@@ -114,4 +114,3 @@ await sns.verifyNotification(payload, async (pem, msg, sigB64) => {
bunx turbo lint typecheck test build --filter=@suaveplan/sms-providers
bunx turbo test:coverage --filter=@suaveplan/sms-providers # 100/100/100/100
```

2
plugins/document-navigator/docs/communication/messaging/sms-providers/src/crypto/default-hmac.md
View File

@@ -71,4 +71,4 @@ const sig = toHex(await hmac("SHA-256", utf8("secret"), utf8("payload")));
## Implementation Notes
`toHex` builds the string with `String#padStart(2, "0")` per byte rather than the bigint-shift trick to keep the implementation legible. `constantTimeEqual` never short-circuits on length mismatch *during* iteration — the early `length` check is unavoidable but does not leak content. Subtle's `importKey` is called inside `defaultHmac` rather than cached because production callers typically supply a fresh `key` per call.
`toHex` builds the string with `String#padStart(2, "0")` per byte rather than the bigint-shift trick to keep the implementation legible. `constantTimeEqual` never short-circuits on length mismatch _during_ iteration — the early `length` check is unavoidable but does not leak content. Subtle's `importKey` is called inside `defaultHmac` rather than cached because production callers typically supply a fresh `key` per call.

1
plugins/document-navigator/docs/communication/messaging/sms/README.md
View File

@@ -130,4 +130,3 @@ await service.send({
- [`service/legacy-emitter.md`](./src/service/legacy-emitter.md) — legacy `on/off/emit` mirror
- [`routes/problem-json.md`](./src/routes/problem-json.md) — RFC 7807 Hono helper
- [`otel/metrics.md`](./src/otel/metrics.md) — OpenTelemetry instruments

2
plugins/document-navigator/docs/communication/messaging/telegram-client/README.md
View File

@@ -88,5 +88,3 @@ Call `resetTelegramClientMetrics()` from tests after replacing the global
- Tests use injected `fetch` / `clock` — no mocks, no network.
- 100% istanbul coverage on touched modules.