mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-04 19:28:46 +01:00
merge: reconcile published native prerequisite and current master
Preserve canonical startup ownership, scoped evidence, current Storybook IDs, and the Codex form controls while carrying Claude effort and immutable source bindings. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
commit
48ffca9438
415 files changed
+22501
-15340
No files matched your search
@@ -81,10 +81,12 @@ different observations, both required in the evidence.
|
||||
- Authentication/model discovery does not establish tool, image, steering, or resumption capability parity.
|
||||
- Use [recovery](./recovery.md) for interrupted runs and [execution environments](./execution-environments.md) for local/SSH/sandbox differences.
|
||||
|
||||
Native setup retirement must join owned startup before cleanup can be confirmed.
|
||||
Native setup retirement joins owned startup before cleanup can be confirmed.
|
||||
[Transport ownership controls](../../packages/paperclip-runner/src/live/runnerd-codex-transport.test.ts)
|
||||
hold credential preparation or registration without launching a provider, then
|
||||
verify bounded close, no later launch, and retention of unconfirmed state. A
|
||||
primary setup timeout remains a failure even when teardown also fails. These
|
||||
controls cover the lifecycle boundary; final packaged provider execution is
|
||||
separate evidence.
|
||||
hold preparation or registration without launching a provider, then check bounded
|
||||
close, rejected duplicate requests, no later launch and retention of unconfirmed
|
||||
state. Readiness observes shutdown; resumed startup cannot reactivate ingress
|
||||
after close. These are lifecycle controls, separate from installed provider proof.
|
||||
The real daemon readiness and recovery controls require their existing native
|
||||
fixtures in hosted CI; passing credential-free controls does not qualify them.
|
||||
A primary setup timeout remains a failure even when teardown also fails.
|
||||
Reference in new issue
Block a user