Mentor Roster - enough mentors for every hackathon track, reachable when a team is stuck

Enter the hackathon brief's challenge tracks and sponsor integration, the hacking window and rooms, and the mentors you have with what each actually knows, and get coverage depth set per track rather than a headcount, the recruitment channels your roster deadline allows, every mentor tagged in the brief's vocabulary with the mentor-judge conflict handled, the gaps by track and hour - then the request mechanic teams will read and the mentor briefing with the help-versus-build boundary. Free in your browser: the rung and commitment per track (a sole-substrate or required sponsor API guaranteed on the floor whenever its track is worked), every unmatched tag listed, the hour-by-hour coverage with the overnight gaps called out, the contact log whenever a mentor also judges, the recruitment, request-mechanic and briefing-depth menus re-ranked with deleted rungs struck, rotation by expertise and the constraint handed to the volunteers' shift plan as text, with CSV, calendar, Markdown and JSON exports. A metered run writes the mentor plan, or the request mechanic and the mentor briefing. A mentor is not a volunteer, and not a judge: it never invents a mentor-to-participant ratio, a staffing formula or a response-time target, and never infers anyone's identity or seniority from a name. Built on the SkillSafe skill @samber/hackathon-mentoring, from samber/dev-event-organizer-skills (MIT), by Samuel Berthe.