Reader 0.2 release repair and ready-backlog consolidation #275

Owner-requested delivery cleanup, 2026-10-18. #268 and #272 are now merged into master; #267/#271 closed. The remaining executable product issues are #269 and #273. #265 has separate missing administration/branch-deletion capabilities, not an analyzer blocker.

Delivery claim

Reuse the existing un-PR'd scrip-site-two-full-work-gallery branch at c411e29030e7e778f99cd9689441d348f75a7715 for one successor PR against current master. Preserve its three unique gallery files, adopt the existing Reader integration from #274 without reimplementation, fix the exact site_renderer.py syntax regression and verify the pending crash-safe publisher patch. Preserve the original histories and all current master changes. #270/#274 stay as provenance until the successor is accepted; do not start another competing integration.

Acceptance

• One runnable installable Reader with all existing 29 metrics, private bounded UTF-8 input, JSON/HTML/CSV and canonical five-route site.
• Full repository CI, clean installed-wheel smoke and deterministic site rebuild on the successor's exact head. Crash recovery/concurrent publication regressions; no weakened tests or publication allow-list.
• Reuse and verify the two-work source-free gallery; no new literary text or parity claim.
• Refresh the existing compact queue, reconcile delivery-oriented ownership into local instructions, and add the next key roadmap tasks with acceptance and scoped dependencies.
• No same-run merge of the repaired semantic change. No scheduler, access, visibility, administrative or external registry change.

M1-M5 completion remains unclaimed; M2 remains 0/5.