docs: prep vesseld v0.1.0 GA (Status, TCP quickstart, vesseld-with-history demo)#92
Merged
Conversation
- README.md: rewrite Status section against shipped reality (durable Postgres/SQLite checkpoints, OTel, Prometheus /metrics and the seven-suite eval/ harness are all in place); update the v0.2/v0.3 milestone descriptions to align with the refreshed roadmap. Add a TCP + bearer-token Quickstart snippet so remote access is documented before users hit it. - examples/vesseld-multi-vessel/README.md: add a "Remote access via TCP + bearer token" section with the tokenFile YAML and a curl example, and an mTLS-tracked-for-v0.2 caveat. - CHANGELOG.md: add vesseld/v0.1.0 GA, vesseld/v0.1.0-rc.2 (vessel rc.2 dep bump + supervisor races fix), and vessel/v0.1.0 GA entries with known-limitations callouts deferred to v0.2. Co-authored-by: Cursor <cursoragent@cursor.com>
Companion to examples/vesseld-multi-vessel/ (which shows multi-agent + Kanban delegation); this one demonstrates how a Vessel preserves conversation transcripts across turns via a shared HistoryStore keyed by request context_id. The README is explicit that v0.1.0 only ships ref: buffer (in-memory) — cross-restart persistence requires the Compacted flavor + SessionStore wiring on the v0.2 track, with a pointer to examples/chatbot-with-recall/ for the in-process pattern callers can use today. Validated with `vesseld validate -R` and `vesseld plan -R`. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Summary
Three doc-only changes to clear the runway for cutting
vessel/v0.1.0andvesseld/v0.1.0GA tags. No Go code touched.README.md— rewrite Status section against shipped reality (Postgres/SQLite checkpointers, OTel, Prometheus/metrics, seven-suiteeval/harness all in place); refresh the v0.2 / v0.3 milestone descriptions; add a TCP + bearer-token snippet to the Quickstart so remote access is documented before users hit it.examples/vesseld-multi-vessel/README.md— add a "Remote access via TCP + bearer token" section with thetokenFileYAML and acurl -H "Authorization: Bearer …"example; mTLS explicitly tagged asv0.2scope.examples/vesseld-with-history/(new) — single-vessel demo that wires a sharedHistoryStore(ref: buffer) so the agent remembers earlier turns of the samecontext_idconversation. README is explicit that v0.1.0 only ships in-memory buffer history; cross-restart persistence is deferred to v0.2'sCompactedflavor +SessionStore.CHANGELOG.md— addvessel/v0.1.0,vesseld/v0.1.0-rc.2(vessel rc.2 dep bump + supervisor race fix), andvesseld/v0.1.0GA entries with known-limitations callouts.Test plan
make vet— clean across all modulesmake test-e2e—tests/e2e/vesseld(29.5s) +tests/e2e/retrieval(0.5s) both greentests/quality/vessel— 1.3s greenvesseld validate -Ron bothvesseld-multi-vesselandvesseld-with-history→okvesseld plan -Ronvesseld-with-historyconfirmsHistoryStoreref resolutionFollow-up
Once this merges, the planned tag sequence is:
release-vesseld.ymlthen auto-builds the 5-arch matrix + SHA-256s.auto-tag.ymlis a no-op for this PR (filters onsdk|sdkx|voice|vessel/**paths, none of which we touched).Made with Cursor