Integrate pi-agent-core with NiceEval non-invasively

Comparison targets:

before: https://github.com/CorrectRoadH/niceeval/tree/main/examples/zh/origin/pi-sdk — a standalone @earendil-works/pi-agent-core HTTP service, before any eval integration.
after: https://github.com/CorrectRoadH/niceeval/tree/main/examples/zh/tier1/pi-sdk — the same app after integrating NiceEval.

Integration path: official converter — mapping pi native AgentEvent events into standard events is handled by createPiAgentEventStream (exported from "niceeval/adapter"). The adapter only keeps transport glue: which URL the app uses and which endpoint handles approvals (calculate goes through HITL approval). You start the app yourself in its normal way (pnpm start); evals do not manage the process. App-side src/backend/* files are byte-for-byte unchanged. All integration code changes (measured from both directories when generated):

File list

pi-sdk/
├── package.json                    modified
├── tsconfig.json                   modified
├── pnpm-workspace.yaml             modified
├── niceeval.config.ts              added
├── agents/
│   └── pi-sdk.ts                   added
├── evals/
│   ├── basic-qa.eval.ts            added
│   ├── hitl-approve.eval.ts        added
│   ├── hitl-deny.eval.ts           added
│   ├── session-isolation.eval.ts   added
│   └── weather-tool.eval.ts        added
└── experiments/
    └── assistant.ts                added

Choose an Example

Connect an Agent Framework

Full Eval Projects

Integrate pi-agent-core with NiceEval non-invasively

File list

App-side changes (dependency declarations only)

Added adapter, evals, and experiments

​File list

​App-side changes (dependency declarations only)

​Added adapter, evals, and experiments

File list

App-side changes (dependency declarations only)

Added adapter, evals, and experiments