# Changelog of Apify Store Opportunity Radar: Gaps, Prices & Alerts (`clearfeedlabs/apify-store-market-intel`) Actor

- **URL**: https://apify.com/clearfeedlabs/apify-store-market-intel/changelog.md
- **Full Actor documentation**: https://apify.com/clearfeedlabs/apify-store-market-intel.md

## Changelog

### 0.2.x (2026-11-09)

- A Store total that changes mid-scan is retried once. If it changes again, the run ends successfully with one free `run-status` row: nothing is charged and history is not updated.
- An empty Store page after the first one (the public API stops at about offset 15,000) now ends the scan as an observed cohort with `truncationReason: store-offset-limit` instead of failing the run.
- The input form now pre-fills `maxPages: 5` for a quick first run. The default stays 30.
- If the shared history store name is not accessible under Apify's limited permissions, a clearfeedlabs-prefixed history store is used instead.

### 0.2

- Comparable prices are per 1,000 results only. Pages, minutes, reports, starts, and other units stay on their own unit price and are not ranked as overpriced against results.
- Missing Store stats stay null. They are not treated as zero.
- Partial, capped, inconsistent, and failed listings do not replace the weekly baseline and do not create dropped-from-listing alerts.
- The first complete snapshot in an ISO week is kept. History keys are isolated by Actor task.
- `modifiedAt` is fetched for the bounded leader set on every run. Build count is not used as a modified time.
- `snapshot`, `gap-report`, `alert`, and `deep-dive` are charged only after the matching artifact is stored. The platform start event is not charged again in code.
- Listing output reports observed Actors, API total, pages, and truncation. Fixed coverage and request-count claims were removed.
- Weekly history claims are a single request-queue `uniqueKey` insert. A second writer does not overwrite the snapshot. A claim without a stored snapshot fails the run instead of being reused.
- Transitive `basic-ftp` is pinned to 6.2.6 and `minimatch` to 11.0.5. `apify` stays 3.7.2.
- Weekly history keeps a verified-complete baseline only when every Store page has `count` equal to `items.length` and the offset windows cover `total`. Otherwise it stores a separate observed popularity cohort. Missing ids are `not-observed-this-scan`, not removals.