fix naming

integration-test/README.md

@@ -1,6 +1,6 @@
 # Integration Tests
 
-Dockerized integration tests for the vibe server.
+Dockerized integration tests for the tbd server.
 
 ## Quick Start
 
@@ -13,7 +13,7 @@ docker-compose up --abort-on-container-exit
 
 ## Manual Run (app already running)
 
-If your vibe app is running locally on port 3000:
+If your tbd app is running locally on port 3000:
 
 ```bash
 cd integration-test
@@ -65,7 +65,7 @@ unit tests, the integration tests, and both combined. From the repo root:
 | Task | What it does | Output |
 |------|--------------|--------|
 | `script/unit-coverage` | Runs `test/` under Cloverage | `target/coverage/unit/` |
-| `script/integration-coverage` | Runs the integration suite against a Cloverage-instrumented `vibe-app` container | `target/coverage/integration/` |
+| `script/integration-coverage` | Runs the integration suite against a Cloverage-instrumented `tbd-app` container | `target/coverage/integration/` |
 | `script/coverage-report` | Merges the two `lcov.info` files, prints a per-file table | `target/coverage/merged/` |
 | `script/coverage` | All three, in order (the full suite with a joint report) | all of the above |
 
@@ -74,7 +74,7 @@ merged report a line counts as covered if either suite hit it; the HTML shows pe
 counts per suite (`u:` unit, `i:` integration).
 
 How the integration numbers are collected: `docker-compose.coverage.yml` starts the app via
-`vibe.integration.coverage`, which lets Cloverage instrument `src/` and then serves real
+`tbd.integration.coverage`, which lets Cloverage instrument `src/` and then serves real
 traffic until it receives SIGTERM. `script/integration-coverage` stops the container
 (`docker compose stop`) so the report gets written, then copies it out with `docker compose cp`.
 Plain `script/integration-test` / `script/test` are unchanged and run the uninstrumented app.