- Add the TypeScript contract for `known_incompatibilities` and render it
on the generated database docs pages (both top-level and within each
compatible-database entry), so the field added for the Aurora Data API /
D1 SQLAlchemy 2.0 warnings is actually visible instead of just reaching
the JSON unused.
- Teach the AST-based docs fallback extractor to resolve module-level
literal constants (e.g. AURORA_DATA_API_KNOWN_INCOMPATIBILITIES) so a
metadata dict that references a shared constant by name no longer
serializes as the bare identifier string when Flask context isn't
available.
- Correct the d1.py known_incompatibilities reason: sqlalchemy-d1's only
release (0.1.0) pins `sqlalchemy<2,>=1.4`, which explicitly excludes
SQLAlchemy 2.0 rather than merely lacking confirmation either way.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
