August 2025 monthly summary for developer work across goutils, api, and motion-tools. Delivered robustness improvements and API data enhancements that reduce operational risk, improve monitoring fidelity, and clarify multi-host deployments. Key outcomes include stronger resilience to transient failures, clearer API semantics for multi-machine deployments, richer part metadata for diagnostics, and kept dependencies current to accelerate downstream development. Highlights include: - Cloud Run exporter: Fallback env vars to identify service/revision in Cloud Run Worker Pools, increasing monitoring accuracy and cross-environment consistency. Commit: bde94ecac9bc73d6c096e3f359a5089deb6a8559 - Secret Manager fetch resilience: Added exponential backoff with jitter and per-retry timeout up to 500ms for secret fetches, improving reliability under transient failures. Commits: aac3c7b951f303bda993e601ec148ef37f8d04b8; 9251174ab6301afcb953b3400ad4815f07bb3435 - API clarity: AppType enum (APP_TYPE_UNSPECIFIED, APP_TYPE_SINGLE_MACHINE, APP_TYPE_MULTI_MACHINE) introduced with app_type in GetAppContentResponse to differentiate single vs multi-machine apps. Commit: 51464aa1b2f0b4c6bcbcbbd09a5f53c60a54a629 - Part metadata enrichment: DNS names added to PartSummary and is_main_part flag to distinguish primary parts. Commit: ffe70d06ecd1ba2706cd2dcf552c6febb799f96c - Dependency modernization: RDK bumped to 0.90.0 with accompanying patch changeset to align core libraries. Commit: afecbdf8ee6e1a58f190c088a2fb396ad441b5f4 Overall impact: Reduced runtime exposure to transient failures, enhanced API ergonomics for customers building against multi-machine deployments, improved observability and diagnostics, and maintained alignment with upstream dependencies to support longer-term maintenance and feature velocity.