fix(ci): build native plugin fixtures for the host target

The macOS job failed with no_matching_artifact because the integration test
copied the Linux-only example manifest and built a Linux-named .so. Tests now
generate a manifest for the actual host triple, use the platform dynamic
library name and compiler flags, and never rewrite the tracked example
manifest.

- add a cross-platform no_matching_artifact test that runs without a C compiler
- add real tamper and ABI-major-mismatch rejection tests
- make worker fixtures platform-native; Windows remains explicitly unsupported
  (no cc) rather than counted as a pass
- example build scripts emit host-specific build/ fixtures (gitignored)
- CI smoke points at the generated fixtures
This commit is contained in:
cflmy committed 2026-11-20 13:54:18 +08:00
1 parent c7f3a8422c
commit 53cdea2325
7 files changed
+285 -85

No files matched your search

+3 -3
View File
@@ -41,7 +41,7 @@ interchangeable. Update `artifacts[0].target` and `sha256` in
[`plugin.yaml`](plugin.yaml) to match what you built:
```sh
sha256sum examples/plugin-demo/solver.so
sha256sum examples/plugin-demo/build/solver.so
```
## Inspect
@@ -51,8 +51,8 @@ Manifest validation and artifact verification are implemented by
never loads plugin code):
```sh
./examples/plugin-demo/build.sh # builds solver.so and refreshes sha256
marqdo plugin inspect examples/plugin-demo
./examples/plugin-demo/build.sh # writes build/solver.<dylib> + manifest
marqdo plugin inspect examples/plugin-demo/build
```
A typical inspection flow is: