mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-07 16:11:46 +02:00
Dotta
560e7e48b5
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - The runner package already provides the production protocol and execution spine. > - Contributors still need stable SDK surfaces, deterministic test tools, and local inspection tools. > - Those surfaces share generated contracts and must change as one package boundary. > - This pull request adds the package-local SDK, labs, examples, and drift checks. > - The benefit is a reviewable developer platform that does not change application execution selection. ## Linked Issues or Issue Description **Subsystem affected** `packages/paperclip-runner` — runner SDK, conformance tools, and developer tooling. **Problem or motivation** The production runner spine is present, but package consumers cannot build deterministic integrations, inspect sessions, or verify provider-neutral behavior through supported surfaces. **Proposed solution** Add browser, React, standalone, live-session, scenario, conformance, and evaluation surfaces. Add generated contract inventories and package-local verification scripts. Keep production application routing unchanged. **Alternatives considered** We considered splitting each generated catalog, SDK surface, and demo into separate pull requests. Those changes share exports, fixtures, and drift gates. Splitting them would create intermediate package states that do not build. **Roadmap alignment** No overlapping item appears in `ROADMAP.md`. This work extends the runner package that is already on `master`. ## What Changed - Add browser, React, standalone, live-session, and issue-thread SDK surfaces. - Add deterministic mock control-plane, scenario, conformance, replay, and evaluation tools. - Add bounded Codex, OpenCode, and ACPX development transports and fixtures. - Keep deferred managed-provider execution fail-closed. Persisted compatibility data remains readable. - Add generated capability inventories with their source files and drift checks. - Add examples, package documentation, browser checks, and clean-consumer checks. - Preserve the reviewed protocol bounds, replay compatibility aliases, process environment isolation, and semantic redaction limits. - Update the ACPX package patch that the existing workspace patch registry already tracks. - Do not change `pnpm-lock.yaml`, repository workflows, server runtime selection, or the application UI. ## Verification GitHub Actions is the verification authority for this pull request. The repository CI, package TypeScript and Rust checks, package tests, generated-output drift checks, browser checks, security scans, and Greptile review must pass on the exact head. Local test suites were not run because this series uses parallel GitHub Actions for verification. ## Risks This is a large greenfield package change. The main risks are public export drift, generated-output drift, and optional React consumer compatibility. Package boundary checks, clean-consumer checks, and browser tests cover those risks. Production adapter selection and server execution are outside this pull request. ## Stack 1. **This PR:** runner SDK and developer tooling. 2. [Codex production server integration](https://github.com/paperclipai/paperclip/pull/12616). 3. [Provider-neutral task-thread UI](https://github.com/paperclipai/paperclip/pull/12617). ## Model Used OpenAI Codex, GPT-5, high-reasoning mode, with tool use and code execution. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have described the issue in-PR following the feature request template - [x] I have not referenced internal/instance-local Paperclip issues or links - [x] My branch name describes the change and contains no internal Paperclip ticket id - [ ] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented risks above - [ ] All Paperclip CI gates are green - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge
2.9 KiB
2.9 KiB
Capability Verification Commands
Every command here runs from the repository root, is offline and deterministic,
starts no Paperclip service, and holds no credential. All are prefixed
pnpm --filter @paperclipai/paperclip-runner.
| Surface | Command | Expected result |
|---|---|---|
| Capability contract completeness and drift | check:capability-inventory |
Capability inventory completeness and generated-output checks passed. |
| Contract validator negatives | test:capability-inventory |
4 tests pass |
| Mock control plane + shared port | exec vitest run src/conformance/control-plane-port.test.ts src/mock-core/capability-mock-control-plane-adapter.test.ts |
9 tests pass |
| Semantic tools + authorization/redaction | exec vitest run src/tools/capability-semantic-tools.test.ts |
9 tests pass |
| 106-case conformance | test:capability-evals |
1 file (all 106 cases) passes |
| Fake-agent matrix + bounded Codex + parity report | report:capability-evals |
Capability eval conformance passed: 106 cases across 16 groups. |
| Scenario runtime + explorer + clean room + routes | test:scenarios |
159 tests pass |
| Browser IA, accessibility, determinism, boundary | test:browser:scenarios |
Playwright suites pass (60 in the issue-thread/clean-room suite) |
| Screenshot acceptance set | deferred recorded-evidence campaign | 24 deterministic images |
| Documentation links | docs:validate |
all local links resolve |
Live commands (not offline)
The clean-room chat has no fake or replay path, so its end-to-end proof needs a Rust toolchain and a locally authenticated Codex. These are the only Capability commands that start a provider.
| Surface | Command | Expected result |
|---|---|---|
| Real Codex through real runnerd on a fresh mock tenant | smoke:capability:cleanroom |
every assertion true; two MCK- identifiers, one per chat |
| Preset issue thread against real Codex | smoke:capability:ui |
every assertion true |
| Clean-room screenshots | deferred recorded-evidence campaign | 7 images; intentionally not byte-stable |
Notes
- No Rust toolchain is needed for any Capability command. The full
verifytarget still builds the Rust workspace, but nothing above does. - Determinism. Fake-mode runs render fixture time only, so repeat runs and repeat screenshots are byte-identical.
- The parity report is generated on demand.
report:capability-evalswrites.paperclip-local/evidence/capability/eval-parity-report.{json,md}, which are not committed or scanned bydocs:validate. - Browser libraries. On minimal or rootless hosts, extract Playwright's
browser libraries first; the package's
verify:rootlesstarget shows the pattern.