itowlson

This might not be a viable option, but what if you modified 3 so that if a consumer _requested_ an invoice that was not yet marked complete, the server checked...

Another possibility is that the server recomputes the completeness of an invoice when any parcel is uploaded. However, this could go amiss if two bindles are each missing the same...

The misleading message occurs when the client is constructed with `http2_prior_knowledge` set to `false`. ~The Bindle CLI never does that; I changed the Hippo CLI to do it on one...

Semi-closing the loop on this one: - With a nonexistent server all is well - With a server that reliably returns 404 for unknown URLs, this will always produce `Invoice...

So I think the fundamental issue is that the generic status unwrap code always assumes it's an _invoice_ that was not found rather than the general _invoice endpoint_ (or whatever...

@technosophos As an implementer, I would find an example useful! @fibonacci1729 When you talk about "the merkle root," am I right in understanding you are referring to the input of...

I like that idea. Another idea is to provide a `prerequisites` section which would be a bunch of command lines that need to 'pass' (for some value of 'pass') or...

Thinking more about this... this doesn't belong on templates, but in the `[component.build]` section, so that if Alice creates an application from a template, commits it, and then Bob checks...

What is the expectation here for maintenance, given no CI and the nightly toolchain requirement? Is this something that we will do as and when the spirit moves us, or...

Nah, "as and when" was the arrangement I assumed and I'm happy with it. Thanks!