Add a composition test that sends a gateway 500 relaying an upstream 401
through the real Anthropic SDK, so a change in the SDK's rendering fails
here instead of reaching the classifier unnoticed. Label the unit matrix,
assert the preserved message, and pin a 400 that quotes a retryable 429.
Document the remaining text-classification gaps in the README.
Refs #8182
The forge subsystem page gains the overview and viewed mark types and
contracts, and the generated Cordis, configuration, and event catalogs
follow the new service methods and the maxViewedFiles option.
A change request's view of all its commits reads and saves viewed marks
on the code host, disabling a checkbox while its mark is saved and every
checkbox when the marks cannot be read; local changes and chosen commits
keep their marks in the browser. The expanded card shows one row per
fact with a glyph and its value: checks open a grouped menu that reruns
failed ones, the review row shows reviewer avatars and requests reviews,
the merge row updates a head behind its base at the displayed head, the
changes row counts unresolved threads, and linked issues take one row.
Status reads add review requests, latest reviews, closing issue
references, and whether the viewer may update or rebase the head.
Viewed files are read through the files listing, bounded by the new
maxViewedFiles, and set with markFileAsViewed or unmarkFileAsViewed after
a head check. Failed GitHub Actions runs are rerun through the REST API,
reviews are requested with requestReviewsByLogin, and branches are
updated with expectedHeadOid. Every mutation goes through the sender
review writes use, now in mutation.ts.
ChangeRequestSnapshot now carries the reviewers, linked closing issues,
branch update methods, and the viewer's rights to request reviews and
rerun checks; each check names its rerun. Providers may implement viewed
mark reads and writes, failed check reruns, review requests with a
reviewer search, and head-pinned branch updates. The registry fails an
action a provider lacks without polling, and polls a watched change
request after every action the provider answered.
pi-ai's SDK-backed providers render an HTTP failure as `<status> <body>`.
A gateway 500 that embeds its upstream's 401 in the body matched the AUTH
rule before the 5xx rule, so Chat reported an invalid API key and the
retry policy gave up. When a message leads with a 4xx/5xx status, the
status rules now read only that status; other wordings still scan the
whole message.
Refs #8182
A narrow changes toolbar wrapped its controls onto a second row and the
header's buttons broke their labels across two lines. Side by side, a
right-side comment was placed with clamp(10px, 100% - 700px, 50% + 10px),
so below about 1,420 px it crossed into the left column, and only one
comment editor could be open at a time.
The toolbar now keeps one line. observeToolbarFold measures what each
fold level needs and sets data-fold to the shallowest level that fits:
level 1 moves the line totals, expanding all files, two columns, and
wrapping into a More view options menu, level 2 the test file switch,
with the viewed progress shown as a ring and a count, and level 3
refresh; at level 3 the file list entry shortens its label. The menu
lists the controls of the level shown when it opens. Measuring instead of
fixed widths keeps every locale on one line: the full toolbar needs about
650 px in Chinese and nearly 800 px in Russian. Header buttons keep their
labels on one line.
Side by side, the comments that end on a row now sit in a row of two
cells under its columns, each continuing its line's gutter and
background, so a left and a right comment share the row. Any number of
editors can stay open; choosing an open editor's range focuses it.
Resolves#8176
`typescript/no-confusing-void-expression` rejects the shorthand arrow that
returns `rmSync`'s void expression; the staged lint configuration does not
enable type-aware rules, so only the full lint gate caught it.
The Windows coverage lane provisions the locked Electron binary through the
runner proxy. A gateway timeout on that one fetch failed the required lane
before any test ran: on 2026-11-09 four jobs on three branches stopped at
`504 (Gateway Time-out)` for the release archive, while other jobs fetched the
same archive minutes later (2.5 s from a warm cache, 14.7 s cold).
`electron-install` now declares two retries with a 15 s wait, and the
aggregate executor repeats a failed gate only when it declares `retries`. A
gate the fail-fast signal terminated is not repeated, and the returned
duration covers every attempt.
A write to a thread or comment now reads, in the head check, the pull
request that holds it and is refused without a mutation when that is
another pull request. Submitting the pending review keeps the
submission to reconcile, so an unknown outcome blocks a second review.
GraphQL errors count as refusals only when every type names one, so a
GitHub timeout reports an unknown outcome. Pending reviews are found
by viewerDidAuthor among up to 100, without the unused commit field. A
resolved thread stays open while the reader writes in it, unsupported
writes no longer poll, and the docs state the partial two-step write.