We can only respond to the request if the request's slot range is in the past (some time for the chain index to update itself). targetSlot is the earliest time at which we can answer the request, so we may need to wait a little before we submit it.

This caused the marlowe follower contract to miss the past updates when it is first started.

Pre-submit checklist:

• Branch
  • Commit sequence broadly makes sense
  • Key commits have useful messages
  • Relevant tickets are mentioned in commit messages
  • Formatting, materialized Nix files, PNG optimization, etc. are updated
• PR
  • Self-reviewed the diff
  • Useful pull request description
  • Reviewer requested

Pre-merge checklist:

• Someone approved it
• Commits have useful messages
• Review clarifications made it into the code
• History is moderately tidy; or going to squash-merge