feat(dead-code): exclude framework entry points and overrides on JVM codebases - #1622

find_dead_code is close to unusable on an Android codebase: almost everything it reports is framework-invoked and therefore alive. This PR teaches the query the two ways JVM code gets called without any project function calling it.

The problem

Nothing in an Android app calls onCreate. The framework does. Same for onBindViewHolder, doWork, onReceive, and every override of a superclass or interface member — the call site is a supertype reference, which the graph does not resolve to the override.

On a real multi-module Android repo the report was dominated by these, which is the failure mode where a dead-code tool stops being read at all.

The change

Two AND NOT clauses, plus one exported constant.

Framework entry points, scoped to lang IN ['kotlin', 'java'] so every other language keeps the existing global behaviour:

AND NOT (
      func.lang IN ['kotlin', 'java']
      AND toLower(func.name) IN ['oncreate', 'onstart', ...]
    )

29 lifecycle names, lowercased on both sides. Scoping by language matters — onCreate is not special in Python, and a global list would silently change results for existing users.

Overrides, using the modifiers array this stack's first PR adds:

AND NOT (
      func.modifiers IS NOT NULL
      AND 'override' IN func.modifiers
    )

The IS NOT NULL guard is required, not defensive noise. In Cypher 'override' IN null evaluates to null, and a null predicate drops the row — so without the guard every function whose modifiers is unset (i.e. every function in every other language) would vanish from the report. I verified this behaviour directly rather than assuming it.

ANDROID_DECORATOR_PRESET — 22 annotation names to pass as exclude_decorated_with when analysing an Android project: @Composable, @Preview, @Test, @Inject, @Provides, @Dao, @TypeConverter and so on. Each means "something other than project code calls this". It's exported rather than hardcoded into the query because the choice is the caller's — a project that wants its unused @Test functions reported can simply not pass it. Matching is by substring, so the bare names match annotations carrying arguments.

Verification

pytest tests/unit -q → 12 failed, 1191 passed, 19 skipped.
Same 12 failures on unmodified origin/main (12 failed, 1176 passed, 19 skipped) — pre-existing and unrelated.

The new tests assert both directions: a lifecycle method and an override are excluded, and a genuinely uncalled ordinary function is still reported. A one-directional test here would pass trivially against a query that returns nothing at all.

Scope

code_finder.py +39, one new test file, two doc lines. No schema change.

Second of five. Requires the modifiers column from #1620 — the override clause is inert without it. Review only the last commit; the earlier one is that PR, carried along because GitHub can't host a stacked base across a fork boundary.