Check the clock, the setup, the push and the pitch line

Run this at the start of every working session in the team's clone, before any other work: the clock comes first, because a team that loses track of it loses its submission. The hackathon CLI does the checks; this skill runs it, reads the --json answers and walks the participant through the fixes. Run from the team's clone. If the participant never joined (no hackathon command, or hackathon connect says to sign in), use the hackathon-setup skill instead.

1. The clock, first

hackathon event status --json

Read, from the answer: phase (scheduled, building, grace, closed), serverTime, event.buildEndsAt, event.freezeAt (always the build end plus 15 minutes), event.timezone, event.lastReschedule (the organizers moved the build end, with their reason), me.project (the team: id, name) and, in the team's line of projects[], submission.repository.designatedBranch and submission.lastReceipt (sha, receivedAt, late).