v0.36.0

Changed

• ankra exec and the ankra dev shims forward GOMEMLIMIT. A Go build
  that CI holds to a soft memory ceiling (ankra-cli's own workflow sets
  GOMEMLIMIT=5GiB for the 105k-line ankra/cmd compile) can now be held to
  the same one in the Ankra Workspace: set it here and the remote command
  sees it. Unset, the workspace's own default applies (five eighths of a run
  slot, 5GiB in a workspace of 8 GiB or more). Platforms older than the
  allowlist change refuse the variable with "This environment variable
  cannot be forwarded"; unset it for one command to run there.
• A node-group write submitted without --wait now says where a late
  refusal is recorded. The platform can accept a node-group change (an
  instance-type resize, scale, add, delete, labels, taints or autoscaling) and
  then have the provider refuse it, for example when the requested server type
  has no stock in the cluster's location. That refusal is recorded as a failed
  node_group_write operation carrying the provider's reason, and the
  "submitted" output (and the hint in -o json) now names
  ankra cluster operations list --failed --cluster <id> to read it. With
  --wait the refusal still fails the command with the provider's reason.
• ankra org usage says why a closed month's vCPU line has no amount. A
  closed month with no invoice reads "no invoice for this month, so unknown"
  (never zero), a day or part of a closed month reads "priced on the whole
  month's invoice; view by month", and an invoice that does not price the line
  reads "invoice does not price it", instead of unpriced (<basis>).