POST NEWS READERSHIP STATISTICS RESTORATION — V32

Root cause:
- The Post News API already returns view_count, unique_readers and views_today for published articles from slps_news_views.
- The Post News card renderer did not display any of those returned fields.
- The public news page did not load post-news-analytics.js, so newly opened public articles were not sending tracking events.

V32 changes:
1. Published article cards now display Opens, Unique readers, and Today.
2. The public news page loads the anonymous analytics tracker for a valid published article.
3. The existing visitor token is stored locally and hashed server-side; no names, emails or IP addresses are stored.
4. Cache versions are bumped for the Staff Post News JavaScript and CSS.
5. The API's campus_id insert from V31 is preserved; no change to the news ownership/migration logic.

Metric definitions:
- Opens = total accepted page-open events (one unique view token per page load).
- Unique readers = distinct browser visitor tokens, not verified human identities.
- Today = page-open events since UTC midnight.
- These are page-open analytics, not proof that a reader scrolled to or completed the entire article.

Installation:
1. Back up the application files and database.
2. Upload this cumulative V32 package preserving slps/ paths.
3. Keep the V31 campus_id migration already applied; do not re-add the column.
4. Ensure migration database/migrations/20261026_post_news_analytics.sql has been applied. It creates slps_news_views. If table already exists, do not recreate it.
5. Hard-refresh Staff Post News and open a published public article in a separate browser/incognito window.
6. Reload Post News library to see counters. Analytics events may take a short moment to appear.

Validation: local PHP/JS syntax and ZIP integrity checks. No production database/browser test.
