npm run sku:candidates
The priced rows the collector saw that the registry does not track.
npm run sku:candidates
npm run sku:candidates -- --allBy default it shows rows seen at least twice. --all includes rows seen once.
Why a second sighting
A row seen once may be a parse artefact of one malformed page. A row seen twice is something the provider is actually publishing.
Same discipline as the confirmation rule on price periods, applied to existence rather than to value.
The collector counts, a person decides
witness.sku_candidate carries a status, and the collector holds UPDATE on the counting columns only, not on the status.
So discovery is automatic and admission is not. A row becomes a sku by promotion, is linked to one registered by hand, or is ruled out.
