fix: keep runner traceability inputs in Docker context
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
parent
0ffc091473
commit
73ad2bf2e1
|
|
@ -37,3 +37,11 @@ packages/paperclip-runner/scripts/*-smoke.mjs
|
|||
# now guards this in PR CI.
|
||||
!packages/paperclip-runner/generated/**
|
||||
!packages/paperclip-runner/docs/capability-contract.md
|
||||
!packages/paperclip-runner/src/backends/harness-driver-backend.test.ts
|
||||
!packages/paperclip-runner/src/contracts/native-execution.test.ts
|
||||
!packages/paperclip-runner/src/drivers/acpx/codex-acpx-driver.test.ts
|
||||
!packages/paperclip-runner/src/drivers/acpx/runtime-host.test.ts
|
||||
!packages/paperclip-runner/src/drivers/opencode/mcp-bridge.test.ts
|
||||
!packages/paperclip-runner/src/drivers/opencode/opencode-server-driver.test.ts
|
||||
!packages/paperclip-runner/src/native-session-runtime.test.ts
|
||||
!packages/paperclip-runner/src/protocol/result-normalization.test.ts
|
||||
|
|
|
|||
|
|
@ -30,7 +30,8 @@ COPY . .
|
|||
RUN test -f packages/paperclip-runner/generated/capability/semantic-tool-contracts.json \
|
||||
&& test -f packages/paperclip-runner/generated/semantic-action-catalog.json \
|
||||
&& test -f packages/paperclip-runner/spec/evals/stress-workflow-traceability.json \
|
||||
&& test -d packages/paperclip-runner/protocol/fixtures/replay
|
||||
&& test -d packages/paperclip-runner/protocol/fixtures/replay \
|
||||
&& node -e "const fs=require('node:fs');const path=require('node:path');const root='packages/paperclip-runner';const manifest=JSON.parse(fs.readFileSync(path.join(root,'spec/evals/stress-workflow-traceability.json'),'utf8'));for(const finding of manifest.findings){for(const regressionTest of finding.regressionTests){fs.accessSync(path.resolve(root,regressionTest));}}"
|
||||
# ajv is installed in an isolated directory (the runner's own package.json
|
||||
# uses workspace: ranges npm cannot install from) and symlinked in so ESM
|
||||
# resolution finds it from the scripts' location.
|
||||
|
|
|
|||
Loading…
Reference in New Issue