docs: stop explaining a submodule loop that no longer exists

Since the pin moved to ff4e11e, TechEngine carries no submodule, so a
recursive checkout has nothing to loop on. The comments in pages.yml,
pr-checks.yml, final-check.yml and build-api.sh, and two notes in the
README, still warned about it. The checkouts stay plain and
non-recursive; only the wording changes.

Author: Seungpyo1007

.github/scripts/build-api.sh

@@ -4,7 +4,7 @@
 # (data/_verify/status.json) with the pinned TechEngine, and check the result.
 # pages.yml runs this before publishing.
 #
-# Needs the TechEngine submodule checked out (never recursively) and its
+# Needs the TechEngine submodule checked out and its
 # dependencies installed: python -m pip install -e ./TechEngine
 set -euo pipefail
 

.github/workflows/final-check.yml

@@ -35,8 +35,9 @@ jobs:
     env:
       PYTHONIOENCODING: utf-8
     steps:
-      # The merge commit, as pages.yml would build it after merging. Not
-      # recursive: TechEngine carries TechAPI as its own submodule.
+      # The merge commit, as pages.yml would build it after merging. A plain,
+      # non-recursive submodule checkout is all it needs: TechEngine has no
+      # submodules of its own.
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           fetch-depth: 2

.github/workflows/pages.yml

@@ -30,8 +30,8 @@ jobs:
     steps:
       # Full history: the dump stamps created_at/updated_at from git log of
       # data/ (a shallow clone stamps every record with the tip time), and the
-      # growth chart reads old commits. Submodules are not recursive: TechEngine
-      # carries TechAPI as its own submodule.
+      # growth chart reads old commits. A plain, non-recursive submodule
+      # checkout is all it needs: TechEngine has no submodules of its own.
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           fetch-depth: 0

.github/workflows/pr-checks.yml

@@ -29,8 +29,8 @@ jobs:
     steps:
       # The pull_request ref is GitHub's merge commit. Depth 2 brings both
       # parents, so HEAD^1 is the base the PR merges into: no deepening, no
-      # second checkout. submodules: true is NOT recursive (TechEngine carries
-      # TechAPI as its own submodule; recursion re-clones ~1.8 GB).
+      # second checkout. submodules: true is a plain, non-recursive checkout,
+      # which is all it needs: TechEngine has no submodules of its own.
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           fetch-depth: 2

README.md

@@ -39,7 +39,7 @@ only the hand-made `site/public/v1/games/index.json` pointer is. To preview the
 site with the API locally:
 
 ```bash
-git submodule update --init TechEngine   # never --recursive
+git submodule update --init TechEngine
 python -m pip install -e ./TechEngine
 bash .github/scripts/build-api.sh        # validates, then writes site/public/v1
 cd site && npm ci && npm run dev
@@ -99,9 +99,7 @@ This repo follows git-flow:
 
 A release is a PR from `develop` to `main`; merging it deploys the site.
 The TechEngine pin and the pinned action SHAs are bumped by hand, in a PR into
-`develop` that pr-checks validates like any other. Dependabot can't do it:
-TechEngine carries TechAPI as its own submodule, and Dependabot's recursive
-clone runs out of disk on that loop.
+`develop` that pr-checks validates like any other; Dependabot is not used.
 
 ## Contributing