4.16.0

4.16.0

• Completion payload planning reads the optional advertised
  limits.max_workflow_task_completion_bytes separately from ordinary request
  and per-value limits. Individually valid inline batches no longer demand
  unavailable external storage when the Server advertises this allowance and
  storage is explicitly unconfigured, disabled or unsupported. Missing fields
  retain the conservative ordinary cap; malformed fields refuse completion
  planning before uploads. Published Rust 4.16.0 with native Server 3.9.1
  passes the Linux amd64/SQLite installed Worker controls: 300 × 10 KB inline
  arguments, a 60 × 450 KB rejected batch with zero partial activities, and a
  successful follow-up on the same worker. Exact tuple and acceptance receipt.

• Worker metrics emit the revision-2 schedule-to-start histogram in seconds
  for workflow and activity claims when the Server advertises
  claimed_task_ready_age. Missing or invalid producer values are omitted.
  Prometheus export uses only the task kind and task queue labels.

The same published tuple passes all seven shared worker metrics and the
registry-only lifecycle/deadline controls. The larger completion allowance
requires the explicit discovery field; older producers retain the conservative
ordinary cap. Caller-key #216
and native timeout-cleanup runtime acceptance remain separate.