Walking the site as a student (desktop, a phone-width screen, dark) found
these. Each is small; together they are what got in the way.
Defects:
- Opening a problem in the Bridge saved the generated Mojo over the
exercise's own program. The workspace fills every pane's editor as it
opens, the editor reported that as typing, and the Bridge's read-only
Mojo pane holds the generated text. Developer then showed generated
Mojo labeled "your edits", and the problem counted as edited. The
value setter now marks its change as a load, the change listener
leaves loads out, and a Bridge session refuses a Mojo edit.
- A page opened at #/#problems or #/#reference stopped about 45px past
the heading: the fonts arrived after the place was computed. A page
built this moment goes straight to its section and finds it again
when the fonts are in; a page already on screen still scrolls there.
The workspace:
- With no run to step, the Run view said "Nothing to run yet." It and
the stepper now give one reason (src/core/norun.ts): how many problems
the stepped pane has and the first with its line, with a button to the
line and the Problems list; or that the pane is empty.
- In the Bridge the dock starts at about a quarter of the height (it
holds a call, a line of output, a short list), so the code and the run
get the room. Developer keeps a third for the compiler's answer. A
double-click on a divider returns to the area's default, not to the
student's last position.
- The reason a pane is not in step wraps instead of ending in an
ellipsis, and a button in the pane's head keeps its words on one line.
- A problem that does not exist keeps the site's navigation and links
the problem list.
- Help, the theme switch and the stepper's first, back, step and last
buttons have names a screen reader can say.
A phone-width screen:
- The toolbar is three rows in every area and on every tab (it was four
or five): the mark, the area, help and the theme; the problem,
Versions and Reset; the actions. About 30px more of the code shows.
An embedded workspace keeps its own toolbar.
- The Share dialog puts each row's name above what it holds (a note had
been squeezed to a word per line), and the Versions menu opens across
the screen instead of running off its right edge.
- The stepper's speed label stays with its slider.
Checked by hand, in headless Chromium at 1440x900, 1366x768, 390x844 and
320x640, light and dark: each state above before and after; the editor
has line numbers and highlighting; the stepper steps; embeds
(playground, trace, Developer) are unchanged; 31 smoke scenarios clean
but the ones that err on purpose.
The deploy job's directory under /srv/www defaulted to the repository's
name. This repository is pplus-web and the site is served from
/srv/www/pplus, so the first job that passed here published to
/srv/www/pplus-web and the live site stayed as it was. The default is
pplus; SITE_SLUG still overrides it.
The deploy server is a slow container with other work to do. Its job ran
core's tests, which failed there (no C compiler, no ICU, limits written
for a fast machine), so nothing was published.
- pixi run ci, which the deploy job runs, is the site's tests and core's
mojo-status-strict at the pinned commit. Core's own tests and
everything that builds Mojo are core's gate, on a runner of its own;
pixi run core-test stays for moving the pointer.
- The workflow and docs/deploy.md describe the runner as it is: a new
container for every job, not a host shell.
- core moves to b10a5c8: a pinned C compiler for the Mojo compiler to
link with, a Dafny that starts without ICU, time limits at the
machine's pace, and a prover whose time on the clock is the caller's
(the Prove tab keeps its 3 seconds).