📖About

Follow-on to closed CAROL-INI-2685. Ninad asked on 2026-08-05 to move the AI readers crawler-fetch chart, 30-day total, and page drill-down out of human Stats into another tab. Keep all AI reader behavior intact while making Stats a human-readership-only surface. The parent is closed; this is new presentation scope, not remediation of the historical blocked attempt.

⚖️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)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> blocked | event=reviewer_verdict | bypass twin reviewer verdict != pass (CAROL-INI-2039) (orion)
• Bypass review failed — initiative blocked (exec 1291) — Standing attempt 1291 was auto-created after the 30-minute heartbeat expired during the 34-minute full regression and contains zero checks; the completed evidence is on exec 1290. Rework re-performs that evidence on the standing attempt. (shared.bypass.bypass_review_fail)
• [status-router] blocked -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [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

• Admin Monitor has a dedicated AI Readers tab containing the crawler-fetch chart, 30-day total, and page/day drill-down. (must_have)
• The Stats tab contains only human visitor charts and no AI Reader section. (must_have)
• Visits, Stats, and AI Readers tabs switch and load their own data without browser console errors on desktop and mobile. (must_have)