Best Practices
- 1If the sidebar is broken — run the parity gate first, restore from known-good SHA, never fresh-fix
- 2The 5-card system is locked: restore by git checkout, not by rewriting
- 3Reader signals drive card selection — always pass the latest launchd signal file
- 4Use --layout CLI to select the sidebar layout before assembling
- 5Sidebar parity gate must exit 0 before any publish
CLI Examples
# Daily assembly act as pearl_news — assemble today's Pearl News with --layout three-wide # Sidebar restore (if broken) python3 scripts/ci/check_pearl_news_sidebar_parity.py git checkout 8070e81fd -- artifacts/pearl_news/snapshots/CANONICAL_SIDEBAR.html # Process reader signals pearl_news: process reader signals from artifacts/pearl_news/reader_signals/launchd.stderr.log # Parity gate python3 scripts/ci/check_pearl_news_sidebar_parity.py --strict
Do Not Use For
- Fresh-fixing a broken sidebar — always restore from SHA first
- Publishing without the parity gate passing
- Changing the 5-card layout without operator approval — it is locked