Epic: Admin Console and External Tool Compatibility Roadmap (v1.6.0)

[MPCoreDeveloper]

Summary

Deliver an administration and observability roadmap for SharpCoreDB that prioritizes compatibility with existing database tools and optionally adds a lightweight native admin experience.

This roadmap is based on current v1.6.0 behavior:

• tools/SharpCoreDB.Viewer exists but remains minimal.
• Server binary protocol is PostgreSQL-wire-compatible in foundation form.
• Existing docs/spec mention compatibility direction, but broad GUI tool certification and metadata completeness are not finalized.

Problem Statement

Users need practical development and operations tooling now:

• Browse databases/data reliably.
• Inspect indexes, constraints, relationships, triggers, and metadata.
• Run ad-hoc SQL with clear result UX.
• Access diagnostics and server metrics.

Building a full admin console from scratch is expensive; compatibility with mature tools (DBeaver, Beekeeper, DataGrip, pgAdmin) is likely the fastest value path.

Goals

1. Make external tool compatibility first-class and measurable.
2. Close metadata introspection gaps (pg_catalog/information_schema equivalents).
3. Improve query UX and diagnostics endpoints.
4. Evolve SharpCoreDB.Viewer into a stronger developer utility.
5. Optionally deliver a lightweight web admin for core operations.

Non-Goals

• Full SSMS/TDS emulation.
• Replacing all external database clients with a bespoke UI in one release.

Workstreams

• External tool compatibility matrix and CI smoke validation.
• Metadata compatibility expansion.
• Protocol/auth hardening for GUI ecosystems.
• SQL compatibility and error/reporting polish.
• Diagnostics and monitoring enhancements.
• Viewer modernization.
• Optional lightweight web admin track.
• ODBC/JDBC strategy and feasibility pack.

Milestones

• M1: Compatibility Baseline and Matrix
• M2: Metadata + Protocol Maturity
• M3: Diagnostics + Viewer UX
• M4: Optional Web Admin and Driver Strategy

Acceptance Criteria

• Documented support matrix with tested versions and known limitations.
• Significant metadata introspection improvements in common PostgreSQL clients.
• Stable diagnostics endpoints and actionable telemetry.
• Updated docs and onboarding guidance.

Definition of Done

• Epic checklist completed.
• All child issues closed with tests/docs.
• Release notes include compatibility status and migration guidance.
• Version labels/docs aligned to v1.6.0 policy.

[MPCoreDeveloper]

Tracking checklist for this epic:\n\n- [ ] #135 Tool compatibility matrix and certification for external clients\n- [ ] #136 Expand pg_catalog and information_schema compatibility for GUI introspection\n- [ ] #137 Binary protocol authentication and session hardening for client tools\n- [ ] #138 SQL compatibility and DDL introspection polish for admin tools\n- [ ] #139 Diagnostics and metrics surface upgrades for admin workflows\n- [ ] #140 Viewer v2 foundation: desktop browsing and query UX improvements\n- [ ] #141 Viewer diagnostics panel and lightweight admin actions\n- [ ] #142 Optional web admin MVP with Razor Pages\n- [ ] #143 ODBC/JDBC strategy and feasibility for broader tool ecosystem\n- [ ] #144 Documentation and adoption playbook for admin/tooling workflows\n- [ ] #145 CI smoke tests for external tool compatibility regression detection\n\nSuggested sequencing:\n- Foundation: #135 #136 #137 #138 #145\n- Observability + desktop tooling: #139 #140 #141\n- Optional expansion: #142 #143\n- Productization: #144