Add genlocke leg progression with advance endpoint and run context
When a run belonging to a genlocke is completed or failed, the genlocke status updates accordingly. The run detail API now includes genlocke context (leg order, total legs, genlocke name). A new advance endpoint creates the next leg's run, and the frontend shows genlocke-aware UI including a "Leg X of Y" banner, advance button, and contextual messaging in the end-run modal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -80,8 +80,8 @@ A dedicated page showing:
|
||||
- [x] The first leg starts automatically upon genlocke creation
|
||||
- [ ] Each leg is a full nuzlocke run, tracked identically to standalone runs
|
||||
- [ ] Completing a leg triggers a transfer step where surviving Pokemon can be carried forward
|
||||
- [ ] Failing a leg marks the entire genlocke as failed
|
||||
- [ ] Completing the final leg marks the genlocke as completed
|
||||
- [x] Failing a leg marks the entire genlocke as failed
|
||||
- [x] Completing the final leg marks the genlocke as completed
|
||||
- [ ] A genlocke overview page shows progress, configuration, cumulative stats, lineage, and graveyard
|
||||
- [ ] Transferred Pokemon appear as eggs (base form, level 1) in the next leg
|
||||
- [ ] Pokemon lineage is trackable across multiple legs
|
||||
|
||||
Reference in New Issue
Block a user