Lann

As written this depends on https://github.com/seanmonstar/warp/pull/942 being merged. Another possible approach would be to extract client cert with a Tower layer, though from a brief review that looks like significantly...

This still needs attention to yanking.

I'm sure I didn't catch everything but I think this is pretty close to complete.

One option for the invoice signatures file would be to make it a "TOML-compatible" file format (`invoice.sigs` perhaps?), reusing the current spec's `[[signature]]` blocks and appending the signature itself to...

I hate to say it, but this would be simplified by using JSON...

Another proposal for signatures; I think this is what I would prefer for a TOML-based solution: ```toml [[signature]] # Untrusted label: Maybe Real Signer signer = """ key = "1c44..."...

I think I've covered most of the changes in #322 now. Biggest change to the protocol is that bindle GET/POST would work with a string version of the invoice, e.g....

The best-performing way (probably) to do this would be for tsc to do it while type-checking. I hacked this together by modifying estrella locally; it was a little messy with...

Sure, I'd be happy to not carry the patch myself. Is the approach alright? Another possibility would be to add a `noEmit` option that defaults true.

Or simpler: some kind of `notes` field that will just be printed on template instantiation. At least for _our_ templates we could point at TinyGo et al there.