Docs: correct MEMORY.md UTM-forwarding claim for Component B (feature not implemented)

[Salem874]

Problem

Project MEMORY.md (Phase 7) states UTM forwarding is implemented in Component B via g2ml_extractTrackingParams() / g2ml_appendUtmToDestination() in redirect_resolver.php, with logData click-IDs, dedicated tblActivityLog UTM columns, migration 009_add_utm_to_activity_log.sql, and sp_lookupShortURL returning stored UTM. A grep across web/G2My.Link (and the SQL tree) finds none of this: no such functions, no UTM extraction in index.php, no migration 009 (migrations stop at 008), no UTM columns in 030_analytics.sql, and no UTM params in sp_logActivity/sp_lookupShortURL. This is documentation/code drift — the audited "UTM forwarding" surface for Component B is empty. (Open issue #92 already tracks building the feature; this issue is specifically to fix the inaccurate memory/status note so the project board reflects reality.)

Affected files

• MEMORY.md (Phase 7 section)
• web/G2My.Link/_functions/redirect_resolver.php (functions claimed but absent)

Recommended fix

Correct MEMORY.md to state UTM forwarding is not yet implemented in Component B (tracked by #92), removing references to non-existent functions, columns, and migration 009. When the feature is built under #92, ensure user/destination-controlled UTM values are URL-encoded before being appended.

Acceptance criteria

• MEMORY.md no longer claims UTM forwarding is complete in Component B
• The note cross-references [Phase 7] Capture and store UTM parameters and tracking data on redirect #92 as the implementation issue
• No other docs assert the feature is shipped

---

Filed from the 2026-06-04 deployment-readiness audit — see docs/AUDIT_2026-06-04.md.