A GitHub create call timed out. What now?

How a contract and correlation marker help an agent recover a reference without blindly creating another issue.

A timeout tells you that the caller did not receive a response in time. It does not tell you whether the receiving system completed the write. Repeating the same create call may produce a duplicate.

Before the original write, register the expected GitHub issue state with Verify. Put the returned correlation marker in the issue body. The contract records the repository, title, required labels and expected state. Registration itself does not create an issue.

After an ambiguous response, ask Verify to read the receiving system. If a known issue reference is available, Verify checks that resource. Otherwise it performs a bounded search for the marker and refreshes a candidate before comparing the declared fields.

A matching observed resource can give the agent an issue reference to reuse. Conflicting fields or multiple observed matches need reconciliation. Missing or incomplete evidence stays indeterminate. None of these results gives unconditional permission to repeat the original write.

This first connector checks GitHub issue state. It does not establish that a customer was notified, that engineering accepted the request, or that the underlying problem was solved. Add those as separate, explicitly supported checks when the workflow requires them.