**Difficulty:** L1 · **Labels:** `orbit::hackathon`, `orbit_hackathon::L1`, `orbit_hackathon::code-indexer`, `backend`, `type::maintenance` ## Outcome A fixture in `crates/integration-tests-codegraph/fixtures/kotlin/data_classes.yaml` asserts that the auto-generated `componentN()` and `copy()` functions on a `data class` are either extracted as definitions or correctly handled (i.e. the indexer doesn't crash on `val (a, b) = pair`). ## Background Kotlin data classes generate `component1()`, `component2()`, `copy()`, `equals()`, `hashCode()`, `toString()` implicitly. Destructuring syntax compiles to component calls. Current Kotlin grammar coverage may not see these — this fixture pins down the behaviour. > **Validated:** `grep -rn "data class" crates/integration-tests-codegraph/fixtures/kotlin/` returns nothing. There is no `data class` coverage today. `fixtures/kotlin/companion_object.yaml` exists but doesn't touch `data class`. ## Acceptance criteria - [ ] Fixture defines a `data class Pair(val a: Int, val b: Int)` and a function that destructures one (`val (a, b) = pair`) - [ ] Assertions document current behaviour (one of: components are extracted, components are not extracted but destructuring works, etc.) — document what the test discovers - [ ] Fixture registered in `tests/suites.rs`: `yaml_test!(kotlin_data_classes, "kotlin/data_classes.yaml");` - [ ] If a gap is found, file a follow-up issue