docs: LP-STUB markers + intent-based section detection + wrapper-aware hook analyzer

Users running --fix will see LP-STUB markers in their CLAUDE.md — now documented
so they know to replace the boilerplate (or run /lp-enhance) to clear the flag.
Also notes that intent detection accepts heading aliases / body keywords and
that the memory hook can delegate to a .sh wrapper.

Author: mboss37

docs/content/docs/doctor.mdx

@@ -56,6 +56,7 @@ claude-launchpad doctor
   </Accordion>
   <Accordion title="CLAUDE.md">
     - Missing sections: Stack, Commands, Architecture, Off-Limits, Session Start, Backlog, Stop-and-Swarm, Memory & Learnings
+    - Section detection is intent-based: a heading like `## Sprint Planning`, `## Workflow`, or `## Security Notes` satisfies the matching intent even without the canonical name. Doctor looks at heading aliases first, body keywords second.
     - Attribution migration (includeCoAuthoredBy → attribution object)
   </Accordion>
   <Accordion title="Files">
@@ -74,6 +75,10 @@ claude-launchpad doctor
   After `--fix`, use `/lp-enhance` inside Claude Code to restructure your CLAUDE.md. The fixer appends sections mechanically - the skill rewrites them into clean, project-specific content.
 </Callout>
 
+<Callout type="info">
+  **LP-STUB markers.** Sections injected by `--fix` are wrapped in `<!-- LP-STUB: ai-recommended -->` markers. Doctor treats a stub-wrapped section as unsatisfied, so the flag keeps showing until you replace the boilerplate with your own content (or delete the markers). Running `/lp-enhance` rewrites the section and removes the markers in one pass.
+</Callout>
+
 ## When to re-run
 
 Doctor isn't a one-time setup tool. It's a health check. Re-run it when:

docs/content/docs/memory.mdx

@@ -51,7 +51,7 @@ Running `claude-launchpad memory` without flags uses a smart default:
 ## What it installs
 
 - SQLite database at `~/.agentic-memory/` (shared across projects, scoped per project internally)
-- SessionStart hook that injects relevant memories at session start
+- SessionStart hook that injects relevant memories at session start. The hook command can delegate to a wrapper `.sh` script inside your project — doctor reads one level of wrapper body, so `bash .claude/session-start.sh` that internally runs `claude-launchpad memory context` passes the check.
 - SessionStart pull hook and SessionEnd push hook (when sync is configured) for automatic cross-device sync
 - 7 MCP tools for storing, searching, and managing memories
 - Memory guidance section in CLAUDE.md (or `.claude/CLAUDE.md` for local placement)