Files
pplus-web/scripts/quarto-export.mjs
T
alexmandClaude 82e18f7966 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
2026-10-05 05:43:58 +00:00

47 lines
3.0 KiB
JavaScript

#!/usr/bin/env node
/**
* Put a program from mojo/local/ next to a Quarto page, with everything the playground shows for it:
*
* pixi run quarto-export demo ../site/programmingplus/demo
*
* writes into that folder
* demo.mojo the program, header and all (the shortcode leaves the header out of the pane and listing)
* demo.asm the compiler's x86-64 for it, as the x86-64 pane shows it (from src/mojo/generated/listings.ts)
* demo.setup the setup block that goes with it: the arguments' registers and the listing's data
* and prints the shortcodes that embed the whole playground with them, and that run it with the page. Run `pixi run --manifest-path core/pixi.toml play demo` first so
* the listing is current; without one (no godbolt answer yet, or the program has no function of its own
* left at this build), only the .mojo is written and the shortcode says so.
*
* Every option the shortcode takes is at the top of quarto/_extensions/pplus/pplus.lua.
*/
import fs from 'node:fs';
import path from 'node:path';
import { fileURLToPath, pathToFileURL } from 'node:url';
const ROOT = fileURLToPath(new URL('..', import.meta.url));
const [name, outDir] = process.argv.slice(2).filter((a) => !a.startsWith('--'));
const die = (m) => { console.error(`quarto:export: ${m}`); process.exit(1); };
if (!name || !outDir) die('usage: pixi run quarto-export <program in mojo/local/> <folder beside the .qmd page>');
const src = path.join(ROOT, 'core/mojo/local', `${name}.mojo`);
if (!fs.existsSync(src)) die(`core/mojo/local/${name}.mojo does not exist`);
const listingsJs = path.join(ROOT, 'core/dist/mojo/generated/listings.js');
if (!fs.existsSync(listingsJs)) die('core/dist/ is missing; run `pixi run build` first');
const { MOJO_LISTINGS } = await import(pathToFileURL(listingsJs).href);
fs.mkdirSync(outDir, { recursive: true });
const wrote = [];
const put = (file, text) => { fs.writeFileSync(path.join(outDir, file), text.endsWith('\n') ? text : text + '\n'); wrote.push(file); };
put(`${name}.mojo`, fs.readFileSync(src, 'utf8'));
const listing = MOJO_LISTINGS[name];
if (listing) { put(`${name}.asm`, listing.asm); put(`${name}.setup`, listing.setup); }
const attrs = [`mojo="${name}.mojo"`];
if (listing) attrs.push(`asm="${name}.asm"`, `setup="${name}.setup"`);
attrs.push(`area="${listing ? 'hw' : 'dev'}"`, `title="${name}"`);
console.log(`wrote ${wrote.map((f) => path.join(outDir, f)).join(', ')}`);
if (!listing) console.log(`no x86-64 listing for ${name} yet: run \`pixi run --manifest-path core/pixi.toml play ${name}\` (with # mode: both and -O0 in its header), then export again`);
console.log(`\nin the page, the whole playground:\n\n{{< pplus-playground ${attrs.join(' ')} >}}\n`);
console.log(`or, rendered with the page (no iframe):\n\n{{< pplus-run mojo="${name}.mojo" code="1" >}}\n{{< pplus-lifetimes mojo="${name}.mojo" >}}\n`);
console.log('Other arrangements: panel="compiler" (open on the compiler\'s answer), build="default", dock="closed", editor="0.6"; {{< pplus-embed view="life" >}} for one live view. The gallery at #/quarto shows them all.');