ci: exercise the real install contract for ep_ai_core (#35)

Drop the manual ep_ai_core pre-install from both backend-tests and frontend-tests so CI walks the same path a user does (`pnpm run plugins i ep_ai_chat`). ep_ai_core now resolves via "dependencies"; a regression back to peerDependencies fails the frontend job, which runs on same-repo PRs. README install command simplified accordingly. Follow-up to #34 (closed #33).

Author: JohnMcLear

.github/workflows/backend-tests.yml

@@ -58,13 +58,15 @@ jobs:
         name: Install Etherpad core dependencies
         working-directory: ./etherpad-lite
         run: bin/installDeps.sh
-      - name: Install peer dep ep_ai_core from registry
-        working-directory: ./etherpad-lite
-        run: pnpm run plugins i ep_ai_core
+      # Deliberately do NOT pre-install ep_ai_core here. It is a hard runtime
+      # dependency declared in package.json "dependencies", so installing the
+      # plugin alone must pull it in automatically. Pre-installing it would mask
+      # a regression if it were ever moved back to peerDependencies (peer deps
+      # are not auto-installed), which is exactly the bug that closed #33.
       - name: Install optional peer dep ep_comments_page from registry
         working-directory: ./etherpad-lite
         run: pnpm run plugins i ep_comments_page
-      - name: Install plugin
+      - name: Install plugin (must resolve ep_ai_core on its own)
         working-directory: ./etherpad-lite
         run: |
           pnpm run plugins i --path  ../../plugin

.github/workflows/frontend-tests.yml

@@ -45,15 +45,20 @@ jobs:
         name: Install Etherpad core dependencies
         working-directory: ./etherpad-lite
         run: bin/installDeps.sh
-      - name: Install peer dep ep_ai_core from registry
-        working-directory: ./etherpad-lite
-        run: pnpm run plugins i ep_ai_core
-      # Intentionally NOT installing ep_comments_page here. The frontend
+      # Deliberately do NOT pre-install ep_ai_core. It is a hard runtime
+      # dependency declared in package.json "dependencies", so installing the
+      # plugin alone must pull it in automatically — and the AI editing specs
+      # below can only pass if it loads. This is the path a real user walks
+      # (`pnpm run plugins i ep_ai_chat`). Unlike backend-tests, this job runs
+      # on same-repo PRs, so it is what actually guards against ep_ai_core
+      # being moved back to peerDependencies (the bug that closed #33).
+      #
+      # Also intentionally NOT installing ep_comments_page here. The frontend
       # editing specs expect AI requests to apply edits directly to the
       # pad; with ep_comments_page present, the plugin's "auto" default
       # routes to suggest mode and the pad text would not change in
       # response to those tests.
-      - name: Install plugin
+      - name: Install plugin (must resolve ep_ai_core on its own)
         working-directory: ./etherpad-lite
         run: |
           pnpm run plugins i --path ../../plugin

README.md

@@ -9,12 +9,12 @@ edit lands inline with its own author colour and an explanation in chat.](demo.g
 
 ## Installation
 
-Requires `ep_ai_core`.
-
 ```bash
-pnpm run plugins i ep_ai_core ep_ai_chat
+pnpm run plugins i ep_ai_chat
 ```
 
+This pulls in `ep_ai_core` automatically — it is a required runtime dependency.
+
 Configure the LLM provider in `settings.json` under the `ep_ai_core` key.
 See the [ep_ai_core README](https://github.com/ether/ep_ai_core#readme) for
 full configuration details.