organic-os v0.6.0 - the loop speaks to a site's actual stage

Every detector this project ships assumes an established site. Striking distance looks for positions 4 to 15. Content decay needs 50 clicks in the older window. Anomaly alerts skip any metric whose median is under 10. Cannibalization needs two pages sharing a query with real volume.

A new site clears none of those bars. So the loop would run every day, find nothing that met a threshold, and report 'quiet day, nothing sent' - while sitting on genuinely readable data: indexed pages, live queries, positions climbing. Twelve days of that reads exactly like a broken product, and every site starts there.

Now the daily and weekly classify the site's stage from its own data and speak to it.

On an early-stage site they report which queries the site is visible for at all, the closest-to-breakthrough opportunities banded by position - top, page two, visible, distant - each with the lever that plausibly moves it, and an explicit line that zero clicks at those positions is expected rather than a fault. The dormant detectors are named alongside the threshold that wakes each one, so the silence is explained instead of mysterious. A note describes a lever, never a promised position change: the evidence discipline that applies to everyone else's claims applies here too.

Early sites get the channel summary weekly rather than daily, because a daily 'still climbing' is noise. They always get an alert the moment a query appears that the site was not visible for before, because on a new site that is the real progress signal.

Growing and established sites are unaffected. Their behaviour is unchanged.

464 tests, 9 audit checks, 8 gate probes, CI green.