Platform foundation: add Qlivik core WP plugin, DB schemas, admin API panel, health endpoints, and full‑stack starters - #1

Motivation

• Establish the Qlivik platform foundation by adding a WordPress plugin that provisions the core schema and runtime hooks.
• Provide a safe, DB-backed API key management surface so providers can be rotated without hardcoding keys.
• Ship a full‑stack starter mono-repo (API + three Vite React apps) and documentation to accelerate local development and future feature work.

Description

• Added QLIVIK_PLATFORM_PROMPT.md containing the platform identity, principles, product surface, and technical requirements as the master reference.
• Implemented a new WordPress plugin qlivik-core with bootstrap qlivik-core.php, activation routine QLVK_DB::activate that creates all qlvk_ tables via dbDelta(), and QLVK_PLUGIN_VERSION constants.
• Added QLVK_API which registers a public REST route GET /wp-json/qlivik/v1/health returning plugin version, table readiness, and status.
• Added QLVK_Admin that registers an admin menu and renders the DB-backed API Management Panel to save provider keys (openai, gemini, stripe, google_maps, google_calendar, calendly, twilio, brevo).
• Added QLVK_Plugin singleton to wire REST routes and admin menu, plus class-qlvk-* implementations.
• Included qlivik-core docs: README.md, TESTING.md, and PHASE-COMPLETE.md documenting install, health checks, and next steps.
• Added a full-stack starter under qlivik-platform with a Node/Express API (/api/health, /api/city-unlock, /api/recommendations/:businessId), a database/schema.sql baseline, and three Vite + React apps for business-dashboard, customer-platform, and super-admin with proxy configs for local development.
• Added top-level workspace package.json with dev scripts to run services and apps together and docs/roadmap for phased build-out.

Testing

• No automated CI test suite was executed as part of this change.
• A step-by-step local validation guide for the WordPress plugin is included at qlivik-core/TESTING.md and describes activation, schema verification, and curl checks against GET /wp-json/qlivik/v1/health.
• The Node API starter exposes sample endpoints documented in qlivik-platform/services/api/src/server.js for local smoke testing via npm --workspace @qlivik/api run dev, and the frontends are configured to proxy to http://localhost:4100 for interactive verification.
• Manual and local smoke tests are recommended following the instructions in qlivik-core/TESTING.md and qlivik-platform/README.md before proceeding to further integration or CI tests.

Codex Task