7 Commits
Author SHA1 Message Date
alexm 5202c96318 The home page shows at once
It was blank until every module had loaded and the page's examples had
been run, a fuzzer's report among them (about a second of work): first
paint came 1.3 seconds into a repeat visit and about 3 into a first one.

- The assembler draws the home page once, in Node, with the app's own
  homeView, and puts it inside #app. The browser paints it with the
  HTML and the stylesheet.
- When the app has loaded it draws the page again, with its controls,
  and puts it in the prerendered one's place; the fuzzer's reports and
  the proof's counts are copied from the prerendered page, not worked
  out again.
- The prerendered page shows only on the home address: the page's first
  inline script marks it before the first paint, and without the mark it
  stays hidden, so an embed or a problem's address never shows it. That
  script changed, and its hash in docs/Caddyfile with it.

Served locally, first paint is at 0.1 to 0.2 seconds and the page with
its controls at 0.2 to 0.3; both were at 1.2 to 1.4.
2026-11-13 07:28:38 -05:00
alexm 7000662539 A proof's time limit is the reader's to set
Build, test, deploy / site (push) Successful in 7m44s
The Prove view gives each routine 3 seconds on the clock. On a slow or
busy device that runs out before the proof does, and claims stay open
with nothing to say why.

- The view says when the time, not the proof, stopped the checker, that
  what was not finished is open and not disproved, and offers to prove
  again with the next longer time. The setting is at the foot of the
  view: 3, 10 or 30 seconds or 2 minutes for each routine, kept in the
  browser (pplus.proveclock).
- A proof rendered with Quarto takes prove-seconds on the shortcode or
  pplus-prove-seconds for the site, and the render warns when the time
  ran out.
- The home page's own example is proved with no time on the clock, and
  the tests that hold a proof's outcome give it time to spare, so
  neither depends on the machine.
- core moves to 38e6e2c, whose report says which routines the clock
  stopped.
2026-11-13 07:01:35 -05:00
alexm d1955ad358 Run the deploy job's smoke test by default
Build, test, deploy / site (push) Successful in 7m22s
After publishing, the job asks the live site for its version and fails
if it is not the commit it published. The test ran only when the
repository variable SITE_URL was set, and it was not, so a job that
published to a directory nothing serves passed. The address defaults to
https://pplus.scient.ing; SITE_URL still overrides it.
2026-11-13 06:50:58 -05:00
alexm 3c5097d9d0 A UX pass over the workspace, and two defects it turned up
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.
2026-11-13 06:27:00 -05:00
alexm eb77cf6902 Publish to the directory the site is served from
Build, test, deploy / site (push) Successful in 6m43s
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.
2026-11-13 06:26:50 -05:00
alexm 3ebf2e2203 A light deploy job, on a core whose gate does not depend on its machine
Build, test, deploy / site (push) Successful in 9m10s
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).
2026-11-13 06:14:46 -05:00
alexm e092cb029c Initial commit
Build, test, deploy / site (push) Failing after 15m13s
2026-11-12 22:24:02 -05:00