docs: remove the screenshot from the docs introduction page

CONTRIBUTING.md

@@ -89,7 +89,7 @@ sideways or the header's nav runs under the account menu; unlike the jsdom check
 `npx playwright install chromium`; after a run, `npx playwright show-report` opens the HTML
 report (CI uploads it as the `playwright-report` artifact).
 
-The README and docs screenshot (`docs/src/assets/screenshots/apps-list.png`) comes from the same
+The README screenshot (`docs/src/assets/screenshots/apps-list.png`) comes from the same
 mocked API: after a UI change that alters the apps list, run `npm run build && npm run screenshot`
 in `ui/` and commit the new image.
 

docs/src/content/docs/index.md

@@ -13,8 +13,6 @@ Everything converges on one declarative resource: the **`App`** custom resource
 Service, and a `NebariApp` — and the [nebari-operator](https://github.com/nebari-dev/nebari-operator)
 turns that into routing, TLS, authentication, and (when the app opts in) a landing-page tile.
 
-![The Apps page: a banner saying two apps need attention above status filter chips and a table of launched apps with their type, source, status, replicas and owner, the failed app first](../../assets/screenshots/apps-list.png)
-
 Each app gets its own URL under the cluster's apps domain:
 
 ```

ui/scripts/readme-screenshot.ts

@@ -1,5 +1,5 @@
 /*
- * The apps list screenshot used by the README and the docs landing page
+ * The apps list screenshot used by the README
  * (docs/src/assets/screenshots/apps-list.png). Run `npm run build` and then
  * `npm run screenshot`; it uses the e2e suite's mocked apps-api with the
  * made-up apps below, so the image holds no real data.