{"version":"2.1.191","anchor":"bug-fixes","canonical_anchor":"bug-fixes","heading":"","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191\/e\/bug-fixes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191","markdown":"- Atomic write error handling improved: if the temp-file close fails after a write error, the original write error is preserved and re-thrown with the close failure attached as context, rather than losing the original error. (search for `\"atomic write failed first:\"`)\n\n- Config file read no longer reports `\"resetting to defaults\"` when the file is corrupted \u2014 it now auto-repairs from cache or reports backup location accurately. (search for `\"Config file corrupted:\"`)\n\n- Cloud session registration no longer silently swallows HTTP 503 errors; 503 is now treated as a retryable server error rather than a client error, matching the intended error-handling strategy. (search for `\"registerWorker failed\"`)\n\n- Memory byte-cap stripping now correctly accounts for byte sizes when deciding which media to remove, and reports removed byte counts to telemetry (`tengu_media_byte_cap_stripped`). Previously only item counts were tracked, which could leave the cap under-enforced for large images.\n\n- `\/design-login` credential rejection now includes a more specific message for HTTP 403 responses: `\"token may be missing a scope this server needs \u2014 run \/design-login\"`, distinguishing scope issues from full re-auth requirements. (search for `\"token may be missing a scope this server needs\"`)"}