Indexing gap: backend

[MMatlacz]

Summary\n\nA macOS arm64 index of a Kotlin/PostgreSQL project reported a best-effort indexing gap in two backend SQL files. The files were indexed, but constructs in the flagged ranges may be missing from the graph.\n\n## Flagged backend ranges\n\n- backend/db/dev/roles.sql:2\n- backend/src/main/resources/db/migration/V1__create_users_table.sql:4\n\nThe ranges are 1-based. No files were skipped in this run; other partial files were outside the backend.\n\n## Constructs at those ranges\n\n1. The first range contains a PostgreSQL database-level privilege grant (granting all privileges on a database to a role).\n2. The second range contains a named inline primary-key constraint attached to an id column inside a CREATE TABLE definition.\n\nThese are standard PostgreSQL constructs. The coverage report provides line ranges rather than a parser diagnostic; surrounding syntax may be recovered, but graph constructs in these ranges may be absent.\n\n## Expected\n\nThe SQL grammar should parse these valid PostgreSQL constructs and retain their graph structure, or report a precise unsupported-syntax diagnostic.\n\n## Actual\n\nIndexing succeeds but records parse_partial for both backend ranges, making backend graph completeness uncertain.\n\n## Reproduction\n\n1. Index a project containing equivalent PostgreSQL role/grant SQL and a migration with a named inline primary-key constraint.\n2. Run index_status.\n3. Observe parse_partial on the corresponding lines.\n\nNo source snippet is included because the triggering checkout is private.