chore: required review changes (#35)

Author: archief2910

.github/workflows/checks.yml

@@ -58,24 +58,13 @@ jobs:
         run: npm ci
       - name: Run build check
         run: npm run build:check
-  compose-validate:
-    name: Validate Docker Compose overlays (Tor / I2P)
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-      - name: Validate merged compose files
-        env:
-          SECRET: ci_placeholder_not_for_production_use_repeat_to_64chars_aaaaaaaa
-        run: node ./scripts/verify-compose-overlays.mjs
   test-units-and-cover:
     name: Unit Tests And Coverage
     runs-on: ubuntu-latest
     needs:
       - commit-lint
       - lint
       - build-check
-      - compose-validate
     steps:
       - name: Checkout
         uses: actions/checkout@v3
@@ -111,7 +100,6 @@ jobs:
       - commit-lint
       - lint
       - build-check
-      - compose-validate
     steps:
       - name: Checkout
         uses: actions/checkout@v3

CONFIGURATION.md

@@ -73,7 +73,6 @@ Tunnel keys are persisted at `.nostr/i2p/data/` so the `.b32.i2p` address surviv
 
 - Start with I2P: `./scripts/start_with_i2p`
 - Print hostname hints: `./scripts/print_i2p_hostname`
-- Validate compose merges without starting containers (requires Docker): `npm run compose:validate` (same logic as the `compose-validate` CI job).
 
 If you've set READ_REPLICAS to 4, you should configure RR0_ through RR3_.
 

README.md

@@ -244,12 +244,6 @@ Print the I2P hostname:
   ./scripts/print_i2p_hostname
   ```
 
-Verify that Docker Compose files merge correctly (no stack started; requires Docker on PATH):
-  ```
-  npm run compose:validate
-  ```
-  This runs `docker compose … config -q` for the I2P-only, Tor-only, and Tor+I2P overlay combinations (same check as the `compose-validate` CI job).
-
 ### Importing events from JSON Lines
 
 You can import NIP-01 events from a `.jsonl` file directly into the relay database.
@@ -642,7 +636,7 @@ To observe client and subscription counts in real-time during a test, you can in
    ```bash
    docker compose logs -f nostream
    ```
-=======
+
 ## Export Events
 
 Export all stored events to a [JSON Lines](https://jsonlines.org/) (`.jsonl`) file. Each line is a valid NIP-01 Nostr event JSON object. The export streams rows from the database using cursors, so it works safely on relays with millions of events without loading them into memory.

package.json

@@ -61,7 +61,6 @@
     "i2p:docker:compose:start": "./scripts/start_with_i2p",
     "i2p:hostname": "./scripts/print_i2p_hostname",
     "i2p:docker:compose:stop": "./scripts/stop",
-    "compose:validate": "node ./scripts/verify-compose-overlays.mjs",
     "docker:integration:run": "docker compose -f ./test/integration/docker-compose.yml run --rm tests",
     "docker:test:integration": "npm run docker:integration:run -- npm run test:integration",
     "docker:cover:integration": "npm run docker:integration:run -- npm run cover:integration",