Competitor Changelog Strategy Read

Visit the changelog or release notes page of the competitor I give you. Read the last 6 months of dated entries, or the most recent 30 dated entries if that covers more history. State the actual date range and entry count; if dates or enough entries are unavailable, say so instead of claiming a trend.

Classify every entry into one primary bucket, or mark it MULTI with the two relevant buckets
when one release materially spans both:
- CORE: deepens the existing product for existing users
- EXPAND: opens a new use case, market, or user type
- ENTERPRISE: compliance, permissions, SSO, audit, admin controls
- CATCH-UP: something the rest of the category already had
- MAINTENANCE: fixes, performance, infrastructure

Then:
1. Show the bucket counts, and the trend: compare the first and second halves of the actual selected dated set. If the set is too small or dates are missing, say trend unavailable. A shift in mix is a signal to investigate, not proof of strategy.
2. Name the 2-3 entries that don't fit their current public positioning. Off-positioning releases are usually the first public evidence of a strategy change.
3. In three sentences, state where they're most likely headed over the next two quarters and which of my customer segments that puts at risk. Mark this as inference, not fact.

Start by asking me for the competitor's changelog URL, then wait for my reply before doing anything.