E3 - Annotations, suite structure & module rework

[jgebal]

Target release or timeframe

No response

Scope and goals

Problem

Annotations are defined via PL/SQL object types (UDTs), which are harder to extend, search, and filter than a structured JSON format.
The current ut_suite object structure conflates structural dependencies with execution information.
Both currently live inside the monolithic framework rather than as reusable modules.

Proposed direction

• Rework annotations to use JSON instead of UDTs.
• Separate suite structural dependencies from execution information.
• Split annotations, cache, suites, expectations, shared utils, reporting into standalone, reusable modules - a direct prerequisite for E9 (cucumber-utPLSQL).

Breaking change

Yes — affects custom reporters/tools that introspect suite/annotation internals directly.

Tracking

• Rework annotations to use JSON instead of UDTs utPLSQL#1367
• Separate suite structural dependencies from execution information utPLSQL#1368
• Split into reusable, isolated modules utPLSQL#1369

Open questions for the community

No response