chore(release): v0.37.0

[arantespp]

Summary

Version-and-changelog only bump of 0.36.0 → 0.37.0, cut with pnpm lerna version --yes --no-push.

@soat/sdk and @soat/cli publish to npm; app, postgresdb, server and website are private and bump in lockstep.

Why minor, not major

This range carries a breaking change (the snake_case wire renames in #1199), and the changelog records it under BREAKING CHANGES. The conventional-commits preset resolves a breaking change under a 0.x major to a minor bump, so the cut is 0.37.0 rather than 1.0.0. Nothing here decides whether SOAT is ready for 1.0.0 — that stays an explicit call.

Contents

Type	Change
Breaking	snake_case stop condition types, delete meta and tool context identity keys (#1199)
Fix	bound loop / sub_orchestration nesting depth (#1197)
Fix	defer replace-cleanup until dependents are re-pointed, and report a leak (#1195)
Fix	let a first price take effect immediately (#1198)

Upgrading callers need the three renames from #1199: the has_tool_call and max_chain_generations stop condition types, the generation_count / trace_count keys on a 409 AGENT_HAS_DEPENDENTS, and the X-Soat-Context-session_id, -actor_id and -actor_external_id tool headers.

Merge instructions

Squash and merge, so the commit landing on main keeps a subject starting with chore(release):. Every job in main.yml re-checks that prefix on head_commit.message; a default merge commit is titled Merge pull request #NNN…, which would silently skip the tag push, the npm publish and the Docker image while the PR still shows green.

Per .claude/rules/release.md, pr.yml skips the build, smoke and tutorials jobs on a chore(release): title, since these commits were already validated on main. The 49-file diff in #1199 passed the full suite there, including smoke and tutorials.

After merging, confirm the main.yml run actually started for the merge commit rather than being skipped.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DRwsGecUbNX8PcAzZ5L2ov

---

Generated by Claude Code