aboutsummaryrefslogtreecommitdiff
path: root/castle-search/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'castle-search/README.md')
-rw-r--r--castle-search/README.md29
1 files changed, 14 insertions, 15 deletions
diff --git a/castle-search/README.md b/castle-search/README.md
index 60930b3..23a36e6 100644
--- a/castle-search/README.md
+++ b/castle-search/README.md
@@ -1,4 +1,7 @@
-# pi-castle-cdp-search
+# castle-search
+
+Part of [sz-chrome-remote-cdp](../FORK.md); until 2026-10 it was its own repo,
+pi-castle-cdp-search.
Web search for [pi](https://pi.dev) through a Chrome that is **already running**
on the wire network, driven over the Chrome DevTools Protocol.
@@ -190,17 +193,9 @@ container at all" (query, or rate limiting).
## Install
-```
-pi install git:git@git.soarez.net:sz/pi-castle-cdp-search.git
-```
-
-That is the fleet's form, over ssh. Anyone else can install from the public
-clone: `pi install https://git.soarez.net/sz/pi-castle-cdp-search.git`. Either
-is portable, unlike a local path: pi records local-path installs by resolved
-absolute path, and `settings.json` is shared across hosts through the dotfiles
-symlink.
-
-To try it without installing:
+It comes with sz-chrome-remote-cdp: the root `package.json` lists
+`./castle-search/src/index.ts` among its pi extensions, so installing that
+package installs this tool. To try it on its own, from this directory:
```
pi -e ./src/index.ts
@@ -208,10 +203,14 @@ pi -e ./src/index.ts
## Development
+It keeps its own `package.json` and dev dependencies, separate from the
+harness's. From the repository root, `npm run check` runs these too, once they
+are installed:
+
```
-npm install
-npm run typecheck
-npm test # unit tests, no browser needed
+npm --prefix castle-search install
+npm --prefix castle-search run typecheck
+npm --prefix castle-search test # unit tests, no browser needed
```
The tests cover engine selection and precedence, URL building for all four