Agent-First HTTP v0.4.3: Release Hardening for Agent Tools

Agent tools are only useful if agents can install and trust them consistently.

Agent-First HTTP v0.4.3 was a release-hardening update: less about changing the HTTP protocol, more about making afhttp easier to adopt as part of Agent-First Kit.

The identity change: afhttp moved into Agent-First Kit

The release migrated repository metadata, bonds, docs, and publication identity to agentfirstkit.com. That gave afhttp the same home as the rest of the kit: structured data, HTTP, PostgreSQL, and payments.

The README was rewritten around agent ergonomics, with the detailed guide moved into docs/overview.md. The project page became a short adoption surface; the docs became the place for operational detail.

The discipline change: structured output stayed protected

v0.4.3 tightened clippy rules around unwrap, expect, panic, and stdout or stderr prints in production code.

That is not just Rust tidiness. afhttp’s core promise is that runtime output is a structured event stream. Accidental prints and panics are protocol leaks. The lint rules make those leaks harder to introduce.

The packaging change: releases became easier to consume

The release infrastructure was overhauled so CI builds platform binaries with checksums, and local release scripts update Homebrew and Scoop packaging.

For agents, this matters indirectly: a tool that installs cleanly across machines is a tool users are more willing to put into an agent’s default toolbox.

Where this fits: reliability includes distribution

An agent-first protocol is not enough. The binary has to be packaged, checked, installed, and documented in a repeatable way.

v0.4.3 made afhttp feel less like an experiment and more like a kit component.