A quiet day: Continue's wind-down is the only real signal among three notes-light feeds

The lead

Only three products produced new commentary in the last 24 hours, all in AI assistants, so this is a quiet day and we won't stretch it. The one item with substance is Continue, whose feed shows a mid-June "final stable release" of its VS Code extension. That release removed the CLI-install banner and Generate Rule, and moved onboarding and new configs to explicit model definitions instead of Hub slugs.

The other two feeds say little. Their release records show cadence but not content, so what they add to the day is the absence of readable change.

What moved

• Spark: Continue is stripping Hub-dependent paths and pointing users at an export. The later 2.0.0 and 2.1.0 tags carry no notes, so they read as version housekeeping rather than a revival.
• Cadence without content: Goose has four automated GDK v0.1.0 alpha tags (alpha.10 to alpha.13) from late September to October 24, cut by a release bot with no notes. GDK looks to be under active development, but the feed doesn't show what it does for Goose users.
• Almost nothing: Tabby has one entry, a February 2026 internal-only "next-alpha" build with no feature notes, and nothing since.

Sectors today

• ai-assistants: three products updated, but only Continue shipped anything a user could act on, and that was a deprecation; Goose and Tabby add release tags without notes.

Watch tomorrow

The pattern in today's data is thin changelogs. For Goose, the next GDK alpha on the one-to-two-week rhythm is the likeliest entry, and a 0.1.0 final or an annotated Goose release would be the first readable signal. For Continue, the open question is whether any 2.x release arrives with notes. For Tabby, the first public, annotated release after the February alpha would be the first real signal.