Simplify to one yml, drop Makefile / config / local-mode

Karan's review (#1, #2, #4) pushed back on the per-mode config files
and the Makefile-as-profile-switcher. Aligning with the canonical
cucumber-ruby-browserstack shape (one feature run unchanged):

- Drop Makefile and config/{single,local}.yml — the Python SDK reads
  only ./browserstack.yml so the swap was the workaround; aligning
  instead means one yml, one command.
- Drop features/local.feature, local-html/, and local_steps.py.
  Customers needing the Local tunnel flip browserstackLocal: true and
  rerun the same command (documented in README).
- Drop buildIdentifier from browserstack.yml — pure dashboard UX, not
  required, and Karan flagged it as noise.
- CI workflow runs browserstack-sdk behave directly (no make targets).
- README pruned to single-mode setup + Running + Local-toggle note.

Author: Jimesh-browserstack

.github/workflows/build.yml

@@ -58,13 +58,12 @@ jobs:
           cache: pip
 
       - name: Install dependencies
-        run: make install
+        run: |
+          pip install -r requirements.txt
+          playwright install chromium
 
-      - name: Run parallel sample on BrowserStack
-        run: make parallel
-
-      - name: Run local sample on BrowserStack
-        run: make local
+      - name: Run sample on BrowserStack
+        run: browserstack-sdk behave features/sample.feature
 
       - if: always()
         uses: actions/github-script@98814c53be79b1d30f795b907e553d8679345975

.gitignore

@@ -1,6 +1,5 @@
 .venv/
 __pycache__/
 *.pyc
-browserstack.yml.bak
 log/
 local.log

Makefile

@@ -10,42 +10,38 @@ This repo shows how to run [behave](https://behave.readthedocs.io/) tests on Bro
   pip install -r requirements.txt
   playwright install chromium
   ```
-  Or simply: `make install`
-* Set `BROWSERSTACK_USERNAME` and `BROWSERSTACK_ACCESS_KEY` as environment variables, or replace `userName` and `accessKey` directly in `browserstack.yml` (and the variants under `config/`) with your [BrowserStack Username and Access Key](https://www.browserstack.com/accounts/settings). Env vars take precedence.
+* Set `BROWSERSTACK_USERNAME` and `BROWSERSTACK_ACCESS_KEY` as environment variables, or replace `userName` and `accessKey` directly in `browserstack.yml` with your [BrowserStack Username and Access Key](https://www.browserstack.com/accounts/settings). Env vars take precedence.
 
 ### Running your tests
-* Run tests in parallel across the 3 Playwright browser engines (chromium / firefox / webkit): `make parallel`
-* Run a single-platform test: `make single`
-* Run with the BrowserStack Local tunnel against a local HTTP server: `make local`
+Run the sample in parallel across the 3 Playwright browser engines (chromium / firefox / webkit) declared in `browserstack.yml`:
+
+```sh
+browserstack-sdk behave features/sample.feature
+```
 
 Understand how many parallel sessions you need by using our [Parallel Test Calculator](https://www.browserstack.com/automate/parallel-calculator?ref=github).
 
 Alternatively the variables can be set in the environment using env or your CI framework (like GitHub Actions or Jenkins). See `.github/workflows/build.yml` for a GitHub Actions example — it runs on `workflow_dispatch` (manual trigger) with a commit SHA input and posts a status check back to that commit.
 
+### Testing a private host (BrowserStack Local)
+If your app lives on `localhost`, a staging host, or behind a firewall, set `browserstackLocal: true` in `browserstack.yml` and rerun the same command. The SDK starts and stops the BrowserStack Local tunnel for you — no manual binary download or lifecycle management. Then point your scenarios at `http://bs-local.com:<port>/` (a hostname BrowserStack Local resolves to your machine) instead of a public URL.
+
 ### How the SDK changes things
-- **One `browserstack.yml`** declares platforms; the SDK picks them up automatically — no per-task config switching inside `environment.py`.
+- **One `browserstack.yml`** declares platforms; the SDK picks them up automatically.
 - **The SDK runs platforms in parallel for you** — no hand-rolled parallel runner; the SDK forks one behave run per `(platform × parallelsPerPlatform)` cell.
 - **The SDK monkeypatches Playwright's browser launches** — the test code calls `chromium.launch()` and the SDK transparently routes the launch to the per-platform browser configured in `browserstack.yml` (chromium, firefox, or webkit). No `chromium.connect(wss_url)` plumbing is needed in customer code.
-- **The SDK starts and stops BrowserStack Local** when `browserstackLocal: true` — no manual tunnel lifecycle management.
-- **The CLI is `browserstack-sdk behave …`** — the `make` targets shell out to that.
+- **The CLI is `browserstack-sdk behave …`** — wraps `behave` and injects the SDK at runtime.
 
 ### Repo layout
 ```
 .
-├── browserstack.yml                  # 3-platform parallel default
-├── config/
-│   ├── browserstack.single.yml       # 1 platform
-│   └── browserstack.local.yml        # 1 platform + browserstackLocal: true
+├── browserstack.yml           # SDK config: credentials, 3 parallel platforms, Local toggle, reporting
 ├── requirements.txt
-├── Makefile
 └── features/
-    ├── sample.feature                # bstackdemo add-to-cart scenario
-    ├── local.feature                 # localhost scenario for the Local tunnel
-    ├── local-html/index.html         # static page served on :45454 by `make local`
-    ├── environment.py                # behave hooks: launch browser, hand to context.page
+    ├── sample.feature         # bstackdemo add-to-cart scenario
+    ├── environment.py         # behave hooks: launch browser, hand to context.page
     └── steps/
-        ├── sample_steps.py
-        └── local_steps.py
+        └── sample_steps.py
 ```
 
 ### Further Reading

README.md

@@ -12,9 +12,6 @@ accessKey: YOUR_ACCESS_KEY
 # ======================
 projectName: BrowserStack Samples
 buildName: behave-playwright-sdk-build-1
-# `buildIdentifier` is a unique id appended to buildName for every run.
-# ${BUILD_NUMBER} (default) is an incremental counter; ${DATE_TIME} is a timestamp.
-buildIdentifier: '#${BUILD_NUMBER}'
 
 # `framework` lets the SDK send test context (test name, status) to BrowserStack.
 framework: behave
@@ -47,7 +44,8 @@ parallelsPerPlatform: 1
 # ===================================
 # BrowserStack Local (private hosts)
 # ===================================
-# Default false in this config. The local-mode example sets this true.
+# Set to true to test localhost / staging hosts. The SDK starts and stops
+# the BrowserStack Local tunnel for you — no manual binary management.
 browserstackLocal: false
 
 # ===========