op-supernode: Superroot SLA Updates #19180
Description
The SLA of the Superroot object is ill-defined, but also it is not currently behaving as we'd like.
The addage from Proofs is "whenever you can get output roots for all the chains, you should be able to provide a super root"
What this means to me is that we should ensure two distinct categories:
1: the superroot should be eagerly available. That is, if there are output roots at the timestamp for all chains, let's construct the super-root
2: the extended information regarding verification and local derivation must accurately represent the condition of data which yielded the superroot. IE - if the root is built from un-verified components, that should be obvious when inspecting the verification and local safety information.
DoD: Super-Root API is fully integrated with Proofs testing.
Probably a co-task between @axelKingsley and @Inphi