# Changelog of WeChat Article Comments Scraper — 公众号文章评论 + 回复抓取 (`opspilot.cc/wechat-article-comments-scraper`) Actor

- **URL**: https://apify.com/opspilot.cc/wechat-article-comments-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/opspilot.cc/wechat-article-comments-scraper.md

## Changelog

### 0.2.0 — 2026-09-24

- **Fix**: Added `defaultRunInput` to `.actor/actor.json` (Layer 3 of §226).
- Symptom: Apify Store auto-QA runs with empty input hit Layer 2 fallback (`rawUrl || DEFAULT_URL`) instead of running with the defaultRunInput the schema advertises.
- Fix: `defaultRunInput` mirrors schema defaults 1:1 (`url`, `mode`, `commentId`, `maxComments`, `maxReplies`, `raw`), so empty-input runs now execute the schema-declared defaults.
- README + CHANGELOG clean of upstream platform names (already true pre-fix; re-verified).

### 0.1.2 — 2026-09-16

- **Actor ID**: `ier1jWLNCkvLh8vpS` ([opspilot.cc/wechat-article-comments-scraper](https://console.apify.com/actors/ier1jWLNCkvLh8vpS))
- **Build ID**: `EEYOuHLmNigebSxfb` (0.1.2, SUCCEEDED)
- Production runs:
  - `Q91ktCikxLYWmj32V` (mode=comments, maxComments=3) — SUCCEEDED, fetchedCount=3, totalCount=28
  - `OhX8FM6cMyPllX7d2` (mode=with-replies, maxComments=10, maxReplies=3) — SUCCEEDED, 10 comments + 4 reply batches, maxReplies cap verified
- Two endpoints:
  - `POST /api/v1/wechat_mp/v2/fetch_article_comments` (page via base64 `buffer`)
  - `POST /api/v1/wechat_mp/v2/fetch_comment_replies` (page via int `next_offset`)
- Two modes:
  - `comments` (top-level only, cheapest)
  - `with-replies` (top-level + per-comment reply batches)
- Per-row output: `totalCount`, `electedTotal`, `fetchedCount`, `hasMore`, `continueFlag`, `commentsPages`, `comments[]` with `contentId` (string), `nickName`, `content`, `likeNum`, `createTime`, `ipRegion` (flattened from `ip_wording`), `ipIds`, `replyTotal`, `replies[]`.
- §98 coercion: all big-integer IDs (`contentId`, `replyId`, `commentId`, `appmsgId`) returned as strings.
- Free tier: 5 runs/day. Paid: 1 PPE event per upstream page (`article-comments-result`).
- 33 unit assertions + 9 integration scenarios pass.

### 0.1.1 — 2026-09-16 (build FAILED)

- Initial build attempted but `package-lock.json` was missing in the deploy context → Dockerfile `COPY` failed.
- Fixed in 0.1.2 by reinstalling deps.