---
name: hd-wiki-review
description: >
  After editing ANY wiki.adom.inc page (an adom-wiki push/publish, a README/doc/hero change),
  immediately LOAD that page in pup so the user can see and double-check the rendered result —
  don't just report the commit hash and move on. Covers how to open the page in pup on the
  user's machine, refresh it, and post a screenshot to the shotlog for review.
  Trigger words: wiki update, adom-wiki push, adom-wiki publish, wiki page, show wiki in pup,
  review wiki, verify wiki page, load wiki page, wiki hero, wiki readme, double-check wiki.
---

# Show every wiki edit in pup for review

Whenever you change a wiki.adom.inc page — `adom-wiki repo push`, `adom-wiki pkg publish`, or
any edit to a page's README / docs / hero — **open that page in pup right away** so the user
can eyeball the rendered result. A successful push is not proof the page looks right; the user
wants to verify it. Never stop at "pushed, commit abc123."

## Do this after every wiki change

```bash
# 1. Push / publish the page (the change itself).
adom-wiki repo push <slug> -m "…" --files README.md docs/foo.md
#    (or: adom-wiki pkg publish --org adom)

# 2. Immediately load the page in pup on the user's machine so they can review it.
adom-desktop browser_open_window '{"sessionId":"wiki-review","profile":"wiki-review","url":"https://wiki.adom.inc/<owner>/<slug>"}'
#    Already open from a prior review? Refresh + cache-bust instead of opening a duplicate:
#    adom-desktop browser_navigate '{"sessionId":"wiki-review","url":"https://wiki.adom.inc/<owner>/<slug>?cb=2"}'

# 3. Screenshot it and post to the shotlog with a one-line description, then hand the user the URL.
```

## Rules

- **Always the real `https://wiki.adom.inc/...` URL** — never a `localhost:<port>` (pup/webviews
  can't reach those).
- **Proactive, not offered** — load it without being asked; the whole point is the user reviews
  every wiki change as it happens.
- **Wiki ops go through the `adom-wiki` CLI**, not raw API calls.
- Keep related content on ONE page (e.g. all Hydrogen Desktop docs live on the `hydrogen-desktop`
  page) — don't spray a new wiki page per small doc.

## Why

The user runs the same setup as every Adom user and validates the shared experience by eye.
Loading each wiki edit in pup closes the loop: they confirm the page renders correctly (hero,
screenshots, links, formatting) instead of trusting a silent push.