Provide supported Roassal 3 SQL visualizations and retire unsafe legacy entry points #22

Problem

LegacyUI still uses RTMondrian, RTArrowedLine, RTLegendBuilder and GTObjectPrinter. The legacy FK analyzer also calls removed referencedColumns. Current core correctly excludes these packages.

Found during the 2026-09-20 FAMIXNGSQL/Moose 13 compatibility audit.

Implementation scope

Provide current schema/table, foreign-key and routine-call visualizations in a supported optional package; migrate current relation access and clearly retire or isolate obsolete GT/Roassal2 entry points. Document capabilities and migration.

Implementation PR target: deem0n/FAMIXNGSQL, in the deem0n fork first. Keep this issue separate from the other v3.0.0 fixes. The PR must explain the previous failure, resulting behavior, compatibility implications, and actual validation.

Acceptance criteria and tests

Synthetic schemas/tables/columns, FK direction and deduplication, candidate routine calls, empty/disconnected graphs, no model mutation, UI-independent canvas construction and clean optional-group loading.

• Regression tests demonstrate the reported problem and pass with the fix.
• Relevant existing tests pass; validation environment and limitations are recorded in the PR.
• A separate implementation PR is linked here and reviewed.
• Integrated v3.0.0 acceptance is verified before this release blocker is closed.

Release

Part of the v3.0.0 milestone. An open PR is not a completed fix; release qualification is tracked separately.

Implementation

#31

Combined qualification: #32. The implementation is available for review; this issue remains open until its integrated release acceptance is verified.