Nexora Agent 1.3.2

What

The documented spend guard is now real. Nexora 1.3.2 wires the per-run cost limit into the agent
runtime: README and earlier changelogs advertised a working "financial spend guard (per-run
micro-USD budget)", but the only production entry point passed None, so the limit could never be
set. It can now be set from Settings, and every new agent run reads it.

Changes

• New setting agent.spend_limit_micro_usd with a "Run cost limit (micro-USD)" field in the
  Provider & model settings section. Empty means no limit; a positive integer caps the spend of new
  agent runs.
• The stored value is resolved backend-side on every run, so the guard also applies to runs started
  outside the settings UI.
• Fixed: the terminal spend_limit_exceeded run state, the pricing/metering code and the run-steps
  UI were already shipped but unreachable in a release build.
• No schema change, no migrations.

File	Size (bytes)	SHA256
Nexora_1.3.2_x64_en-US.msi	6 995 968	aed4de2ae783b356f3add050f11c3d19368dcedb31bc0b2486854ccf6f3b30f9
Nexora_1.3.2_x64-setup.exe	5 018 047	1e329816bb1b2114383ea61c1bf8d14a8f8b5f6d29aac59625c4565da44e5bee

Compare link: v1.3.1...v1.3.2

Notes

• Out of scope: F-1 (no frontend test framework), D-1b (attachment path provenance and hash
  pinning), B-6 (comment encoding), context compaction, and the agent-runtime transport rework.
• Migrations: none. Schema unchanged since v6; the spend columns shipped with v5 in an earlier
  release.
• Base ba0ebae.