@punica/editor 1.32.1 → 1.34.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -389,6 +389,22 @@ declare module 'punica' {
|
|
|
389
389
|
* active (meta-tools not counted). Default 40.
|
|
390
390
|
*/
|
|
391
391
|
hotSetSize?: number;
|
|
392
|
+
/**
|
|
393
|
+
* Whether the tools outside the hot set ride along as a one-line
|
|
394
|
+
* index the model can load on demand (`'full'`, the default) or are
|
|
395
|
+
* left out entirely (`'none'`: the hot set ships alone, without the
|
|
396
|
+
* `capability.search` / `capability.describe` meta-tools, since with
|
|
397
|
+
* nothing indexed there is nothing for them to load).
|
|
398
|
+
*
|
|
399
|
+
* The index was priced as one line per tool inside a cached prompt
|
|
400
|
+
* prefix. A local core caches no prefix across runs, so every fresh
|
|
401
|
+
* chat re-evaluates the whole index: measured on a 9B model, a 48 KB
|
|
402
|
+
* index plus 50 schemas made 16,878 input tokens and 46 seconds
|
|
403
|
+
* before a 44-token answer. The substrate cannot see which core is in
|
|
404
|
+
* front of the loop; the product can, and says so here. Ignored when
|
|
405
|
+
* `toolFilter` is supplied (verbatim selection carries no index).
|
|
406
|
+
*/
|
|
407
|
+
deferredIndex?: 'full' | 'none';
|
|
392
408
|
/**
|
|
393
409
|
* Capability ids guaranteed a place in the hot set, whatever the
|
|
394
410
|
* intent ranking says. Exact ids only — no globs, so the substrate
|
|
@@ -242,6 +242,12 @@ declare module 'punica' {
|
|
|
242
242
|
* waiters/UI can match a pending to its run.
|
|
243
243
|
*/
|
|
244
244
|
traceId?: string;
|
|
245
|
+
/**
|
|
246
|
+
* The sentence of the rule that stopped the call, when a rule did
|
|
247
|
+
* (`.punica/policy.yaml` `reason:`). Carried into the pending
|
|
248
|
+
* approval as its `reason`, ahead of the capability's description.
|
|
249
|
+
*/
|
|
250
|
+
reason?: string;
|
|
245
251
|
}
|
|
246
252
|
): void;
|
|
247
253
|
|