List the sections of the Tank Fight specification, with a one-line summary of each, so you can fetch only the part you need.

Start here when you don't yet know where a rule lives. Fetching the whole spec is rarely necessary and wastes context.

Return one section of the Tank Fight specification as JSON.

Use this to get the authoritative numbers and rules before implementing a feature — screen size, tank and bullet stats, wall layout, controls, AI parameters, and so on. Do not infer these values from an existing implementation and do not invent them; this file is what the implementations are supposed to agree with.

Args: section: A section name from list_sections, or a dotted path to go straight to a value, e.g. "entities.bullet" or "ai.enemy.turn_chance_per_tick".

Search the specification for the rule or value that answers a question.

Use this whenever you are about to assume how the game behaves — "do bullets stop at walls?", "can allies shoot each other?", "how fast is a bullet?", "what happens when a player is destroyed?". Searching costs far less context than loading whole sections, and the answer is authoritative.

If the search comes back empty, the spec may genuinely not cover it: check open_questions() before deciding anything yourself.

Args: query: Plain words describing what you need, e.g. "friendly fire" or "spawn interval" or "health bar colour".

Resolve what a level number actually means: how many enemy tanks the round fields in total, how many may be alive at once, and how often they arrive.

Levels are GENERATED from a ramp formula, not stored anywhere, so this cannot be answered by reading a file — call this tool instead of computing it yourself, because the formula truncates with integer division and a floating-point version disagrees at several levels.

The result also names the level's maze; call get_maze for its actual layout.

Args: level: The level number. Out-of-range values are clamped to the supported range rather than rejected.

Get a level's brick layout: the rectangles, and those rectangles expanded into the exact 20x20 tiles the level starts with.

Every level has its own maze, and all of the brick in it is destructible — bullets from either side chew through it, so the terrain changes as a round is played. Border walls are separate and indestructible.

Use the expanded tile list rather than expanding the rectangles yourself: that expansion is the step two implementations most easily get subtly different, and a one-tile disagreement changes which shots open a route.

Args: level: The level number. Out-of-range values are clamped. ascii_map: Include a picture of the layout — '#' border, 'B' brick, 'E' enemy entry point, 'A' ally start. Useful for checking a build renders the level you think it does; set false to save context.

List the design decisions the specification deliberately has NOT made.

Check this before inventing an answer to something the spec is silent on. If your question is here, the honest answer is "not decided yet" — say so and ask, rather than picking something and moving on. Anything on this list is a place where two implementations will otherwise diverge.