A kódbázis kommentek nélkül marad

Kérésre: minden magyarázó komment kikerült a forrásfájlokból — 89 Ruby, 16
TypeScript, 14 Vue, plusz a CSS/JS/CJS. Nem soralapú kereséssel: a Ruby-t a
Ripper tokenizálta, a JS/TS/CSS-t állapotgép járta végig, hogy az URL-ekben,
reguláris kifejezésekben és heredocokban álló // és # jelek helyükön
maradjanak.

Három komment maradt, mert nélkülük nem indul a kód: az entrypoint.sh
shebangja, a vite-env.d.ts hármas perjeles referenciája, és a sanitize
teszt @vitest-environment direktívája (ez utóbbi a magyarázó része nélkül).

Egy helyen kódot is kellett írni: a CommandBlock másolás-hibaágán a komment
volt a catch egyetlen tartalma, és üres blokkot az eslint nem enged — a
copied jelző visszaállítása került a helyére.

A yaml, Dockerfile, Makefile, erb és markdown fájlokat nem érintettem.

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

apps/api/db/migrate/20260728000003_add_cascade_to_software_foreign_keys.rb

@@ -9,7 +9,6 @@ class AddCascadeToSoftwareForeignKeys < ActiveRecord::Migration[8.1]
     remove_foreign_key :software_images, :softwares
     add_foreign_key :software_images, :softwares, on_delete: :cascade
 
-    # Keep download stats when a release is removed.
     remove_foreign_key :downloads, name: "fk_downloads_release"
     add_foreign_key :downloads, :releases, name: "fk_downloads_release", on_delete: :nullify
   end

apps/api/db/migrate/20260802000001_create_release_assets_and_backfill.rb

@@ -20,8 +20,6 @@ class CreateReleaseAssetsAndBackfill < ActiveRecord::Migration[8.1]
     add_index :release_assets, :path, name: "idx_release_assets_path"
     add_foreign_key :release_assets, :releases, name: "fk_releases_release_assets", on_delete: :cascade
 
-    # A soft-deletelt release-ek asset sorai a release deleted_at-jét öröklik,
-    # így az unscoped alapú admin/updater logika konzisztens marad.
     COLUMN_KINDS.each do |column, kind|
       execute <<~SQL.squish
         INSERT INTO release_assets (release_id, kind, path, deleted_at, created_at, updated_at)

apps/api/db/migrate/20260802000002_drop_legacy_path_columns_from_releases.rb

@@ -17,7 +17,6 @@ class DropLegacyPathColumnsFromReleases < ActiveRecord::Migration[8.1]
       add_column :releases, column, :string
     end
 
-    # rollbacknél az adat a release_assets-ből áll vissza, nem veszik el
     COLUMN_KINDS.each do |column, kind|
       execute <<~SQL.squish
         UPDATE releases r

apps/api/db/migrate/20260818000001_create_stores.rb

@@ -3,9 +3,7 @@ class CreateStores < ActiveRecord::Migration[8.1]
     create_table :stores, id: { type: :bigint, unsigned: true },
                           charset: "utf8mb4", collation: "utf8mb4_0900_ai_ci",
                           if_not_exists: true do |t|
-      # A store is a WarpEngine catalog plus the repository that configures a
-      # client for it. The registry lives here rather than in the engine: the
-      # engine serves one catalog and knows nothing about who ships stores for it.
+
       t.string   :name,                 null: false
       t.string   :catalog_url,          null: false
       t.string   :store_repository_url, null: false

apps/api/db/migrate/20260818120000_allow_stores_without_a_repository.rb

@@ -1,9 +1,5 @@
 class AllowStoresWithoutARepository < ActiveRecord::Migration[8.1]
-  # A store repository is now optional. The client only ever needed identity from
-  # it — a name, a catalog and a slug — and the engine's own defaults cover
-  # everything else, so a record with a catalog URL is a complete store. A
-  # repository is still honoured when there is one: it stays the authority on how
-  # that store behaves.
+
   def change
     change_column_null :stores, :store_repository_url, true
   end

apps/api/db/migrate/20260819000001_carry_the_store_config_in_the_registry.rb

@@ -1,15 +1,5 @@
 class CarryTheStoreConfigInTheRegistry < ActiveRecord::Migration[8.1]
-  # The store's own configuration moves into this record.
-  #
-  # It used to live as a `config.json` in a repository the client fetched over HTTP,
-  # which made a store's behaviour depend on a second thing existing and staying
-  # reachable. The registry already answers what a store *is*; carrying how it behaves
-  # in the same record makes this the one source of truth, and lets a store exist with
-  # no repository at all — which is the ordinary case now that the store engine ships
-  # inside the client.
-  #
-  # Nullable, because a store that configures nothing is still a store: the client
-  # falls back to the engine's built-in defaults, which need only a name and a catalog.
+
   def change
     add_column :stores, :config, :json
   end

apps/api/db/migrate/20260819120000_a_store_is_a_name_and_a_catalog.rb

@@ -1,16 +1,5 @@
 class AStoreIsANameAndACatalog < ActiveRecord::Migration[8.1]
-  # Both extras go. A store record is a name and a catalog, and nothing else.
-  #
-  # `config` was added earlier today on the idea that the registry should say how each
-  # store behaves. It should not: the configuration is fixed per installed client — the
-  # client carries it and knows its own machine — so a copy on the server was a second
-  # authority over decisions the client had already made correctly, including where it
-  # may delete. Keeping two stores on one machine apart is a subfolder, which the client
-  # derives itself.
-  #
-  # `store_repository_url` goes for the same reason it stopped being read: the store
-  # engines it pointed at do not exist any more, and a URL nobody follows is a URL that
-  # goes stale.
+
   def change
     remove_column :stores, :config, :json
     remove_column :stores, :store_repository_url, :string

apps/api/db/migrate/20260819121824_add_active_to_stores.rb

@@ -1,16 +1,5 @@
 class AddActiveToStores < ActiveRecord::Migration[8.1]
-  # A store that exists but should not be offered yet.
-  #
-  # Soft deletion already covered "this store is gone"; what was missing is "not yet" —
-  # a catalog being set up, or one taken out of the picker for a while without losing
-  # the row and its history. The client has no notion of either: it lists whatever
-  # /api/stores hands it, so the filtering has to happen here.
-  #
-  # Default true, so every store that exists today keeps being listed. A migration that
-  # silently emptied the registry would be a client with nothing to install from.
-  #
-  # No index: this table holds a handful of rows and is read once per client on first
-  # run. An index on a two-valued column would be ceremony.
+
   def change
     add_column :stores, :active, :boolean, null: false, default: true
   end

apps/api/db/schema.rb

@@ -1,15 +1,3 @@
-# This file is auto-generated from the current state of the database. Instead
-# of editing this file, please use the migrations feature of Active Record to
-# incrementally modify your database, and then regenerate this schema definition.
-#
-# This file is the source Rails uses to define your schema when running `bin/rails
-# db:schema:load`. When creating a new database, `bin/rails db:schema:load` tends to
-# be faster and is potentially less error prone than running all of your
-# migrations from scratch. Old migrations may fail to apply correctly if those
-# migrations use external dependencies or application code.
-#
-# It's strongly recommended that you check this file into your version control system.
-
 ActiveRecord::Schema[8.1].define(version: 2026_08_19_121824) do
   create_table "admin_users", charset: "utf8mb4", collation: "utf8mb4_0900_ai_ci", force: :cascade do |t|
     t.datetime "created_at", null: false

apps/api/db/seeds.rb

@@ -16,9 +16,6 @@ end
   end
 end
 
-# The store registry the graphical desktop client reads. Our own catalog is the
-# first record; anyone running this site would add their own the same way, from
-# the admin panel or here.
 Store.find_or_create_by!(name: "Teletype Games") do |store|
   store.catalog_url = ENV.fetch("STORE_CATALOG_URL", "https://teletypegames.org")
 end