--- name: live-inject-release-notes description: Release notes are now injected straight into the production releasenotes table as unapproved metadata: node_type: memory type: project originSessionId: a919958d-8286-4e1d-89cd-4ca33d65672e modified: 2026-07-21T07:51:08.044Z --- **Policy (from 2026-07-17):** release notes drafted in the repo are pushed **directly into the production `evolution.releasenotes` table as unapproved** (`status = 0`), rather than pasted into the *Support → Release Notes → Add* form. Extends [[feature_release_docs_policy]]. **Claude does this manually from the dev box via the mysql client** — NOT app code, no in-app live inject. Connection details: [[prod_mysql_access]] (creds stashed in the `sqlClaude*` .env trio for Claude to read). **How to insert (matching the Add-form handler `support_releasenotes.php`):** - Columns: `ticket_id, dev_id, feature_name, type, status, feature_description, module, support_doc_required, public, date_added`. - `status` = approve flag → **0 = unapproved** (what we want; shows an Approve button in the UI). - `public` column is written from `$notreleasenote`, but the two handlers in `support_releasenotes.php` set that var with **opposite logic for the same "Do not record release notes" checkbox**: the **add/save** path (`addreleasenote`, ~L15) does `ticked?1:0` (so `public=1` = do-NOT-record), while the **approve** path (`approvereleasenote`, ~L84) does `ticked?0:1` (so `public=1` = a real, shown note). Because customer-visible notes always go through *approve*, the operative meaning for anything with `status=1` is **`public=1` = show it** (data: of `status=1` release notes, 88 are `public=1` vs 7 `public=0`). So the `login2.inc` / customer filter `status=1 AND public=1` is **correct**, NOT an inverted bug (earlier note here was wrong). For a manual INSERT of a note you want shown, set `public=1`. **Fixed 2026-07-17:** the two handlers previously set `public` from `$notreleasenote` with *opposite* sign (add `?1:0`, approve `?0:1`) and the 3 edit-modal populate blocks (support_releasenotes.inc, support_ticketedit.inc ×2) ticked "Do not record" when `public==1` — all now consistent on the canonical meaning (renamed var `$isPublic = isset($_REQUEST['notreleasenote']) ? 0 : 1;` in both handlers; populate ticks only when `public==0`). Left as-is: 25 legacy `status=0` drafts hold pre-fix `public` values, so their approve-modal "Do not record" default is wrong until reviewed (Shane opted not to migrate); 7 approved notes at `public=0` remain hidden from the login splash. - `dev_id` = `$_SESSION['userid']`; use **304** (Shane; 55+ existing rows). - `type` = enum, normally `'Release Note'`. `ticket_id` = 0 when the draft names no ticket. - `module` is **varchar(15)** — keep it short (a single keyword like `Purchasing`/`Inventory`); longer values silently truncate. - `support_doc_required` tinyint: 1 when the draft says a new doc is needed ("Yes"), else 0. - `date_added` = `CURDATE()`. **Encoding gotcha:** the table is `CHARSET=latin1` but the app stores **raw UTF-8 bytes** in it (e.g. em-dash = `E2 80 94`) and serves pages as UTF-8. Insert with a **latin1 client connection** (`mysql --default-character-set=latin1`) so UTF-8 bytes pass through raw. A utf8mb4 connection would transcode and strip `— · → −`. Build the INSERT file programmatically (double `'`→`''`) to avoid escaping errors on apostrophe-heavy copy. **Cleaner alternative:** write copy with **HTML entities** (`— “ ·`) — pure ASCII, sidesteps the charset issue entirely and renders correctly (see HTML-embed note below). **HTML in release notes works** — `feature_description` is echoed **raw, unescaped** at every render point: `releasenotes_customers.inc` (Release Notes page), `login2.inc` (login splash, via `nl2br`), and the internal support tables. So `

/