Add independent HTTP lifecycle client and integration guide - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ship integrations need a lifecycle example that runs without Akiroo or direct storage access. Add a dependency-free Node HTTP client and usage guide for submission, workspace progress, explicit decisions, cancellation and follow-ups using existing public-facing routes.
The example retains stable request IDs, does not automatically retry mutations, refuses stale decision responses, reads cancellation state back, and never follows authenticated redirects. It documents the distinction between current dashboard-compatible endpoints and a versioned SDK.
Validation: real local HTTP contract test covers auth refusal, stale decisions, redirect refusal, stable request fields and cancellation state. Lint passed; 1,411 runtime and 101 script tests passed (one existing skip). Live standalone lifecycle acceptance is still pending; this PR does not claim it.