chore: version packages - #763
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
11 times, most recently
from
September 2, 2026 22:37
d44624a to
33bfbb4
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 3, 2026 00:20
33bfbb4 to
3834aa9
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@sapiom/harness@0.13.0
Minor Changes
516f13a: Add durable, path-free Studio project identities and lazy Agent Map workspace state. The authenticated local server now exposes project workspace and root-binding association endpoints, and stores the new catalog at
studio-projects.jsonwith per-project records beneathagent-map/in the configured harness state root. The legacy System Graph and per-agent Canvas remain unchanged.fb2486d: Open Studio Agent Maps as a dedicated planning workspace with a live, project-scoped planning conversation beside the durable map. Planner tabs can resume, start fresh, rename, and end; transcript updates refetch through content-free invalidations, map and planner failures retry independently, and mobile keeps the conversation primary behind an explicit Agent Map sheet.
This release adds variants to the public
BusMessage,UiEventName, andAnalyticsEventTypeunions. Consumers that switch over these forward-extensible event types should retain a default arm so later additive events remain source-compatible.ae0a77e: Resolve the latest saved credential and selected environment whenever Agent Studio creates, resumes, or runs a background Claude session. A confirmed credential removal now clears the launch key, while a malformed or unreadable store preserves the last-known key. Unknown selected environments now fail the affected launch with an explicit configuration error instead of silently routing it to production. Preserve
--no-authas a process-wide opt-out and expose a strict credential-store reader for safe live reconciliation.31bdf89: Expose the shared Agent Map proposal through one capability-authenticated embedded HTTP MCP endpoint. Project planner, assigned-builder, and manual-builder sessions receive identical read, validate, and propose tools through private per-session Claude or Codex launch configuration, with rotation on resume and revocation on exit.
1729542: Prepare crash-atomic, project-wide Agent Map proposal persistence for the SAP-3060 transport, with attributed operation history, bounded session-scoped idempotency receipts, and history-derived stale-write rebasing. Exact results are retained for a bounded retry window, while older same-session request IDs cannot apply twice. Agent Map workspace reads now return a coherent versioned workspace-and-proposal snapshot, and the named browser-safe contracts required by the accepted-delta bus payload are exported from the package entry point.
189eaf1: Open durable Studio projects in a pinned Agent Map workspace and remember the selected Agent Map or agent per user and project. Preferences live in the new
agent-map/studio-workspace-preferences.jsonstate file and are exposed through the path-freeGETandPUT /api/projects/:projectId/current-workspaceroutes. Agent identities remain opaque outside the server, survive authenticated moves, and repair safely when a complete project scan proves that an agent was deleted.ac9a35f: Add trusted, project-scoped Agent Map planner sessions with deterministic
resume-or-create/fresh resolution, focused path-free context, a durable
automatic-greeting state machine, FIFO user input, bounded lifecycle telemetry,
public planner session/greeting state, and per-session ingest capabilities that
cannot be replayed across PTYs or used for host
/apimutations. Rehydratedplanner replacements atomically inherit the exact predecessor FIFO while their
focused brief can reuse an older recorded ancestor.
Breaking: generic
POST /api/sessionsnow strictly rejects unknown fields,so clients can no longer attach planner metadata to a generic create request.
Generic planner input, resume, and adopt routes also reject planner-owned
sessions. Generic adopt additionally rejects every conflicting current owner
or durable historical vendor identity, including ordinary pre-
/clearandpre-
/resumealiases, with a bounded 409 before adapter probing. Migrateplanner clients to the project-scoped open, message, and greeting-retry routes
under
/api/projects/:projectId/planner-sessions.All coding-agent sessions now pin
vendor identity to a durable session owner: conflicting
SessionStartclaimsare rejected. The only rotation exception is a short-lived, one-shot
server-observed
/clearor/resumeterminal gesture;/resumepicker inputmay refresh its soft window only within a bounded hard deadline.
On upgrade, duplicate legacy vendor resume pointers are migrated with the first
persisted
sessions.jsonrow as owner. Later duplicate rows are rewritten withagentSessionId: nulland cannot resume or re-adopt that fenced identity underthe losing row. Provider transcripts and conversation history are not deleted;
start a fresh session in the losing row's directory to continue there.
6bc9d58: Agent Studio now fetches its coding-agent system prompt from the Sapiom backend on session start (
GET /v1/harness/system-prompt), instead of using only the copy baked into this package. Prompt improvements now reach a session after a backend deploy rather than after an npm upgrade. The bundled prompt remains the offline fallback — a non-200, empty body, network error or 5s timeout starts the session on it, exactly as before.The request is unconditional: it fetches configuration rather than reporting usage, so it is not gated on the telemetry opt-in, and it carries no session content, identifiers or API key. Set
SAPIOM_HARNESS_PROMPT_FETCH_DISABLED=1(ortrue) to skip it and always use the bundled prompt — see the README's "Outbound requests" section.Patch Changes
@sapiom/mcp@0.14.0
Minor Changes
--no-authas a process-wide opt-out and expose a strict credential-store reader for safe live reconciliation.Patch Changes
@sapiom/tools@0.35.0
Minor Changes
5808e8f:
contentGeneration: an async image or video job that terminally FAILS is now distinguishable from one that is merely slow (SAP-3097).wait()fails fast — live in this release. Every non-OK poll response used to be treated as "still generating", so a job that failed in three seconds burned the caller's wholetimeoutMsand then threwImage generation did not complete within 300000ms— the opposite of what happened.wait()(andvideo.create, which polls the same way) now reads the queue's terminal state and throws the newContentGenerationFailedErroras soon as the job fails, carryingrequestIdand the provider's ownproviderError. A plainErrorabout the timeout now means only what it says: the job was still running when you stopped waiting.ContentGenerationFailedErroris exported from@sapiom/tools.A transport blip still keeps polling. A non-OK result poll is ambiguous on its own, so it is disambiguated against the status endpoint, and anything short of an explicit terminal marker keeps the poll going.
generationErroron the resume payload — a type, populated by the platform.ImageResultPayloadandVideoResultPayloadoutputs gaingenerationError?: string. A terminal provider failure has been arriving onstorageError— the field documented as "persisting this output failed" — so a resumed workflow step concludes storage broke when in fact nothing was ever generated. The platform sends one field or the other, never both, so a step can branch without string-matching a message.Nothing in this package produces
generationError; it appears on the wire once the corresponding gateway change is deployed, and a step running against an older gateway still sees a generation failure onstorageError. CheckgenerationErrorfirst and fall back tostorageError— that reads correctly on both sides of the deploy.The type is also what makes
VIDEO_RESULT_SIGNAL's documented "carries the result either way (ready OR failed)" contract expressible; the payload previously had nowhere to put the failure.IMAGE_RESULT_SIGNALcarries the same contract.Patch Changes
images.launchin the content-generation README: the launch handle,wait()and its 2min/2s defaults,IMAGE_RESULT_SIGNAL,ImageResultPayload, and when to preferlaunchovercreate. The async image path shipped in 0.25.0 with no README coverage. Also corrects the pause/resume snippets in both the image and video sections —defineStep'spauserequiressignalandresumeStepand belongs on the pausing step, and the pause/resume helpers are imported from@sapiom/agent.@sapiom/agent@0.13.1
Patch Changes
@sapiom/agent-core@0.13.4
Patch Changes
@sapiom/agent-studio@0.1.22
Patch Changes
@sapiom/cli@12.0.0
Patch Changes
@sapiom/sandbox-preview@0.1.21
Patch Changes
@sapiom/harness-desktop@0.4.3
Patch Changes