Quick wins

# Rewrite the GitHub README top: category line, facts table, links to cheapseats.dev

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Cheap Seats vs Otterly.AI for a startup that wants to track AI visibility cheaply?
- How does Cheap Seats compare with Gauge for tracking and improving AI visibility?
- Cheap Seats or Semrush AI Toolkit for tracking our brand in ChatGPT and Claude?
- Is Cheap Seats a good open-source alternative to paid AI visibility tools?
- What are the downsides of self-hosting Cheap Seats to measure AI search visibility?
- Is Cheap Seats a good fit for a developer-tools company checking whether ChatGPT and Claude recommend it?

## What the assistant said
"unclear branding (Popcorn vs Cheap Seats)" (P6); "renamed recently" (P5)

## Your task
Write or update the page at https://github.com/cheapseatsdev/cheapseats/blob/main/README.md so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
The README is the only Cheap Seats page assistants find. It currently yields objections, not facts. Open with one line: 'Cheap Seats (formerly Popcorn) is an MIT-licensed, self-hosted AI visibility tracker: one Docker container plus SQLite.' Follow with a facts table: engines (Claude and OpenAI via API, or local Claude Code/Codex CLIs on your own subscriptions), the search and recall tracks, recommended/mentioned/absent grading with position, top pick, share of voice and objections, the ranked fix list, the daily budget cap, web UI/CLI/JSON API/MCP, and Docker/Helm/exe.dev deploy. Link each row to cheapseats.dev/docs and cheapseats.dev/compare.

## Done when
Re-run search answers for prompts 3–7 and 10 that cite the repo state the engines, the two tracks and the MIT license correctly, and no longer list 'unclear branding' or 'renamed recently'.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Cut a tagged v0.x GitHub release with changelog, versioned Docker image and Helm chart

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a product gap: a real capability gap that content can't paper over.

## The questions it affects
- Cheap Seats vs Otterly.AI for a startup that wants to track AI visibility cheaply?
- How does Cheap Seats compare with Gauge for tracking and improving AI visibility?
- Cheap Seats or Semrush AI Toolkit for tracking our brand in ChatGPT and Claude?
- Is Cheap Seats a good open-source alternative to paid AI visibility tools?
- What are the downsides of self-hosting Cheap Seats to measure AI search visibility?

## What the assistant said
"Very new: 0 GitHub stars, no releases" (P3)

## Your task
This is a product gap, not a content one: https://github.com/cheapseatsdev/cheapseats/releases. Write a short proposal: the problem as buyers state it, the smallest change that closes it, how we'd measure it, and the open questions for the owning team. If this repo has the relevant code, point to where the change would go.

## What it must say
Assistants that do read the repo cite '0 stars, no releases' as the reason to distrust it. Tag a v0.x GitHub Release with release notes and a CHANGELOG.md, and publish a versioned Docker image and Helm chart. This gives search answers a concrete maturity signal to quote.

## Done when
Re-run search answers for prompts 3–7 no longer contain 'no releases'.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.