pi-roundtable-sandbox 0.31.4 → 0.31.6

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## [Unreleased]
 
+## [0.31.6] - 2026-11-02
+
+- Release in lockstep with pi-roundtable 0.31.6: the `channelContext` option takes `peerMessageChars` (an integer from 1 to 4000), where a peer bot's message is cut; a listed peer's messages read up to 4000 characters by default instead of 80.
+
+## [0.31.5] - 2026-11-02
+
+- Release in lockstep with pi-roundtable 0.31.5; no package-specific behavior changes.
+
 ## [0.31.4] - 2026-11-02
 
 - Release in lockstep with pi-roundtable 0.31.4; no package-specific behavior changes.

package/README.md

@@ -213,7 +213,7 @@ The sandbox calls `DISCORD.channelContext` with the addressed message, which rea
 Core's defaults and caps apply (the newest 15 messages, 500 characters each, other bots 80), and so do the host's `discord.channelContext` settings, which the option overrides key by key; a host `channelContext: false` turns it off and the option then does nothing. `attachments` is ignored, because the sealed worker has no image input.
 The addressed message (with its quote) comes first and the block follows it, framed as untrusted public text, not instructions, so the worker's saved history, which keeps the head of an entry, keeps the message. The framing says the addressed message is only the text before the block.
 It is cut oldest first so the whole stays within `runTurn`'s 32,000 characters and the worker's current-message budget; the addressed message is never cut, and when no context fits, the turn is sent as before.
-Options are validated at startup with core's bounds (`keep`, `fetch` at most 100; `messageChars`, `botMessageChars` at most 4000; unknown keys refused), and the option needs the Discord plugin.
+Options are validated at startup with core's bounds (`keep`, `fetch` at most 100; `messageChars`, `botMessageChars`, `peerMessageChars` at most 4000; unknown keys refused), and the option needs the Discord plugin.
 A failed read is logged as a warning and the turn runs without it.
 `replyText` works unchanged.
 It is host-only: no worker protocol change and no image rebuild.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-roundtable-sandbox",
-	"version": "0.31.4",
+	"version": "0.31.6",
 	"description": "Sealed guest channels and an allow-listed credential broker for pi-roundtable",
 	"type": "module",
 	"license": "MIT",
@@ -52,7 +52,7 @@
 		"@biomejs/biome": "2.5.15",
 		"@types/bun": "1.4.3",
 		"discord.js": "14.27.0",
-		"pi-roundtable": "0.31.4",
+		"pi-roundtable": "0.31.6",
 		"typebox": "1.3.37",
 		"typescript": "7.0.2"
 	}

package/src/channel-context.ts

@@ -43,6 +43,7 @@ const KEYS = [
 	"similarity",
 	"messageChars",
 	"botMessageChars",
+	"peerMessageChars",
 	"foreignWebhook",
 	"attachments",
 ];
@@ -70,6 +71,7 @@ export function resolveChannelContextOptions(
 	bounded("keep", given.keep, 100);
 	bounded("messageChars", given.messageChars, 4000);
 	bounded("botMessageChars", given.botMessageChars, 4000);
+	bounded("peerMessageChars", given.peerMessageChars, 4000);
 	if (
 		given.similarity !== undefined &&
 		!(