Runs should (must at WFs) get published as soon as available

[eldering]

Closes: #222

[deboer-tim]

I know we discussed this hours ago, buuuut.... :)

Reading this now feels odd for the Contest API. If we need to specify that CCSs should create runs as soon as they're ready, does the lack of a similar statement in submissions or judgements or X imply that those don't? What if CCS does but CDS doesn't? It also wasn't clear to me whether the original issue was due to runs not getting created immediately, created but not getting exposed to the API, or notifications not sent until later. If the latter this doesn't say anything about notifications.

Just my 2 cents, but I would leave the CCS comment out of the Contest API and maybe update the run description to include the rest, e.g. Runs are judgements of individual test cases of a submission, allowing clients to track judging progress in real-time. which implies the rest

If anyone was concerned that we don't require objects to be created or notifications to be sent immediately, I would do that in a general way instead of anywhere object-specific. E.g. in the notification guarantees section we could add something slightly vague like notifications will be sent in a timely manner.

[niemela]

Reading this now feels odd for the Contest API.

Yeah... Maybe we could word it as more of a "A common use case for the runs/ endpoint is the give real time updates on judging progress. For this to be possible, the endpoint should be updated in near real time"? I.e. more informational, and less require-y.