docs: complete Wasp fullstack essentials integration

Complete all 4 action items from wasp-fullstack-essentials-eval.md resource
evaluation (score 3/5). Framework-agnostic insights only, promotional content
excluded.

Changes (3 sections):

1. Background tasks workflow (Section 9.5)
   - New subsection: "Background Tasks for Fullstack Development"
   - When to background tasks (5 scenarios table)
   - Fullstack workflow pattern with examples
   - Context rot prevention strategies
   - Limitations and workarounds
   - Integration with teleportation
   - /tasks monitoring guide
   - ~100 lines added to Section 9.5 "Tight Feedback Loops"

2. Chrome DevTools MCP (mcp-servers-ecosystem.md)
   - New server entry in "Browser Automation" section
   - Official Anthropic server (not community)
   - Comparison table vs Playwright MCP (debugging vs testing)
   - Setup and configuration
   - Use cases and limitations
   - Updated stats: 3 browser servers (was 2), 6 official servers (was 5)
   - ~60 lines added to Browser Automation section

3. Convention-over-config for AI (Section 9.18.1)
   - New subsection: "Convention-Over-Configuration for AI Agents"
   - Why opinionated frameworks reduce agent cognitive load
   - Comparison table: custom vs opinionated architectures
   - Examples: Next.js, Rails, Phoenix, Django
   - Real-world impact on agent productivity
   - Trade-offs analysis
   - Connection to CLAUDE.md sizing (token reduction)
   - ~60 lines added to Section 9.18.1

Total additions: ~220 lines (workflow patterns + MCP server + AX framework)

Source evaluation: docs/resource-evaluations/wasp-fullstack-essentials-eval.md
Primary sources: llmstxt.org (llms.txt), official docs (background tasks, Chrome
DevTools MCP), existing Section 9.18 (Marmelab/AX framework)

Related commits:
- 783c43b: llms.txt conceptual documentation (completed earlier)

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

docs/resource-evaluations/om-nalinde-30-concepts-infographic.md

@@ -0,0 +1,167 @@
+# Resource Evaluation: "30 Claude Code Concepts" - Om Nalinde (LinkedIn)
+
+**URL**: https://www.linkedin.com/posts/that-aum_if-youre-just-getting-started-with-claude-activity-7425498761629601792-nyO6
+**Date de publication**: 6 février 2026
+**Auteur**: Om Nalinde (LinkedIn)
+**Format**: Infographic visuelle (30 cartes, grid 5x6)
+**Engagement**: 731 likes, 61 commentaires
+**Date d'évaluation**: 9 février 2026
+
+---
+
+## Score: 2/5 (Marginal)
+
+**Justification**: Glossaire visuel de 30 concepts Claude Code sans profondeur technique. Le guide couvre déjà 22/30 concepts en détail. Aucune information nouvelle intégrable, aucun code, aucun workflow. Erreur factuelle sur "Slack Integration". Auteur non vérifié techniquement.
+
+---
+
+## Résumé du contenu
+
+- Infographic "cheat sheet" listant 30 concepts en 5 catégories:
+  - **Core** (6): Claude Code, CLI, CLAUDE.md, Context, Compaction, Checkpoints
+  - **Configuration** (6): Permissions, MCP, Tool Use, Commands, Plan Mode, Background Tasks
+  - **Extensibility** (6): Subagents, Hooks, Skills, Plugins, Agent SDK, Worktrees
+  - **Integration** (6): VS Code, JetBrains, GitHub Actions, Chrome, Slack, Headless
+  - **Features** (6): Inline Diffs, @Mentions, LSP, Model Selection, Ultrathink, Settings
+- Chaque concept = 1 titre + 1 description d'une ligne (~15 mots)
+- Post texte promet un guide "100 Pro Hacks" à venir
+- Format visuel attrayant, zéro code, zéro profondeur technique
+
+---
+
+## Comparatif avec le guide
+
+| Concept | Infographic | Guide actuel | Gap? |
+|---------|-------------|--------------|------|
+| **Core (6)** | 1 ligne/concept | Sections dédiées (centaines de lignes) | ❌ |
+| **Configuration (6)** | 1 ligne/concept | Sections dédiées + exemples | ❌ |
+| **Extensibility (6)** | 1 ligne/concept | Sections dédiées + templates | ❌ |
+| **Background Tasks** | 1 ligne | Références dispersées, pas de section | ✅ PARTIAL |
+| **Agent SDK** | 1 ligne | Mention Xcode uniquement | ✅ PARTIAL |
+| **VS Code/JetBrains** | 1 ligne chacun | 5-6 lignes chacun | ✅ PARTIAL |
+| **Chrome** | 1 ligne | 1 ligne | ❌ |
+| **Slack** | 1 ligne | ABSENT (mais info inexacte) | ⚠️ |
+| **Headless** | 1 ligne | Bien documenté | ❌ |
+| **LSP Support** | 1 ligne | BARELY mentionné | ✅ PARTIAL |
+| **@Mentions** | 1 ligne | Présent dans tables, pas de section | ✅ PARTIAL |
+| **Inline Diffs** | 1 ligne | BARELY mentionné | ✅ PARTIAL |
+| **Worktrees/Ultrathink/Settings** | 1 ligne chacun | Bien documentés | ❌ |
+
+**Couverture**: 22/30 concepts déjà bien documentés dans le guide.
+
+---
+
+## Fact-Check
+
+| Affirmation | Vérifiée? | Source |
+|-------------|-----------|--------|
+| "Claude in Chrome - Browser extension for live debugging" | ✅ | v2.0.72 Beta (claude-code-releases.yaml:313) |
+| "Slack Integration - Mention Claude in Slack for PRs" | ❌ **INEXACT** | MCP server Slack existe (v2.1.13) mais PAS de feature native "@claude dans Slack". L'infographic confond MCP server avec integration native type GitHub. |
+| "Agent SDK - Dev toolkit to build custom agents" | ✅ | Produit Anthropic séparé (TypeScript/Python), distinct de Claude Code |
+| "Plugins - Bundled packages you can install" | ✅ | Plugin system documenté (v2.1.x) |
+| "Background Tasks - Long-running processes" | ✅ | Feature existante (Ctrl+B, /tasks) |
+| "LSP Support - Go-to-definition, find references" | ✅ | Ajouté dans v2.0.74 (releases:328) |
+| "Inline Diffs - Visual side-by-side display" | ✅ | Feature IDE extensions |
+
+**Erreur factuelle**: "Slack Integration" tel que décrit n'existe pas dans Claude Code. Il existe un MCP server Slack (OAuth, channels), mais ce n'est PAS la même chose qu'une intégration native permettant de "@claude" dans Slack pour des PRs.
+
+---
+
+## Valeur ajoutée
+
+**Pour utilisateurs débutants**:
+- Format visuel attrayant comme point d'entrée
+- Liste des 30 concepts principaux en un coup d'œil
+- Peut servir de checklist "ai-je exploré ce concept?"
+
+**Pour le guide**:
+- ❌ Aucune information technique nouvelle
+- ❌ Aucun code, workflow, ou exemple intégrable
+- ❌ Profondeur nulle (1 ligne par concept)
+- ⚠️ Erreur factuelle sur Slack réduit la crédibilité
+
+**Gaps identifiés** (indépendants de cette ressource):
+
+L'analyse a révélé 8 concepts sous-couverts dans le guide:
+
+| # | Gap | Priorité | Justification |
+|---|-----|----------|---------------|
+| 1 | Background Tasks (section dédiée) | **Haute** | Feature officielle, références dispersées, aucune section dédiée |
+| 2 | IDE Extensions (VS Code + JetBrains) | **Haute** | 5-6 lignes chacun pour des surfaces d'intégration majeures |
+| 3 | LSP Support | **Moyenne** | Feature v2.0.74, pas de section dans le guide |
+| 4 | Agent SDK | **Moyenne** | Produit séparé, mérite clarification vs Claude Code |
+| 5 | @Mentions (@path) | **Moyenne** | Présent dans tables mais pas de section dédiée |
+| 6 | Claude in Chrome | **Moyenne** | Beta v2.0.72, 1 seule ligne dans le guide |
+| 7 | Inline Diffs | **Basse** | Feature UI implicite, pas critique |
+| 8 | GitHub @claude mentions | **Basse** | Feature distincte du CI/CD headless déjà documenté |
+
+**Note**: Ces gaps sont des **lacunes du guide à traiter séparément**, pas de la valeur apportée par cette infographic.
+
+---
+
+## Challenge technique
+
+**Points soulevés par technical-writer**:
+
+1. **Argument pour 1/5**:
+   - Contenu = repackaging de 30 termes sans profondeur
+   - Aucune valeur intégrable
+   - Erreur Slack réduit crédibilité
+   - Auteur non vérifié techniquement
+
+2. **Argument pour 3/5**:
+   - Aucun argument solide trouvé
+   - L'engagement (731 likes) ne valide pas la profondeur technique
+   - Pas de credentials vérifiées (contrairement à Wooldridge qui a été bumped 2→3)
+
+3. **Angle mort identifié**:
+   - L'engagement élevé signale une **demande pour du contenu entry-level/visuel**, pas une validation de qualité technique
+
+**Score ajusté**: 2/5 (inchangé)
+
+---
+
+## Crédibilité de l'auteur
+
+**Om Nalinde** (LinkedIn @that-aum):
+- ❌ Pas de credentials techniques vérifiables via Perplexity
+- ❌ Pas de contributions open-source identifiables
+- ❌ Pas d'expertise Claude Code démontrée
+- ✅ Engagement élevé sur LinkedIn (731 likes)
+- ⚠️ Promet un "100 Pro Hacks" guide à venir (non publié à ce jour)
+
+**Comparaison**:
+- Wooldridge (score 3/5): PhD + livre publié + credentials vérifiées
+- Om Nalinde (score 2/5): Engagement LinkedIn uniquement
+
+---
+
+## Décision finale
+
+**Action**: Ne pas intégrer
+
+**Raisons**:
+1. Aucune information technique nouvelle
+2. Couverture déjà existante pour 22/30 concepts
+3. Erreur factuelle sur Slack Integration
+4. Format glossaire non compatible avec la profondeur du guide
+5. Auteur non vérifié techniquement
+
+**Actions dérivées**:
+- ✅ Tracer les 8 gaps identifiés comme améliorations futures (indépendamment de cette ressource)
+- ✅ Considérer la création d'une infographic officielle basée sur le guide (format visuel demandé par la communauté)
+
+**Confiance**: Haute (contenu vérifié, challenge effectué, fact-check complet)
+
+---
+
+## Métadonnées
+
+- **Evaluateur**: Claude Sonnet 4.5 (via research + technical-writer challenge)
+- **Méthode**: Comparative analysis + fact-check (claude-code-releases.yaml) + challenge
+- **Sources**: LinkedIn post, claude-code-releases.yaml, Perplexity research
+- **Version du guide**: 3.9.9
+- **Fichiers consultés**:
+  - `machine-readable/claude-code-releases.yaml`
+  - `guide/ultimate-guide.md`
+  - `docs/resource-evaluations/README.md`

docs/resource-evaluations/weller-session-migration-skill.md

@@ -0,0 +1,209 @@
+# Resource Evaluation: claude-migrate-session Skill
+
+**Author**: Jim Weller (inspired by Alexis Laporte)
+**Type**: Community Skill
+**Date Evaluated**: 2026-02-09
+**Evaluator**: Claude Code Ultimate Guide Team
+**Score**: 3/5 (Pertinent - Complément utile)
+
+---
+
+## Executive Summary
+
+A bash skill that automates cross-folder session migration for Claude Code. Addresses a real gap (GitHub issue #1516) but has zero community adoption. Manual filesystem operations are safer and recommended over this automation tool.
+
+---
+
+## Source Information
+
+| Field | Value |
+|-------|-------|
+| **LinkedIn Post** | https://www.linkedin.com/posts/jwweller_claude-code-skill-that-clones-a-claude-session-activity-7426010179659309056-ZaUH |
+| **GitHub Repository** | https://github.com/jimweller/dotfiles/tree/main/dotfiles/claude-code/skills/claude-migrate-session |
+| **Publication Date** | February 2026 |
+| **Last Updated** | February 2026 |
+| **License** | Not specified (personal dotfiles) |
+| **Stars/Forks** | 0/0 (as of 2026-02-09) |
+| **Issues/PRs** | 0/0 |
+
+---
+
+## What It Does
+
+**Problem solved**: Native `--resume` command is limited to the current working directory. When you move a project or want to fork a session to a new folder, the session becomes inaccessible.
+
+**Solution provided**:
+1. **Global search**: Finds sessions across all projects with keyword filtering
+2. **Interactive selection**: Filters results, excludes current directory sessions
+3. **Automated migration**: Copies `.jsonl` + subagents directory, generates new UUID
+4. **Resume command**: Provides `claude --resume <new-id>` for immediate use
+
+**Technical implementation**:
+- Uses ripgrep for performance
+- Filtering support (`cleanupPeriodDays: 90` for large histories)
+- Bash scripts: `search.sh` + `migrate.sh`
+- Command syntax: `/claude-migrate-session <source> <target>`
+
+---
+
+## Evaluation Criteria
+
+### 1. Accuracy (4/5)
+
+**Strengths**:
+- ✅ Correctly identifies the architectural limitation (CWD-scoped sessions)
+- ✅ Preserves full context (`.jsonl` + subagents)
+- ✅ Generates independent copies (new UUID)
+
+**Weaknesses**:
+- ⚠️ No explicit handling of hardcoded paths in session context
+- ⚠️ No validation of MCP server compatibility
+- ⚠️ No warning about secrets in `.jsonl` files
+
+### 2. Relevance (3/5)
+
+**Confirmed gap**: GitHub issue #1516 documents community requests for cross-folder resume.
+
+**But**:
+- Niche use case (estimated 1-5% of users)
+- Alternative manual approach is trivial (`mv ~/.claude/projects/...`)
+- Zero adoption (0 stars/forks) suggests limited real-world demand
+
+### 3. Completeness (2/5)
+
+**Missing critical elements**:
+- ❌ No error handling examples
+- ❌ No edge case documentation (secrets, paths, MCP mismatches)
+- ❌ No testing strategy or test results
+- ❌ No security considerations
+- ❌ No rollback mechanism
+
+### 4. Quality (3/5)
+
+**Code quality**: Clean bash implementation, uses standard tools (ripgrep).
+
+**Documentation quality**:
+- ✅ Clear 4-step workflow explanation
+- ⚠️ Minimal usage examples
+- ❌ No troubleshooting guide
+- ❌ No comparison with manual approach
+
+### 5. Practicality (2/5)
+
+**Barriers to adoption**:
+- Requires installation from personal dotfiles (not a standard package)
+- No community validation (0 usage stats)
+- Manual approach is simpler and safer for most cases
+
+**When it makes sense**:
+- Frequent session forking workflows
+- Large session histories (ripgrep optimization beneficial)
+- Automation preference over manual control
+
+---
+
+## Comparative Analysis
+
+| Aspect | Weller Skill | Manual Approach | Claude Guide |
+|--------|--------------|-----------------|--------------|
+| **Cross-folder migration** | ✅ Automated | ✅ Manual (30 sec) | ❌ Not documented |
+| **Complexity** | ⚠️ Requires skill install | ✅ Zero dependencies | N/A |
+| **Safety** | ⚠️ Untested edge cases | ✅ Explicit control | N/A |
+| **Adoption** | ❌ 0 stars/forks | ✅ Native filesystem ops | N/A |
+| **Maintenance** | ⚠️ Personal repo | ✅ Self-maintained | N/A |
+
+---
+
+## Integration Decision
+
+**Integrated as**: Section addition in `guide/observability.md`
+
+**Rationale**:
+1. **Gap confirmed**: GitHub issue #1516 validates the problem
+2. **Manual approach prioritized**: Safer, simpler, zero dependencies
+3. **Community tool mentioned**: Attribution with honest caveats (0 adoption)
+4. **Risks documented**: Secrets, paths, MCP mismatches explicitly warned
+
+**Placement**: `guide/observability.md` § "Session Resume Limitations & Cross-Folder Migration" (40 lines)
+
+**Priority**: P2 (Important, not urgent) - integrate after critical guide updates
+
+---
+
+## Fact-Check Results
+
+| Claim | Verified | Source |
+|-------|----------|--------|
+| "Clones sessions cross-folder" | ✅ | SKILL.md + LinkedIn post |
+| "Inspired by Alexis Laporte" | ✅ | LinkedIn post attribution |
+| "Uses ripgrep for performance" | ✅ | LinkedIn post |
+| "cleanupPeriodDays: 90" | ✅ | LinkedIn post |
+| "14 likes, 3 comments" | ✅ | LinkedIn engagement metrics |
+| "GitHub issue #1516 exists" | ✅ | Perplexity search confirmed |
+| "0 stars/forks" | ✅ | GitHub repo metadata |
+| "Widely adopted" | ❌ | Contradicted by 0 stars/forks |
+
+---
+
+## Risks of Non-Integration
+
+**Low risk**:
+- 95%+ users won't need cross-folder migration (based on use case analysis)
+- Manual workaround exists and is well-documented in community discussions
+- No significant community pressure (minimal GitHub issue activity)
+
+**Opportunity cost of NOT integrating**:
+- Users facing this niche issue would discover manual solution via web search anyway
+- Guide completeness improved marginally (covers 1-5% more use cases)
+
+---
+
+## Technical Writer Challenge Results
+
+**Initial score**: 4/5
+**Challenged score**: 3/5 (adjusted down)
+
+**Key corrections**:
+- Adoption metrics (0 stars/forks) reduce score
+- Alternative manual approach is simpler → reduces uniqueness value
+- Edge cases and risks not addressed by skill → reduces quality score
+- Niche use case (1-5%) → reduces overall relevance
+
+**Integration recommendation refined**:
+- From: "200-300 line workflow + skill template"
+- To: "40-line section with manual approach + skill mention"
+
+---
+
+## Recommendations
+
+### For Guide Maintainers
+
+1. **Document manual approach first** (recommended solution)
+2. **Mention community skill** (attribution + honest caveats)
+3. **Warn about risks** (secrets, paths, MCP mismatches)
+4. **Link GitHub issue #1516** (feature request tracking)
+
+### For Users
+
+1. **Prefer manual approach** for safety and control
+2. **Test skill thoroughly** before production use (0 community validation)
+3. **Audit `.jsonl` files** for secrets before migration
+4. **Verify MCP compatibility** between source and target projects
+
+### For Skill Author (Jim Weller)
+
+1. **Add comprehensive testing** (edge cases, different project types)
+2. **Document security considerations** (secrets, credentials handling)
+3. **Provide rollback mechanism** (undo failed migrations)
+4. **Consider submitting to Claude Code official skills** for broader visibility
+
+---
+
+## Conclusion
+
+**Score: 3/5** - Addresses a real but niche gap with minimal adoption. Manual approach is safer and simpler for most users. Integration as lightweight documentation (40 lines) is appropriate given the use case frequency and lack of community validation.
+
+**Action**: Integrated in `guide/observability.md` with manual approach prioritized and community tool mentioned with caveats.
+
+**Confidence**: High (based on GitHub issue confirmation, Perplexity search validation, and repository inspection)