billion-context-omp 0.2.7 → 0.2.9

package/dist/wire-fold.d.ts

@@ -1,5 +1,5 @@
 import { type BiliMessage } from "acp-kernel/wire";
-import { type CompressionState, type CoreMessage } from "acp-kernel";
+import { type CompressionState, type Config, type CoreMessage } from "acp-kernel";
 import type { AgentMessage, BlockLike, StreamCompressCall } from "./messages.js";
 export type ProviderWireFormat = "anthropic" | "openai";
 /** Kernel format detection narrowed to the formats the omp pipeline can
@@ -10,6 +10,22 @@ export declare function payloadToCore(payload: unknown, fmt: ProviderWireFormat)
     cacheControls?: Map<string, unknown>;
 };
 export declare function coreToPayloadMessages(msgs: BiliMessage[], fmt: ProviderWireFormat, cacheControls?: Map<string, unknown>): unknown[];
+export type Representability = {
+    ok: true;
+} | {
+    ok: false;
+    reason: string;
+};
+/** Whether the payloadToCore → coreToPayloadMessages round-trip can rebuild
+ *  this payload WITHOUT content loss. The sets above mirror the kernel
+ *  codec switches; everything they do not parse is dropped or flattened on
+ *  the rebuild. Unrepresentable payloads must fail the transform OPEN —
+ *  pass through untouched rather than lose content (issue #3 review). */
+export declare function payloadRepresentable(payload: unknown, fmt: ProviderWireFormat): Representability;
+export type WireTagRenderScope = {
+    config: Config;
+    tokenCount: number;
+};
 /** omp's wire tag contract (issue #66) on top of the kernel's "text-only"
  *  render: the proxy keeps tool content pristine, but omp's nudge ranges
  *  target tool results — the model must be able to cite them by ref, so tag
@@ -17,8 +33,16 @@ export declare function coreToPayloadMessages(msgs: BiliMessage[], fmt: Provider
  *  kernel's "text-only" also tags assistant text — strip it: the model
  *  echoes tags it sees on its own responses (the contract patchRefTag
  *  enforced in the AgentMessage bridge). Tool-call args stay clean (replay
- *  JSON-parses them). */
-export declare function applyWireTagContract(msgs: BiliMessage[], state: CompressionState): BiliMessage[];
+ *  JSON-parses them).
+ *
+ *  Rendering goes through the kernel's render-refs NODE so token counts in
+ *  the tags come from the fold state's tokenSnapshot (written once per ref,
+ *  reused forever) instead of being recomputed per call; the updated
+ *  snapshot is written back into the fold state in place. Tool names are
+ *  re-attached from the call pieces first — the codecs drop them on
+ *  tool-result pieces and classifyType would render type="tool" where the
+ *  context path (and the system-prompt contract) shows the real name. */
+export declare function applyWireTagContract(msgs: BiliMessage[], state: CompressionState, scope: WireTagRenderScope): BiliMessage[];
 /** Stable cross-turn identity for the core-space LCP fold. The text carries
  *  our own <acp> ref tags from the previous turn's output (the model sees
  *  them and they ride back in the next request) — stripped before hashing

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "billion-context-omp",
-	"version": "0.2.7",
+	"version": "0.2.9",
 	"description": "One billion, not one million. Model-driven context management for the oh-my-pi (omp) coding agent.",
 	"main": "dist/index.js",
 	"types": "dist/index.d.ts",
@@ -68,7 +68,7 @@
 		"@oh-my-pi/pi-coding-agent": "17.3.8",
 		"@oh-my-pi/pi-utils": "17.3.8",
 		"@types/node": "^26.1.2",
-		"acp-kernel": "0.0.28",
+		"acp-kernel": "0.0.31",
 		"billion-context-kit": "0.2.0",
 		"bun-types": "^1.3.14",
 		"tsup": "^8.5.1",