📖About

The Carolopedia hero picture (the building-blocks arch, already the link-preview image at static/dl/carolopedia_hero.png) is not visible anywhere on the site itself. Show it as the hero/banner of the Carolopedia landing page. Must be served CSP-safe (the carolopedia subdomain only allows images from itself), responsive, and must not displace the existing Carol/Orion entry cards.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• UAT rework (Ninad): refresh landed mid-page. Root cause: the search box carried an autofocus attribute; the browser scrolls the focused field into view, invisible before the tall hero pushed it below the fold. Cure: attribute removed, focus applied on DOM-ready with preventScroll and a null guard (first attempt ran before the element existed and its error also killed the search-index loader — caught by verifying search, not just scroll). Verified: scrollY 0 on load+refresh, search focused, 25 hits for a test query, no console errors.
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• The landing page displays the building-blocks arch hero image at the top, on both the public subdomain and any internal route (must_have)
• The image loads without CSP violations (served from the same origin as the page) (must_have)
• Existing landing content (Carol/Orion cards, search, sections) remains intact below the hero (must_have)
• Page renders correctly on mobile widths (hero scales, no horizontal scroll) (must_have)