Repository navigation
Design: FRLG AutoStory goal-driven Pokedex collection - #489
Conversation
|
Review of 7fa5530 against
Smaller points: map failures to the shared I am pushing a revision of the doc that fixes these and collects the user decisions in an "Open questions" section, then merging per the brief. |
… lookups, save mode; add open questions
Stacked on fork PR #435 (
frlg/design-2026-11-12). The diff contains only this new design document.Problem
FRLG AutoStory can run authored captures, routes, shops, field moves and checkpoint retries, but it cannot read the save's caught Pokédex state, choose an obtainable missing species and location, or repeat that process durably.
Design
Specify a goal-driven collection controller that scans the Pokédex, plans from a pinned acquisition catalog and the runtime maps, emits one ordinary AutoStory checkpoint per target, verifies the caught entry, returns to a known anchor, saves, and replans.
The document names the proposed readers, detectors, routines and code layout; separates a standalone pilot from later AutoStory continuation; records capture extensions and method-specific actions; and defines blocker reporting, retry semantics, tests and implementation slices. It also calls out existing pieces to reuse and current gaps such as ball selection, dynamic start-frame keys and the unwired opponent HP reader.
Validation
git diff --checkpasses.main; this change adds no C++.