Propose what an entry over a range of intervals would say, in the cloud

The hand-made entry's ranges, as the daemon's POST /entries/propose takes them. Decided in the request: 202 answers the proposal and names the run it was decided as, which GET /v1/pipeline/runs/{id} answers too. It first waits, at most 30 s, for the cloud's own interval runs of what the device already uploaded over the ranges, as a Generate does. Over the caller's daily cap, or on a failure, the answer is offline with no proposal. Writes nothing but the answer. The internal firm's alone until firms outside it join (403 otherwise). It reads the activity of the device X-Six-Minute-Device names (without it, until the follow-up, the caller's most recently active device), and the words where each interval is an entry's evidence: under an entry generated on any of the caller's devices, that device's; under a hand-made entry or free time, the asking device's and the earlier ids X-Six-Minute-Device-Known names. An entry's evidence is the activity it was generated from (O12).