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:
1567 files changed
+3670
-981
No files matched your search
@@ -31,7 +31,11 @@ jobs:
|
||||
runs-on: quarto-deploy
|
||||
steps:
|
||||
# actions/checkout needs node on the host, which the job needs anyway.
|
||||
# core/ is pplus-core, a submodule pinned to one commit; the job's token
|
||||
# must be able to read that repository.
|
||||
- uses: actions/checkout@v4
|
||||
with:
|
||||
submodules: recursive
|
||||
|
||||
- name: Toolchain on the host
|
||||
run: |
|
||||
@@ -41,12 +45,17 @@ jobs:
|
||||
command -v rsync >/dev/null || echo "rsync missing: local deploys fall back to cp, SSH deploys need it"
|
||||
|
||||
- run: npm ci
|
||||
# Builds core (with this repository's TypeScript), then the site, then tests the site.
|
||||
- run: npm test
|
||||
# pplus-core's own tests, at the pinned commit (its CI runs them too; this catches a bad pin).
|
||||
- name: Core's tests
|
||||
run: node --test tests/*.test.mjs
|
||||
working-directory: core
|
||||
|
||||
# The same check as `pixi run mojo-status-strict`: offline, from the stored godbolt answers.
|
||||
# Core's mojo-status-strict task: offline, from the stored godbolt answers.
|
||||
- name: Our Mojo programs pass
|
||||
run: |
|
||||
if command -v python3 >/dev/null; then python3 scripts/mojo/corpus.py status --strict
|
||||
if command -v python3 >/dev/null; then python3 core/scripts/mojo/corpus.py status --strict
|
||||
else echo "python3 missing: corpus status skipped"; fi
|
||||
|
||||
- name: Assemble the site
|
||||
|
||||
Reference in new issue
Block a user