Move the engine core into core/, a project of its own (pplus-core)

What programs mean (the languages, translators, Mojo checker and
interpreter, prover, fuzzer, machine model, catalog problems and the Mojo
corpus with godbolt's stored answers) was mixed into the site's tree, so a
change to the prover and a change to a button went through the same gate
and the same docs. This moves all of it under core/, laid out as its own
repository, ready to be extracted with its history and pinned here as a
git submodule.

- core/: src/{engines,services,sync,mojo,exercises,curriculum,common},
  mojo/, syntax/mojo.xml, its tests (with Workspace and workForProblem in
  place of the site's Session), scripts (corpus pipeline, play, the
  exercise and probe starters, engines export/diff), and its docs
  (engines, trust, mojo-corpus, exercises, coverage). Its own pixi.toml,
  package.json, README, AGENTS.md and CI workflow.
- core/tests/boundary.test.mjs: library modules use no DOM, import no
  page widget, and import nothing outside src/.
- core/scripts/cli.mjs: pixi run cli check|run|prove|fuzz|translate.
- core/scripts/dafny.py: Dafny 4.11.0 pinned by version and SHA-256 per
  platform, fetched into .tools/ (pixi run dafny-fetch, pixi run dafny).
- The site imports core only as #core/<path>.js: an import map in
  index.html, "imports" in package.json for node, core's declarations for
  tsc. The site's TypeScript builds core first (npm run build).
- assemble.sh, the Quarto engine copy, the render cache key, check-pages,
  quarto-export and quarto-css read core/dist and core/mojo; quarto-css
  copies core's syntax/mojo.xml into the extension.
- Site tests that covered engines moved to core; the rest keep Session.
- README, AGENTS.md, docs/app.md, docs/deploy.md and the CI workflow
  describe the split (checkout with submodules; core's tests and corpus
  status run against the pinned commit).

Gate: site 110 pass; core 307 pass; corpus status --strict passes.
Manual check: the assembled site opens Bridge (count-base-proved),
Developer and Hardware (count-base) with the editor, the stepper and the
board, and no module errors.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FgvbRdoEheAHqsRmr2WuKZ
This commit is contained in:
alexmandClaude committed 2026-10-05 05:43:58 +00:00
1 parent f43bbfe0cf
commit 82e18f7966
1567 files changed
+3670 -981

No files matched your search

+7 -2
View File
@@ -1,11 +1,16 @@
#!/usr/bin/env sh
# Assemble the deployable site into ./site: what a static host needs (the page, its styles, dist/, and the Quarto extension).
# Assemble the deployable site into ./site: what a static host needs (the page, its styles, dist/, pplus-core's
# core/dist/ that the page's import map points at, and the Quarto extension).
set -eu
cd "$(dirname "$0")/.."
rm -rf site && mkdir -p site
cp -r index.html styles.css styles dist site/
rm -f site/styles/course/README.md # the provenance notes stay in the repository
rm -rf site/dist/curriculum # a test fixture for the interpreter; the site no longer loads it
# pplus-core's built modules, without source maps, declarations, or the lesson corpus (a test fixture)
mkdir -p site/core
cp -r core/dist site/core/
find site/core/dist \( -name '*.map' -o -name '*.d.ts' \) -delete
rm -rf site/core/dist/curriculum
# the Quarto extension, which the "With Quarto" page loads (pplus.css, pplus.js) and links to, file by file
mkdir -p site/quarto/_extensions
cp -r quarto/_extensions/pplus site/quarto/_extensions/