TCG Deck Doctor public beta is live.

Starter Deck 09 has been added to the card catalog, so its cards should now appear in search, card detail views, and deck building workflows.

The linked catalog data was refreshed alongside the card import, which means the ST09 cards are also available in the connected analysis and linkage surfaces instead of being present only as raw card records.

If you spot a card-data issue in the ST09 release, use the contact flow and include the card code so we can fix the source data quickly.

This release turns the site into a usable public beta instead of a collection of isolated tools. The main goal was to make the deck workflow feel coherent from first visit to saved workspace.

You can now move from card search into the deck workspace, generate decks with auto-build, inspect card details, and keep working inside a saved cloud-backed deck flow without losing the current editor state.

The beta is intentionally narrow. We are prioritizing stable deck creation, saved workspace behavior, and core analysis surfaces before broadening feature coverage.

Tournament match pages were expanded from a mostly static reference into a workflow entry point. Users can inspect lists visually, open card details in context, and bring decks into the editor for iteration.

The goal here was to reduce context switching. Match research is much more useful when it can immediately feed into workspace edits instead of stopping at read-only inspection.

A public beta needs basic product and trust surfaces, not just feature pages. This update added the site-level pages that explain what the product is, how to reach us, and what policies apply.

It also created the foundation for this updates feed so new releases can be announced in a consistent place instead of being scattered across the app.

The new landing page puts the value proposition, primary actions, and beta framing in front of users earlier. That reduces ambiguity for first-time visitors and shortens the path into the workspace.

This was also part of making the product feel more like a real beta launch and less like an internal tool with a public URL.

The analysis layer moved beyond a simple result blob into dedicated UI that helps users inspect card relationships and deck-level patterns.

This is still early-stage analysis work, but it establishes the direction for explainable recommendations and reference deck comparisons.

Feedback loops matter more during beta than polished growth flows. This update added a direct way for users to report bugs and product issues so we can tighten weak spots faster.

That input is especially useful for deck persistence issues, card-data edge cases, and confusing workflow transitions.