You are auditing the Memento repo at `/Users/raghuveer/dev/memento` for drift between documentation and actual code/behavior. The user is preparing a "stale content cleanup" PR. You may be running alone or as one of several parallel agents covering different slices; cover only your slice.

## Your slice: skills + landing-page copy

Files to audit:

- `skills/README.md`
- `skills/memento/SKILL.md`
- `skills/memento-dev/SKILL.md`
- `packages/cli/skills/memento/SKILL.md` (a build-time copy of `skills/memento/SKILL.md`)
- `packages/cli/skills/memento-dev/SKILL.md` (a build-time copy of `skills/memento-dev/SKILL.md`)
- `packages/landing/src/App.tsx`
- `packages/landing/src/comparison.ts`
- `packages/landing/src/faq.ts`
- `packages/landing/src/howto.ts`
- `packages/cli/scripts/copy-skills.mjs` (so you understand which skill copy is canonical)

## Already verified for any audit run

- `skills/memento/SKILL.md` is byte-identical to `packages/cli/skills/memento/SKILL.md`. The copy is regenerated by `packages/cli/scripts/copy-skills.mjs` at every CLI build.
- `skills/memento-dev/SKILL.md` is byte-identical to `packages/cli/skills/memento-dev/SKILL.md`.
- `skills/memento-dev/SKILL.md` (and its CLI mirror) deliberately uses repo-root-relative paths — e.g. `[AGENTS.md](AGENTS.md)`, not `[AGENTS.md](../../AGENTS.md)` — because Claude Code reads the skill at runtime with the user's repo as cwd at skill-load time. The `<!-- doc-links: resolve-from-repo-root -->` marker near the top of the file declares this convention and the structural `pnpm docs:links` check honours it. Do **not** flag those links as broken — they're by design.

## What to look for, in priority order

1. **Skill-vs-code drift.** The skill files reference specific MCP tool names (`get_memory_context`, `search_memory`, `write_memory`, `confirm_memory`, `extract_memory`, `supersede_memory`, etc.). Verify each appears in `docs/reference/mcp-tools.md` (auto-generated, ground truth) or in the registry. If a skill references a tool that no longer exists or has been renamed, that is HIGH.

2. **Skill drift from current behavior.** The skills describe how to use Memento. Verify behavioral claims:
   - "Bulk destructive operations default to `dryRun: true` and require `confirm: true`" — true today?
   - "Conflict detection runs via post-write hook" — true today?
   - "Decay is computed at query time" — true today?
   - "Schema migrations are append-only" — true today?
   - The 14 architectural rules in `memento-dev/SKILL.md` — do they still match `AGENTS.md`?

3. **Landing copy claims.**
   - `faq.ts`: every concrete claim (Apache-2.0, five kinds, JSONL export, etc.) — verify.
   - `comparison.ts`: every Yes/No cell about Memento should match reality.
   - `App.tsx`: section copy should agree with README + actual behavior. Notice that `App.tsx` has a comment "Source of truth (do not drift): the 'A minimal end-to-end persona snippet' section in `docs/guides/teach-your-assistant.md`. Keep this verbatim with that file." Verify the `PERSONA_SNIPPET` constant in `App.tsx` matches the corresponding section in `docs/guides/teach-your-assistant.md` byte-for-byte.
   - `howto.ts`: HowTo step text should match the actual install flow.

4. **Internal / session notes.** TODOs, FIXMEs, "(rewrite)", scratch text.

5. **Dead cross-references.** Links to GitHub URLs, docs, guides — verify the targets exist. Note: links inside `skills/memento-dev/SKILL.md` are repo-root-relative by design, see the "Already verified" section above.

6. **Version / number claims.** "11 memories in engineering-simplicity" — verify against `packs/engineering-simplicity/v0.1.0.yaml` (or the current version file). Avoid version-number claims like "Bundled with v0.X"; the current version drifts under your feet.

7. **Hard-coded URLs.** `runmemento.com`, `github.com/veerps57/memento`, npm package URLs — verify these match the canonical project URLs in `package.json`.

## Verify against actual code

Use Read / Grep on source files. Don't speculate.

## How to report

Plain text, file by file. For each finding:

- File and line.
- Exact stale or wrong claim (quote the sentence or fragment).
- Correct version (or what to verify).
- Severity: HIGH / MEDIUM / LOW.

Aim for 1000–2000 words.
