virello 0.1.0 → 0.1.1

package/BREAKING_CHANGES.md

@@ -1,5 +1,24 @@
 # Breaking changes
 
+## Virello rename
+
+- The framework is now Virello, with package name `virello`. Replace `rilo`
+  imports and subpath imports with `virello`; TypeScript declaration augmentation
+  must target `virello`. Availability of the npm package name is unverified.
+- Rename `RiloClient` and `RiloClientOptions` to `VirelloClient` and
+  `VirelloClientOptions`. The previous names are no longer exported.
+- Replace the `RILO_` prefix with `VIRELLO_` in environment variables and GitHub
+  repository variables, including `VIRELLO_RELEASES` and
+  `VIRELLO_TEST_REDIS_URL`.
+- Upgrade coordinators, hosts and children together: transport headers and the
+  reserved stats request now use `x-virello-*` and `virello:stats`.
+- Redis task keys now use `virello:tasks:v1:`. Existing tasks under `rilo:tasks:v1:`
+  are not read; drain or migrate them before switching. Branded symbols and
+  pagination component IDs also use the new name, so avoid mixing framework
+  versions in one application and recreate active pagination messages.
+- The Rilo migration below describes the earlier Kairo-to-Rilo rename. When
+  migrating directly from Kairo, apply both renames and use the Virello names.
+
 ## Rilo rename
 
 - Install `rilo` and update all imports and subpath imports from `kairojs` to

package/README.md

@@ -1,4 +1,4 @@
-# Rilo
+# Virello
 
 A modular Discord framework for Bun, written in TypeScript and built on discord.js. Organise your bot into commands, listeners and services, with explicit module loading and shared lifecycle management.
 
@@ -15,11 +15,11 @@ A modular Discord framework for Bun, written in TypeScript and built on discord.
 
 ## Original engine milestone
 
-The experimental [native Discord engine](docs/engine.md) is available through `rilo/engine`. It owns gateway sessions, REST and cache while the existing framework keeps its current runtime. Run `bun examples/engine/offline.ts` for a local connect/reply/resume demonstration with no Discord credentials.
+The experimental [native Discord engine](docs/engine.md) is available through `virello/engine`. It owns gateway sessions, REST and cache while the existing framework keeps its current runtime. Run `bun examples/engine/offline.ts` for a local connect/reply/resume demonstration with no Discord credentials.
 
 ## Getting started
 
-Use **Bun 1.4.3 or newer**. Rilo runs TypeScript directly; no compilation step is required.
+Use **Bun 1.4.3 or newer**. Virello runs TypeScript directly; no compilation step is required.
 
 From this repository, install dependencies:
 
@@ -40,10 +40,10 @@ The host starts two bot processes by default. Try `/ping`, `/stats` and `/shard`
 
 ### Create your own bot
 
-In a separate Bun project, install your local Rilo checkout and discord.js. Replace the path with your checkout location:
+In a separate Bun project, install your local Virello checkout and discord.js. Replace the path with your checkout location:
 
 ```sh
-bun add /absolute/path/to/Rilo discord.js
+bun add /absolute/path/to/Virello discord.js
 ```
 
 Use this layout:
@@ -60,12 +60,12 @@ Create `index.ts`:
 
 ```ts
 import { GatewayIntentBits } from "discord.js";
-import { RiloClient } from "rilo";
+import { VirelloClient } from "virello";
 
 const token = Bun.env.DISCORD_TOKEN;
 if (!token) throw new Error("Set DISCORD_TOKEN in your .env file.");
 
-const client = new RiloClient({
+const client = new VirelloClient({
 	intents: [GatewayIntentBits.Guilds],
 	root: import.meta.dir,
 	modules: { commands: "commands/**/*.ts" },
@@ -81,7 +81,7 @@ await client.login(token);
 Create `commands/ping.ts`:
 
 ```ts
-import { Command } from "rilo";
+import { Command } from "virello";
 
 export default class PingCommand extends Command {
 	static override options: Command.Options = {
@@ -115,13 +115,13 @@ The filename supplies the command name. Module paths are explicit glob patterns
 Import from the package root or a focused entrypoint:
 
 ```ts
-import { RiloClient } from "rilo/client";
-import { Command, Precondition } from "rilo/commands";
-import { Task } from "rilo/scheduling";
-import { Result } from "rilo/utilities";
+import { VirelloClient } from "virello/client";
+import { Command, Precondition } from "virello/commands";
+import { Task } from "virello/scheduling";
+import { Result } from "virello/utilities";
 ```
 
-Other entrypoints include `modules`, `events`, `extensions`, `localisation`, `services`, `sharding`, `discord`, `time` and `validation`. Root and category imports share the same classes and state. Keep TypeScript declaration augmentation on `rilo`.
+Other entrypoints include `modules`, `events`, `extensions`, `localisation`, `services`, `sharding`, `discord`, `time` and `validation`. Root and category imports share the same classes and state. Keep TypeScript declaration augmentation on `virello`.
 
 ## Examples
 
@@ -146,11 +146,11 @@ Use **Bun canary**, the project's standard toolchain. Install it with `bun upgra
 | `bun fmt --check` | Check formatting without writing files  |
 | `bun fmt`         | Apply formatting                        |
 
-Redis integration tests require `RILO_TEST_REDIS_URL` pointing to a disposable Redis instance; otherwise those tests are skipped locally.
+Redis integration tests require `VIRELLO_TEST_REDIS_URL` pointing to a disposable Redis instance; otherwise those tests are skipped locally.
 
 Run `bun scripts/ci.ts` with that loopback Redis URL for complete validation: zero skipped tests, native Bun type checking, linting, formatting and both offline examples. On the Ubuntu x64 CI runner, `bash scripts/checkActions.sh` also checks the workflow with checksum-pinned actionlint.
 
-See [migration notes](BREAKING_CHANGES.md) when moving from an earlier Rilo API.
+See [migration notes](BREAKING_CHANGES.md) when moving from an earlier Virello API.
 
 See [console logging](docs/console-logging.md) for readable text/JSON output,
 redaction, custom logger compatibility and the offline `bun scripts/logging-demo.ts` preview.

package/docs/console-logging.md

@@ -1,8 +1,8 @@
 # Console logging
 
-Rilo uses actual `@lilsnibbi/logger` instances. The library draws the
+Virello uses actual `@lilsnibbi/logger` instances. The library draws the
 timestamps, source names, severity markers, bars, badges, boxes and error trees.
-Rilo prepares safe message content and chooses native per-call display
+Virello prepares safe message content and chooses native per-call display
 options. It adds no console interception, logging service, dependency, buffer
 or background timer.
 
@@ -43,17 +43,17 @@ messages remain literal `\n` and cannot forge additional records.
 
 ## Configuration
 
-| Variable          | Values                                                          | Default                                         |
-| ----------------- | --------------------------------------------------------------- | ----------------------------------------------- |
-| `RILO_LOG_LEVEL`  | `debug`, `info`, `warn`, `error`; `notif`/`alert` also accepted | `info`                                          |
-| `RILO_LOG_FORMAT` | `text`, `json`                                                  | `text`                                          |
-| `RILO_LOG_DETAIL` | `compact`, `full`                                               | `compact`; `DEBUG` defaults to `full`           |
-| `RILO_LOG_LAYOUT` | `auto`, `badge`, `bar`, `box`                                   | `auto`                                          |
-| `RILO_LOG_STACKS` | `off`, `short`, `full`                                          | `short`                                         |
-| `RILO_LOG_WIDTH`  | Integer columns, `32`–`200`                                     | Terminal width capped at `120`; pipes use `100` |
-| `NO_COLOR`        | Any defined value disables color                                | Unset                                           |
-| `FORCE_COLOR`     | `0` disables; a nonempty value enables when permitted           | Unset                                           |
-| `TERM`            | `dumb` disables color                                           | Unset                                           |
+| Variable             | Values                                                          | Default                                         |
+| -------------------- | --------------------------------------------------------------- | ----------------------------------------------- |
+| `VIRELLO_LOG_LEVEL`  | `debug`, `info`, `warn`, `error`; `notif`/`alert` also accepted | `info`                                          |
+| `VIRELLO_LOG_FORMAT` | `text`, `json`                                                  | `text`                                          |
+| `VIRELLO_LOG_DETAIL` | `compact`, `full`                                               | `compact`; `DEBUG` defaults to `full`           |
+| `VIRELLO_LOG_LAYOUT` | `auto`, `badge`, `bar`, `box`                                   | `auto`                                          |
+| `VIRELLO_LOG_STACKS` | `off`, `short`, `full`                                          | `short`                                         |
+| `VIRELLO_LOG_WIDTH`  | Integer columns, `32`–`200`                                     | Terminal width capped at `120`; pipes use `100` |
+| `NO_COLOR`           | Any defined value disables color                                | Unset                                           |
+| `FORCE_COLOR`        | `0` disables; a nonempty value enables when permitted           | Unset                                           |
+| `TERM`               | `dumb` disables color                                           | Unset                                           |
 
 Invalid environment values fall back to defaults. Explicit `loggerOptions.level`,
 `loggerOptions.layout` and `logging.format/detail/stacks/width` take precedence.
@@ -64,9 +64,9 @@ for framework events as they are emitted. `NO_COLOR`, `TERM=dumb`,
 always color free.
 
 ```ts
-import { RiloClient, createConsoleLogger, logEvent } from "rilo/client";
+import { VirelloClient, createConsoleLogger, logEvent } from "virello/client";
 
-const client = new RiloClient({
+const client = new VirelloClient({
 	intents: [],
 	loggerOptions: { layout: "bar", colors: "auto" },
 	logging: { detail: "compact", stacks: "short", width: 100 },
@@ -101,17 +101,17 @@ short display wording in compact mode. Full mode restores the original wording.
 
 ## Detailed records and collection
 
-Set `RILO_LOG_DETAIL=full` to inspect the original event message, full component,
+Set `VIRELLO_LOG_DETAIL=full` to inspect the original event message, full component,
 every retained safe context field and complete request/connection/generation
-identifiers. `RILO_LOG_LEVEL=debug` additionally enables frame and module
+identifiers. `VIRELLO_LOG_LEVEL=debug` additionally enables frame and module
 metadata and defaults to full detail unless compact detail was explicitly chosen.
 No wire bodies are included. Compact request/warning records may show an
 eight-character `ref`; use the full ID from detailed text or JSON for tracing.
 
 ```powershell
-$env:RILO_LOG_LEVEL = 'debug'
-$env:RILO_LOG_DETAIL = 'full'
-$env:RILO_LOG_FORMAT = 'json'
+$env:VIRELLO_LOG_LEVEL = 'debug'
+$env:VIRELLO_LOG_DETAIL = 'full'
+$env:VIRELLO_LOG_FORMAT = 'json'
 bun --env-file=examples/.env examples/coordinator.ts
 ```
 
@@ -126,7 +126,7 @@ change after reconnects.
 
 `Logger`, `LoggerOptions` and `LogLevel` still come directly from the dependency.
 `LogLayout`, `LogCallOptions`, `LogBoxOptions`, `LogFileOptions`, `LogTheme` and
-`LogStyle` are also available from `rilo` / `rilo/client`.
+`LogStyle` are also available from `virello` / `virello/client`.
 
 Native `layout`, `box` corners, `symbols`, `theme`, `timeformat`,
 `includeTimestamps`, `filter`, `transport` and file options work with built-in safe
@@ -158,19 +158,19 @@ const logger = createConsoleLogger(
 Text file sinks retain full safe detail even when console presentation is compact.
 `file.level` can retain debug records filtered from the console. `file.json` keeps
 the dependency's native envelope (`time`, `level`, `name`, `message`); parse its
-`message` string as JSON for the canonical Rilo record. The native transport
+`message` string as JSON for the canonical Virello record. The native transport
 receives a plain rendered line and a record whose `value` is the full sanitized
-Rilo record. Filters still run before formatting. File ownership, rotation,
+Virello record. Filters still run before formatting. File ownership, rotation,
 flushing and closing stay with the dependency.
 
 An explicit `format` / `serialize` hook or native `inspectDepth` / `relativePaths`
 serialization control selects the dependency's original formatting contract and
 owns redaction/presentation. Passing `new Logger(...)`
 directly also retains native behavior. The exported helpers are available on
-`rilo/engine` without importing Discord.js or changing the engine runtime.
+`virello/engine` without importing Discord.js or changing the engine runtime.
 
 Supplying `logger` to a client, coordinator or host preserves that exact instance,
-its settings, method binding and ownership; Rilo never configures or closes it.
+its settings, method binding and ownership; Virello never configures or closes it.
 Custom loggers still need only `debug`, `notif`, `alert` and `error`. They receive
 one contextual string for notices or one contextual `Error` whose `cause` is the
 original thrown value. User error callbacks, events and their arguments are

package/docs/engine.md

@@ -1,6 +1,6 @@
 # Original Discord engine milestone
 
-`rilo/engine` is an experimental, independent Bun client implemented inside Rilo. It owns its gateway session, REST transport and synchronous cache. The existing RiloClient, module system, commands, extensions and root exports retain their current behavior. Importing the engine does not migrate framework features.
+`virello/engine` is an experimental, independent Bun client implemented inside Virello. It owns its gateway session, REST transport and synchronous cache. The existing VirelloClient, module system, commands, extensions and root exports retain their current behavior. Importing the engine does not migrate framework features.
 
 ## Run it
 
@@ -19,7 +19,7 @@ The offline example creates a loopback HTTP/WebSocket server, receives a message
 `bun examples/engine/live.ts` only logs instructions. To opt into Discord yourself, set `DISCORD_TOKEN` and add `--live`. The example requires Guilds, GuildMessages and MessageContent intents, plus permission to read and send in the channel. It replies to `!engine-ping`. Its interaction branch handles an already registered `engine-ping` command; it does not register commands. No live Discord validation was performed.
 
 ```ts
-import { createConsoleLogger, EngineClient, logEvent } from "rilo/engine";
+import { createConsoleLogger, EngineClient, logEvent } from "virello/engine";
 import {
 	GatewayIntentBits,
 	InteractionResponseType,
@@ -103,7 +103,7 @@ Historical validation on 2026-10-11 used Bun 1.4.2 on Windows x64 and a disposab
 
 - `bun install --frozen-lockfile --ignore-scripts`: succeeded without lock changes.
 - `bun run engine:test`: 76 passing tests across four files, 279 assertions.
-- `bun scripts/ci.ts` with `RILO_TEST_REDIS_URL`: 2,361 passing tests across 226 files, 4,943 assertions, zero failures and zero skipped tests.
+- `bun scripts/ci.ts` with `VIRELLO_TEST_REDIS_URL`: 2,361 passing tests across 226 files, 4,943 assertions, zero failures and zero skipped tests.
 - The same CI run passed type checking, the lint and formatting checks configured at the time, the existing offline framework example, the engine offline example and `bun run smoke`.
 - The smoke test packed and installed the package in a temporary consumer, audited public exports/notices, loaded a framework command and ran the native engine connect/reply/resume example.
 
@@ -123,22 +123,22 @@ Reviewed on 2026-10-11:
 
 `$MessageUpdateData` conservatively permits omitted native update fields with Partial plus required id/channel_id. Version 0.38.56 declares the create fields required for updates. This engine retains the agreed partial-update contract without renaming or reinterpreting fields.
 
-The Ovencord checkout was read only. Package boundaries, WebSocketShard/identify strategies, REST SequentialHandler's bucket/major/global separation, and CachedManager's resident patching boundary informed the review. Its source, Collection abstraction, compatibility API and benchmark claims were not copied. Rilo uses its own Map/Set stores, scheduler, lifecycle and helpers.
+The Ovencord checkout was read only. Package boundaries, WebSocketShard/identify strategies, REST SequentialHandler's bucket/major/global separation, and CachedManager's resident patching boundary informed the review. Its source, Collection abstraction, compatibility API and benchmark claims were not copied. Virello uses its own Map/Set stores, scheduler, lifecycle and helpers.
 
 ## Production gaps
 
 - A real bot session needs explicit approval. Extended reconnect soak tests and large real guild payloads remain untested; this milestone uses deterministic mocks and local servers.
-- One shard per client is supported. The local identify budget cannot account for other processes or persist session starts across restarts. Supply waitForIdentify when sharing a token and integrate the existing Rilo coordinator.
+- One shard per client is supported. The local identify budget cannot account for other processes or persist session starts across restarts. Supply waitForIdentify when sharing a token and integrate the existing Virello coordinator.
 - Add full payload validation and broader cache projections. Reaction counts, user updates across every guild, thread membership and ancillary guild collections still need reconciliation. This is not complete Discord cache coverage.
 - Add compression, multipart uploads, additional typed endpoints, proactive global pacing, route-specific sublimits, retry telemetry and deadline-aware prioritization. Different routes can be coalesced only after headers reveal their shared bucket.
 - Interaction callbacks share the bounded REST scheduler. Respond or defer promptly to meet Discord's initial-response deadline; automatic deferral, follow-up helpers and deadline reservation remain future work.
 - Profile real traces before changing policy. Activity traversal, cache misses and JSON parsing need realistic workload evaluation.
 
-## Future Rilo integration
+## Future Virello integration
 
 1. Introduce engine-facing command/listener contexts using native payloads and thin helpers, then test adapters for current framework contracts.
 2. Replace discord.js-specific permission, resolver, collector, pagination and registration dependencies at explicit boundaries without building a compatibility clone.
 3. Wire ShardLink.waitForIdentify, shard readiness and cleanup into EngineClient's injected permits and state hooks.
-4. Port extensions and example bots with contract tests before changing RiloClient's runtime and retiring discord.js dependencies.
+4. Port extensions and example bots with contract tests before changing VirelloClient's runtime and retiring discord.js dependencies.
 
-The independent subpath is deliberate. The root API baseline stays intact, and a test verifies that this engine and the existing offline RiloClient coexist without changing the framework container.
+The independent subpath is deliberate. The root API baseline stays intact, and a test verifies that this engine and the existing offline VirelloClient coexist without changing the framework container.

package/docs/sharding-recovery.md

@@ -20,7 +20,7 @@ through coordinator outages. Unmanaged clients default to `maintenance = false`.
 
 Only authenticated control, an accepted lease, local assignment application and
 coordinator registration clear maintenance. Opening a socket or receiving a
-welcome is insufficient. Rilo does not install a command policy or send outage
+welcome is insufficient. Virello does not install a command policy or send outage
 replies: developers choose the response appropriate to each operation.
 
 ```ts
@@ -93,7 +93,7 @@ Discord shard IDs. Dormant clients remain in maintenance.
 
 Recovery with the same ID and total preserves the Discord session. If the total
 changed, the child closes its old gateway and reconnects with the accepted ID
-and current total, even when the numerical ID is unchanged. RiloClient, modules
+and current total, even when the numerical ID is unchanged. VirelloClient, modules
 and application listeners stay alive. Assignment changes reset gateway resume
 data and guild/channel/user caches. Extension login hooks run once per client;
 Discord ready events may repeat. The gateway adapter targets discord.js 14.
@@ -154,7 +154,7 @@ fetching fresh `GET /gateway/bot` limits. This is an IDENTIFY cooldown, not a
 reconciliation grace period. Permits are charged before sending and never refunded
 on loss. An unexpired allowance cannot increase. `sessionStartLimit` is the
 manual/offline alternative and needs a fresh snapshot on every start and expiry.
-Restarting Rilo does not reset Discord's allowance.
+Restarting Virello does not reset Discord's allowance.
 
 Upgrade coordinator, hosts and children together: the internal protocol changed.
 Restart running processes deliberately to load the new version. `statePath`,

package/docs/sharding-scaling.md

@@ -8,7 +8,7 @@ the same `ShardManager` and bot entrypoint.
 ## Coordinator configuration
 
 ```ts
-import { ShardCoordinator } from "rilo/sharding";
+import { ShardCoordinator } from "virello/sharding";
 
 const coordinator = new ShardCoordinator({
 	shardCount: 2,
@@ -180,7 +180,7 @@ cooldown, readiness and allowance checks. Periodic checks continue automatically
 
 Structured logs emit `scaling_status`, `scaling_failed` and host `reassigned`
 events. Ordinary waiting/stable reasons are logged only when status changes.
-Use `RILO_LOG_FORMAT=json` for full context. Logs contain counts and host IDs,
+Use `VIRELLO_LOG_FORMAT=json` for full context. Logs contain counts and host IDs,
 not guild IDs, tokens or application payloads.
 
 Upgrade coordinator, hosts and children together. The internal transport adds

package/docs/sharding-stats.md

@@ -22,8 +22,8 @@ const shardZero = one.get(0);
 ```
 
 The return type is `Promise<ReadonlyMap<number, ShardStatsResult>>`. Import
-`ShardStats`, `ShardStatsResult` and `ShardCallOptions` from `rilo` or
-`rilo/sharding`. Entries follow the existing request result shape: `{ shard,
+`ShardStats`, `ShardStatsResult` and `ShardCallOptions` from `virello` or
+`virello/sharding`. Entries follow the existing request result shape: `{ shard,
 ok: true, value }` or `{ shard, ok: false, error }`. Errors are frozen `ShardError`
 copies with a `code` and `message`; a failed entry has no `value` property.
 
@@ -33,7 +33,7 @@ Every call makes new requests through the coordinator, including a request to
 the caller's own shard. The destination reads its client and process state only
 when that request arrives. Stats never use the coordinator's periodic scaling
 metrics, an earlier successful result, or a local shortcut as a fallback.
-The private request name `rilo:stats` is reserved and cannot be registered with
+The private request name `virello:stats` is reserved and cannot be registered with
 `handle()`.
 
 Without an ID, the target set is `0..shardCount - 1` from the caller's reconciled

package/examples/README.md

@@ -56,7 +56,7 @@ Run these commands from the **repository root**, using Bun 1.4.3 or newer.
    bun --env-file=examples/.env examples/host.ts
    ```
 
-The host starts `bot.ts` for each assigned shard. Don't run `bot.ts` directly or set `RILO_SHARD` yourself. Wait for each shard's ready message, then try the commands in Discord. The coordinator may space out logins, so the shards won't always become ready together.
+The host starts `bot.ts` for each assigned shard. Don't run `bot.ts` directly or set `VIRELLO_SHARD` yourself. Wait for each shard's ready message, then try the commands in Discord. The coordinator may space out logins, so the shards won't always become ready together.
 
 ## Try the commands
 
@@ -106,7 +106,7 @@ Coordinator calls fail immediately while unavailable. Opt into bounded waiting
 with `{ waitForCoordinator: true, timeoutMs: 5000 }`; the deadline includes the
 wait and execution. Broadcasts share one deadline across all targets. Sent calls
 are never replayed. `/shard` demonstrates an application-selected outage reply
-using `client.maintenance`; Rilo does not automatically block your commands.
+using `client.maintenance`; Virello does not automatically block your commands.
 
 Restart the host after editing bot code. Stop the host first, then the coordinator, with Ctrl+C. A normal host shutdown stops its children and releases its assignment. Child crashes are retried with backoff; repeated crashes eventually stop that shard, so check the logs.
 
@@ -127,8 +127,8 @@ bounded error trees. Pipes use plain badges. Routine events show concise source
 names and useful counts without repeated date rows, field grids or UUID blocks.
 Queueing, permitting and confirming a login remain three distinct records.
 Output wraps to the terminal, capped at 120 columns; pipes default to 100.
-Set `RILO_LOG_WIDTH=64` or `logging.width` for a fixed width, and
-`RILO_LOG_LAYOUT=badge|bar|box` to select a native layout explicitly.
+Set `VIRELLO_LOG_WIDTH=64` or `logging.width` for a fixed width, and
+`VIRELLO_LOG_LAYOUT=badge|bar|box` to select a native layout explicitly.
 
 Each live bot emits one info readiness message after the registration pass,
 with its shard, command and guild counts. The ready listener adds a debug cache
@@ -146,13 +146,13 @@ set it. Startup failures release any constructed resources. Ctrl+C/SIGTERM
 reports shutdown requested, then completion or a cleanup failure; a failed
 startup or cleanup sets a nonzero exit status.
 
-Use `RILO_LOG_DETAIL=full` for original messages and full correlation fields.
-`RILO_LOG_LEVEL=debug` adds frame/heartbeat metadata and defaults to full detail.
-`RILO_LOG_FORMAT=json` keeps the full structured schema, independent of compact
-text choices; `RILO_LOG_STACKS=off` omits locations. See
+Use `VIRELLO_LOG_DETAIL=full` for original messages and full correlation fields.
+`VIRELLO_LOG_LEVEL=debug` adds frame/heartbeat metadata and defaults to full detail.
+`VIRELLO_LOG_FORMAT=json` keeps the full structured schema, independent of compact
+text choices; `VIRELLO_LOG_STACKS=off` omits locations. See
 [console logging](../docs/console-logging.md) for native themes, symbols, files,
 per-call options and the local demo. To supply your own logger, pass it to
-`createBot(logger)` in `client.ts`; Rilo keeps that exact instance.
+`createBot(logger)` in `client.ts`; Virello keeps that exact instance.
 
 The coordinator and hosts keep sharding coordination in memory. During a
 coordinator restart, existing children keep Discord open in maintenance while
@@ -178,8 +178,8 @@ and obsolete configuration. Existing state files can stay unused.
 For detailed coordinator diagnostics in PowerShell:
 
 ```powershell
-$env:RILO_LOG_LEVEL = 'debug'
-$env:RILO_LOG_FORMAT = 'json'
+$env:VIRELLO_LOG_LEVEL = 'debug'
+$env:VIRELLO_LOG_FORMAT = 'json'
 bun --env-file=examples/.env examples/coordinator.ts
 ```
 
@@ -208,7 +208,7 @@ other. An existing process keeps its loaded code; the old plain
 | `SHARD_HOST_MAX_SHARDS`           | Local host capacity, required for automatic scaling without `SHARD_WORKERS`                     |
 | `SHARD_TLS_CERT`, `SHARD_TLS_KEY` | PEM certificate and private key paths for the coordinator's TLS listener                        |
 
-The env file is ignored by Git. Legacy `sharding.sqlite*` files and `.rilo-sharding/` directories remain ignored and are no longer used.
+The env file is ignored by Git. Legacy `sharding.sqlite*` files and `.virello-sharding/` directories remain ignored and are no longer used.
 
 ## More than one machine
 

package/examples/bot.ts

@@ -1,4 +1,4 @@
-import { logEvent } from "rilo/client";
+import { logEvent } from "virello/client";
 import { createBot } from "./client";
 import { ExampleConfigurationError, requiredEnv } from "./config";
 import { cleanupFailedStartup, exampleLogger, startupFailed } from "./logging";
@@ -15,7 +15,7 @@ async function main(): Promise<void> {
 	try {
 		if (!client.sharding.enabled)
 			throw new ExampleConfigurationError(
-				"RILO_SHARD",
+				"VIRELLO_SHARD",
 				"Start examples/host.ts; the host launches one bot process per assigned shard.",
 			);
 		if (offline) {

package/examples/client.ts

@@ -1,16 +1,16 @@
 import "./contracts";
 import { GatewayIntentBits } from "discord.js";
-import { RiloClient, type LoggerLike } from "rilo/client";
-import { ApplicationCommandRegistries } from "rilo/commands";
+import { VirelloClient, type LoggerLike } from "virello/client";
+import { ApplicationCommandRegistries } from "virello/commands";
 import { developmentGuild } from "./config";
 import { exampleLogger } from "./logging";
 
-export function createBot(logger: LoggerLike = exampleLogger): RiloClient {
+export function createBot(logger: LoggerLike = exampleLogger): VirelloClient {
 	const guildId = developmentGuild();
 	ApplicationCommandRegistries.setDefaultGuildIds(
 		guildId ? [guildId] : undefined,
 	);
-	const client = new RiloClient({
+	const client = new VirelloClient({
 		intents: [GatewayIntentBits.Guilds],
 		logger,
 		root: import.meta.dir,

package/examples/commands/ping.ts

@@ -1,5 +1,5 @@
 import { MessageFlags } from "discord.js";
-import { Command } from "rilo/commands";
+import { Command } from "virello/commands";
 import { registerCommand } from "../registration";
 
 export default class PingCommand extends Command {

package/examples/commands/shard.ts

@@ -1,6 +1,6 @@
 import { MessageFlags } from "discord.js";
-import { logEvent } from "rilo/client";
-import { Command } from "rilo/commands";
+import { logEvent } from "virello/client";
+import { Command } from "virello/commands";
 import { registerCommand } from "../registration";
 
 export default class ShardCommand extends Command {

package/examples/commands/stats.ts

@@ -1,6 +1,6 @@
 import { MessageFlags } from "discord.js";
-import { logEvent } from "rilo/client";
-import { Command } from "rilo/commands";
+import { logEvent } from "virello/client";
+import { Command } from "virello/commands";
 import { registerCommand } from "../registration";
 import { formatStats, summarizeStats } from "../stats";
 

package/examples/config.ts

@@ -1,4 +1,4 @@
-import { type } from "rilo/validation";
+import { type } from "virello/validation";
 
 /** Names identify configuration problems without printing their values. */
 export class ExampleConfigurationError extends Error {

package/examples/contracts.ts

@@ -8,7 +8,7 @@ export interface ExampleShardStats {
 	commands: string[];
 }
 
-declare module "rilo" {
+declare module "virello" {
 	interface ShardRequests {
 		exampleStats: { input: null; output: ExampleShardStats };
 	}

package/examples/coordinator.ts

@@ -1,4 +1,4 @@
-import { ShardCoordinator } from "rilo/sharding";
+import { ShardCoordinator } from "virello/sharding";
 import {
 	ExampleConfigurationError,
 	integerEnv,

package/examples/engine/live.ts

@@ -2,7 +2,7 @@ import {
 	GatewayIntentBits,
 	InteractionResponseType,
 } from "discord-api-types/v10";
-import { EngineClient, logEvent } from "rilo/engine";
+import { EngineClient, logEvent } from "virello/engine";
 import { requiredEnv } from "../config";
 import { exampleLogger, startupFailed } from "../logging";
 import { onShutdown } from "../shutdown";
@@ -45,7 +45,7 @@ async function main(): Promise<void> {
 	client.on("messageCreate", async (message) => {
 		if (!message.data.author.bot && message.data.content === "!engine-ping")
 			await message.reply({
-				content: "Pong from Rilo engine.",
+				content: "Pong from Virello engine.",
 				allowed_mentions: { parse: [] },
 			});
 	});
@@ -57,7 +57,7 @@ async function main(): Promise<void> {
 			await interaction.respond({
 				type: InteractionResponseType.ChannelMessageWithSource,
 				data: {
-					content: "Pong from Rilo engine.",
+					content: "Pong from Virello engine.",
 					allowed_mentions: { parse: [] },
 				},
 			});

package/examples/engine/offline.ts

@@ -1,4 +1,4 @@
-import { EngineClient, logEvent } from "rilo/engine";
+import { EngineClient, logEvent } from "virello/engine";
 import { exampleLogger } from "../logging";
 import { MockDiscord } from "./MockDiscord";
 
@@ -34,7 +34,7 @@ async function main(): Promise<void> {
 	const resumed = Promise.withResolvers<void>();
 	client.on("messageCreate", async (message) => {
 		await message.reply({
-			content: "Pong from the original Rilo engine.",
+			content: "Pong from the original Virello engine.",
 			allowed_mentions: { parse: [] },
 		});
 		replied.resolve();

package/examples/host.ts

@@ -1,4 +1,4 @@
-import { ShardManager } from "rilo/sharding";
+import { ShardManager } from "virello/sharding";
 import { integerEnv, requiredEnv } from "./config";
 import { cleanupFailedStartup, exampleLogger, startupFailed } from "./logging";
 import { onShutdown } from "./shutdown";

package/examples/listeners/ready.ts

@@ -1,5 +1,5 @@
-import { logEvent } from "rilo/client";
-import { Events, Listener } from "rilo/events";
+import { logEvent } from "virello/client";
+import { Events, Listener } from "virello/events";
 
 export default class ReadyListener extends Listener<typeof Events.ClientReady> {
 	static override options: Listener.Options = {

package/examples/logging.ts

@@ -1,4 +1,4 @@
-import { createConsoleLogger, type LoggerLike, logEvent } from "rilo/engine";
+import { createConsoleLogger, type LoggerLike, logEvent } from "virello/engine";
 import { ExampleConfigurationError } from "./config";
 
 // One logger per process; framework and example records use the same output settings.

package/examples/offline.ts

@@ -1,6 +1,6 @@
 import "./contracts";
-import { logEvent } from "rilo/client";
-import { ShardCoordinator, ShardManager } from "rilo/sharding";
+import { logEvent } from "virello/client";
+import { ShardCoordinator, ShardManager } from "virello/sharding";
 import { exampleLogger } from "./logging";
 import { summarizeStats } from "./stats";
 

package/examples/registration.ts

@@ -1,5 +1,5 @@
-import { container } from "rilo/client";
-import type { Command } from "rilo/commands";
+import { container } from "virello/client";
+import type { Command } from "virello/commands";
 
 export function registerCommand(
 	registry: Command.Registry,

package/examples/shutdown.ts

@@ -1,4 +1,4 @@
-import { type LoggerLike, logEvent } from "rilo/engine";
+import { type LoggerLike, logEvent } from "virello/engine";
 import { exampleLogger } from "./logging";
 
 export function onShutdown(

package/examples/stats.ts

@@ -1,4 +1,4 @@
-import type { ShardResult } from "rilo/sharding";
+import type { ShardResult } from "virello/sharding";
 import type { ExampleShardStats } from "./contracts";
 
 /** Console diagnostics stay separate from the Discord reply copy below. */

package/package.json

@@ -1,12 +1,12 @@
 {
 	"name": "virello",
-	"version": "0.1.0",
+	"version": "0.1.1",
 	"description": "A modular Discord framework for Bun, written in TypeScript.",
 	"type": "module",
 	"license": "MIT AND Apache-2.0",
 	"repository": {
 		"type": "git",
-		"url": "https://github.com/lilsnibbi/rilo.git"
+		"url": "https://github.com/lilsnibbi/virello.git"
 	},
 	"exports": {
 		".": {