Ship CLI 0.4.0, the first build that targets /api/v1

Ship CLI 0.4.0, the first build that targets /api/v1

The base-path consolidation (#214) and the rename (openagents.com #212)
both landed, so the CLI reaches /api/v1 through one constant and the
server answers /api/v3 through its alias either way. This is the
version that carries them (#213). The pinned repositories contract
already regenerated with the rename and its SHA-256 still matches.

Publishing the package to npm stays an owner action.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GoYpb8FEmdxVErsv7ABCYi

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GoYpb8FEmdxVErsv7ABCYi

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

modified packages/openagents-cli/package.json

Diff

1 file changed, +1 -1

{
  "name": "@openagentsinc/cli",
  "version": "0.3.5",
  "version": "0.4.0",
  "private": false,
  "description": "Effect TypeScript command-line client for OpenAgents repositories",
  "keywords": [

1	1		`{`
2	2		`"name": "@openagentsinc/cli",`
3		-	`"version": "0.3.5",`
	3	+	`"version": "0.4.0",`
4	4		`"private": false,`
5	5		`"description": "Effect TypeScript command-line client for OpenAgents repositories",`
6	6		`"keywords": [`