chore: final post-Rust cleanup

.bazelignore

@@ -1,4 +1,3 @@
-target/
 node_modules/
 examples/
 gen/

.github/dependabot.yml

@@ -10,19 +10,8 @@ updates:
     schedule:
       interval: "weekly"
 
-  - package-ecosystem: "bazel"
-    directory: "/examples/workspace"
-    schedule:
-      interval: "weekly"
-
   - package-ecosystem: "npm"
     directory: "/examples/rules_js"
     schedule:
       interval: "weekly"
     open-pull-requests-limit: 10
-
-  - package-ecosystem: "npm"
-    directory: "/examples/workspace"
-    schedule:
-      interval: "weekly"
-    open-pull-requests-limit: 10

.gitignore

@@ -4,7 +4,4 @@ bazel-*
 .ijwb/
 node_modules
 out/
-# Added by cargo
-
-/target
 MODULE.bazel.lock

CONTRIBUTING.md

@@ -19,12 +19,6 @@ pre-commit install
 
 Otherwise later tooling on CI will yell at you about formatting/linting violations.
 
-## Updating BUILD files
-
-Some targets are generated from sources.
-Currently this is just the `bzl_library` targets.
-Run `bazel run //:gazelle` to keep them up-to-date.
-
 ## Using this as a development dependency of other rules
 
 You'll commonly find that you develop in another WORKSPACE, such as

README.md

@@ -6,14 +6,6 @@ Bazel rules for downloading and using Playwright browsers. These rules provide a
 
 `rules_playwright` provides Bazel targets for downloading Playwright browser binaries for use in your Bazel builds. It handles platform-specific downloads and configuration, making it easier to integrate browser-based testing into your Bazel workspace.
 
-## Documentation
-
-For detailed information on the rules and how to use them, see:
-
-- [Module extension](docs/extensions.md)
-- [Repository rule](docs/repositories.md)
-- [Generating an integrity map](docs/integrity_map.md)
-
 ## Setup
 
 Add the following to your `MODULE.bazel` file: