docs: reconcile spec/plan + code comment with the kubernetes category

Second Copilot review flagged that the design spec, implementation plan, and
the DeployTarget.github comment still described the original 4-category model
(stars 'oss-paas only') after the kubernetes category was added.

- deploy-targets.ts: corrected the github-field comment to 'open-source
  platforms: oss-paas + kubernetes' (live code — must be accurate).
- spec + plan: added dated post-implementation amendment notes documenting the
  divergences (5 categories, stars on both oss-paas + kubernetes, Koyeb/Render
  deploy links) rather than rewriting the historical design record.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: cevheri

docs/superpowers/plans/2026-06-22-deploy-anywhere.md

@@ -2,6 +2,16 @@
 
 > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 
+> **Amendment (2026-06-22, post-implementation).** This plan describes the
+> original 4-category build. The shipped feature added a 5th category afterward;
+> where this plan and the code differ, the code is authoritative:
+> - `CategoryId` is `'registry' | 'oss-paas' | 'kubernetes' | 'managed-paas' | 'cloud'`
+>   (a `kubernetes` "Kubernetes & orchestration" category was added).
+> - GitHub star counts show on open-source platforms in **both** `oss-paas` and
+>   `kubernetes` (the global constraint "ONLY on `oss-paas`" is superseded);
+>   `starRepos` derives from both, and `FALLBACK_STARS` covers both.
+> - Koyeb/Render gained one-click `deployUrl`s (Render `planned → available`).
+
 **Goal:** Build a `/deploy` page plus a condensed homepage section that present LibreDB Studio's "one open-source image → every layer of the deploy stack" distribution story, with live GitHub star counts on open-source platform cards.
 
 **Architecture:** A typed data layer (`src/data/`) is the single source of truth for every platform/registry. A build-time helper (`src/lib/github-stars.ts`) fetches star counts (with a baked fallback) and a client script refreshes them live. Astro components (`PlatformCard`, `StatusBadge`) render the data on a full `/deploy` page and a condensed homepage `DeployAnywhere` section.

docs/superpowers/specs/2026-06-22-deploy-anywhere-design.md

@@ -4,6 +4,19 @@
 **Status:** Approved design, ready for implementation plan
 **Repo:** `libredb-website` (Astro 6, Tailwind v4, static output)
 
+> **Amendment (2026-06-22, post-implementation).** This spec captures the
+> original design. The shipped feature evolved during the PR; where the text
+> below says otherwise, the implementation is authoritative:
+> - **5 categories, not 4.** A `kubernetes` ("Kubernetes & orchestration")
+>   category was added between `oss-paas` and `managed-paas`. So `CategoryId` is
+>   `'registry' | 'oss-paas' | 'kubernetes' | 'managed-paas' | 'cloud'`, the stat
+>   strip reads "5 categories", and the classification grids span ①–⑤.
+> - **Stars show on all open-source platforms**, i.e. targets with a `github`
+>   repo in *either* `oss-paas` or `kubernetes` — not "OSS PaaS only". The
+>   aggregate sums those.
+> - Koyeb and Render gained one-click `deployUrl`s (Render moved `planned →
+>   available`); the Koyeb URL ships no default credentials.
+
 ## 1. Purpose & audience
 
 LibreDB Studio is now distributed as one-click apps / marketplace listings and as

src/data/deploy-targets.ts

@@ -11,7 +11,7 @@ export interface DeployTarget {
   logo?: string;       // '/logos/deploy/<slug>.svg' — omit for lettermark fallback
   deployUrl?: string;  // one-click deploy link
   docsUrl?: string;    // our deploy docs / repo instructions
-  github?: string;     // 'owner/repo' — live star count (oss-paas only)
+  github?: string;     // 'owner/repo' — live star count (open-source platforms: oss-paas + kubernetes)
   blurb?: string;      // one short line
 }