chore: update async-miniweb repository metadata

Author: PatrickJS

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## [0.1.0](https://github.com/async-framework/miniweb/releases/tag/v0.1.0) - 2026-05-28
+## [0.1.0](https://github.com/async-framework/async-miniweb/releases/tag/v0.1.0) - 2026-05-28
 
 Initial public release of MiniWeb as `@async/miniweb`.
 

docs/releasing.md

@@ -13,7 +13,7 @@ When the release PR merges, push the release tag. The `Release` workflow verifie
 Configure npm Trusted Publishing for this package before the first automated publish:
 
 - npm package: `@async/miniweb`
-- GitHub owner/repository: `async-framework/miniweb`
+- GitHub owner/repository: `async-framework/async-miniweb`
 - Workflow filename: `release.yml`
 - Environment: leave unset unless npm requires one for the package
 

package.json

@@ -4,13 +4,13 @@
   "type": "module",
   "description": "A tiny web-stack simulator for static-hosted demos and Node-side integration tests.",
   "license": "MIT",
-  "homepage": "https://github.com/async-framework/miniweb#readme",
+  "homepage": "https://github.com/async-framework/async-miniweb#readme",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/async-framework/miniweb.git"
+    "url": "git+https://github.com/async-framework/async-miniweb.git"
   },
   "bugs": {
-    "url": "https://github.com/async-framework/miniweb/issues"
+    "url": "https://github.com/async-framework/async-miniweb/issues"
   },
   "bin": {
     "miniweb": "./dist/cli.js"

tools/brave-miniweb-redirect/README.md

@@ -17,7 +17,7 @@ It only redirects top-level page navigations for the MiniWeb preview hostname. I
 4. Select this folder:
 
 ```txt
-/Users/patrickjs/code/async-framework/miniweb/tools/brave-miniweb-redirect
+/Users/patrickjs/code/async-framework/async-miniweb/tools/brave-miniweb-redirect
 ```
 
 Then open: