feat(neo4j): project analysis.json into a Neo4j property graph

[rahlk]

Summary

Ports the codeanalyzer-typescript v0.4.0 Neo4j feature to Python, keeping the same CLI arg entrypoints. One in-memory analysis can now be emitted three ways via --emit: the canonical analysis.json (default), a Neo4j property graph, or the version-stamped schema contract.

What's included

New codeanalyzer/neo4j/ package (mirrors src/build/neo4j/):

• catalog.py — declarative schema catalog (single source of truth), SCHEMA_VERSION = 1.0.0
• project.py — pure projection PyApplication → graph rows
• cypher.py — self-contained graph.cypher snapshot writer
• bolt.py — incremental live-push writer (lazy neo4j import; content-hash module diffing, vanished-decl cleanup, full-run orphan prune)
• rows.py / schema.py / emit.py

CLI — --emit {json,neo4j,schema}, --app-name, --neo4j-uri/-user/-password/-database. -i/--input is now optional for --emit schema. -f/--format msgpack retained on the json path.

Emit shapes

• --emit neo4j -o ./out → ./out/graph.cypher (no driver needed)
• --emit neo4j --neo4j-uri bolt://… → incremental Bolt push (needs the [neo4j] extra)
• --emit schema → schema.json (no project required; checked in as schema.neo4j.json)

Tests

• test/test_neo4j_schema.py — always-on anti-drift conformance guard (emitter never produces a label/rel/property the catalog doesn't declare; checked-in schema.neo4j.json stays current)
• test/test_neo4j_bolt.py — opt-in (RUN_CONTAINER_TESTS=1) Neo4j Testcontainers integration test: full push, idempotent re-push, vanished-module prune

Packaging / release / docs

• packaging/install/codeanalyzer-installer.sh — curl | sh installer (uv / pipx / pip)
• release.yml — syncs schema.neo4j.json from source, publishes schema.json + the installer as Release assets
• README consolidated (it was duplicated) with Neo4j docs; CHANGELOG 0.2.0; version bump 0.1.15 → 0.2.0
• schema-uml.drawio — UML of the PyApplication containment tree

Schema relationship to TypeScript

Same design DNA, intentionally a structural subset driven by the Python IR: shared :Symbol merge label, schema_version stamp, first-class CallSite/Variable/Attribute/Decorator nodes, _module provenance, identical DDL and incremental algorithm. Python has 10 node labels / 11 relationships vs TS's 14 / 14 (no interfaces/enums/type-aliases/namespaces, exports, or entrypoint markers — those aren't in the IR yet).

Verification

8/8 non-container tests pass (3 existing CLI + 5 schema). --emit schema and --emit neo4j exercised end-to-end (valid graph.cypher produced). The live bolt test runs wherever Docker/Podman is available.