TavernKeeper Scan Report

MentallyQuill/Directive

Commit 3bdde99 Reviewed Sep 4, 2026

No material or immediate-danger concern was identified in this review.

This advisory report describes what the named tools and review process found at one exact commit. Unknown or unobserved behavior may still exist.

0 immediate danger 0 material 46 low

What this review found

No material or immediate-danger item was identified.

Minor cautions

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.unsafe-regex. The match applies to this repository.

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: src/runtime/v1-accepted-pair-source.mjs:4

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.unsafe-regex. The match applies to this repository.

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: src/time/time-evidence.mjs:10

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.unsafe-regex. The match applies to this repository.

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: src/hosts/sillytavern/preset-manager.mjs:15

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.unsafe-regex. The match applies to this repository.

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: src/time/ship-time.mjs:2

Deterministic technical evidence (37)

JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-mobile-campaign-mission-accordions.mjs:39
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-ship-mechanics-state.mjs:146
JavaScript analysis reported javascript.xray.unsafe-regex · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-unsafe-regex-inert · Execution scope: tooling-only

Source: tools/scripts/test-campaign-required-empty-state.mjs:95
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/repair-sam-vickers-pending-pair.mjs:478
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-mission-journey.mjs:93
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-character-creator-assist-layout.mjs:201
JavaScript analysis reported javascript.xray.unsafe-regex · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-unsafe-regex-inert · Execution scope: tooling-only

Source: tools/scripts/helpers/fake-dom.mjs:82
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-directive-launcher-button-visual.mjs:23
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-mission-evidence.mjs:567
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/repair-sam-vickers-premature-evidence.mjs:555
JavaScript analysis reported javascript.xray.prototype-pollution · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

The code has a known weakness, though this scan does not show that anyone can exploit it here.

Policy reason: javascript-xray-structured-weakness · Execution scope: runtime

Source: src/runtime/state-delta-gateway.mjs:7
JavaScript analysis reported javascript.xray.unsafe-regex · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-unsafe-regex-inert · Execution scope: tooling-only

Source: tools/scripts/test-expanded-interface-shell.mjs:92
JavaScript analysis reported javascript.xray.unsafe-regex · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-unsafe-regex-inert · Execution scope: tooling-only

Source: tools/scripts/test-cohesion-ship-visual.mjs:82
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/capture-runtime-route-live.mjs:6
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/repair-sam-vickers-pending-pair.mjs:39
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-state-delta-codec.mjs:47
JavaScript analysis reported javascript.xray.shady-link · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/capture-runtime-route-live.mjs:6
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-cohesion-ship-visual.mjs:32
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-mission-reducer.mjs:61
JavaScript analysis reported javascript.xray.prototype-pollution · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

The code has a known weakness, though this scan does not show that anyone can exploit it here.

Policy reason: javascript-xray-structured-weakness · Execution scope: runtime

Source: src/storage/v1-state-delta-codec.mjs:5
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-episode-evaluator.mjs:326
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-command-bearing.mjs:77
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-sam-vickers-pending-pair-repair.mjs:78
JavaScript analysis reported javascript.xray.shady-link · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/serve-expanded-interface-preview.mjs:56
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/repair-sam-vickers-premature-evidence.mjs:37
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/serve-expanded-interface-preview.mjs:8
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-sam-vickers-premature-evidence-repair.mjs:149
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-campaign-required-empty-state-visual.mjs:54
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-gameplay-notification-visual.mjs:62
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-turn-activity-indicator-visual.mjs:23
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-browser-runtime-safety.mjs:28
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-certified-ui-authority.mjs:10
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-duty-report-runtime.mjs:147
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-mission-entry-capabilities.mjs:142
JavaScript analysis reported javascript.xray.encoded-literal · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-v1-duty-report-planner.mjs:166
JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-authoritative-ship-chronometer-visual.mjs:14
JavaScript analysis reported javascript.xray.shady-link · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

This technical signal is not part of the shipped runtime behavior.

Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

Source: tools/scripts/test-sillytavern-fresh-chat-hygiene.mjs:667

Contextual expected matches (5)

JavaScript analysis reported javascript.xray.serialize-environment

Expected behavior · high confidence

This test script launches a small local helper program to serve preview pages for automated visual checks. It hands that helper the same environment settings any program normally inherits. Nothing is collected or sent anywhere; this is a standard way to start a helper program.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.serialize-environment. The match applies to this repository.

Contextual assessment: The serialize-environment signal corresponds to spawning a local preview-server helper script with the parent process environment copied to the child so it inherits PATH and other standard runtime variables. This is ordinary child-process plumbing for a developer-run conformance test: the environment is forwarded locally to a repository-owned script, never serialized to storage, a network destination, or any output that leaves the machine. No credentials are read, transformed, or transmitted beyond normal process inheritance, and the file is tooling-only with no shipped extension behavior.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.serialize-environment
File role: tooling
Source: tools/scripts/test-expanded-interface-visual-conformance.mjs:70

JavaScript analysis reported javascript.xray.shady-link

Expected behavior · high confidence

The scanner mistook the official technical name used for drawing vector graphics for a suspicious web link. It is just a required label for creating SVG drawings on screen; nothing connects to the internet or sends information anywhere.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.shady-link. The match applies to this repository.

Contextual assessment: The scanner flagged three string literals that resemble web addresses, but every occurrence in the supplied source is the standard SVG namespace identifier passed to the browser's namespaced element-creation API when building SVG shapes, leader lines, and cohesion-ring graphics for the ship journal UI. The string is a namespace constant required by the DOM API, not a network destination. The surrounding code contains no fetch, socket, script loading, or resource retrieval of any kind, and no data is transmitted. The flagged capability matches the extension's stated purpose of rendering its own interface.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.shady-link
File role: production
Source: src/ui/ship-journal.js:158

JavaScript analysis reported javascript.download-to-execution

Expected behavior · high confidence

An automated test needs two things: it starts a small local helper server, and it opens pages from that local server in a headless browser to check the interface visually. A scanner saw both 'network' and 'run a program' in one file and flagged the combination, but the program being run is a fixed helper script from the project itself, and the only network traffic goes to that same local helper. Nothing downloaded is ever executed.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.download-to-execution. The match applies to this repository.

Contextual assessment: The correlation arises because the file both performs network requests and spawns a process. Examining actual data flow: the network requests are fetches to a loopback-only preview server on a dynamically chosen port started by this same script, and the process spawn is a fixed, repository-relative helper script executed with the same interpreter, not a command derived from network input. No data retrieved over the network is ever passed to the process execution path, and the entire flow is confined to the developer machine within a test harness. This is the ordinary architecture for a browser-based conformance test, not a download-to-execution chain, and the file ships no runtime behavior to extension users.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.download-to-execution
File role: tooling
Source: tools/scripts/test-expanded-interface-visual-conformance.mjs:58-1894

OpenGrep reported tavernkeeper.credential-exfiltration.javascript-secret-to-network

Expected behavior · high confidence

This is a developer tool that opens a private, invisible browser on the developer's own computer, points it at their own local chat install, and takes pictures of the interface for design checks. The scanner saw an environment variable near a network operation, but the variable only holds the local address to visit. There is no password or API key involved, and no information leaves the developer's machine.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.credential-exfiltration.javascript-secret-to-network. The match applies to this repository.

Contextual assessment: This is a developer-only screenshot-capture tool that is not part of the shipped extension runtime. The flagged line passes a base address, read from an environment variable and defaulting to the local loopback host where a SillyTavern instance runs, to a page-navigation command sent over a DevTools protocol WebSocket. That WebSocket connects to a headless browser the script itself spawned with its debug endpoint bound to the loopback interface. The environment variable holds a destination address, not a credential; no key, token, password, or secret is read anywhere in the file. The value flows only to a locally spawned browser process on the same machine, and nothing is transmitted to any external host. The pattern is a false positive for credential exfiltration: a URL configuration value reaching a local automation sink, proportionate to the tool's stated purpose of capturing UI layout screenshots.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: opengrep 1.26.0
Rule: tavernkeeper.credential-exfiltration.javascript-secret-to-network
File role: tooling
Source: tools/scripts/capture-runtime-route-live.mjs:234

JavaScript analysis reported javascript.xray.encoded-literal

Expected behavior · high confidence

The test takes a known artwork file, computes a fingerprint of it, and checks that fingerprint against a fixed expected value written in the code. That long string of letters and numbers is just a recorded fingerprint used to notice if the artwork file ever changes by accident. It is not hidden code.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.encoded-literal. The match applies to this repository.

Contextual assessment: The encoded-literal signal at the flagged location corresponds to a long hexadecimal digest used as an expected value in a conformance assertion: the test hashes the alpha channel of a known bundled image with SHA-256 inside the browser and compares the result against a pinned literal to detect accidental asset changes. A hardcoded expected digest is a standard deterministic testing technique, not concealment of executable content or a covert channel. The literal is compared, never decoded or executed, and the file is tooling-only.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.encoded-literal
File role: tooling
Source: tools/scripts/test-expanded-interface-visual-conformance.mjs:1147

Coverage and limitations

Inventory: 1124 files · 57823311 bytes
Contextual coverage: 46 of 46 candidates assessed

JavaScript coverage

Status: Complete
Candidates: 322 files · 3635957 bytes
X-Ray review families: 77 warning occurrences compacted to 44 evidence-preserving review families
Representations: 322 raw · 6 decoded · 0 normalized · 0 bundle modules
Stage scans: 322 raw signatures · 322 raw AST · 322 raw OpenGrep · 6 derived signatures · 0 derived AST · 6 derived OpenGrep

Tools

inventory 0.1.0 — completed
tavernkeeper-static 5 — completed
gitleaks 8.30.1 — completed
opengrep 1.26.0 — completed
javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1 — completed
osv-scanner 2.4.0 — completed
zizmor 1.28.0 — not-applicable
malcontent 1.25.7 — completed

Limitations

This advisory review cannot prove the absence of unknown behavior.

Technical scan identity

Full commit: 3bdde99ad29f9b682d29f3f354aacd60e884067e
Completed: Sep 4, 2026
History depth: 7 commits
Method: Deterministic evidence with contextual review
Reviewer: nano-gpt.com · zai-org/glm-latest
Scanner: 0.1.0
Scanner policy: 5
Rule catalog: 2
Contextual policy: 5
Ecosystem context: sillytavern-community-v1
Prompt: contextual-review-v7
Assessment schema: contextual-assessment-v2
Review provenance: 3 fresh / 0 reused groups · 5 fresh / 0 reused candidates
Review source reports: none
Evidence triage: 41 deterministic / 5 contextual candidates · 3 contextual / 41 total behavior cases
Model budget: 2 model calls · 3 / 12 fresh cases · 72984 / 200000 estimated input · 54980 / 250000 actual input · 3720 / 40000 output tokens
Review batching: 2 model calls · up to 2 groups and 3 candidates per call · 0 retry calls · 0 over-budget singleton calls
Review usage: 54980 input · 3720 output · 1344 cache read · 177 reasoning tokens
Report: 25751d20ee4bada0cf04c179bda8e18cc3058bd577f9a6094e42d061cf51b74d