fix: acknowledge completed pull execution receipts

[alongubkin]

When an executor commits a terminal result but loses the sync response, its next request still carries the completed execution claim. Renewal rejects that claim indefinitely, preventing it from fetching new work.

On a typed claim or lease rejection during renewal or reconciliation, ask a claim-capable deployment store whether the exact receipt is already complete. Return an acknowledgment-only response, preserving the configured tunnel endpoint, so the executor drops its durable receipt and acquires work on its next sync. Stores that do not issue claims deliberately decline recovery. Unrelated errors retain their behavior.

The generated release contract gains an explicit completed-receipt mode; no new sync endpoint is introduced and renewal continues to require a live lease.

Validation: all 42 Manager sync unit tests passed with sqlite/openapi enabled. An HTTP/SQLite Operator test checks durable receipt clearing and the next request without a claim. API contracts were generated with the API OpenAPI generator and pnpm run generate:api-copy-openapi.

Linear: ALIEN-1221

[alongubkin]

@greptileai review

[alongubkin]

@greptile review

[greptile-apps]

Confidence Score: 5/5

[Critical risk] Adds execution claim acknowledgment to the sync protocol.

The PR appears safe to merge; no outstanding finding or new actionable issue was identified.

Summary

The PR adds recovery for completed execution receipts when claim or lease renewal or reconciliation rejects a replayed claim.

• The Manager checks whether the exact receipt is complete and returns an acknowledgment-only response that preserves the configured tunnel URL.
• The Operator test verifies that the acknowledgment clears the durable receipt and that the next sync omits the claim.
• The release contracts document completed-receipt acknowledgment.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Operator syncs with execution receipt] --> B[Manager renews or reconciles]
  B -->|Accepted| C[Continue ordinary sync]
  B -->|Typed claim or lease rejection| D{Exact receipt complete?}
  D -->|Yes| E[Return acknowledgment with tunnel URL]
  E --> F[Operator clears durable receipt]
  F --> G[Next sync requests work without claim]
  D -->|No| H[Return original rejection]

Loading

_{Reviews (7) · Last reviewed commit: "fix: retain release session wire compati..."}

[alongubkin]

@greptile review. Both findings are fixed: recovery handles reconciliation rejections and preserves the configured tunnel endpoint. Added a real HTTP/SQLite Operator receipt compatibility test. Please review the latest commit.

[alongubkin]

@greptile review. The latest generated contract reuses sync release with an explicit acknowledge-completed mode and removes the extra endpoint. The claim-capable embedder hook is documented; SQLite does not issue execution claims. Please reassess the latest commit.

[alongubkin]

The latest outside-diff finding conflates two different API surfaces. client-sdks/platform/openapi.json and its Rust copies describe the upstream API consumed by embedders; they do not describe or route requests to the Manager release handler. The Manager API has its own contract under client-sdks/manager and its ReleaseRequest does not gain this mode. The upstream release server implements the scoped exact-terminal acknowledgment mode; the Manager store hook is the capability boundary, and the Manager handler remains strict. The generated upstream contract was copied from its source generator, not hand-edited. @greptile please reassess this finding and the latest commit.

[alongubkin]

@greptileai review. Please reassess the outside-diff finding in comment 5987334141: it compares an upstream API client contract against an unrelated Manager server route. These upstream client contracts are not served by the Manager. Its own contract under client-sdks/manager is unchanged. No Manager client can send the new mode through these upstream client files. The upstream source handler implements exact terminal pull acknowledgment before ordinary release.

[alongubkin]

@greptileai review. The upstream release contracts and Manager API are separate surfaces; the outside-diff concern uses the wrong server handler. The latest contract also preserves the original release session type. Manager sqlite/openapi tests and the Operator HTTP/SQLite receipt test pass.