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.
7.6 KiB
Changelog
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning. No version has been tagged yet. What programs mean is pplus-core's, and its changelog has those changes; this one says what changed on the site.
[Unreleased]
Changed
-
The site runs on pplus-core for Mojo 1.2.0: generated Mojo the real compiler accepts and that prints what the pseudo prints, 18 prover rules that proved what a run breaks closed, and the interpreter audit's fixes. The pin is consistent again: a fresh clone's tests pass.
-
The deployed site carries its license and the third-party notices (
LICENSE.md,NOTICE.md,THIRD_PARTY.md). -
Compile & run asks before the first send to godbolt.org, builds every program one stated way (
--target-cpu x86-64-v3 --fp-mode contract=off, shown on each compile), and shows the kept answer when the source, the input and the level are unchanged. -
The site serves its own fonts; nothing is asked of any other server except godbolt.org by Compile & run. A Content-Security-Policy and the other security headers are in
docs/Caddyfile. -
The copy says what the site holds and no more: what runs in the browser and what does not, that the Hardware area is a model machine, and what "verified" means.
-
A shared link never saves over the reader's own work on the same problem.
-
Below 700px a workspace shows one part at a time; every page has a main landmark and a heading, and the contrast findings are fixed.
-
With no run to step, the Run view and the stepper say why: how many problems the pane has and the first one with its line (and a button to the Problems list), or that the pane is empty. It said "Nothing to run yet."
-
In the Bridge the dock starts at about a quarter of the height, not a third, 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 it to the area's default.
-
A phone-width toolbar is three rows in every area (it was four or five): about 30px more of the code on screen. The stepper's speed label stays with its slider.
-
A problem that does not exist keeps the site's navigation and links the problem list.
-
The icon-only buttons (help, the theme, the stepper's first, back, step and last) have names a screen reader can say.
-
The Quarto extension's syntax definitions state their license as Apache-2.0 (they said MIT), and
THIRD_PARTY.mdsays that the stylesheets and syntax definitions that came from the course are under this repository's copyright and license. -
The deploy job is light: it runs the site's tests and core's
mojo-status-strictat the pinned commit, then publishes. It no longer runs core's own tests (15 to 22 minutes on the deploy server, where they also failed for want of a C compiler and for the server's speed, so the site was not published). Core's tests and everything that builds Mojo are core's gate, on a runner of its own; runpixi run core-testbefore moving the pointer.docs/deploy.mdand the workflow describe the runner as it is, a new container for every job, not a host shell. -
The site runs on a pplus-core whose gate does not depend on the machine: a pinned C compiler for the Mojo compiler to link with, a Dafny that starts without ICU, and a prover whose time on the clock is the caller's (the Prove tab keeps its 3 seconds).
Added
THIRD_PARTY.md, with the copyright notice of every package bundled into the editor, and a test that holds it to the bundle, the copied stylesheets, the fonts and the locks.- The Apache License 2.0, a NOTICE, contributing rules, a security policy, a code of conduct, and a citation file.
- A footer with the license, the notices, the disclaimer about Modular, the build's commit, and "What this site stores and sends", each statement held to the code by a test.
pixi run caddy-checkserves an assembled site with a real Caddy underdocs/Caddyfileand holds its headers, caching and missing-path answers;pixi run release-checksays whether the three repositories' pointers line up;site/build.jsonnames the three commits a site was built from.- Tests for the copy, for every badge having a row in core's
docs/trust.md, for what the site stores and sends, for load, accessibility and narrow screens.
Fixed
- The deploy job publishes to
/srv/www/pplus, the directory the site is served from, unlessSITE_SLUGsays otherwise. Its default was the repository's name, so the job published to/srv/www/pplus-weband the live site did not change. docs/Caddyfileserved the page in place at a missing nested path, where its own files could not be found (a blank page). A missing page is sent to/; a missing file is a plain 404.- Core's limits reach the site: no text in a pane, a link or a file ends in the engine's own error; a CSV export cannot start a spreadsheet formula; a framed Quarto view cannot make itself taller than 4,000px.
- From the library, the nav's Problems and Reference links opened nothing.
- Open in Hardware on a large compiled function made work whose share link the app then refused to open (its setup was 2.5 MB); core writes the function's data compactly now, and a link for it opens.
- A Quarto page's Mojo run, and the page checker, build Mojo as the app does.
pixi run check-pagesread only shortcode names with one hyphen, so it skipped everypplus-hw-<view>shortcode: a missing file or a misspelled view went unreported.- With
pplus-strict: true, a program withEXPECTlines that does not run at all stops the render; it was only a warning. quarto/README.mdis corrected against the extension:followbelongs to the stepper only, the defaults and limits ofheightandmax, what a non-HTML format gets, whatcheck-pagesruns, and whatquarto-exportwrites.- From core: brackets that each hold a long chain are one
too-deeperror in the pseudo pane; they ended in the engine's own stack error. - Opening a problem in the Bridge saved the generated Mojo over the exercise's own program, so the Developer area then showed the generated text labeled "your edits" and the problem counted as edited. Text the app loads into an editor is no longer reported as typing, and a Bridge session refuses a Mojo edit.
- A page opened at
#/#problemsor#/#referencestopped about 45px past the section's heading (the fonts arrived after the place was computed); it now goes straight to the section and finds it again when the fonts are in. - On a phone-width screen the Share dialog squeezed a note into a column one word wide, and the Versions menu ran off the right edge.
- The reason a pane is not in step was cut off with an ellipsis; it wraps.
[0.1.0] - 2026-10-06
The first version of the site, as main holds it. Never tagged.
Added
- Three areas: the Bridge (lingo, matho, pseudo and speco, kept in step as you type, with Mojo generated from the pseudo), the Developer area (Mojo with the checker, a Run view of every step, a fuzzer and Compile & run on godbolt.org), and the Hardware area (the code beside a board of registers, memory, caches, the pipeline and the out-of-order core).
- The library page (
#/library): every verified routine with how its checks ended, its pseudo, cases, references and proof, and a way to open it in the Bridge. - A catalog of worked problems, share links that carry the whole state, embeds, and a Quarto extension that renders the views into a page.
- A static deployment:
pixi run siteandpixi run deploy, a Caddy site block, and a CI workflow.
Changed
- The engines live in pplus-core, the submodule
core/; the site keeps its session over core'sWorkspace.