Source and example scope
Replay the saved synthetic requests and compare each observed label with its authored expectation. Any disagreement stays visible; the model is not rerun to obtain a preferred answer.
Show the added lines and their stated purpose. Compare temporary tracing or a debug bypass with intentional diagnostics and test fixtures before editing the code.
The temporary HERE trace and the documented audit event both produce output. Their stated purposes differ. This rubric uses that context instead of rejecting every logging call.
The same distinction applies to localhost and skipped tests. A local test server can be intentional; a test skipped solely during debugging deserves review before release. The missing-purpose input keeps an explicit Need context outcome.
The page returns a review label for the added text. It does not parse a repository, remove code, run tests or guarantee that all debugging artifacts have been found.
These six synthetic inputs and Choice rules are original demonstrations. The API-collected X post links to jev-commit, whose pinned README describes related checks using Noul questions. This page is not that hook, does not execute Git, and does not reproduce its measurements or credential-blocking policy.

Use the sample to understand the rule, then test your own input for debug-code leftovers.

Show the added lines and their stated purpose.

Open the decision rules and keep the intended distinction between Debug leftover, Intentional diagnostic, No debug cue, Need context. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Need context before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Temporary trace | Debug leftover | 95.0% |
| Documented audit event | Intentional diagnostic | 91.0% |
| Debug-only test skip | Debug leftover | 92.0% |
| Local test fixture | Intentional diagnostic | 98.0% |
| Ordinary validation | No debug cue | 100% |
| Unexplained print | Need context | 63.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
Replay the saved synthetic requests and compare each observed label with its authored expectation. Any disagreement stays visible; the model is not rerun to obtain a preferred answer.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.jsonInput scope and downstream handling determine what the label can tell you.
No. This example uses the stated purpose and execution context. An intentional product diagnostic has its own outcome.
It could be a temporary trace or an expected operational message. The supplied line does not establish which interpretation is correct.
No. It is the distribution for this request. Six synthetic fixtures check the workflow and preserve disagreements; they are not a production benchmark.
The window shows an error and returns no fresh judgment. The replay runner makes one request without retries. A missing-evidence label is about the input, not a substitute for an API failure.
Edit the supplied evidence above, or open the Playground for a different decision rule.