Outcome: done
Changed: tests/test_research_client.py:1-700
Verified by: make verify -> exit_code 0, 140 tests OK (36 new), "verification passed"; only pre-existing StarletteDeprecationWarning from tests/test_api.py:1, none introduced
Findings: 36 stdlib-unittest tests with retoor header; parsing covered for web results, ai memory/provider variants, deep block (sources, grades, rounds, queries_tried), images extra metadata, chat usage, describe get/upload/raw; error-in-body asserted via real _request (patched urllib.request.urlopen): {success:false,error:"Empty query"}->RsearchError 400, providers-exhausted 503, success:false with HTTP 200, detail/title fallback, empty/invalid/non-dict body, URLError; count clamping contract asserted at client boundary: count=0 sent and parsed server clamp 1, count=25 -> 10, invalid -> 10, count=None omits param; request construction asserted (params, deep timeout 180 vs 30, cache=false, content cache fill); each parsing test asserts exact mapped values so any field-mapping regression fails; no test skipped or weakened
Open: none
Confidence: high - all acceptance criteria asserted by passing tests against verified pre-change baseline
Typosaurus-Run: 4e2afb673c7f4578a12276d9181b982d
Typosaurus-Node: 05afdbb5c5324f2ca0b0dfd8ce320f12
Typosaurus-Agent: @sveta
Refs: #31
retoor retoor@molodetz.nl
typosaurus-sandbox
Sandbox for Typosaurus end-to-end verification.
A FastAPI application serving arithmetic operations over HTTP with JSON request/response bodies.
Configuration
The application uses a single .env.json file at the project root as its central point of truth
for configuration. Defaults are plug-and-play and require no setup:
{
"host": "127.0.0.1",
"port": 8000
}
When no .env.json is present, the application starts with these defaults. To customise, create
.env.json in the project root and populate only the keys that differ.
Usage
Start the server
python -m typosaurus_sandbox
The server listens on http://127.0.0.1:8000 by default.
Health check
GET /health
Response:
{"status": "ok"}
API endpoints
All calculator endpoints accept POST requests with a JSON body and return a JSON response.
POST /api/v1/calculator/add
Add two integers.
Request:
{"left": 3, "right": 5}
Response:
{"result": 8}
POST /api/v1/calculator/subtract
Subtract the right integer from the left.
Request:
{"left": 10, "right": 3}
Response:
{"result": 7}
POST /api/v1/calculator/clamp
Clamp a value between a low and high bound.
Request:
{"value": 15, "low": 0, "high": 10}
Response:
{"result": 10}
Boundaries are inclusive. A low > high combination produces a 422 validation response.
POST /api/v1/calculator/clamp-to-byte
Clamp an integer to the byte range [0, 255].
Request:
{"value": 300}
Response:
{"result": 255}
POST /api/v1/calculator/average
Compute the arithmetic mean of a list of values.
Request:
{"values": [1, 2, 3, 4, 5]}
Response:
{"result": 3.0}
An empty list produces a 422 validation response.
POST /api/v1/calculator/median
Compute the median of a list of values. Values are sorted internally; an even-length list returns the average of the two middle values as a float.
Request:
{"values": [1, 3, 5]}
Response:
{"result": 3.0}
Request (even length):
{"values": [1, 2, 3, 4]}
Response:
{"result": 2.5}
An empty list produces a 422 validation response.
POST /api/v1/calculator/variance
Compute the population variance of a list of values.
Request:
{"values": [1, 2, 3, 4, 5]}
Response:
{"result": 2.0}
An empty list produces a 422 validation response.
POST /api/v1/calculator/percentage
Compute what percentage value is of total.
Request:
{"value": 50, "total": 100}
Response:
{"result": 50.0}
A zero total produces a 422 validation response.
Verification
make verify
Runs compile-all checks against all source and test files, then executes the full test suite. Zero warnings are tolerated.