Display and highlight SQL definitions in the standard Source Text browser #14

Problem

MiSourceTextBrowser accepts SQL source entities but chooses MiSourceTextNullAdapter and raises No source anchor adpater found. Definitions are stored in entities, not source files.

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

Implementation scope

Add optional MooseIDE integration for owner-backed SQL sources and reliable offset translation. Use plain text when ranges are absent. Keep UI dependencies outside Core.

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

Routine and view definitions; query fragments; missing/invalid anchors; correct highlight offsets; no mutation of original source; clean Core load without MooseIDE.

• 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

#27

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