fix: register Section in NODE_TABLES and NODE_SCHEMA_QUERIES

[abhigyanpatwari]

Summary

• Fixes CI failure from feat: add markdown file indexing (headings + cross-links) #399 — Section schema was defined but never registered, so the table was never created in the database
• Adds 'Section' to NODE_TABLES array
• Adds SECTION_SCHEMA to NODE_SCHEMA_QUERIES array
• Adds missing FROM File TO Section relation entry

Error was: Binder exception: Table Section does not exist

Test plan

• CI passes on all 3 platforms (ubuntu, macos, windows)

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
gitnexus	Ready	Preview, Comment	Mar 20, 2026 10:20pm

[github-actions]

CI Report

✅ All checks passed   a34669b

Pipeline

Stage	Status	Ubuntu	Windows	macOS
Typecheck	✅ success	—	—	—
Tests	✅ success	✅	✅	✅

Tests

Metric	Value
Total	3459
Passed	3439
Skipped	20
Files	998
Duration	1m 49s

✅ All 3439 tests passed across 998 files

20 test(s) skipped

• buildTypeEnv > known limitations (documented skip tests) > Ruby block parameter: users.each { |user| } — closure param inference, different feature
• Python match/case as-pattern type binding > resolves u.save() to User#save via match/case as-pattern binding
• Python match/case as-pattern type binding > does NOT resolve u.save() to Repo#save (negative disambiguation)
• Swift constructor-inferred type resolution > detects User and Repo classes, both with save methods
• Swift constructor-inferred type resolution > resolves user.save() to Models/User.swift via constructor-inferred type
• Swift constructor-inferred type resolution > resolves repo.save() to Models/Repo.swift via constructor-inferred type
• Swift constructor-inferred type resolution > emits exactly 2 save() CALLS edges (one per receiver type)
• Swift self resolution > detects User and Repo classes, each with a save function
• Swift self resolution > resolves self.save() inside User.process to User.save, not Repo.save
• Swift parent resolution > detects BaseModel and User classes plus Serializable protocol
• Swift parent resolution > emits EXTENDS edge: User → BaseModel
• Swift parent resolution > emits IMPLEMENTS edge: User → Serializable (protocol conformance)
• Swift cross-file User.init() inference > resolves user.save() via User.init(name:) inference
• Swift cross-file User.init() inference > resolves user.greet() via User.init(name:) inference
• Swift return type inference > detects User class and getUser function
• Swift return type inference > detects save function on User (Swift class methods are Function nodes)
• Swift return type inference > resolves user.save() to User#save via return type of getUser() -> User
• Swift return-type inference via function return type > resolves user.save() to User#save via return type of getUser()
• Swift return-type inference via function return type > user.save() does NOT resolve to Repo#save
• Swift return-type inference via function return type > resolves repo.save() to Repo#save via return type of getRepo()

Coverage

Metric	Coverage	Covered	Base (main)	Delta
Statements	68.14%	8703/12772	68.16%	＝
Branches	59.46%	5949/10004	59.66%	📉 -0.2%
Functions	70.27%	754/1073	70.13%	📈 +0.1%
Lines	70.46%	7779/11039	70.49%	＝

---

_{📋 Full run · Coverage from Ubuntu · Generated by CI}

[xkonjin]

Code Review: Registers Section as a first-class node type for Markdown indexing support.

What looks good:

• Complete coverage: NODE_TABLES, NODE_SCHEMA_QUERIES, getCopyQuery, insertNodeToLbug, batchInsertNodesToLbug, and the File-to-Section relationship edge are all wired up.
• Section schema fields (level, content, startLine/endLine, description) are well chosen for Markdown heading hierarchy.
• Test updates for count assertions are correct (27->28 nodes, 29->30 total schemas).
• Better error diagnostics in skills-e2e.test.ts (stdout/stderr in assertion messages) is a nice improvement.

Suggestions:

1. The comment in schema.test.ts still says '9 core + 18 multi-language = 27' but the count is now 28. The arithmetic comment should be updated to '9 core + 18 multi-language + 1 markdown = 28' for accuracy.
2. Section only has a relationship FROM File TO Section. Consider whether Section-to-Section edges would be useful for representing heading nesting (h1 -> h2 -> h3). This could be a follow-up.
3. No migration path mentioned. If existing indexed repos upgrade GitNexus, they will have the old 27-table schema. Will queries against Section fail gracefully, or does this require a re-analyze? Worth a note in the PR description.
4. The COPY query column ordering must exactly match the CSV output from the analyzer. Verify the markdown parser emits columns in the same order (id, name, filePath, startLine, endLine, level, content, description).