Module artifacts 

Artifact tokens (architecture.md §8) + on-disk path resolution.

Default fetches start with the HTTP-safe body artifact and expand to the browser artifact set only when rendering is used. Storage stays opt-in due to sensitive-data risk. Each artifact maps to a fixed filename; the response JSON references produced files as absolute paths under --out/<request_id>/.

Structs

ArtifactPaths

Concrete on-disk locations for a single fetch. Built from --out (or the default system temp afhttp-out/) plus the request id.

Enums

Artifact

Artifact kinds. Body is the default HTTP-safe artifact; browser-backed fetches can produce the richer DOM/network artifacts. Storage is default-off due to sensitive-data risk — agents must request it explicitly via --want. Per-artifact warnings (§8 last ¶) are emitted when a backend lacks the capability rather than failing the fetch.