novahiz 0.1.0

package/bundled-skills/customer-research/references/source-guides.md

@@ -0,0 +1,401 @@
+# Customer Research — Source Guides
+
+Detailed, source-by-source playbooks for gathering customer intelligence from online watering holes.
+
+---
+
+## Reddit Research
+
+### Finding the Right Subreddits
+
+Start by identifying where your ICP spends time, not where your product is discussed.
+
+**Discovery methods:**
+- Search `site:reddit.com "[job title] tools"` or `site:reddit.com "[problem category] software"`
+- Use [subreddit search tools](https://www.reddit.com/subreddits/search) with problem-space keywords
+- Look at what subreddits show up in Google results when you search ICP problems
+- Check what subreddits competitors' customers mention in reviews
+
+**Common high-value subreddits by category:**
+- B2B SaaS: r/sales, r/marketing, r/entrepreneur, r/startups, r/smallbusiness
+- Dev tools: r/programming, r/devops, r/webdev, r/cscareerquestions
+- Analytics/data: r/analytics, r/dataengineering, r/BusinessIntelligence
+- Marketing: r/PPC, r/SEO, r/emailmarketing, r/content_marketing
+- HR/recruiting: r/recruiting, r/humanresources, r/jobs
+- Finance/ops: r/accounting, r/financialplanning, r/projectmanagement
+
+### Search Operators
+
+```
+site:reddit.com/r/[subreddit] "[keyword]"
+site:reddit.com "[problem]" "recommend" OR "suggestion" OR "alternative"
+site:reddit.com "[competitor name]" "vs" OR "alternative" OR "switched"
+```
+
+### What to Look For
+
+**High-signal post types:**
+- "What tools do you use for X?" → reveals alternatives and vocab
+- "Frustrated with [competitor], looking for alternatives" → reveals pain and switching triggers
+- "How do you handle X?" → reveals workflow and workarounds
+- "Is [your category] worth it?" → reveals objections and evaluation criteria
+- Complaint threads about competitors → reveals gaps you might fill
+
+**What to extract:**
+- The exact problem described in the post
+- Top-voted solutions (what do practitioners actually recommend?)
+- Complaints about existing solutions in comments
+- The language used — note specific words and phrases
+- Upvote patterns — consensus vs. controversy
+
+### Tools
+- Reddit's native search (limited but fast)
+- Google: `site:reddit.com [query]` (better results)
+- Pullpush.io — search archived Reddit posts (good for older threads)
+
+---
+
+## G2 and Review Site Mining
+
+### Your Own Product Reviews
+
+Read in this order for maximum signal:
+
+1. **3-star reviews** — these are the most honest. Customer liked it enough to stay but felt something was missing.
+2. **1-star reviews** — understand the failure modes. Separate product issues from support/onboarding issues.
+3. **5-star reviews** — extract the "what they love" language. These are your proof points.
+4. **4-star reviews** — often contain "the only thing I wish…" buried in praise.
+
+**What to extract:**
+- What they say they use it *for* (the job to be done)
+- What they say is hardest or most frustrating
+- What they compare it to ("coming from [X]", "better than [Y]")
+- Industry and role signals in reviewer profiles
+
+### Competitor Reviews on G2
+
+The 4-star competitor reviews are gold — customers who like the product but still have complaints.
+
+**G2 structure to exploit:**
+- "What do you like best?" → their strengths (your battlecard intel)
+- "What do you dislike?" → their weaknesses (your opportunities)
+- "What problems are you solving?" → the job to be done
+
+**Capterra** has similar structure. **Trustpilot** skews B2C. **AppSumo** reviews are useful for SMB/prosumer SaaS.
+
+### Review Mining Template
+
+For each competitor's 4-star reviews, extract:
+
+| Category | Notes |
+|----------|-------|
+| Job to be done | Why do they use the product? |
+| Top praise | What do they love (and might be hard for you to match)? |
+| Top complaint | What frustrates them? |
+| Switching context | Did they mention switching from something else? |
+| Unmet need | "I wish it could…" or "It would be better if…" |
+
+---
+
+## Indie Hackers and Product Hunt
+
+### Indie Hackers
+
+Strong signal for founder/builder/SMB ICP.
+
+**Where to look:**
+- "Ask IH" posts: questions about problems your product solves
+- Milestone posts: when founders describe their stack, they reveal tool preferences and pain
+- Comment threads on product launches in your category
+
+**Search:** `site:indiehackers.com "[problem]"` or use IH's native search.
+
+### Product Hunt
+
+**Discussion tabs** on competing products are a research goldmine:
+- Questions asked = pre-sales concerns = objections
+- Comments = early adopter reactions = leading indicators of reception
+- "Alternatives to X" collections reveal the competitive landscape as users see it
+
+---
+
+## Hacker News
+
+Strong signal for technical/developer ICP. Skews toward builders and skeptics.
+
+**High-value searches:**
+- `site:news.ycombinator.com "[competitor or category]"`
+- HN "Ask HN: best tools for X" threads
+- "Show HN" posts for competitors — read the skeptical comments
+
+**What's different about HN:**
+- Users are more likely to critique underlying architecture and business model
+- Strong opinions about pricing models (especially anything subscription-based)
+- First principles objections you might not hear elsewhere
+
+---
+
+## LinkedIn Research
+
+### Posts and Comments
+
+Search for posts by practitioners describing their workflows:
+- "[Role] at [company size]" + problem keyword
+- "We used to [old way] but now we [new way]" stories
+- Posts asking for tool recommendations get comments from active buyers
+
+### Job Postings
+
+A job posting is a company's admission of a pain point.
+
+**What to look for:**
+- What tools are listed as "nice to have" vs. "required"? (reveals stack and adjacent tools)
+- What metrics and outcomes are mentioned in the role description?
+- What does the role spend most of its time doing? (reveals the job to be done)
+
+**Search:** `site:linkedin.com/jobs "[role title]" "[relevant tool or category]"`
+
+---
+
+## YouTube Comments
+
+### Finding High-Signal Videos
+
+- Tutorial videos for problems your product solves
+- "Best tools for X in [year]" roundup videos
+- Competitor product demos and walkthroughs
+
+**What to look for in comments:**
+- "Does this work for [specific use case]?" → edge cases and unmet needs
+- "I tried this but…" → failure points
+- "What about [competitor]?" → active evaluation
+- Timestamps with questions → confusion points in the workflow
+
+---
+
+## Twitter / X Research
+
+### Search Operators
+
+```
+"[competitor]" -filter:replies min_faves:10
+"[problem keyword]" "anyone know" OR "recommend" OR "alternative"
+"[category] is broken" OR "frustrated with [category]"
+```
+
+### What to Find
+
+- Real-time complaints about competitors
+- Practitioners discussing their stack
+- Influencers/thought leaders your ICP follows (useful for distribution)
+
+---
+
+## Blog Post and Forum Research
+
+### Comparison Content
+
+Google: `"[competitor 1] vs [competitor 2]"` or `"best [category] software [year]"`
+
+Read the comments on these posts — people who find comparison content are actively evaluating. Their comments are questions your sales process should answer.
+
+### Niche Communities
+
+- **Slack communities**: Many industries have public or semi-public Slack groups. Search "[industry] Slack community".
+- **Discord servers**: Growing for developer and creator communities.
+- **Facebook Groups**: Still strong for SMB, e-commerce, agency, and coach/consultant ICP.
+- **Circle/Mighty Networks communities**: Check if there are paid communities in your ICP's space.
+
+---
+
+## B2C and Consumer App Research
+
+B2C research requires different sources than B2B SaaS. Consumer buyers don't congregate on LinkedIn or G2 — they leave traces in app stores, social media, and communities built around the activity your product serves.
+
+### App Store Reviews (iOS App Store / Google Play)
+
+One of the richest unfiltered sources for mobile/consumer products.
+
+**Read in this order:**
+1. **1-2 star reviews** — failure modes, unmet expectations, frustration peaks
+2. **3-star reviews** — honest tradeoffs and "it's good but…" feedback
+3. **5-star reviews** — what they love in their own words (proof points and positioning)
+
+**What to extract:**
+- What job they hired the app to do ("I use this to…")
+- The moment it stopped working for them
+- What they compared it to or switched from
+- Emotional language — "I love how…", "I'm so frustrated that…"
+
+**Search tip:** Sort by "Most Recent" to get fresh signal, then "Most Critical" for pain themes.
+
+### Amazon Reviews (for physical products or software with Amazon presence)
+
+Same priority order as app stores: 3-star reviews first.
+
+**G2 analog for consumer SaaS**: Trustpilot, Sitejabber, and product-specific review aggregators.
+
+### Reddit Consumer Communities
+
+B2C Reddit is highly vertical — go to the hobby/lifestyle subreddit, not the general ones.
+
+**Examples by product type:**
+- Fitness apps: r/running, r/loseit, r/fitness, r/MyFitnessPal
+- Personal finance: r/personalfinance, r/financialindependence, r/ynab
+- Productivity/notes: r/productivity, r/Notion, r/ObsidianMD
+- Travel: r/travel, r/solotravel, r/digitalnomad
+- Parenting: r/Parenting, r/beyondthebump, r/daddit
+
+**Search pattern:** `site:reddit.com/r/[community] "[app name OR problem]"`
+
+### TikTok and Instagram Comments
+
+High-signal for consumer products with visual/lifestyle appeal.
+
+**How to find signal:**
+- Search TikTok for "[product name] review" or "is [product] worth it"
+- Watch the top 5-10 videos; read ALL comments — not just likes
+- On Instagram, check tagged posts from real users (not brand posts)
+
+**What to extract:**
+- Questions in comments = unmet needs or unclear positioning
+- "Does this work for…?" = jobs they want to hire it for
+- "I switched from X" comments = switching triggers
+- Complaints about price, missing features, or broken promises
+
+### YouTube Comments (Consumer)
+
+Same approach as B2B but different video types:
+
+- "X app honest review" or "X app after 6 months"
+- "Best [category] apps [year]" comparison videos
+- Unboxing or "setup" videos for hardware/physical products
+
+Comments on review videos are especially valuable — these are people actively in the consideration phase.
+
+### Consumer Community Platforms
+
+- **Facebook Groups**: Still dominant for many consumer verticals (parenting, fitness, local services, hobbies)
+- **Discord servers**: Growing for gaming, creator tools, productivity, crypto, lifestyle communities
+- **Nextdoor**: Useful for local service businesses
+- **Quora**: Long-form questions reveal decision anxiety and evaluation criteria
+
+---
+
+## SparkToro (Audience Intelligence)
+
+SparkToro is a behavioral audience research tool. Instead of mining individual posts and comments, it aggregates clickstream, search, and social data to show what your audience does at scale — what they read, watch, listen to, follow, and search for.
+
+### When to Use SparkToro vs. Manual Research
+
+- **SparkToro first** when you need to understand where your ICP spends time, what content they consume, and which influencers they follow — it answers these questions in seconds with aggregated data
+- **Manual research first** (Reddit, G2, communities) when you need raw language, exact quotes, emotional context, and the "why" behind behavior
+- **Best together**: Use SparkToro to identify which podcasts, subreddits, and websites matter, then go mine those sources manually for voice-of-customer language
+
+### Key Queries to Run
+
+**By competitor:**
+- "People who follow @competitor" — reveals shared audience affinities
+- "People who visit competitor.com" — shows what else they consume
+
+**By audience description:**
+- "People who frequently talk about [topic]" — finds audience behaviors
+- "People whose bio contains [job title]" — profiles a role-based segment
+
+**By your own audience:**
+- "People who visit yourdomain.com" — understand your actual audience
+- Compare against competitor audience profiles to find gaps
+
+### What to Extract
+
+| Data Type | What It Tells You | Use It For |
+|-----------|------------------|------------|
+| Top websites visited | Where your audience reads | Content partnerships, guest posting targets |
+| Top podcasts | What they listen to | Podcast guesting, sponsorship decisions |
+| Top YouTube channels | What they watch | Video content strategy, ad placements |
+| Top subreddits | Where they discuss | Community participation, Reddit ad targeting |
+| Search keywords | What they Google | SEO and content topic planning |
+| AI prompt topics | What they ask AI tools | Emerging content opportunities |
+| Social accounts followed | Who influences them | Influencer partnerships, co-marketing |
+| Demographics | Who they are | Persona building, ad targeting |
+
+### Source Weighting
+
+SparkToro data is aggregated and anonymized — it shows patterns, not individual opinions. Treat it as:
+- **High confidence** for behavioral data (what they visit, follow, search for)
+- **Medium confidence** for demographic data (self-reported, may be incomplete)
+- **Not a substitute** for qualitative research (doesn't capture language, emotions, or the "why")
+
+### Limitations
+
+- Free tier: 5 reports/month, shallow results (top 5–10)
+- No public API — all research done through web interface
+- Skews English-language, US-centric
+- Shows what audiences do, not why — pair with qualitative sources
+
+See [tools/integrations/sparktoro.md](../../../tools/integrations/sparktoro.md) for full tool details and pricing.
+
+---
+
+## Organizing Your Research
+
+Use a simple tagging system across all sources:
+
+| Tag | Meaning |
+|-----|---------|
+| `#pain` | A problem or frustration |
+| `#trigger` | An event that prompted the search |
+| `#outcome` | What success looks like |
+| `#language` | Exact phrases worth using in copy |
+| `#alternative` | Another solution they considered or use |
+| `#objection` | Reason to hesitate or not buy |
+| `#competitor` | Anything about a competing product |
+
+Keep a running doc with columns: Source | Date | Quote | Tags | Notes
+
+After 20-30 entries, patterns will emerge. Look for quotes that appear in multiple unrelated sources — those are your highest-confidence insights.
+
+---
+
+## Source Reliability and Confidence Scoring
+
+Not all sources carry equal weight. Use this guide when assigning confidence labels.
+
+### Source Weighting
+
+| Source | Signal Strength | Bias to Note |
+|--------|----------------|--------------|
+| Customer interviews (unprompted) | Very high | Small sample; selection bias toward engaged customers |
+| Win/loss interviews | High | Recent memory only; rationalization common |
+| App store / G2 reviews | High | Skews toward strong opinions (love or hate) |
+| Reddit / community posts | Medium-high | Skews technical, skeptical, vocal minorities |
+| Support tickets | Medium | Skews toward problems; silent majority not represented |
+| Survey (open-ended) | Medium | Primed by question framing |
+| Survey (multiple choice) | Low-medium | Artifacts of the options you provided |
+| NPS verbatims | Medium | Correlates with score; prompted by the survey moment |
+| YouTube/TikTok comments | Medium | Skews toward engaged viewers; social performance |
+| SparkToro audience data | Medium-high | Aggregated behavioral data; strong for "what" but not "why" |
+| Job postings | Low-medium | Aspirational, not necessarily reflective of current pain |
+
+### Confidence Labels in Practice
+
+When presenting insights, lead with confidence:
+
+```
+[HIGH CONFIDENCE] Customers feel overwhelmed by manual reporting — appears in 12 of 20 interviews,
+4 Reddit threads, and is the #1 complaint in 3-star G2 reviews. Consistent across SMB and mid-market.
+
+[MEDIUM CONFIDENCE] Customers compare us to spreadsheets more than to direct competitors —
+mentioned in 6 interviews and 3 Reddit threads, but not yet seen in review data.
+
+[LOW CONFIDENCE] Enterprise buyers may have procurement concerns — mentioned by 2 interviewees
+from companies 500+. Needs more signal before acting on it.
+```
+
+### Recency Window
+
+- **Use as primary source**: Data from the last 12 months
+- **Use with caution**: 12-24 months (product and market may have shifted)
+- **Use only for baseline context**: 2+ years old
+
+When a theme appears consistently across old and new data, that's a durable signal worth acting on.

package/bundled-skills/daily-update/SKILL.md

@@ -0,0 +1,223 @@
+---
+name: daily-update
+description: >
+  Run the daily wiki maintenance cycle: check all source freshness, update the index, and regenerate hot.md.
+  Use this skill when the user says "/daily-update", "run the daily update", "update everything", "morning sync",
+  "refresh the wiki index", or when triggered by the launchd cron at 9 AM. Also use to set up or verify the
+  cron + terminal notification infrastructure for the first time ("set up the daily cron", "install the
+  terminal notification", "how do I get the morning reminder?").
+---
+
+# Daily Update — Wiki Maintenance Cycle
+
+You run a lightweight maintenance pass over the wiki: check source freshness, refresh the index, update hot.md, and write the state file that the terminal notification reads.
+
+## Before You Start
+
+1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (inline `@name` override → walk up CWD for `.env` → global config → prompt setup). This gives `OBSIDIAN_VAULT_PATH` and `OBSIDIAN_WIKI_REPO`.
+2. **Derive vault-scoped state dir** — all runtime state is scoped to the resolved vault, not global:
+   ```bash
+   VAULT_ID=$(echo "$OBSIDIAN_VAULT_PATH" | md5sum 2>/dev/null | cut -c1-8 || md5 -q - <<< "$OBSIDIAN_VAULT_PATH" | cut -c1-8)
+   STATE_DIR="$(obsidian_wiki_config_dir)/state/$VAULT_ID"
+   mkdir -p "$STATE_DIR"
+   ```
+3. Read `$OBSIDIAN_VAULT_PATH/.manifest.json`.
+
+## Modes
+
+### Run Mode (default — triggered by cron or `/daily-update`)
+
+Execute the maintenance cycle:
+
+**Step 1: Source freshness check**
+
+Compare each source in `.manifest.json` against its file's modification time. Classify as:
+- **Fresh** — `mtime ≤ ingested_at`
+- **Stale** — `mtime > ingested_at` (new content exists, not yet ingested)
+- **Missing** — source file no longer exists
+
+**Step 2: Index refresh**
+
+Read `$OBSIDIAN_VAULT_PATH/index.md`. If any pages in the vault are missing from the index (or vice versa), update the index. Use `find $OBSIDIAN_VAULT_PATH -name "*.md" -not -path "*/_*"` to enumerate vault pages, then reconcile against the index.
+
+**Step 3: hot.md update**
+
+Read `hot.md`. If it's >48h old based on its `updated:` frontmatter, regenerate it: read the 10 most recently modified wiki pages and write a fresh ~500-word semantic snapshot of what the wiki covers. This keeps the next session's context warm without a full vault crawl.
+
+**Step 4: Write state**
+
+Write to the vault-scoped `$STATE_DIR` derived in "Before You Start":
+
+```bash
+date +%s > "$STATE_DIR/.last_update"
+echo "<stale_count>" > "$STATE_DIR/.pending_delta"
+echo "$OBSIDIAN_VAULT_PATH" > "$STATE_DIR/.vault_path"
+```
+
+**Step 4a: Scheduled health check (wiki-lint)**
+
+`LINT_SCHEDULE` (default `weekly`) controls how often this cycle also runs `wiki-lint`:
+
+- `manual` — never auto-run; skip this step entirely.
+- `daily` — run `wiki-lint` every cycle.
+- `weekly` — run `wiki-lint` only if `$STATE_DIR/.last_lint` is missing or older than 7 days.
+
+```bash
+LINT_SCHEDULE="${LINT_SCHEDULE:-weekly}"
+NOW=$(date +%s)
+LAST_LINT=$(cat "$STATE_DIR/.last_lint" 2>/dev/null || echo 0)
+```
+
+If the schedule says to run, invoke the `wiki-lint` skill, then record the run:
+
+```bash
+date +%s > "$STATE_DIR/.last_lint"
+```
+
+Fold its summary (broken links, orphans, stale pages found) into Step 7's report as a `Health check:` line; omit the line entirely on a cycle where lint didn't run.
+
+**Step 5: Spawn impl-validator**
+
+After the cycle, spawn `impl-validator` as a subagent:
+
+```
+impl-validator check:
+  goal: "Daily wiki maintenance — index reconciled, hot.md refreshed, state file written"
+  artifacts:
+    - $OBSIDIAN_VAULT_PATH/index.md
+    - $OBSIDIAN_VAULT_PATH/hot.md
+    - $STATE_DIR/.last_update
+    - $STATE_DIR/.pending_delta
+  checks:
+    - Does .last_update contain a recent Unix timestamp (within the last 60 seconds)?
+    - Does .pending_delta contain a non-negative integer?
+    - Does hot.md have an updated: frontmatter field set to today?
+    - Does index.md list at least as many pages as exist in the vault?
+```
+
+Apply any FAILs before logging.
+
+**Step 6: Log**
+
+Append to `$OBSIDIAN_VAULT_PATH/log.md`:
+```
+- [TIMESTAMP] DAILY-UPDATE fresh=N stale=N missing=N index_added=N hot_refreshed=true|false lint=ran|skipped
+```
+
+**Step 7: Report to user**
+
+```
+## Daily Wiki Update
+
+- Sources: N fresh · N stale · N missing
+- Index: N pages (N added, N removed)
+- hot.md: refreshed / up to date
+- Health check: N broken links, N orphans, N stale pages (omit this line if lint didn't run this cycle)
+
+Stale sources (run to sync):
+  /wiki-history-ingest claude   — N sessions since last ingest
+  /wiki-history-ingest codex    — N sessions since last ingest
+```
+
+### Setup Mode (triggered by "set up the daily cron" or "install terminal notification")
+
+Walk the user through first-time setup:
+
+**Step 1: Verify script exists**
+
+Check that `$OBSIDIAN_WIKI_REPO/scripts/daily-update.sh` exists and is executable. If not, point the user to it.
+
+**Step 2: Install launchd plist**
+
+```bash
+# Replace placeholder in plist
+sed "s|OBSIDIAN_WIKI_REPO|$OBSIDIAN_WIKI_REPO|g" \
+  "$OBSIDIAN_WIKI_REPO/scripts/com.obsidian-wiki.daily-update.plist" \
+  > "$HOME/Library/LaunchAgents/com.obsidian-wiki.daily-update.plist"
+
+# Load it
+launchctl load "$HOME/Library/LaunchAgents/com.obsidian-wiki.daily-update.plist"
+```
+
+**Step 3: Install terminal notification (optional)**
+
+Ask the user: "Do you want a terminal reminder when your wiki is stale? (y/n)" — skip this step if they say no, or if the environment is headless/VPS.
+
+If yes, detect the user's shell and target the right rc file:
+
+```bash
+SHELL_NAME=$(basename "$SHELL")   # zsh, bash, fish, etc.
+case "$SHELL_NAME" in
+  zsh)  RC_FILE="$HOME/.zshrc" ;;
+  bash) RC_FILE="$HOME/.bashrc" ;;
+  *)    echo "Shell '$SHELL_NAME' not auto-detected. Add the source line manually to your shell rc file." ; return ;;
+esac
+```
+
+Check if `wiki-notify.sh` is already sourced in that rc file. If not, append:
+
+```bash
+echo "" >> "$RC_FILE"
+echo "# obsidian-wiki terminal notification" >> "$RC_FILE"
+echo "source $OBSIDIAN_WIKI_REPO/scripts/wiki-notify.sh" >> "$RC_FILE"
+```
+
+For Fish shell, source syntax is different — provide the manual instruction:
+```fish
+# Add to ~/.config/fish/config.fish:
+bass source $OBSIDIAN_WIKI_REPO/scripts/wiki-notify.sh
+# (requires bass plugin, or copy the logic natively)
+```
+
+**Step 4: Run the script once**
+
+```bash
+bash "$OBSIDIAN_WIKI_REPO/scripts/daily-update.sh"
+```
+
+This initializes `$STATE_DIR/.last_update` so the terminal notification works immediately.
+
+**Step 5: Confirm**
+
+Tell the user:
+- The cron runs daily at 9 AM (or on next login if missed)
+- `wiki-lint` health checks run on the `LINT_SCHEDULE` cadence (default `weekly`) as part of that cycle — set `LINT_SCHEDULE=daily` or `manual` in `.env` to change it
+- Terminal notifications appear when the wiki is >20 hours stale
+- State is stored in `<global config dir>/state/<vault-id>/` (XDG-style `~/.config/obsidian-wiki` by default, or the legacy `~/.obsidian-wiki` if that already exists) — supports multiple vaults independently
+- They can run `/daily-update` anytime to force a sync
+- Logs go to `/tmp/obsidian-wiki-daily.log`
+
+## QMD Refresh After Vault Writes
+
+QMD is a search index, not the source of truth. If `$QMD_WIKI_COLLECTION` is empty or unset, skip this step. Run it only after this skill has written or rewritten vault markdown. If QMD refresh fails, do not roll back the vault changes; report the QMD status separately.
+
+Use `$QMD_CLI` if set; otherwise use `qmd`.
+
+```bash
+${QMD_CLI:-qmd} update
+```
+
+If the output says vectors are needed or embeddings may be stale, run:
+
+```bash
+${QMD_CLI:-qmd} embed
+```
+
+Verify the collection with either:
+
+```bash
+${QMD_CLI:-qmd} ls "$QMD_WIKI_COLLECTION"
+```
+
+or, when a specific page path is known:
+
+```bash
+${QMD_CLI:-qmd} get "qmd://$QMD_WIKI_COLLECTION/<page>.md" -l 5
+```
+
+Record one of:
+- `QMD refreshed: update + embed + verified`
+- `QMD refreshed: update only + verified`
+- `QMD skipped: QMD_WIKI_COLLECTION unset`
+- `QMD skipped: qmd CLI unavailable`
+- `QMD failed: <short error summary>`