refactor: tighten extension test support boundaries

This commit is contained in:
Peter Steinberger
2026-04-28 03:52:16 +01:00
parent e5452a9c57
commit 129b996a4e
16 changed files with 223 additions and 70 deletions

View File

@@ -1,2 +1,2 @@
6c33fafd66396c2c769b8f8d1f5d0792beb8b4b2d23b5f0323ff2bb2d0a79805 plugin-sdk-api-baseline.json
27336f313c029843be409d22d79caf6f45884cf37458d9f52c0a88c4e8b268fd plugin-sdk-api-baseline.jsonl
343a555f212dd5ebf26dccbefff1cb4b56a08e4dcc2c801ac7ab5fb98973192a plugin-sdk-api-baseline.json
02aaccbe13f261de2d41fcb4270fc9ae70b931966089e56d21a4ebc8e80c8821 plugin-sdk-api-baseline.jsonl

View File

@@ -45,6 +45,9 @@ plugins.
Prefer the focused subpaths below for new plugin tests. The broad
`openclaw/plugin-sdk/testing` barrel is legacy compatibility only.
Repo guardrails reject new real imports from `plugin-sdk/testing` and
`plugin-sdk/test-utils`; those names remain only as deprecated compatibility
surfaces for external plugins and compatibility-record tests.
```typescript
import {