pi-roundtable 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -5,6 +5,153 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-10-01
+
+### Added
+
+- A Traditional Chinese README, `README.zh-TW.md`, linked from the English one.
+
+### Changed
+
+- `bin` is `src/cli/roundtable.mjs`, without the leading `./`: the npm that publishes from CI warned that it removed the `./` path, though 0.2.0's registry entry kept the `roundtable` command. An export test refuses a `bin` path that starts with a dot.
+
+## [0.2.0] - 2026-10-01
+
+### Added
+
+- Main entry contracts and operational errors: `Admission`, `AgentTurnScope`, `AttachmentRef`, `BackgroundTurn`, `ChannelKey`, `ConversationPort`, `DefineOverrides`, `DrainOptions`, `EventSink`, `HoldCheck`, `HoldContext`, `HttpRoute`, `ImageDrawer`, `InboundMessage`, `Judge`, `JudgeError`, `JudgeModel`, `LinkedSessions`, `ListenerAddress`, `ListenerConfig`, `Locale`, `LogEntry`, `LogFn`, `Logger`, `MigrationError`, `Pronouns`, `ProviderError`, `Providers`, `QueuePort`, `ReferenceImage`, `ResolvedProviders`, `ScheduledOutcome`, `SessionContext`, `SessionPlan`, `SessionToolSnapshot`, `ThinkingLevel`, `TierConfig`, `ToolSelection`, `ToolTierTable`, `ToolTiers`, `TransientTask`.
+- Testing fixtures: `OWNER_SPEAKER`, `TEST_GUILD`, `TestStore`, `describeDb`, `fakeThreads`, `openTestStore`, `silentLogger`, `testDatabaseUrl`, `useTestLocale`.
+- The unstable-before-1.0 `pi-roundtable/kit` entry for owner commands, claims, and naming existing core services.
+  Its helpers and their supporting data types are `AUTO_THINKING`, `AgentCategory`, `AgentChannelLookup`, `AgentChannels`, `AgentError`, `AgentModels`, `AgentOps`, `AgentPost`, `AgentTurnRunner`, `Approval`, `AskOption`, `AssistantLike`, `Backlog`, `CategoryLayout`, `ChannelMessage`, `ChannelQueue`, `ChatSurface`, `ChoiceAnswer`, `ChoiceQuestion`, `DashboardBoard`, `DelegationWorker`, `DispatchThread`, `DispatchThreads`, `DispatchThreadsOptions`, `GroupMessage`, `ModelRef`, `OutboundReply`, `OwnerAnswer`, `OwnerIdentity`, `OwnerNotifier`, `OwnerPrompts`, `OwnerQuestion`, `ScoreQuestion`, `SpeakerFacts`, `SpeakerPolicy`, `THINKING_LEVELS`, `ThinkingPicker`, `ThreadHost`, `YesNoQuestion`, `attachmentsOf`, `channelSegment`, `discordKey`, `formatModelRef`, `headline`, `lastAssistant`, `outcome`, `ownerAttachmentDir`, `parseModelRef`, `quietLinks`, `settleTurn`, `splitReply`, `textOf`, `thinkingLabel`, `toolError`, `toolText`, `withAttachmentsBlock`, `withReference`.
+- The migration ledger: a migration's `runs` is `"once"` (the default) or `"every-boot"`, and the host records each `once` migration in the table `roundtable_migrations` under the id `<plugin>/<name>`, created by the host itself. A `once` migration runs in its own transaction under an advisory lock with its ledger row written in that transaction, so a failed migration records nothing and two hosts starting together apply it once; an `every-boot` migration runs each start, unrecorded, and must be idempotent, as every migration had to be. A start logs one `migrations` line (ids applied now, number skipped, number every-boot), a migration that fails is named by its id, and `roundtable doctor` runs the same runner in a rolled-back transaction. `migrateDatabase(url, plugins)` and `MigrationReport` are in the main entry: they run plugins' migrations over a URL with the ledger and close their connection, for a test or a script.
+- `Logger` is core's own structural interface (`debug`, `info`, `warn`, `error`, `fatal` as `LogFn`, and `child(fields)`), which a pino logger satisfies as it is, and `LogEntry` (one line as pino writes it) is in the main entry. Every plugin's `context.logger` is a child that adds `plugin: <name>` to its lines, and the error report head shows the plugin next to `app` and `module`; the fingerprint of an error is unchanged.
+- `DefineOverrides.errorSink(entry)`: a plain function that also receives every `error` and `fatal` line of the logger `defineRoundtable` builds, after the ops agent's report (`config.ops`). It must not throw. A logger passed as `DefineOverrides.logger` is the caller's own, and forwards its error lines itself.
+- The `requiredTools` contribution: the tool names startup refuses to run without, besides those each session tool requires, merged over plugins with each name once (`LinkedSessions.requiredTools`). A plugin that owns the owner's conversations contributes it with the `"owner"` persona.
+- Test fidelity: `testHost` with `TestHost` and `TestHostOptions` boots the built-in plugins and yours over the test database with Discord and the runtime standing in, and returns the probe's `context`, the `conversations`, the slash commands `added` and `composed()`, the session tools of an owner or agent scope, a real `sessionContext`, and `stop()`; `sessionTools` lists the tools of any session extension, including one that also registers commands or event handlers. `testPlugin` gains the `holds` result (the plugin's hold rules chained as the host links them), the `owner` and `forwardJoinMs` options, the real `BACKGROUND_TURNS` by default, the real confirmation judge as `AGENTS.approvals` once `AGENTS` is given and a judge provider is, and the agent server's own claim when `AGENTS` is given a `team`. `holdChain` is in `pi-roundtable/kit`, and `useEagerCatalog` and `eagerText` are in `pi-roundtable/testing`: the probe that proves a value was not built from the catalog before the host applied its environment.
+- Socket permissions: a unix-socket `ListenerConfig` takes `mode` (the socket file's permission bits), and the configuration's `http.socketMode` sets it for the `public` listener. The default is `0o660`, so only the socket's owner and group connect; a proxy that runs as a user outside that group needs `0o666` set explicitly.
+- Route errors: a route whose handler throws or rejects answers `500 Internal Server Error` with that fixed body and the listener keeps serving. The host logs one error line with the route's `name` and `listener`, never the request URL, since paths may hold tokens. The listeners' servers also answer errors raised outside a route with the same 500.
+- Declaration-signature and type-leak baseline checks, alongside parser-based runtime/type export snapshots.
+- A guide entry index, context service types, database/locale fixture notes, and tested consumer compiler requirements.
+- `PluginContext.env` (`HostEnv`: `locale`, `timeZone`, `now()`) and the `environment` host option (`HostEnvironment`: locale, time zone, assistant name, root command, Pi agent directory), so a plugin reads its own host's time zone and locale.
+
+- Neutral hooks and keys, replacing the built-in-shaped ones (see Removed): `Service.startInBackground`, the `serviceStarted` event with `ServiceStartedEvent` and `ServiceStartOutcome`, `ChannelClaim.stop`, the agent server's names `AGENT_SERVER_PLUGIN`, `AGENT_TEAM_SERVICE` and `AGENT_SERVER_PRIORITY`, `parseChannelKey` and `channelKey` (`channelKey(surface, id)`) for `<surface>:<id>` channel keys, and `ConversationKind`, which is any string.
+
+- The chat-surface slot: a plugin contributes `surfaces`, each a `ChatSurface` for the channel keys of one prefix (`surface`, `start(deliver)`, `sendReply`, and optionally `stop`, `startTyping`, `showStop`, `react`, `unreact`, `prompts`), and calls them through `PluginContext.surfaces`, a `SurfacePort` that picks the surface by a key's prefix (`of`, `sendReply`, `startTyping`, `showStop`, `react`, `unreact`, `prompts`; calls during setup throw `NotLinkedError`).
+  The host starts each surface as a service named `surface:<prefix>` before its plugin's own services, refuses two surfaces with one prefix, and logs and drops a message delivered under another prefix.
+  The main entry now also names `OutboundReply`, `OwnerPrompts`, `Approval`, `AskOption`, `OwnerAnswer`, and `OwnerQuestion`, which a surface's methods use; they moved there from `pi-roundtable/kit`, together with `ChatSurface`.
+  `examples/fake-surface.ts` is an in-memory surface for tests and a model for a real one.
+- The agent server asks the owner for approvals and `ask_user` answers through `context.surfaces.prompts`, so they work in a channel of any surface that has `prompts`; before, only Discord's channels had them.
+- The runtime slot: `Providers.runtime` takes a `RuntimeFactory` (`(deps: RuntimeDeps) => AgentRuntime`), and a plugin that fills it replaces the whole conversation runtime (agent turns, the owner's conversations, steering, held actions, transcripts) in place of Pi. The agent server builds the Pi runtime only when no plugin fills the slot, so a host that fills none is unchanged. `RuntimeDeps` hands the factory `logger`, `env`, `owner`, `sessions()`, `toolTiers`, `prompts`, `agents` (`AgentSessions`), `confirmations` (`HeldActionStore`), and `judge`.
+  `AgentRuntime` (the main entry's now, with `ContextUse`) has the methods the agent team calls besides the turn: `heldActions`, and the optional `contextUsage`, `preflight`, and `dispose`; the agent server's preflight and its `runtime` service call the optional ones. The unknown-slot refusal names `runtime` among the valid slots.
+  `AgentRunError` is exported, `TurnResult.error` is an `Error`, and the turn types a runtime author needs moved to the main entry from the kit: `AgentRuntime`, `AgentSessions`, `AttachmentFailure`, `ContextUse`, `HeldCall`, `LoadedSkill`, `ModelImage`, `PendingConfirmation`, `StoredAttachment`, `TranscriptEntry`, `TurnAttachments`, `TurnRequest`, `TurnResult`, and `TurnSelection`.
+- Personas: a plugin contributes `personas` (`Persona`: `{ kind, prompt() }`), the system prompt of every non-agent conversation of one kind, and `LinkedSessions.persona(kind)` looks one up. `TurnRequest.kind` names the conversation's kind (`"owner"` when absent), and the Pi runtime picks the persona when it makes the session. Two personas of one kind, and the reserved kind `"agent"`, are refused when the host starts, naming the plugins; a turn of a kind with no persona is refused naming `personas` instead of running with the owner's prompt; `"owner"` keeps the host's `ownerSessions.persona`, and a contributed `"owner"` persona is refused on a host that sets one.
+- `context.turns` (`ConversationTurns`, with `ConversationTurnInput`): `run({ channel, kind, text, speaker, attachments?, selection?, steerable?, interactive?, confirmed?, reply? })` runs one turn of a conversation a claim owns, over the runtime and the surfaces: it shows typing and the stop control, emits `turnStarted` and `turnEnded`, settles a thrown runtime into a failed result, and posts the answer or a failure or stopped notice through the surface unless `reply` is given. Calls during `setup` reject with `NotLinkedError`.
+- `testPlugin` options `surfaces` (injected chat surfaces), `core` (`TestCore`: the parts of `context.core` the plugin reads; an ungiven member throws naming the option), `conversations` (overrides), and `turns`, and the result fields `conversations`, `turns`, `surfaces`, and `runtime` (the runtime the plugin's `runtime` provider built from stand-in dependencies). `runTool(name, args, { speaker, channel })` runs in the given channel. `conversations` now routes to the claims of the plugin under test, so a message a surface delivers reaches them.
+- `examples/echo-runtime.ts` (a plugin that fills the `runtime` slot) and `examples/study-room.ts` (a conversation kind with its own persona, run through `context.turns`), each with a test that uses only the public entries.
+- `activeToolsExtension` in `pi-roundtable/kit`, taking a function that returns the tool names: the extension that pins a session's active tools before every run, the one the core places last in each session, for a runtime or worker of your own.
+- Background targets: a plugin contributes `backgroundTargets` (`BackgroundTarget`: `name`, `label(locale)`, and optional `schedules` and `delegation` limits), which say whose turn a schedule or a delegated task is and how much may be scheduled or delegated for it. `ConversationPort.target(name)` reads one when it is used, the router skips a turn whose target no plugin contributes (`no plugin contributes the background target "<name>"`, recorded as the schedule's last status, never falling back to another target), and two targets of one name are refused at start, naming both plugins. The agent server contributes `OWNER_TARGET` (name `"owner"`, exported from the main entry), and its claim answers only that target. `examples/support-desk.ts` is a plugin with a target of its own, with a test.
+- Keyed services: a plugin provides a service other plugins read, and a plugin replaces a built-in one.
+  `serviceKey` (`serviceKey(id)`) makes a typed name, `ServiceKey`, and `PluginContext.services` (`Services`) has `get(KEY)`, `find(KEY)` and `provide(KEY, value)`; `RoundtablePlugin` has `provides` (the keys its setup provides, which the host checks are provided once setup returns) and `replaces` (the built-in services it takes over: the host drops the plugin that provides them and sets the replacement up where it stood).
+  `get` of a key not provided yet names the key and the plugin to register first, `find` is `undefined` when no registered plugin declares it and throws when one declares it but has not set up yet, `provide` is refused for a key the plugin does not declare, after setup, and twice, and the host refuses two plugins that declare one key, a replaced key nobody else provides, two replacements of one key, a replacement that does not list the key in `provides`, and a partial replacement, where the dropped plugin also provides a key the replacement does not replace.
+  The built-in plugins provide `AGENTS` (`AgentServer`: `team`, `directory`, `runtime`, `approvals`, `avatars`), `SKILLS` (`SkillRegistry`), `SCHEDULES` (`ScheduleStore`), `MEMORY` (`MemoryStore`), `BACKGROUND_TURNS` (`BackgroundTurns`) and `DELEGATION` (`Delegator`), each a port interface that an object with the same methods satisfies, so a stranger can provide or fake one without a class.
+  The main entry also names the ports' parts and data types: `AgentChange`, `AgentDirectory`, `AgentServer`, `AgentTeam`, `AvatarMode`, `AvatarStudio`, `DelegationRequest`, `Memory`, `MemoryKind`, `MEMORY_KINDS`, `PromptMemory`, `SpeakerMemory`, and, moved from the kit, `Agent`, `AgentGroup`, `AgentStatus`, `GroupStatus`, `NewSchedule`, `Recurrence`, `ResolvedSkill`, `Schedule`, `ScheduleChange`, `SkillCatalogEntry`, `SkillSet`, `SkillSource`, `TeamAgentStatus`, `TeamStatus`, `ThinkingSetting`, `Weekday`; `TIERS` is exported (frozen), so `Tier` names a public value.
+  The Discord connection's key is in the Discord entry: `DISCORD` and `DiscordServices` (`connection`, `commands`, `guard`, `threads`) are in `pi-roundtable/discord`.
+  `examples/shared-services.ts` provides, reads and replaces a service, with a test.
+- `testPlugin` option `services` (a list of `servicePair(KEY, { ... })`, replacing `core`; an ungiven member throws naming the option, a service not given reads as absent to `find` and `get` says to give it), and the testing entry exports `servicePair`, `ServicePair` and `FakeThreadHost`.
+- `DelegationJob` and `DelegationOutcome` (in the main entry), the job a `Delegator` runs and how it ended.
+
+- The unstable-before-1.0 `pi-roundtable/discord` entry, the one built on discord.js types (a test checks that the main and kit declarations reach none; `pi-roundtable/testing` names a few, through `testHost`'s composed commands: `ComposedCommands`, `CommandGuard`, `InteractionModule` and `RootOption`): `DISCORD` (`DiscordServices`: `connection`, `commands`, `guard`, `threads`), `DiscordConnection`, `CommandRegistrar`, `CommandGuard`, `CommandGuardOptions`, `commandGuard`, `composeCommands`, `ComposedCommands`, `InteractionContribution`, `InteractionModule`, `RootOption`, `CommandRoot`, `ownerRootCommand`, `ownerCommandModule`, `OwnerCommandHandlers`, `groupOption`, the panel helpers `OwnerFacingError`, `PanelContent`, `ephemeralPanel`, `ownerPanel`, `ownerPanels`, `plain`, `replyWithPanels`, the agent panel `agentPanel`, `AgentPanel`, `AgentPanelMessage`, `AgentPanelOptions`, and the channel-operation tables `CHANNEL_OPERATIONS`, `CHANNEL_TOOLS`, `ChannelExecutor`, `ChannelInfo`, `ChannelOperation`, `ChannelTool`, `ChannelToolError`, `DISCORD_ADMIN_TOOLS`, `ManagedChannel`, `OPERATION_PERMISSIONS`, `OwnerOperations`, `fetchManagedChannel`, `isChannelOperation`, `operationLabel`, `parseChannelTool`.
+  A plugin adds slash commands from `setup` with `context.services.get(DISCORD).commands.add({ module, rootOptions })`. The Discord plugin collects them and composes them under the root command in its preflight, so a duplicate command name, a module that registers the root, or a subcommand added twice stops the start before any service starts; `commands.add` after that preflight throws a `PluginError`. `CommandGuard.isOwner` takes anything with `user.id`, so a test needs no cast.
+  A plugin that only reads a service in `setup` and returns `{}` (such as one that only adds commands) is no longer refused as adding nothing.
+- `agentPanel({ guard, agents, skills? })`: the agent's profile panel with its buttons and form, owning its custom-id prefixes (`roundtable:agent:` and `roundtable:agent-modal:`, unchanged, so panels already posted keep working), the owner check, and the deferred reply of the form.
+- `discord.refusalHint` in the configuration (`DiscordOptions.refusalHint`): text appended as it is to the refusal a non-owner gets from the root command. The core's Chinese refusal no longer carries a sentence about one host's dice commands; a host that wants such a sentence passes it.
+- The agent server publishes the avatar studio as `AgentServer.avatars` and builds it itself (from `config.http.publicUrl` and `config.avatar`).
+- Testing: `fakeDiscord` and `FakeDiscord`, the `DISCORD` service for a plugin that adds slash commands (records `commands.add`, gives a guard, composes the tree).
+
+- **The internal sweep (the last of the unreleased public-surface work):** what the host repository's own code imported from its local `pi-roundtable/internal` mapping has a public home or left the core, so the core's public entries are what a stranger uses to build the same things.
+  The main entry names `ConfigError`, `DelegationError`, `MemoryError` and `ScheduleError`, the errors the public ports throw, `NO_ATTACHMENTS` beside `TurnAttachments`, and `THE_SPEAKER` beside `Speaker`; the testing entry names `TestLocale`.
+  The kit gains the helpers for running a Pi session of your own: `mcpExtension` and `VirtualServer`, `mcpAdapterExtension` and `McpEndpoint`, `readAttachmentExtension`, `promptSlot` and `PromptSlot`, `workTimeout`, `approvalCard`, `canonicalJson`, `runWorkerTask`, `archiveSessions`, the host-shell `SHELL_TOOLS` and `shellHoldRule`, the tool helpers `textToolsExtension`, `requiredString`, `stringList`, `TextToolDef` and `ToolInput`, and `channelQueue` (a queue of your own, apart from the host's).
+  It also has the pieces for mirroring a built-in tool in a worker that cannot reach the host: `DELEGATE_TOOL`, `DELEGATE_TOOL_SPEC`, `SCHEDULE_TOOLS`, `isScheduleTool`, `callScheduleTool`, `scheduleToolSpecs`, and the types `ScheduleToolContext`, `ScheduleToolName`, `ScheduleToolSpec` and `ScheduleToolWording`.
+  The effort policy is a public knob: `effortJudge` (with `EffortBrief`, `EffortJudgeOptions`, `EffortLevel`, `EffortPicker`, `PreviousTurn` and `JUDGE_WORK`), which picks a turn's thinking level from a message.
+  Also in the kit: `thinkingLine` and `zonedStamp` (presentation), `checkRepoName`, `SKILL_LIST_TOOL` and `skillListExtension` (skills), and `searchTerms` (memory).
+
+### Removed
+
+**Breaking for 0.1.0, so this is 0.2.0.**
+A plugin that still has one of these fields is refused when it is defined or when the host starts, with an error that names the replacement.
+
+- `RoundtablePlugin.useCommands(composed)`: the composed slash commands go to the Discord plugin's surface, not to a plugin. Add commands from `setup` with `context.services.get(DISCORD).commands.add(...)` (see the slash-command entry below).
+- `RoundtablePlugin.agentServer()` and the `agentServer(outcome)` event handler, with `AgentServerOutcome`: give a service `startInBackground` and hear how it ended in `serviceStarted`, which names the plugin and service (`AGENT_SERVER_PLUGIN`, `AGENT_TEAM_SERVICE`).
+  The host runs every service's background start after all `start`s and the HTTP listeners, without holding up the boot; a failure is logged and heard as `failed`, and does not stop the other services.
+- `RoundtablePlugin.stopTurn(channel)`: put `stop(channel)` on the `ChannelClaim` that owns the channel. The router asks only the owning claim, and a claim without `stop` means `false`.
+- `PluginContext.core` and its types `CoreAccess`, `CoreServices`, `CoreStores`, `CoreDiscord` and `CoreAgents`: read a service with `context.services.get(KEY)` (`AGENTS`, `SKILLS`, `SCHEDULES`, `MEMORY`, `BACKGROUND_TURNS`, `DELEGATION`, and the Discord entry's `DISCORD`) and provide one with `services.provide`.
+  Reading `context.core` throws a `PluginError` that names `context.services`, at the plugin's first read, instead of returning `undefined`.
+  The stores bag is gone: each store belongs to the plugin that owns its table, and the held-action, skill and agent stores are not published (the agent server reads them; `AGENTS.directory` is the read-only half of the agents store).
+- The `testPlugin` option `core` and its type `TestCore`: use `services` with `servicePair`.
+- Kit: the class types of the built-in services (`AgentStore`, `AgentTeam`, `AvatarStudio`, `BackgroundTurns`, `ConfirmationJudge`, `Delegator`, `OwnerMemoryStore`, `PendingConfirmationStore`, `PiAgentRuntime`, `ScheduleStore`, `SkillRegistry`, `SkillStore`), replaced by the main entry's port interfaces where a plugin needs them, and the `*Options` types of those classes (`AgentTeamOptions`, `AvatarStudioOptions`, `BackgroundTurnsOptions`, `ConfirmationJudgeOptions`, `DelegatorOptions`, `PiAgentRuntimeOptions`, `SkillRegistryOptions`, `TeamTurnsOptions`), with `Detached`, `SkillEntry` and `SkillGroup`.
+- **Renamed, for the unreleased types:** `OwnerMemoryStore`, `OwnerMemory`, `OwnerMemoryKind`, `OwnerPromptMemory` and `OWNER_MEMORY_KINDS` are `MemoryStore` (with `forSpeaker`, returning `SpeakerMemory`), `Memory`, `MemoryKind`, `PromptMemory` and `MEMORY_KINDS`; the tables and the tools' names do not change.
+- Kit: `conversationKind()` and its closed `ConversationKind` (`"owner" | "party" | "agent"`); a conversation kind is any string that a claim's `startFresh` returns, and a plugin narrows the kinds of its own claims itself. `SessionContext.kind` is a `string`.
+- Kit: `channelKey(channelId)` is `discordKey(channelId)`, because the main entry's `channelKey` builds a key on any surface.
+
+- Addons: memory, skills, and Discord administration are built-in plugins of their own (`memory`, `skills`, `discord-admin`) that `defineRoundtable` adds unless the configuration switches them off with `memory: false`, `skills: false`, or `discord: { admin: false }`; all three are on by default. A switched-off addon contributes no tools, no prompt block, and no service, and its tables and rows are left untouched: `services.find(SKILLS)` and `find(MEMORY)` are `undefined`, the agents carry no skills, `agent_get` has no skills line, `agent_create` leaves out its `skills` parameter and refuses a call that passes some with an error saying skills are off, and `services.get` of an addon key fails naming the switch.
+- `Contribution.toolTiers` (`Record<string, Tier>`): a plugin names the tier of each raw session tool it registers, as `defineTool` already does for its own; the operator's setting still wins and two plugins naming one tool are refused.
+- `serviceKey(id, { absent })` and `ServiceKey.absent`: what a read of a service nobody provides says to fix it; `MEMORY` and `SKILLS` name their switches.
+- `SkillRegistry.attach(agent, add, remove)`, which the agent team uses to give a new agent its skills.
+- **Breaking (slash commands move under the Discord surface):** `Contribution.interactions`, `RoundtableOptions.commands`, `ChatSurface.useCommands` and the host's composition of commands are gone; the main entry no longer names `CommandRoot`, `ComposedInteractions`, `InteractionContribution`, `InteractionModule` or `RootOption` (they are in `pi-roundtable/discord`). A plugin that returns `interactions` from `setup`, a surface that has `useCommands`, and a host given `commands` are each refused with an error that names `context.services.get(DISCORD).commands.add(...)`, as `RoundtablePlugin.useCommands` is.
+- **Breaking for the unreleased types:** the kit's Discord names moved to `pi-roundtable/discord` or were dropped: `DISCORD` and `DiscordServices` (now `connection`, `commands`, `guard`, `threads`; the owner's cards and the avatar studio are no longer published), `OwnerGuard` (now `CommandGuard`, a port), `ChannelExecutor`, `ChannelInfo`, `ChannelOperation`, `OwnerCommandHandlers`, `PanelContent`, `OwnerFacingError`, `groupOption`, `ownerCommandModule`, `ownerPanel`, `ownerPanels`, `ephemeralPanel`, `replyWithPanels` and `plain` moved; `DiscordSurface`, `DiscordSurfaceOptions`, `OwnerCards`, `OwnerCardsOptions`, `CardChannel`, `CardMessage` and `CardPayload` are gone (the owner's cards stay private to the Discord plugin and answer held actions through `context.surfaces.prompts`).
+- `DiscordSurface.useCommands` is `setCommands` and is not published. `DiscordConnection` returns the public `AgentChannels`, `DashboardBoard`, `ThreadHost` and `OwnerOperations` (was `OwnerDiscord`) instead of the Discord classes, which removes five leaks from the type-leak baseline (now `ErrorReporter` only).
+- `DISCORD_OWNER_TOOLS` is `DISCORD_ADMIN_TOOLS`.
+
+### Changed
+
+- **Breaking for the unreleased types:** `DefineOverrides` has five fields: `modelRuntime`, `logger`, `errorSink`, `listeners` and `aborted`. `errorReporter` is gone (set `config.ops` for the ops agent's reports, and `errorSink` for your own), `options` is gone (`options.listeners` is `listeners`, which adds listeners to the one `config.http` names, and `options.aborted` is `aborted`; the other host options come from the config), `modules.agentChannelOf` is gone (the modules read `AgentTeam.channelOf` from `AGENTS` when a tool runs), and `agentServer.ownerSessions` is gone (contribute `personas: [{ kind: "owner", prompt }]` and `requiredTools` from the plugin that owns the owner's conversations; the agent server no longer refuses a contributed `"owner"` persona). With no `"owner"` persona the owner's conversations start with an empty system prompt, as before.
+- **Breaking for the unreleased types:** `AgentServerOptions`, `ModulesOptions`, `ErrorReporter`, `ErrorReportDelivery` and `ErrorReporterOptions` are no longer public: they were named by `DefineOverrides` only, and the public type-leak baseline is now empty. `Logger` is no longer pino's type, and `LogEntry` moved from `pi-roundtable/kit` to the main entry.
+- **Breaking for the unreleased types:** migration names are unique inside a plugin, not across plugins (the ledger id is `<plugin>/<name>`), and `MigrationError.migration` and the start's error name that id. The same name in two plugins is allowed; a repeated id is still refused.
+- The upgrade adds the ledger to a database that already ran the migrations without special handling: no id is recorded, so each `once` migration runs once more, as every start did before, and is recorded. **Rollback note:** a build from before the ledger ignores the table and runs every migration at every start; rolling forward again finds its ids recorded, so a `once` migration that fixes rows (for example one that gives rows written before speakers or guilds existed their owner or guild) does not run again over rows an older build wrote in between. Mark such a migration `runs: "every-boot"` if a rollback must converge.
+- The host repository's tests use `migrateDatabase` where they migrated by hand, and its two import scripts read the ledger instead of migrating.
+- **Breaking for the unreleased types:** the skills are provided by the new `skills` plugin, not by the agent server. the agent server takes no skills option (the paths are the `skills` config key's), the agent server provides only `AGENTS`, and the agent team reads the registry with `find(SKILLS)`, so the skill tools are the `skills` plugin's agent session tools (`skill-tools`) and its `agentSelection`, no longer part of `agent-tools`. `memoryPlugin` takes the `owner` and adds the `owner-memory` session tool, and `modulesPlugin` no longer adds that tool or `discord-admin`, which is the new plugin's.
+- **Breaking for the unreleased types:** the core's tier table (`CORE_TOOL_TIERS`) names only `ask_user`, `compact_session` and `read_attachment`; the agent, schedule, delegation, web, skill and memory tools are declared by the plugin that adds them, with the same tiers. The Discord tools stay with the owner, as before.
+- The order of the core's migrations is now memory, schedules, skills, held actions, agents, because the skills plugin sits before the agent server that reads its registry; all of them run before any setup and none touches another's tables. The stored data, the tool set, and each tool's tier under the default configuration are unchanged (a test records them for the owner's session, an agent's, and a group seat).
+- The legacy skill kind `UPDATE` is no longer in the core's skill migrations; a host that still has skills stored under that kind converts them in a migration of its own, after the core's.
+- **Breaking for a plugin that named it:** the built-in plugin list of `defineRoundtable` gains `discord-admin` (after `modules`) and `skills` (after it, before `agent-server`).
+
+- **Breaking (the unreleased `InboundMessage` fields, and the second parameter's name of the published `ChannelClaim.owns`):** `InboundMessage` has neutral fields in place of Discord's. `guildId` is `space`, the server or workspace the channel belongs to; `webhookId` and `ownWebhook` are `integration?: { id, own }`, for a post by an integration such as a Discord webhook and whether it is the assistant's own voice; and `forwarded.channelMention` (`"<#id>"`) is `forwarded.source`, the forwarded-from channel's key. `ChannelClaim.owns(channel, guildId)` is `owns(channel, space)`; the parameter is positional, so callers do not change.
+- **Breaking for the unreleased types (and the published `TurnEvent`):** `TurnEvent.agent` is optional and `TurnEvent` has `kind` (`"agent"` for an agent's turn, else the kind of a turn run through `context.turns`), so `turnStarted` and `turnEnded` also report those turns. `CoreAgents.runtime` is typed `AgentRuntime`, not the concrete `PiAgentRuntime` (the Pi runtime when no plugin fills the slot). `SessionContext.kind` is the turn's kind for a non-agent session, not always `"owner"`.
+- `testPlugin`'s errors say what is possible inside it: `core service <name> is not provided yet` tells you to pass it in the `core` option instead of registering a built-in plugin, and a `conversations` call made from a handler no longer says it is "not during setup", since the harness links them.
+- `DiscordSurface` implements `ChatSurface` (`surface = "discord"`, with `prompts`) and the Discord built-in contributes it: the `surface` service is now `surface:discord`, and a new `threads` service sweeps the dispatch threads once it has started.
+- The agent server owns only `discord:` channel keys. A key of another surface, such as `mcp:<id>` on a host that claims those keys, whose id equals an agent's channel id was taken by the agent server at priority 100, because its ownership check sliced `discord:` off any key; it is now left to the claim that owns that surface.
+  `AGENT_SERVER_PRIORITY` (100) is exported and documented: a claim on `discord:` keys with a lower priority is beaten in the agents' channels and in the rest of the agent guild.
+- The stop button core posts is answered by the Discord built-in (owner only, through `conversations.stop`), so it works on a host that does not add its own handler.
+- An unknown provider slot passed to `providers` is refused, naming the valid slots, as an unknown part of `setup` already was.
+- Trim source tests and test-only helpers from npm contents; retain example tests embedded by the guide, excluding the guide verifier itself.
+- Freeze shared protocol constants and publish readonly types; process-wide locale and time-zone setters are not exported by main, kit, or testing.
+- Keep production integration inspectors out of testing and host-assembly values out of the kit.
+- Without an `images` provider, agents get an avatar generated from their display name and the assistant's icon (a colour from the display name and the initial of the agent's name, always a Latin letter or digit, in a 512 px PNG served by content hash), instead of all sharing the neutral one. They are no longer offered drawing: `agent_create` has no `avatar_prompt`, `agent_avatar` is not registered, agents' prompts and `agent_get` leave avatar prompts out, and the profile panel says no image provider is configured instead of offering to redraw. Startup makes the missing pictures and logs one info line, not a warning per agent on every boot. A host with an `images` provider behaves as before.
+- `roundtable doctor` has an `image provider` check, after `plugins`: it states whether a plugin fills the `images` slot and, without one, how to provide it; it is never a failure.
+- `PluginContext.providers` also has `filled`, the set of slots a plugin fills, so a default can be told from a provider without calling it.
+- **Breaking for the unreleased types:** the core no longer knows owner profiles. A held action carries an opaque `selectionId` (the `id` of the `TurnSelection` whose turn held it) in place of `PendingConfirmation.profile`; the core stores it and the caller resolves it when the owner confirms. `ConfirmationGate.beginTurn(selectionId, confirmed, addressee?)` takes that id, and a call held outside a turn throws instead of being stamped `"general"`.
+- Held actions are stored in a new table, `held_actions(channel_key, selection_id, held_at, calls)`, which the core creates on every boot. A host upgraded from an earlier build keeps its old `pending_confirmations` table, which the core no longer reads; copy its rows across (`selection_id` takes the old `profile` value) in a migration of your own, after the core's.
+- **Breaking for a plugin that named it:** the core extension `profile-tools` is named `active-tools` (a plugin may not take either name); `CoreExtensions.profileTools` is `activeTools`.
+- Log and error wording: the stale-session reason `connectors changed` is `session tools changed`, the startup error `profile tools are not registered` is `required tools are not registered`, `profile tools missing; running without them` is `selected tools missing; running without them`, and the turn log's `profile` key is `selection`.
+- **Breaking for the unreleased types:** the core no longer knows party channels. `BackgroundTurn.mode` (`"owner" | "party"`) is `BackgroundTurn.target`, a `string` naming a contributed `BackgroundTarget`; `Schedule.mode` and `NewSchedule.mode` are `target`, and `DelegationJob.mode` is `target`. The `schedules.mode` column keeps its name and its values (`"owner"`, `"party"`), which are now the target names, so no stored schedule is rewritten. The schedule tools' limits come from `ScheduleToolContext.target` (replacing `mode` and `SCHEDULE_LIMITS`), the delegator's running limit from `DelegatorOptions.targets(name)` (replacing the built-in table), and a target without `schedules` or `delegation` refuses both. The agent server's claim used to skip only `"party"` turns and now answers only `"owner"`, so a turn for any other target never reaches the owner's tools. The `/<root> schedule` list names a schedule's target by its label, or by its name when no plugin contributes it.
+- The built-in plugin `stores` is split by feature, so one store can be replaced: `memory` (migrations and `MEMORY`) and `schedule-store` (migrations and `SCHEDULES`) come first, and the agent server now owns the tables it reads: held actions, and agents and groups; the skills have their own addon.
+  The tables and the tools are unchanged.
+- The default delegation worker is `WebResearchWorker` (it was named for one model), in `web-research-worker.ts`; it is not exported.
+- **Breaking for the unreleased types:** `scheduleToolSpecs({ locale, timeZone })` takes the locale and the time zone its descriptions are written in, and `zonedStamp(date, timeZone)` (the kit's, a stamp in the zone you give) takes the zone, instead of both reading the process-wide setting. A worker of your own no longer sets the process's locale and time zone to get its tool descriptions in the wording and zone it wants. `useTestLocale({ locale, timeZone, assistant, root })` takes the same, with the neutral UTC and English defaults when called with nothing.
+- The transitional local `pi-roundtable/internal` mapping is removed: the tsconfig path, `src/internal/`, and its guard test are gone, and a boundary test fails on any import of it and if the directory returns. It was never an npm export or part of the tarball, so a package consumer sees no change. `CardCadence`, `Expression`, `CardRenderError`, `packageDir`, `serveUnix` and the environment-variable parsers for tier members and tool tiers are no longer the core's: they moved into the host repository's own code, and the core does not export them.
+
+### Fixed
+
+- `defineRoundtable` no longer sets the process's locale, time zone, or `PI_CODING_AGENT_DIR`; `Roundtable.run()` applies the host's `environment`, so defining a second host no longer changes the first's.
+- The root command `defineRoundtable` gives the host is built when `run()` applies the environment, so its description is in the host's language; `RoundtableOptions.commands.root` may be a `CommandRoot` or a function that returns one.
+- One host runs per process: a second `run()` is refused with the fix. A failed `run()` stops what it started, closes the pool, and rethrows, and the same host may retry (tool tiers are declared idempotently per plugin).
+- The shutdown drain waits on the host's own channel queue, not only on services, and the Discord built-in no longer contributes a `channel-queue` service.
+- `shutdown()` runs once however many signals arrive and returns the exit code (non-zero when something did not stop or the boot had failed); only `listen()` exits the process, and the command line exits non-zero on a failed start.
+- Importing `pi-roundtable/testing` in CI without a database URL no longer throws; repository CI requires its PostgreSQL URL in the workflow instead.
+- Record the already-published main/testing API and CLI under 0.1.0 rather than presenting them as unreleased additions.
+
+## [0.1.0]
+
 ### Added
 
 - Main entry exports: `AgentSeed`, `ChannelClaim`, `Contribution`, `DefinedRoundtable`, `EventHandlers`, `HoldRule`, `InteractionContribution`, `Migration`, `NotLinkedError`, `PluginContext`, `PluginError`, `PromptSection`, `PromptTurn`, `Roundtable`, `RoundtableConfig`, `RoundtableOptions`, `RoundtablePlugin`, `Service`, `SessionTool`, `Speaker`, `Tier`, `ToolContribution`, `ToolRefusal`, `ToolSpec`, `ToolTurn`, `TurnEndEvent`, `TurnEvent`, `definePlugin`, `defineRoundtable`, `defineTool`.
@@ -26,3 +173,4 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 - `testPlugin`'s `contribution` includes the `agentSelection` a plugin adds; it was left out.
 - A setup that throws a `NotLinkedError` reports its reason without a doubled period.
+- `pi-web-access` (0.35.0) is a dependency: the built-in delegation worker loads its Pi extension by path, and a project without it failed at the `modules` plugin's setup with `Cannot find module 'pi-web-access/package.json'`.

package/README.md

@@ -1,5 +1,7 @@
 # pi-roundtable
 
+English | [Traditional Chinese](README.zh-TW.md)
+
 A Discord agent server on [Pi](https://github.com/earendil-works/pi).
 You get a team of AI agents in one Discord server: each agent owns a channel and a conversation, they share tools and memory, and you extend the bot with plugins written in TypeScript.
 
@@ -36,7 +38,7 @@ It refuses to write anything when Bun is missing or too old, or when a file it w
 Bun loads `.env` by itself, and `.gitignore` keeps it out of Git.
 
 | Variable | What it is |
-|---|---|
+| --- | --- |
 | `DISCORD_TOKEN` | The bot's token, from the application's Bot page |
 | `DISCORD_GUILD_ID`, `DISCORD_ENTRY_CHANNEL_ID` | The server and the channel where the coordinating agent lives (turn on Developer Mode, then right-click to copy ids) |
 | `OWNER_ID`, `OWNER_NAME` | You: the one person who can change everything |
@@ -52,11 +54,12 @@ Bun loads `.env` by itself, and `.gitignore` keeps it out of Git.
 2. `.env` has a value for every variable `.env.example` lists.
 3. `roundtable.config.ts` against its schema, naming the failing key.
 4. Every plugin loads, and no two share a name.
-5. PostgreSQL is reachable and migratable.
-6. The Discord token is valid, the bot is in your server, the Message Content intent is on, and the bot has the permissions it needs in the entry channel (including Pin Messages).
+5. Whether a plugin fills the `images` slot. Without one is not a failure: agents get avatars generated from their display names.
+6. PostgreSQL is reachable and migratable.
+7. The Discord token is valid, the bot is in your server, the Message Content intent is on, and the bot has the permissions it needs in the entry channel (including Pin Messages).
    When the bot is not in the server, the fix is an invitation link that asks for exactly those permissions.
-7. The model login exists.
-8. `PUBLIC_URL` is a well-formed address; with `--reachable` it also has to answer, which is only true while the bot runs.
+8. The model login exists.
+9. `PUBLIC_URL` is a well-formed address; with `--reachable` it also has to answer, which is only true while the bot runs.
 
 It exits non-zero on any failure and changes nothing it checked.
 A fresh project fails only on the credentials you have not entered yet, and says which.
@@ -108,6 +111,7 @@ test("hello greets", async () => {
 
 The [plugin guide](docs/plugins.md) explains every part a plugin can add (tools, prompt sections, agents, events, services, migrations, providers, slash commands, HTTP routes, and more), the order things start and stop in, and every startup error with its fix.
 Its examples live in [`examples/`](examples), and the test suite runs each of them.
+`pi-roundtable/kit` supplies claim, tool and presentation helpers and type-only names for the context’s existing services, and `pi-roundtable/discord` supplies the slash-command registrar, owner-command and panel helpers, and the agent panel, and is the entry that names discord.js types (`pi-roundtable/testing` names a few, through `testHost`'s composed commands); both are unstable before 1.0 and not covered by semver.
 
 ## Settings
 
@@ -128,7 +132,7 @@ export default {
 ## Commands
 
 | Command | What it does |
-|---|---|
+| --- | --- |
 | `roundtable init [dir]` | Creates a project in `dir` (default: the current directory) |
 | `roundtable doctor [--reachable]` | Checks the setup and says how to fix what is wrong |
 | `roundtable start` | Runs the checks that need no network, then the bot |

package/README.zh-TW.md

@@ -0,0 +1,144 @@
+# pi-roundtable
+
+[English](README.md) | 繁體中文
+
+一個建立在 [Pi](https://github.com/earendil-works/pi) 上的 Discord 智慧體（agent）伺服器。
+你會在一個 Discord 伺服器裡得到一組 AI 智慧體：每個智慧體擁有一個頻道和一段對話，彼此共用工具與記憶，你用 TypeScript 寫外掛（plugin）來擴充這個 bot。
+
+- 為一位擁有者和一個 Discord 伺服器設計。你可以允許其他人與智慧體對話，但這樣的設定與風險由營運者自行承擔。
+- 只支援 Bun。套件直接發佈 TypeScript 原始碼，不需要建置步驟。
+- MIT 授權。
+
+## 你需要準備
+
+- [Bun](https://bun.sh/docs/installation) 1.3 以上。
+- PostgreSQL。`init` 建立的專案附有 `docker-compose.yml`，可以直接啟動一個。
+- 一個 Discord bot：一個含 bot 使用者、已開啟 Message Content intent，並已邀請進你的伺服器的應用程式。
+- 模型登入：你選的模型的供應商 API key（`anthropic/...` 用 `ANTHROPIC_API_KEY`），或用 Pi 做過的登入。
+- 一個能從網際網路連到這個行程的位址，例如通道（tunnel），因為 Discord 會從該位址取得智慧體的頭像。
+
+## 五分鐘上手
+
+```sh
+npx pi-roundtable init my-bot    # 或：bunx pi-roundtable init my-bot
+cd my-bot
+bun install
+docker compose up -d             # PostgreSQL，與 .env.example 一致
+cp .env.example .env             # 然後填入內容
+bunx roundtable doctor
+bunx roundtable start
+```
+
+`init` 會寫出一個可運作的專案，不會向你要任何祕密資訊。
+Bun 不存在或版本太舊，或它要建立的檔案已經存在時，它不會寫入任何東西。
+
+### `.env`
+
+`.env.example` 說明了每個值的來源。
+Bun 會自行載入 `.env`，`.gitignore` 也已讓它不進 Git。
+
+| 變數 | 內容 |
+| --- | --- |
+| `DISCORD_TOKEN` | bot 的 token，在應用程式的 Bot 頁面取得 |
+| `DISCORD_GUILD_ID`、`DISCORD_ENTRY_CHANNEL_ID` | 伺服器，以及負責統籌的智慧體所在的頻道（開啟開發者模式後，按右鍵複製 id） |
+| `OWNER_ID`、`OWNER_NAME` | 你自己：唯一能改動一切的人 |
+| `DATABASE_URL` | PostgreSQL；預設值與 `docker-compose.yml` 一致 |
+| `MODEL` | 智慧體使用的模型，格式為 `<provider>/<id>` |
+| `PUBLIC_URL` | 能從網際網路連到這個行程的位址 |
+
+### `doctor`
+
+`bunx roundtable doctor` 依序檢查下列項目，逐項印出通過或失敗，並說明如何修正：
+
+1. Bun 的版本。
+2. `.env` 對 `.env.example` 列出的每個變數都有值。
+3. `roundtable.config.ts` 符合其 schema，失敗時指出是哪個鍵。
+4. 每個外掛都能載入，且沒有兩個外掛同名。
+5. 是否有外掛填入 `images` 槽位。沒有並不算失敗：智慧體會用顯示名稱產生頭像。
+6. PostgreSQL 連得上，且能執行 migration。
+7. Discord token 有效、bot 已在你的伺服器裡、Message Content intent 已開啟，而且 bot 在入口頻道有它需要的權限（包含 Pin Messages）。
+   bot 不在伺服器裡時，修正方式是一個邀請連結，連結要求的正是這些權限。
+8. 模型登入存在。
+9. `PUBLIC_URL` 是格式正確的位址；加上 `--reachable` 時它還必須有回應，這只有在 bot 執行中才成立。
+
+任何一項失敗，它就以非零狀態結束，並且不更動它檢查過的任何東西。
+全新的專案只會因為你還沒填的憑證而失敗，而且會指出是哪些。
+
+### `start`
+
+`bunx roundtable start` 先執行不需要網路的檢查，其中任何一項失敗就停下來，並印出與 `doctor` 相同的訊息；全部通過則啟動 bot。
+啟動後，`agents.ts` 裡的智慧體都有了自己的頻道，`/roundtable help` 會開啟控制面板。
+收到 `SIGTERM` 或 `SIGINT` 時，它會先讓進行中的工作完成再停止。
+
+## 外掛
+
+`roundtable add plugin <name>` 會建立 `plugins/<name>.ts` 和它的測試，並把它列進 `roundtable.config.ts`。
+外掛是一個有名稱和 `setup` 函式的物件，`setup` 回傳它要新增的東西；下面這個外掛給每個智慧體一個工具：
+
+```ts
+import { definePlugin, defineTool } from "pi-roundtable";
+import { Type } from "typebox";
+
+export const hello = definePlugin({
+	name: "hello",
+	setup: () => ({
+		tools: [
+			defineTool({
+				name: "hello_greet",
+				description: "Greet someone by name. Call it when asked to say hello.",
+				parameters: Type.Object({ who: Type.String() }),
+				minTier: "member",
+				run: ({ who }) => `Hello, ${who}!`,
+			}),
+		],
+	}),
+});
+```
+
+測試時不需要 Discord 或 PostgreSQL：
+
+```ts
+import { expect, test } from "bun:test";
+import { testPlugin } from "pi-roundtable/testing";
+import { hello } from "./hello.ts";
+
+test("hello greets", async () => {
+	const harness = await testPlugin(hello);
+	expect(await harness.runTool("hello_greet", { who: "Ada" })).toBe("Hello, Ada!");
+	await harness.stop();
+});
+```
+
+[外掛指南](docs/plugins.md)（英文）說明外掛能新增的每個部分（工具、提示詞區段、智慧體、事件、服務、migration、provider、斜線指令、HTTP 路由等等）、啟動與停止的順序，以及每一種啟動錯誤和它的修正方式。
+指南裡的範例放在 [`examples/`](examples)，測試套件會執行每一個範例。
+`pi-roundtable/kit` 提供頻道認領（claim）、工具與呈現用的輔助函式，以及 context 現有服務的純型別名稱；`pi-roundtable/discord` 提供斜線指令註冊器、擁有者指令與面板的輔助函式，以及智慧體面板，是會用到 discord.js 型別的入口（`pi-roundtable/testing` 也透過 `testHost` 組合出的指令用到少數幾個）。這兩個入口在 1.0 之前都不穩定，不受語意化版本（semver）保證。
+
+## 設定
+
+`roundtable.config.ts` 放設定和外掛清單。
+未知的鍵會報錯，並指出最接近的已知鍵。
+
+bot 在 Discord 裡顯示的文字語言由 `locale` 設定決定：預設是 `en`，也可以是 `zh-TW`。
+
+```ts
+export default {
+	// ...
+	locale: "zh-TW",
+	timeZone: "Europe/Berlin", // 排程與時間戳記使用的時區；預設為 UTC
+	plugins: [hello],
+} satisfies RoundtableConfig;
+```
+
+## 指令
+
+| 指令 | 作用 |
+| --- | --- |
+| `roundtable init [dir]` | 在 `dir`（預設為目前目錄）建立專案 |
+| `roundtable doctor [--reachable]` | 檢查設定，並說明如何修正有問題的地方 |
+| `roundtable start` | 先執行不需要網路的檢查，再啟動 bot |
+| `roundtable add plugin <name>` | 新增 `plugins/<name>.ts` 和它的測試，並列進設定 |
+
+## 變更與授權
+
+[CHANGELOG.md](CHANGELOG.md)（英文）列出套件匯出名稱的每一項變更。
+[MIT](LICENSE)。