#241–#245, the five findings from the outside review of the web UI.
- #241 builds — a run row led with a ten-character sha.
build listresolves each distinct commit's subject in onegit logand returns it assubjecton every build, so the capability is on every surface rather than the page alone. The row leads with the subject, the sha follows as metadata, and a build whose commit is gone falls back to the sha. - #244 builds — the list was capped at the newest 50 matching builds
with the window unstated, so filtering to a sparse status reached
much further back within the same cap and appeared to raise the run
count.
build listtakes--limit/--cursor, the keyset cursor the other list commands have; without the flags it returns the newest 50 as before. The page asks for 30, offers "older" carrying every filter, and says its count is this page's when there is another. - #242 profile — the About text and the year of squares sat above the
repository list and pushed it below the fold.
/{owner}is the repository list now; About, Activity and an organization's People are tabs beside it under/-/. One handler and one template, because all four read the sameprofile show. A tab with nothing on it is not offered and its URL is a 404. The org member and team forms moved with the People tab, so their results redirect there. - #243 explore — a search showed a shorter list and nothing else. The page carries the line the builds page already had: count, active query, clear. An empty filtered list says nothing matched rather than that the instance has no public repositories.
- #245 landing — the picture was !315, closed without merging, review panel empty, alt text promising reviewers that were not there. It is !450 now: merged, two CI checks reporting success with how long each ran, an approval, and a description a stranger can follow. The picture is a figure with a caption.
Parity rows updated: build list paging, profile sections as tabs, and
the pagination and profile prose.