docs: assume plugin capabilities by default

Signed-off-by: barlind <tobias@barlind.se>

.github/copilot-instructions.md

@@ -14,7 +14,7 @@ This file customizes GitHub Copilot Chat and Copilot inline suggestions for the
 - **No frontend frameworks.** Vanilla JS, Canvas, Tailwind classes. Do not suggest React/Vue/Svelte additions.
 - **Plugin backend logging.** Suggest `context["log"]`, never `print()`.
 - **Plugin Python imports.** For cross-file backend plugins, suggest `context["load_sibling"]("module_name")` instead of bare `from module_name import X`.
-- **Capability metadata.** For new plugin integrations, suggest `standards: ["capability-pipelines.v1"]` and redaction-safe `capabilities` / `ui` metadata as the primary contract.
+- **Capability metadata.** For plugin integrations, suggest `standards: ["capability-pipelines.v1"]` and redaction-safe `capabilities` / `ui` metadata as the primary contract.
 - **DCO/license headers.** When creating a new file in the main repo, no license header is needed (the LICENSE file at root governs). Plugin authors should add an SPDX-License-Identifier comment to their plugin's source files; the `license` field in `plugin.json` must match the allowlist in [`CONTRIBUTING.md`](../CONTRIBUTING.md).
 
 ## Validation

.github/workflows/validate-plugins.yml

@@ -34,7 +34,7 @@ jobs:
           python -m pip install --upgrade pip
           pip install -r requirements-test.txt
 
-      - name: Validate every in-tree plugin.json against capability-aware schema
+      - name: Validate every in-tree plugin.json against capability schema
         run: |
           python - <<'PY'
           import glob, json, sys