Resolve async HTTP research with Carrier #2

Merged

lost-rob0t merged 1 commit from agent/carrier-async-http-research into main

2026-08-12 18:19:20 +00:00

lost-rob0t commented

2026-08-12 18:18:53 +00:00

(Migrated from github.com)

What changed

identifies orthecreedence/carrier as the native asynchronous Common Lisp HTTP client
adds a source-level Carrier evaluation and capability matrix
removes the unresolved Lobster assumption from repository instructions, parity research, transport tests, and architecture notes
records hard production blockers in stock Carrier: cl-async-ssl uses SSL_VERIFY_NONE, Carrier has no public cancellation handle, no connection pooling/reuse, and request-body streaming remains absent
defines two future implementation paths: harden/fork Carrier, or build a small Common Lisp async client over libcurl multi
keeps the repository in research-only phase; this PR adds no runtime Common Lisp/ASDF/provider implementation

Evidence

Reviewed Carrier README, ASDF system, implementation, open issues #13/#16/#17/#25, cl-async-ssl source, and official libcurl multi/multiplexing documentation.

Boundary

This does not approve runtime implementation. It resolves the async-client identification gap and tightens the production transport requirements.

## What changed - identifies `orthecreedence/carrier` as the native asynchronous Common Lisp HTTP client - adds a source-level Carrier evaluation and capability matrix - removes the unresolved `Lobster` assumption from repository instructions, parity research, transport tests, and architecture notes - records hard production blockers in stock Carrier: `cl-async-ssl` uses `SSL_VERIFY_NONE`, Carrier has no public cancellation handle, no connection pooling/reuse, and request-body streaming remains absent - defines two future implementation paths: harden/fork Carrier, or build a small Common Lisp async client over libcurl multi - keeps the repository in research-only phase; this PR adds no runtime Common Lisp/ASDF/provider implementation ## Evidence Reviewed Carrier README, ASDF system, implementation, open issues #13/#16/#17/#25, `cl-async-ssl` source, and official libcurl multi/multiplexing documentation. ## Boundary This does **not** approve runtime implementation. It resolves the async-client identification gap and tightens the production transport requirements.