feat: adaptive onboarding architecture v2.0.0 (v3.23.0)

Major overhaul of onboarding system with adaptive topic selection based on
user context and keywords. Addresses 8 critical gaps identified by technical-
writer agent challenge.

Core Changes:
- Adaptive matrix: core topics (always) + adaptive topics (keyword-triggered)
- Security-first: moved sandbox_native_guide to beginner_5min (before commands)
- Time budget validation: all 18 profiles validated at 6-8 min/topic
- Quiz integration: positioned as exit activity in Phase 4 wrap-up
- New learn_security goal with 2 profiles (beginner_15min, advanced_60min)

Technical Improvements:
- Added onboarding_matrix_meta for version tracking and maintenance triggers
- Created validation script (validate-onboarding.sh) with 6 automated checks
- Created automation script (detect-new-onboarding-topics.sh) for monthly reviews
- Fixed 8 missing deep_dive keys (rules, workflow, fix, architecture, etc.)
- Removed duplicate deep_dive section causing validation failures

Documentation:
- README.md: version 3.23.0, harmonized counts (106 templates, 49 evaluations)
- CHANGELOG.md: comprehensive v3.23.0 entry with all changes
- Onboarding-prompt.md: updated Phase 1.5, 2, 4 with adaptive logic
- Reference.yaml: 180+ lines added for adaptive architecture

Validation:
- All 18 profiles pass time budget constraints (30-50% buffer maintained)
- All deep_dive keys verified (no missing references)
- Version synchronized across 6 files via sync-version.sh

Challenge: technical-writer agent identified 8 gaps in initial analysis
Result: Full adaptive approach implemented, all gaps addressed

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

docs/resource-evaluations/reddit-claude-code-max-plan-optimization.md

@@ -0,0 +1,140 @@
+# Resource Evaluation: Reddit Comment - Claude Code Max Plan Optimization Tips
+
+**Date**: 2026-02-04
+**Evaluator**: Claude (Sonnet 4.5)
+**Source**: https://www.reddit.com/r/ClaudeAI/comments/1qvdpby/comment/o3gysc7/
+**Type**: Reddit comment (r/ClaudeAI), anonymous user
+**Original post date**: ~November 2024 (thread context, but content mentions 2025+ features)
+
+---
+
+## Executive Summary
+
+**Score**: 2/5 (Marginal)
+**Decision**: Do not integrate
+**Confidence**: High (comprehensive fact-check completed)
+
+Anonymous Reddit comment claiming "5x plan has better value than 20x" with optimization tips. **Main claim appears false** based on public pricing ratios (20x offers 4x capacity for 2x price = better value). All valid content already covered extensively in guide. Memory-search tool mentioned has minimal traction (15 stars).
+
+---
+
+## Content Overview
+
+The comment provides six optimization tips:
+
+1. **5x vs 20x comparison**: Claims 5x has better value/dollar, 20x only offers faster bursts with similar weekly limits
+2. **Context management**: Keep sessions under 100k tokens, start fresh often
+3. **Disable unused MCPs**: Reduce overhead by disabling inactive MCP servers
+4. **Plan mode strategy**: More economical than trial-and-error direct implementation
+5. **Mobile SSH workflow**: SSH from phone to dev machine for small tasks
+6. **Memory/search layer**: Tool `rjyo/memory-search` (fork of OpenClaw memory module), installable via `bunx skills add rjyo/memory-search`
+
+---
+
+## Relevance Analysis
+
+### Coverage Comparison
+
+| Aspect | This Resource | Our Guide | Gap? |
+|--------|---------------|-----------|------|
+| 5x vs 20x comparison | Unverified claim ("similar weekly limits") | **Detailed** (ultimate-guide.md:1951-2013, comparative table, tier strategies) | ❌ No gap, our coverage superior |
+| Context < 100k tokens | Generic advice | **Extensive** (ultimate-guide.md:1358-1427, architecture.md:370, zones 0-50-70-90%) | ❌ No gap |
+| Disable unused MCPs | Mentioned in passing | **Partial** (ultimate-guide.md:1886 "Reduce MCP servers", 1740 "2K overhead/MCP") | ⚠️ Could be more visible |
+| Plan mode = cheaper | Assertion without data | **Documented** (ultimate-guide.md:2274 "76% fewer tokens") | ❌ No gap |
+| Mobile SSH | Generic advice | **Dedicated file** (tools/mobile-access.md, 386 lines) | ❌ No gap |
+| Memory-search (rjyo) | Tool presented | **Not covered** (but Serena + doobidoo cover use case) | ⚠️ Minor gap, tool too immature (15 stars) |
+| Rate limit strategies | Implied mention | **Partial** (known-issues.md:105-139, reactive troubleshooting) | ⚠️ Proactive budgeting angle missing |
+
+### New Information Assessment
+
+- **5x vs 20x pricing analysis**: Already covered extensively (ultimate-guide.md:1951-2013)
+- **Context management**: Already covered extensively (multiple sections, detailed zones)
+- **MCP optimization**: Mentioned but could be more prominent
+- **Plan mode economics**: Already documented with metrics (76% reduction)
+- **Mobile access**: Already covered with dedicated 386-line guide
+- **Memory-search tool**: New mention but tool too immature (15 stars, 15 commits)
+- **Proactive rate limit management**: Minor gap (session budgeting strategies)
+
+---
+
+## Fact-Check Results
+
+| Claim | Verified | Source | Notes |
+|-------|----------|--------|-------|
+| "5x has better value per dollar" | **❌ FALSE** | Perplexity: screenapp.io, glbgpt.com | 20x = 100x Free vs 5x = 25x Free. Ratio: 20x gives 4x capacity for 2x price = objectively better value |
+| "20x gives faster bursts but similar weekly limits" | **❌ DOUBTFUL** | No source found | Anthropic doesn't publish separate "weekly limits" beyond rolling 5h windows. No evidence supports this claim |
+| "Keep sessions under 100k tokens" | **⚠️ IMPRECISE** | Guide existing (architecture.md:370) | Guide mentions 80-100K as degradation zone. Real threshold ~200K total with auto-compact at 75-92%. Reasonable but imprecise advice |
+| "Disable MCPs you're not actively using" | **✅ VALID** | Guide existing (ultimate-guide.md:1740) | Each MCP adds ~2K token overhead |
+| "Plan mode cheaper than trial and error" | **✅ VALID** | Guide existing (ultimate-guide.md:2274) | Consistent with 76% fewer tokens documentation |
+| "SSH from phone to dev machine" | **✅ VALID** | tools/mobile-access.md | Valid practice, already documented |
+| "Memory module from OpenClaw" | **❌ VAGUE** | Perplexity: no confirmation | No verifiable link between OpenClaw (AI chatbot framework) and rjyo/memory-search. Author appears confused |
+| "rjyo/memory-search" | **✅ EXISTS** | WebFetch GitHub | 15 stars, hybrid vector+BM25, installable skill. Minimal traction |
+
+### Critical Corrections
+
+**Main claim is likely FALSE**: The assertion that "5x has better value per dollar than 20x" contradicts public pricing ratios:
+- 5x Plan: $100/month = 25x Free tier capacity
+- 20x Plan: $200/month = 100x Free tier capacity
+- **Ratio**: 20x offers 4x capacity for 2x price = objectively better value per dollar
+
+Author may be confusing personal usage patterns (not utilizing 20x capacity) with objective value proposition.
+
+---
+
+## Challenge (Self-Critique)
+
+### Arguments for Score +1 (3/5):
+- "Disable unused MCPs" advice deserves more visibility (currently a sub-bullet)
+- `rjyo/memory-search` mention could enrich third-party-tools.md as lightweight alternative to Serena/doobidoo
+- "Proactive rate limit management" (session budgeting) is a genuine gap in the guide
+
+### Arguments for Score -1 (1/5):
+- Main claim (5x > 20x value) is **provably false** - integrating would misinform readers
+- Zero measured data, zero methodology, pure anecdote
+- Memory-search tool has 15 stars and 15 commits - too immature to recommend
+- OpenClaw attribution unverifiable - author credibility questionable
+
+### Challenge Verdict
+
+**Score maintained at 2/5.** False pricing claim disqualifies direct integration. Few valid insights (disable MCPs, session budgeting) are already covered or too minor to justify formal evaluation.
+
+### Missed Points
+
+None significant.
+
+### Risk of Non-Integration
+
+**Negligible.** Guide already covers everything valid in this comment.
+
+Only real risk would be missing `rjyo/memory-search` if tool gains traction, but 15 stars don't justify action now.
+
+---
+
+## Final Decision
+
+**Score**: 2/5 (Marginal)
+**Action**: **Do not integrate**
+**Confidence**: High
+
+### Rejection Rationale
+
+1. **Main claim (5x > 20x value) is provably false** based on public pricing ratios
+2. **All valid content already extensively covered** in guide
+3. **Memory-search tool too immature** (15 stars) to recommend
+4. **Source lacks authority** (anonymous Reddit comment with unverified claims)
+
+### Optional Minor Actions (Non-Blocking)
+
+- **Optional**: Make "disable unused MCPs" advice more visible in context management section (currently sub-bullet at ultimate-guide.md:1886)
+- **Watch list**: Monitor `rjyo/memory-search` if traction increases (>100 stars)
+- **Optional**: Add "proactive rate limit management" subsection to guide (session budgeting strategies) - but requires real data, not Reddit anecdotes
+
+---
+
+## Metadata
+
+- **Evaluation duration**: ~45 minutes (including Perplexity research, GitHub verification, guide cross-referencing)
+- **External sources consulted**: 2 (Perplexity Pro for pricing verification, GitHub for tool verification)
+- **Guide sections cross-referenced**: 7 (pricing, context management, MCP optimization, plan mode, mobile access, third-party tools, troubleshooting)
+- **Fact-checks performed**: 8
+- **False claims identified**: 2 (pricing comparison, OpenClaw attribution)