task_games__battleship__ship_cell_status_count

Contract

1. Domain: games
2. Scene id: battleship
3. Public task id: task_games__battleship__ship_cell_status_count
4. Supported query_id values: named_ship_hit_cell_count, named_ship_unhit_cell_count
5. Answer schema: integer_count
6. Annotation schema: bbox_set
7. Program schema: count(filter(cells(target_ship), cell_status=target_status)); scene=battleship; scope=ship_cell_status_count

Program Contract

Program: count(filter(cells(target_ship), cell_status=target_status)); scene=battleship; scope=ship_cell_status_count

Candidate set: the visible game board, pieces, tokens, cards, tiles, marked state, legal-move cues, result panels, and labeled options inside the ship_cell_status_count objective scope. Operands: visible scene state and prompt-bound operands named by filter, cells, target_ship, cell_status, target_status, battleship, ship_cell_status_count plus the active query_id branch. Operation: evaluate count over the candidate set using the visible game state, rules, legal moves, comparisons, counts, simulations, or option-selection constraints encoded in the program expression; generation enforces a unique final answer. Output binding: answer uses the integer schema; generation binds a unique final answer. Annotation witnesses: annotation uses the bbox_set schema; the prompt/annotation contract defines the minimal visual witnesses. Query ids: named_ship_hit_cell_count, named_ship_unhit_cell_count.

Reasoning Operations

Families: filtering, counting

Generation Notes

1. Query ids are internal replay/sampling keys and do not define public task units.
2. Target ships are sampled from the five active fleet shapes: Line 5, Line 4, Line 3, Square 2x2, and L 3.
3. Annotation is projected from the counted target-ship cell boxes used for answer verification.