feat: expand bounty task areas to include 道路 and 屋敷, with live testing confirming successful sweeps
This commit is contained in:
parent
d28ad2e3c7
commit
3d8af066fa
File diff suppressed because one or more lines are too long
@ -136,6 +136,17 @@ spend against either new area specifically (per explicit user direction --
|
|||||||
the existing sweep code path is unchanged and already live-verified against
|
the existing sweep code path is unchanged and already live-verified against
|
||||||
the original 3 areas, so this was treated as low-risk enough to skip a
|
the original 3 areas, so this was treated as low-risk enough to skip a
|
||||||
fresh live spend test).
|
fresh live spend test).
|
||||||
|
|
||||||
|
**Live-tested for real the same day**: `./ba_dailies.sh bounty` ran end-to-end
|
||||||
|
against 道路 (today's rotation pick, area 3) and completed cleanly --
|
||||||
|
`result: swept`. One cosmetic-only gap surfaced: the bottom-row stage-number
|
||||||
|
OCR read (`_open_latest_stage_modal`'s diagnostic log line, not on the
|
||||||
|
decision path -- selection is always the bottom-most row regardless of what
|
||||||
|
this reads) came back `None` here instead of a real digit string like it
|
||||||
|
does on the original 3 areas. Left as-is per explicit user direction, since
|
||||||
|
it doesn't affect the sweep itself; if `BOUNTY_STAGE_NUMBER_OCR_X`/
|
||||||
|
`_Y_PAD`'s crop ever needs to read cleanly on 道路/屋敷 too, recalibrate
|
||||||
|
against a fresh screenshot of either area's scrolled-to-bottom stage list.
|
||||||
"""
|
"""
|
||||||
import datetime
|
import datetime
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user