mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-28 12:04:41 +01:00
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work > - Agent adapters run agent sessions through the ACPX engine > - The ACPX engine handled one run attempt as a long implicit procedure > - That shape made resource ownership, cleanup order, and failure behavior hard to verify > - This pull request gives the attempt a coordinator, a typed resource ledger, separate run sites, and explicit turn and settlement sequences > - The benefit is clear ownership, one cleanup path, safer session reuse, and testable failure behavior ## Linked Issues or Issue Description **What existing behavior does this improve?** The ACPX engine manages startup, turn execution, session reuse, and cleanup inside one large run procedure. **Current behavior** The run procedure owns several resources through implicit control flow. Cleanup and session reuse behavior depend on lane-specific branches and error paths. **Proposed behavior** The coordinator owns the run attempt. A typed ledger records six resources and their states. Host and sandbox run sites own lane-specific acquisition. Turn and settlement sequences expose typed outcomes. The engine emits allowlisted phase telemetry. **Reason and benefit** Explicit ownership makes cleanup and failure behavior easier to inspect. The fault matrix and characterization tests protect the external result while the refactor reduces hidden control flow. **Breaking changes** None to the public adapter contract. The host warm-save path now closes and relaunches the runtime because a transferred runtime could retain a run-scoped credential. A cold session-handshake failure now closes the created runtime. **Additional context** This pull request contains the ACPX engine lifecycle refactor, its tests, and the lifecycle document. ## What Changed - Add a run coordinator for startup, turn execution, settlement, and result reproduction. - Add a typed resource ledger with open, sealed, and consumed states. - Add host and sandbox run sites for lane-specific resource acquisition. - Replace separate runtime maps with a generic session reuse store. - Split session fingerprint identity from the outer session key. - Add typed turn and settlement sequences with one cleanup owner. - Add a closed allowlist for phase telemetry. - Add characterization tests and a 17-case fault matrix. - Add `doc/acp-run-lifecycle.md`. ## Verification - `npx vitest run packages/adapter-utils/src/acpx-engine/` passes 18 files and 286 tests at the submitted commit. - `pnpm --filter @paperclipai/adapter-utils typecheck` reports 0 errors at the submitted commit. - Run the full pull request checks after GitHub starts CI. - Run Greptile review after the pull request opens. ## Risks - The refactor changes internal control flow across the ACPX engine. - Host warm-save behavior now closes and relaunches the runtime. - Settlement changes the handling of a cold session-handshake failure from a leak to a close. - The characterization baselines and fault matrix reduce the risk of an external behavior change. > Paperclip is the open source app people use to manage AI agents for work > The adapter layer runs agent sessions through the ACPX engine > The engine needs explicit lifecycle ownership for reliable cleanup > This pull request adds coordinator-owned phases and a typed resource ledger > The result makes lifecycle behavior easier to test and review ## Model Used OpenAI GPT-5 Codex. Exact model ID: GPT-5. The model used tool execution, repository inspection, and code review support. The implementation author supplied the submitted code. ## 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 either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] 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 any risks above - [x] All Paperclip CI gates are green - [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>
191 lines
7.3 KiB
TypeScript
191 lines
7.3 KiB
TypeScript
import { describe, expect, it, vi } from "vitest";
|
|
import { runTurn, type StartedTurn, type TurnFinalizeInput, type TurnSteps } from "./turn-sequence.js";
|
|
import { createRunResourceLedger } from "./run-resource-ledger.js";
|
|
import type { TurnCompletion } from "./run-contracts.js";
|
|
|
|
// The turn sequence owns the run order, the wall-clock timer, and the abort
|
|
// controller. These tests drive it with fakes for the five steps and assert the
|
|
// order, the never-reject guarantee, and the timer ownership. They never touch
|
|
// the engine's real run state.
|
|
|
|
function finalizedTurn(): TurnCompletion {
|
|
return { kind: "finalized" };
|
|
}
|
|
|
|
function failedTurn(error: unknown): TurnCompletion {
|
|
return {
|
|
kind: "failed",
|
|
cause: { kind: "turn_failed", error: error instanceof Error ? error : new Error(String(error)) },
|
|
resources: createRunResourceLedger().takeForSettlement(),
|
|
};
|
|
}
|
|
|
|
function noopStarted(): StartedTurn {
|
|
return { cancel: async () => {} };
|
|
}
|
|
|
|
// A base set of steps whose bodies do nothing. Each test overrides the steps it
|
|
// drives and records the calls it cares about.
|
|
function baseSteps(order: string[], overrides: Partial<TurnSteps<string>> = {}): TurnSteps<string> {
|
|
return {
|
|
timeoutMs: overrides.timeoutMs,
|
|
timeoutMessage: overrides.timeoutMessage ?? "timed out",
|
|
promptBuild: overrides.promptBuild ?? (async () => {
|
|
order.push("promptBuild");
|
|
}),
|
|
preTurnUsage: overrides.preTurnUsage ?? (async () => {
|
|
order.push("preTurnUsage");
|
|
}),
|
|
turnStart: overrides.turnStart ?? (() => {
|
|
order.push("turnStart");
|
|
return noopStarted();
|
|
}),
|
|
eventRelay: overrides.eventRelay ?? (async () => {
|
|
order.push("eventRelay");
|
|
return "terminal";
|
|
}),
|
|
turnFinalize: overrides.turnFinalize ?? (async (input) => {
|
|
order.push(`turnFinalize:${input.kind}`);
|
|
return input.kind === "terminal" ? finalizedTurn() : failedTurn(input.error);
|
|
}),
|
|
};
|
|
}
|
|
|
|
describe("ACPX turn sequence", () => {
|
|
it("test_run_turn_never_rejects_every_error_is_a_completion", async () => {
|
|
// A step error must become a `TurnCompletion`, never a rejection. The event
|
|
// relay throws after the turn started, so the sequence reports a `turn`
|
|
// failure and returns a completion.
|
|
const finalizeInputs: TurnFinalizeInput<string>[] = [];
|
|
const boom = new Error("relay boom");
|
|
const steps = baseSteps([], {
|
|
eventRelay: async () => {
|
|
throw boom;
|
|
},
|
|
turnFinalize: async (input) => {
|
|
finalizeInputs.push(input);
|
|
return input.kind === "terminal" ? finalizedTurn() : failedTurn(input.error);
|
|
},
|
|
});
|
|
|
|
// The returned promise resolves; it never rejects.
|
|
const completion = await runTurn(steps);
|
|
expect(completion.kind).toBe("failed");
|
|
// The error routed through the one finalize step with the `turn` phase.
|
|
expect(finalizeInputs).toHaveLength(1);
|
|
expect(finalizeInputs[0]).toMatchObject({ kind: "error", error: boom, phase: "turn" });
|
|
});
|
|
|
|
it("test_run_turn_owns_timer_and_abort_controller", async () => {
|
|
vi.useFakeTimers();
|
|
try {
|
|
const captured: { signal: AbortSignal | null; cancelReason: string | null } = {
|
|
signal: null,
|
|
cancelReason: null,
|
|
};
|
|
let releaseRelay: (value: string) => void = () => {};
|
|
const relayPromise = new Promise<string>((resolve) => {
|
|
releaseRelay = resolve;
|
|
});
|
|
const finalizeInputs: TurnFinalizeInput<string>[] = [];
|
|
const steps = baseSteps([], {
|
|
timeoutMs: 1000,
|
|
timeoutMessage: "wall-clock timeout",
|
|
turnStart: (signal) => {
|
|
captured.signal = signal;
|
|
return {
|
|
cancel: async (reason) => {
|
|
captured.cancelReason = reason;
|
|
},
|
|
};
|
|
},
|
|
eventRelay: async () => relayPromise,
|
|
turnFinalize: async (input) => {
|
|
finalizeInputs.push(input);
|
|
return input.kind === "terminal" ? finalizedTurn() : failedTurn(input.error);
|
|
},
|
|
});
|
|
|
|
const runPromise = runTurn(steps);
|
|
// Let promptBuild, preTurnUsage, and turnStart run.
|
|
await vi.advanceTimersByTimeAsync(0);
|
|
expect(captured.signal?.aborted).toBe(false);
|
|
// Fire the wall-clock timeout the sequence owns.
|
|
await vi.advanceTimersByTimeAsync(1000);
|
|
// The sequence owns the abort controller: the shared signal is aborted...
|
|
expect(captured.signal?.aborted).toBe(true);
|
|
// ...and it cancelled the started turn with the timeout message.
|
|
expect(captured.cancelReason).toBe("wall-clock timeout");
|
|
// Complete the relay so the sequence finalizes the timed-out turn.
|
|
releaseRelay("terminal");
|
|
const completion = await runPromise;
|
|
expect(completion).toEqual({ kind: "finalized" });
|
|
// The finalize step saw the timeout flag the sequence tracked.
|
|
expect(finalizeInputs).toHaveLength(1);
|
|
expect(finalizeInputs[0]).toMatchObject({ kind: "terminal", timedOut: true });
|
|
} finally {
|
|
vi.useRealTimers();
|
|
}
|
|
});
|
|
|
|
it("test_prompt_build_failure_is_failed_completion_with_prepare_turn", async () => {
|
|
// A prompt-build failure happens before the turn starts, so the sequence
|
|
// reports a `prepare_turn` failure and never runs the later steps.
|
|
const order: string[] = [];
|
|
const finalizeInputs: TurnFinalizeInput<string>[] = [];
|
|
const boom = new Error("prompt build boom");
|
|
const steps = baseSteps(order, {
|
|
promptBuild: async () => {
|
|
throw boom;
|
|
},
|
|
turnFinalize: async (input) => {
|
|
finalizeInputs.push(input);
|
|
return input.kind === "terminal" ? finalizedTurn() : failedTurn(input.error);
|
|
},
|
|
});
|
|
|
|
const completion = await runTurn(steps);
|
|
expect(completion.kind).toBe("failed");
|
|
expect(finalizeInputs).toHaveLength(1);
|
|
expect(finalizeInputs[0]).toMatchObject({ kind: "error", error: boom, phase: "prepare_turn" });
|
|
// The later steps never ran.
|
|
expect(order).not.toContain("preTurnUsage");
|
|
expect(order).not.toContain("turnStart");
|
|
expect(order).not.toContain("eventRelay");
|
|
});
|
|
|
|
it("test_run_turn_finalizes_no_resource", async () => {
|
|
// Structural proof: the sequence borrows the resources and finalizes none.
|
|
// The `TurnSteps` contract has no resource-release method; the sequence runs
|
|
// only the five ordered steps. A test-side resource whose release the
|
|
// sequence could never call stays untouched, and the recorded call order is
|
|
// exactly the five steps. The coordinator settles the resources after the
|
|
// turn, so a resource release inside the sequence would be a double release.
|
|
const order: string[] = [];
|
|
let released = false;
|
|
// A resource the sequence has no hook to release. If the sequence ever
|
|
// released a resource, it would have to reach one, and it cannot.
|
|
const borrowedResource = {
|
|
release: () => {
|
|
released = true;
|
|
},
|
|
};
|
|
void borrowedResource;
|
|
|
|
const steps = baseSteps(order);
|
|
const completion = await runTurn(steps);
|
|
|
|
expect(completion).toEqual({ kind: "finalized" });
|
|
// The sequence ran exactly the five ordered steps, then finalized.
|
|
expect(order).toEqual([
|
|
"promptBuild",
|
|
"preTurnUsage",
|
|
"turnStart",
|
|
"eventRelay",
|
|
"turnFinalize:terminal",
|
|
]);
|
|
// It never released the borrowed resource.
|
|
expect(released).toBe(false);
|
|
});
|
|
});
|