fix(ci): point sibling-checkout at Seungpyo1007/TechAPI and drop PokeAPI mentions

CI was failing on every workflow because the sibling-data checkout pointed at
GetTechAPI/TechAPI, which does not exist — the dataset repo lives at
Seungpyo1007/TechAPI. Bulk-rename across the four workflows (test, refresh-data,
deploy-pages, coverage-report, validate-data), pyproject Data URL, the README,
and the site landing page.

Also strips the now-decided-against PokeAPI inspiration references from
README, app/dump.py docstring, app/main.py API description, refresh-data
header comment, DATA_PIPELINE / DEVELOPMENT / SPEC docs.

Author: Seungpyo1007

.github/workflows/coverage-report.yml

@@ -19,7 +19,7 @@ jobs:
 
       - uses: actions/checkout@v4
         with:
-          repository: GetTechAPI/TechAPI
+          repository: Seungpyo1007/TechAPI
           path: TechAPI
 
       - uses: actions/setup-python@v5
@@ -47,7 +47,7 @@ jobs:
       - name: Sync sticky coverage issue
         env:
           GH_TOKEN: ${{ secrets.TECHAPI_PR_TOKEN || secrets.GITHUB_TOKEN }}
-          TARGET_REPO: ${{ secrets.TECHAPI_PR_TOKEN && 'GetTechAPI/TechAPI' || github.repository }}
+          TARGET_REPO: ${{ secrets.TECHAPI_PR_TOKEN && 'Seungpyo1007/TechAPI' || github.repository }}
         run: |
           set -euo pipefail
           TITLE="Coverage gaps (auto-generated)"

.github/workflows/deploy-pages.yml

@@ -26,7 +26,7 @@ jobs:
 
       - uses: actions/checkout@v4
         with:
-          repository: GetTechAPI/TechAPI
+          repository: Seungpyo1007/TechAPI
           path: TechAPI
 
       - uses: actions/setup-python@v5

.github/workflows/refresh-data.yml

@@ -1,6 +1,6 @@
 name: refresh-data
 
-# Static-dump refresh (PokeAPI api-data style + git-scraping pattern).
+# Static-dump refresh (git-scraping pattern).
 # Pulls the latest TechAPI data, validates, regenerates dump/.
 # - weekly schedule keeps the static dump fresh
 # - manual trigger for on-demand rebuilds
@@ -24,7 +24,7 @@ jobs:
 
       - uses: actions/checkout@v4
         with:
-          repository: GetTechAPI/TechAPI
+          repository: Seungpyo1007/TechAPI
           path: TechAPI
 
       - uses: actions/setup-python@v5

.github/workflows/test.yml

@@ -13,7 +13,7 @@ jobs:
 
       - uses: actions/checkout@v4
         with:
-          repository: GetTechAPI/TechAPI
+          repository: Seungpyo1007/TechAPI
           path: TechAPI
 
       - uses: actions/setup-python@v5

.github/workflows/validate-data.yml

@@ -24,7 +24,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/checkout@v4
         with:
-          repository: GetTechAPI/TechAPI
+          repository: Seungpyo1007/TechAPI
           ref: ${{ inputs.data-ref }}
           path: TechAPI
       - uses: actions/setup-python@v5

README.md

@@ -1,16 +1,16 @@
 # TechEngine
 
-> **Validation, ingestion, and serving engine for the [TechAPI](https://github.com/GetTechAPI/TechAPI) dataset.**
+> **Validation, ingestion, and serving engine for the [TechAPI](https://github.com/Seungpyo1007/TechAPI) dataset.**
 
 [![test](https://github.com/GetTechAPI/TechEngine/actions/workflows/test.yml/badge.svg)](https://github.com/GetTechAPI/TechEngine/actions/workflows/test.yml)
- Code: **MIT** · Data: lives in **[TechAPI](https://github.com/GetTechAPI/TechAPI)** (CC-BY-SA 4.0)
+ Code: **MIT** · Data: lives in **[TechAPI](https://github.com/Seungpyo1007/TechAPI)** (CC-BY-SA 4.0)
 
 TechEngine owns everything *around* the data: schema validation, the FastAPI
-read API, the PokeAPI-style static JSON dump, the engine's own landing site,
-and (next up) automated coverage checks and a weekly ingestion crawler.
+read API, the static JSON dump generator, the engine's own landing site, and
+(next up) automated coverage checks and a weekly ingestion crawler.
 
 The dataset and the public-facing playground site live in
-[TechAPI](https://github.com/GetTechAPI/TechAPI) so each can be versioned,
+[TechAPI](https://github.com/Seungpyo1007/TechAPI) so each can be versioned,
 mirrored, and licensed independently. The site shipped in this repo is the
 engine's own landing — what TechEngine is, what it runs, link out to docs.
 
@@ -20,7 +20,7 @@ engine's own landing — what TechEngine is, what it runs, link out to docs.
 app/
   ├ validate.py        # schema/range/uniqueness checks
   ├ seed.py            # data/ → SQLModel database
-  ├ dump.py            # API → static JSON tree (PokeAPI-style)
+  ├ dump.py            # API → static JSON tree
   ├ main.py            # FastAPI entrypoint
   ├ models/            # SQLModel tables
   ├ routers/           # /v1/{brands,socs,smartphones,gpus,cpus}
@@ -53,7 +53,7 @@ location can be overridden via `TECHAPI_DATA_DIR`; the default looks for
 ## Quickstart
 
 ```bash
-git clone https://github.com/GetTechAPI/TechAPI.git ../TechAPI   # data source
+git clone https://github.com/Seungpyo1007/TechAPI.git ../TechAPI   # data source
 pip install -e ".[dev]"
 python -m app.validate          # check data integrity
 python -m app.seed              # data/ → ./techapi.db (SQLite)

app/dump.py

@@ -1,8 +1,8 @@
 """Generate a static JSON dump from the database (§4.2 data flow, §16.1 dump-data.yml).
 
-PokeAPI-style: the live API responses are written to a tree of static files so a
-client can fetch ``dump/v1/smartphones/galaxy-s25/index.json`` without any server.
-Because the dump is produced by replaying the real endpoints through an in-process
+The live API responses are written to a tree of static files so a client can
+fetch ``dump/v1/smartphones/galaxy-s25/index.json`` without any server. Because
+the dump is produced by replaying the real endpoints through an in-process
 client, the static files byte-match the live API — zero serialization drift.
 
 Run with: ``python -m app.dump`` (writes to ``./dump`` by default).

app/main.py

@@ -20,7 +20,7 @@
 
 DESCRIPTION = (
     "Open data platform for consumer electronics specs. "
-    "Free, open-source, and inspired by PokeAPI. "
+    "Free and open-source. "
     f"Data licensed CC-BY-SA 4.0. Try `GET {PREFIX}/smartphones`."
 )
 

docs/DATA_PIPELINE.md

@@ -18,10 +18,6 @@ daily) refresh is plenty. That makes a pre-generated static dataset ideal:
 - **Fast**: edge-cached files, no cold starts.
 
 ### How others do it
-- **PokeAPI** converted its API to **static JSON files** in 2018, generated
-  from its database by an updater bot and hosted on cheap static hosting +
-  Cloudflare CDN. See [PokeAPI/api-data](https://github.com/PokeAPI/api-data),
-  [pokeapi.co/about](https://pokeapi.co/about).
 - **Git scraping** (Simon Willison): a scheduled GitHub Actions job fetches
   data, pretty-prints it, and commits it back when it changes — no server
   needed. See [simonwillison.net](https://simonwillison.net/2020/Oct/9/git-scraping/).
@@ -80,7 +76,7 @@ real option but is a **strategy change**, so here are the paths:
 
 | Option | What it means | Trade-offs |
 |---|---|---|
-| **A. Public (current SPEC)** | `data/` + static dump public, CC-BY-SA | Simplest; matches open-data mission & PokeAPI model; community can contribute & self-host. Anyone can copy the data. |
+| **A. Public (current SPEC)** | `data/` + static dump public, CC-BY-SA | Simplest; matches open-data mission; community can contribute & self-host. Anyone can copy the data. |
 | **B. Private factory → public product** | Scrapers + raw/messy data in a **private** repo; only a curated, licensed **public dump** is published | Best of both: keep collection methods/raw data private, still ship an open API. Two repos to run. |
 | **C. Fully private** | Data + dump + API all private (private repo, auth-gated API) | Maximum control / proprietary value, but abandons the open-data positioning, CC-BY-SA, and community contributions. The API stays code-MIT but data is closed. |
 

docs/DEVELOPMENT.md

@@ -6,7 +6,7 @@
 ## What this is
 
 TechAPI — a free, open REST API for consumer-electronics specs (smartphones,
-SoCs, GPUs, CPUs, brands). FastAPI + SQLModel, inspired by PokeAPI. **This repo is
+SoCs, GPUs, CPUs, brands). FastAPI + SQLModel. **This repo is
 the public product: the API + a curated dataset + a static JSON dump.** It does
 **not** contain data-collection/scraping tooling (that is maintained separately;
 see "Data scope" below).
@@ -57,7 +57,7 @@ data/                CURATED SEED DATA — singular folder names, organised by b
 scripts/
   seed.py            data/ → DB (recurses brand subfolders; coerces ISO dates)
   validate.py        schema/range/FK/slug checks (run in CI on data changes)
-  dump.py            DB → static JSON dump (replays API; PokeAPI-style) → ./dump
+  dump.py            DB → static JSON dump (replays API in-process) → ./dump
 tests/               unit/ + integration/ (conftest seeds a temp SQLite from data/)
 docs/                SPEC.md, DATA_PIPELINE.md, DEVELOPMENT.md
 .github/workflows/   test.yml, validate-data.yml, refresh-data.yml
@@ -84,8 +84,8 @@ python -m app.dump               # generate ./dump/ static tree (gitignored)
   recorded as **ADR-011** / **§6.7** in docs/SPEC.md (maintainer wants computer chips).
 - **GPU activated** — model existed (§6.5); endpoints + data added.
 - **Data restructured** to singular names + brand subfolders (maintainer request).
-- **Static-dump pivot** — `scripts/dump.py` exports the API to a static JSON tree
-  (PokeAPI api-data style), refreshed by GitHub Actions (`refresh-data.yml`).
+- **Static-dump pivot** — `app/dump.py` exports the API to a static JSON tree,
+  refreshed by GitHub Actions (`refresh-data.yml`).
 - **Scoring** is a Phase-0 reference-based approximation; Phase 1 → dataset-wide
   min-max (§8.4). Raw third-party benchmarks (Geekbench/AnTuTu/Cinebench/Time Spy)
   are stored as algorithm inputs but NOT exposed (ADR-006).