v1.7.7
Cloud Agent runs fall over to a backup tier
v1.7.7 makes a Cloud Agent run survive losing its model tier, and gives a failed code review a visible ending.
A run keeps going when a tier is unavailable
A siGit Code Cloud Agent run used to ride a single model tier, so when Onde Cloud could not serve that tier the whole run died with it. A run now carries an ordered list of up to three fallback tiers behind its primary one. When a request hits a transport error or an upstream 404, 429 or 5xx, it is sent again on the next tier; the choice is made before the first response byte, so a streaming request fails over the same way. The hops share one unit of the run's request budget rather than spending a fresh one each time, and ordinary responses are passed straight through untouched.
Each run records the tier it asked for, and a run re-dispatched by hand can name a tier to use instead of the default.
A failed code review leaves a note
A review that ended up failed used to leave the pull request with nothing. The person who asked got no answer, and there was no trace to debug from. A review that moves into failed for good now posts a short notice with the dashboard link, naming the author first when the review was requested. The notice gives the reason by error class only, so nothing about what runs behind a tier reaches a public comment. A transient error that will be retried posts nothing, and neither does the emergency stop. The notice is best effort and never stands in for the original error, and the reviewer's own failure note is kept out of the conversation fed back to the model.
Review replies survive a repository move
Reviews are filed under a repository's full name. Transferring or renaming a repository changes that name while the pull request keeps its number, its threads and its comment ids, so a follow-up reply or a resolution landed on threads the job could no longer find, and it returned without a word. On one moved repository, five replies and two mentions went unanswered and a requested review approved the head with those threads still open.
The webhook now tells the job which comment opened the thread an event is about. When that comment sits under the repository's old name, the job refiles the pull request's reviews under the new name before it looks them up, so the first reply or resolution after a move carries the reviews across. A row that would collide with a review already under the new name is left where it is.
Release masters: @setoelkahfi and @sigit.