journey-submit

# Journey: Hackathon submission Stage 5 (final) of the guided journey. Resolve the active hackathon, confirm fields, submit. ## When to use - Dispatched by `journey` when `current_stage: submit` and `hackathon_mode: true`. - Directly via `/butterbase-skills:submit`. - No-op (returns with `"submit is disabled outside hackathon mode"`) if `hackathon_mode: false`. ## Preflight If `docs/butterbase/03-preflight.md` is missing, older than 24 hours, or `00-state.md` has `app_id: null`, invoke `butterbase-skills:journey-preflight` first. Wait for it to return successfully before proceeding. Additionally: refuse to run unless `deploy` is ticked in `00-state.md`. If it is not, tell the user to run `/butterbase-skills:journey-deploy` first. ## Inputs - `docs/butterbase/01-idea.md` — title / tagline candidates. - `docs/butterbase/02-plan.md` — feature list. - `docs/butterbase/04-build-log.md` — what actually shipped. - `docs/butterbase/00-state.md` — `app_id`, `deployed_url`. ## Procedure ### Step 1 — Prep (resolve which hackathon) Always start with `action: "prep"`. Do **not** assume there is exactly one hackathon, and do **not** invent a field schema from prior context — the platform owns the schema and it varies per hackathon. ```jsonc // First, ask the user: "Do you have a submission code from the organizer? (paste it, or 'no')" // If yes, pass it. If no, omit it. { "tool": "prep_and_submit_hackathon_entry", "arguments": { "action": "prep", "submission_code": ...