4 lines
1.6 KiB
Plaintext
4 lines
1.6 KiB
Plaintext
2026-08-28T15:14:41-05:00 no semaphore slot after 300s - not launched
|
|
2026-08-28T15:15:41-05:00 semaphore gate unavailable - proceeding UNGATED (install metrics dirs)
|
|
Checklist done. Batch-1b TASK is gated/queued — not my scope. Starting the `crush server` spike.UID 1005 matches the default socket name; no live server. Starting test instance on scratch socket.Server is live on scratch socket. Probing protocol and client attach.HTTP/1.1 with Go's default 404 mux. Hunting route paths.Client `run` over the socket works. Identifying the gRPC service surface.Session persisted server-side in scratch dir. Now testing process ownership + survival across client disconnect.pgrep matched my own turn process — re-checking against real server PID 2579443.Key finding: tool processes (`sleep 20`) parent to the **client**, not the server. Testing client-disconnect behavior.Server hit its 90s timeout mid-test. Restarting with longer window for a clean disconnect test.Session turn completed client-side before my kill (TERM was ignored). Checking debug log + session subcommands for any server-side execution feature.Local evidence sufficient. Quick doc check for authoritative server description.Evidence complete. Cleaning up test instance and scratch dirs.Cleanup verified (remaining matches are my own turn's dispatch screen — untouched). Writing report.Spike done: `crush server` is only a gateway/db service (tool exec + agent loop stay client-side; auth-less 0755 /tmp socket) → NOT a screen replacement today; findings + verdict in inbox-pmo/SPIKE-crush-server.md, test instance killed and scratch cleaned.
|