Consolidated 3.x-era → 4.8.x upgrade migration (for Client B et al.)

[kennethphough]

Consolidated 3.x-era → 4.8.x upgrade migration

A documented, idempotent reference path to bring a pre-4.1.0 ("3.x era") install up to the 4.8.x framework schema in one shot. Pre-4.1.0 schema changes were documented in the CHANGELOG (not .sql files); this consolidates everything from ~3.8.0 → 4.8.0 into a single file, built to the final 4.8.x shape (e.g. version tables are created already without the obfuscation columns, rather than create-then-drop).

First consumer: Client B (kyte-php 3.7.3, MariaDB). Diffed the full 4.8.1 framework set (53 tables) against their live schema (34 tables).

Contents (generated from a live v4.8.1 install's SHOW CREATE TABLE)

• 19 CREATE TABLE IF NOT EXISTS — the 6 versioning tables, 5 cron tables, 3 AI/Bedrock tables, KyteActivityLog, KyteRefreshToken, KyteMCPToken, KyteMCPSession, KyteLibraryAssignment.
• 15 ADD COLUMN IF NOT EXISTS — Application.auth_mode+language; sensitive ×4; KyteAccount.default_language; KyteUser.language; KyteScriptAssignment.global_scope; KyteError ×6.
• 12 DROP COLUMN IF EXISTS — the obfuscation columns (4.8.0).

Portability / safety decisions

• Charset/collation stripped so new tables/columns inherit the target DB's defaults — the source 4.8.1 install was MySQL 8.0, whose utf8mb4_0900_ai_ci collation MariaDB doesn't support, and this also avoids "illegal mix of collations" against the install's existing tables.
• Built for MariaDB — the column-level IF [NOT] EXISTS clauses are MariaDB extensions (MySQL 8.0 doesn't support them on ADD/DROP COLUMN). Noted in the header.

NOT covered here (deliberately) — see the upgrade plan

• config.php 4.x constants (JWT secret + TTLs, auth strategy dispatcher, etc.).
• Cron data-migration (old full-class cron jobs → function-based format) — N/A if the install never used cron (a freshly-created CronJob* set is empty).
• Shipyard 1.5.11 → 2.2.0 (separate major-jump).

⚠️ Process

This is a reference/rehearsal artifact, not a drop-in prod run. Rehearse on a clone of the target DB + a staging install, smoke-test, then apply to the real install.

🤖 Generated with Claude Code