Tools for repository-explorer

Looking up Godot engine API/behaviour while investigating the codebase

godot-docs retrieves the official engine documentation directly — godot_docs_search, godot_docs_get_class, godot_docs_get_page. Use it instead of recalling engine behaviour from memory, and instead of inferring an API's semantics from one call site in this repo. Grep/Glob/Read remain the default for anything about this project's own code.

The distinction that matters: "what does this project's code do" is a Grep/Read question, "what does this engine API actually guarantee" is a godot-docs question. A DirAccess walk that skips subdirectories, a Script.get_instance_base_type() that resolves the whole inheritance chain, a load() that returns an object rather than null for a broken script — each of those is an engine guarantee an investigation can get wrong by reading one usage and generalising.

Flagging what a boundary test does and doesn't cover

tests/unit/test_layer_boundaries.gd and tests/unit/test_battle_event.gd scan core/ for forbidden patterns. When investigating a change that adds files under core/, check what those scans actually reach — their coverage is a property of how they walk the directory, not of what they assert, and a gap there is invisible in a green suite.