Complete multitenancy phases 09-11 and update issue drafts

Author: MPCoreDeveloper

.github/issue-drafts/admin-console-v1.6.0/00-epic-admin-console-and-tool-compatibility.md

@@ -0,0 +1,55 @@
+## 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.

.github/issue-drafts/admin-console-v1.6.0/01-tool-compatibility-matrix-and-certification.md

@@ -0,0 +1,25 @@
+## Summary
+Create a formal compatibility matrix for external tools (DBeaver, Beekeeper Studio, DataGrip, pgAdmin, psql/libpq) with repeatable validation.
+
+## Why
+Adoption depends on transparent compatibility guarantees.
+
+## Scope
+- Define supported tool versions and drivers.
+- Record supported workflows: connect, browse DB/tables, run query, introspect metadata.
+- Capture known gaps and workarounds.
+- Publish matrix in `docs/server`.
+
+## Implementation Plan
+1. Define matrix template and pass/fail criteria.
+2. Build repeatable smoke scripts for key workflows.
+3. Execute validation against candidate tool versions.
+4. Publish results and known limitations.
+
+## Acceptance Criteria
+- Matrix published and linked from server docs/readme.
+- At least 4 mainstream tools validated.
+- Known limitations tracked as linked issues.
+
+## Dependencies
+- Foundation issue for this epic.

.github/issue-drafts/admin-console-v1.6.0/02-pg-catalog-and-information-schema-expansion.md

@@ -0,0 +1,24 @@
+## Summary
+Expand PostgreSQL metadata compatibility (`pg_catalog`, `information_schema`) to improve GUI introspection.
+
+## Why
+GUI tools rely on catalog views to discover tables, indexes, constraints, triggers, and relationships.
+
+## Scope
+- Implement/expand required catalog views and columns used by major clients.
+- Ensure object discovery works for indexes, PK/FK, constraints, triggers.
+- Improve metadata consistency for DDL round-trip scenarios.
+
+## Implementation Plan
+1. Trace metadata queries emitted by target tools.
+2. Prioritize missing views/columns by impact.
+3. Implement metadata mapping layer and tests.
+4. Validate with compatibility matrix scripts.
+
+## Acceptance Criteria
+- External tools can introspect core schema objects without major fallback failures.
+- Metadata query test suite added.
+- Documentation updated with supported catalog coverage.
+
+## Dependencies
+- Depends on compatibility matrix findings.

.github/issue-drafts/admin-console-v1.6.0/03-binary-protocol-auth-and-session-hardening.md

@@ -0,0 +1,24 @@
+## Summary
+Harden binary protocol authentication/session behavior for external GUI and driver expectations.
+
+## Why
+Current binary protocol startup/auth flow is functional but needs stronger parity and production behavior.
+
+## Scope
+- Align auth flow semantics with expected PostgreSQL client patterns where feasible.
+- Improve session context handling and version/status reporting.
+- Add robust error codes/messages for client troubleshooting.
+
+## Implementation Plan
+1. Audit startup/auth/session paths against protocol expectations.
+2. Add missing status parameters and negotiation behavior.
+3. Improve auth failure handling and observability.
+4. Add protocol integration tests for client libraries.
+
+## Acceptance Criteria
+- Stable connect/auth behavior for tested tools.
+- Improved deterministic error handling and logging.
+- Protocol tests cover key handshake scenarios.
+
+## Dependencies
+- Parallel to metadata expansion; feeds matrix certification.

.github/issue-drafts/admin-console-v1.6.0/04-sql-compatibility-and-ddl-introspection-polish.md

@@ -0,0 +1,24 @@
+## Summary
+Improve SQL compatibility and DDL/introspection behavior required by admin tools.
+
+## Why
+Many tools execute introspection SQL and DDL probes beyond regular CRUD workloads.
+
+## Scope
+- Identify unsupported or partially supported SQL patterns from tool traces.
+- Improve compatibility paths for common introspection statements.
+- Normalize command tags and result metadata where needed.
+
+## Implementation Plan
+1. Capture failing SQL traces from target tools.
+2. Group failures by parser, execution, metadata, or result-shape category.
+3. Implement incremental fixes with regression tests.
+4. Re-run tool compatibility scripts.
+
+## Acceptance Criteria
+- Reduced introspection/DDL failures in target tools.
+- Regression test set for known query patterns.
+- Release notes document improved compatibility.
+
+## Dependencies
+- Depends on matrix data and protocol hardening.

.github/issue-drafts/admin-console-v1.6.0/05-diagnostics-and-metrics-surface-upgrades.md

@@ -0,0 +1,24 @@
+## Summary
+Upgrade diagnostics surfaces for admin and monitoring workflows.
+
+## Why
+Developers and operators need reliable health and metrics insight without deep internals access.
+
+## Scope
+- Expand metrics coverage (connections, queries, latency, errors, protocol-level counters).
+- Improve health endpoints with richer status payloads.
+- Document Prometheus scraping and dashboards baseline.
+
+## Implementation Plan
+1. Define diagnostics KPI set for server/admin use.
+2. Extend metrics collector and endpoint payloads.
+3. Add tests for metrics/health contracts.
+4. Publish observability setup guide.
+
+## Acceptance Criteria
+- Metrics endpoints provide actionable server telemetry.
+- Health endpoint supports quick triage.
+- Docs include sample dashboard queries/panels.
+
+## Dependencies
+- Independent but supports all UI/tooling tracks.

.github/issue-drafts/admin-console-v1.6.0/06-viewer-v2-foundation-desktop-tooling.md

@@ -0,0 +1,25 @@
+## Summary
+Evolve `tools/SharpCoreDB.Viewer` into a stronger development companion (`Viewer v2` foundation).
+
+## Why
+A lightweight first-party desktop utility helps validate features and supports local workflows.
+
+## Scope
+- Improve database/table browser UX.
+- Add richer query editor and result grid capabilities.
+- Add metadata panes (indexes/constraints/triggers where available).
+- Add connection profile management improvements.
+
+## Implementation Plan
+1. Define MVP capabilities aligned to current server features.
+2. Refactor view-model/service layers for extensibility.
+3. Implement query/result and metadata exploration upgrades.
+4. Add user docs and basic smoke tests.
+
+## Acceptance Criteria
+- Viewer supports practical daily development tasks.
+- Metadata and query UX clearly improved over baseline.
+- Documentation includes usage and limitations.
+
+## Dependencies
+- Benefits from metadata/protocol improvements.

.github/issue-drafts/admin-console-v1.6.0/07-viewer-diagnostics-and-admin-actions.md

@@ -0,0 +1,24 @@
+## Summary
+Add diagnostics and lightweight admin actions to `SharpCoreDB.Viewer`.
+
+## Why
+Users requested direct access to runtime metrics and common operational actions.
+
+## Scope
+- Diagnostics panel (health, core metrics, active sessions summary).
+- Safe admin actions: refresh schema, session cleanup trigger, export diagnostics snapshot.
+- Audit-conscious UX for sensitive operations.
+
+## Implementation Plan
+1. Define diagnostics view contracts and data polling strategy.
+2. Implement non-destructive admin action commands.
+3. Add localization resources and error handling.
+4. Add tests/smoke verification for command flows.
+
+## Acceptance Criteria
+- Viewer exposes actionable diagnostics data.
+- Admin actions are guarded and logged.
+- UX remains responsive under load.
+
+## Dependencies
+- Depends on diagnostics endpoint upgrades.

.github/issue-drafts/admin-console-v1.6.0/08-optional-web-admin-razor-pages-mvp.md

@@ -0,0 +1,28 @@
+## Summary
+Investigate and deliver an optional lightweight web admin MVP using ASP.NET Core Razor Pages.
+
+## Why
+A browser-based console lowers operational friction without committing to a heavy full console rewrite.
+
+## Scope
+- Razor Pages MVP for:
+  - connection status/health
+  - database list and basic browsing
+  - ad-hoc query execution (guarded)
+  - basic metrics display
+- Strict auth and role checks.
+- Feature toggle and optional deployment mode.
+
+## Implementation Plan
+1. Define web admin boundaries and security model.
+2. Build Razor Pages host shell and auth integration.
+3. Add core pages for health/metrics/query/browse.
+4. Add docs and threat considerations.
+
+## Acceptance Criteria
+- MVP pages support core admin workflows.
+- Security defaults are strict and documented.
+- Feature is optional and does not break server core.
+
+## Dependencies
+- Depends on diagnostics and compatibility maturity.

.github/issue-drafts/admin-console-v1.6.0/09-odbc-jdbc-driver-strategy-feasibility.md

@@ -0,0 +1,25 @@
+## Summary
+Produce a concrete strategy for ODBC/JDBC enablement and external ecosystem integration.
+
+## Why
+Some teams require standard connectivity layers for governance and tool compatibility.
+
+## Scope
+- Evaluate direct driver development vs adapter approach.
+- Define phased roadmap (proof-of-concept to production support).
+- Identify protocol/metadata prerequisites.
+- Provide cost/benefit and maintenance analysis.
+
+## Implementation Plan
+1. Document architecture options and constraints.
+2. Prototype minimal path for one target driver path.
+3. Assess compatibility/performance/security impact.
+4. Publish recommendation and decision record.
+
+## Acceptance Criteria
+- Decision record with selected path and rationale.
+- Clear dependency map to protocol/catalog work.
+- Estimated implementation effort for next phases.
+
+## Dependencies
+- Informed by compatibility matrix and protocol maturity.