Syntax Highlighting Themes

This experiment demonstrates syntax highlighting for TypeScript and YAML using an explicit GitHub light/dark theme pair. The sandbox configuration retains themed backgrounds, enables clipboard controls, and requests token classification. The two source examples exercise different language grammars; the recorded proof below establishes rendered code figures and clipboard-button presence without treating either as proof of a successful interaction.

Active configuration, copied verbatim from /home/loca/dev/quartz-sandbox/sandbox/engine/quartz.config.yaml, lines 68–77:

  - source: "@quartz-community/syntax-highlighting"
    enabled: true
    options:
      theme:
        light: github-light
        dark: github-dark
      keepBackground: true
      clipboard: true
      tokenClassification: true
    order: 20

Actual rendered-example content, copied contiguously from /home/loca/dev/quartz-sandbox/sandbox/vault/experiments/syntax-highlighting-themes.md, lines 55–65. The outer four-backtick fence preserves both inner language fences as source examples.

```typescript
export function isolationBoundaries(): string[] {
  return ["checkout", "node_modules", "config", "dist", "origin port"]
}
```
 
```yaml
configuration:
  pageTitle: Quartz Sandbox
  baseUrl: quartz.loca.zone
```

What the rendered output proves

Live sandbox page: https://quartz.loca.zone/experiments/syntax-highlighting-themes.html

The prior capture in /home/loca/dev/quartz-sandbox/evidence/2026-09-15-quartz-migration-f1fd35c3/sandbox-experiments.json classifies Syntax highlighting themes with these literal proof_markers:

{"syntax_figures":4,"clipboard_button":5}

Its rendered_proof.routes entry records 41,308 DOM bytes and reading_stats: 1. The receipt captured the built release dist-1789511778 through http://127.0.0.1:51963; these values are prior-capture results.

syntax_figures: 4 and clipboard_button: 5 are receipt marker counters, not independently established counts of actual DOM elements. Broad string matches can include quoted source examples; they must not be interpreted as four independently tested code blocks or five successful copies. The source identifies data-rehype-pretty-code-figure as the emitted wrapper and notes that the old shiki CSS class is not the assertion used for this output. The receipt’s aggregate counters do not independently prove each token classification, both computed theme palettes, a dark-mode transition, keyboard activation, clipboard permission, or clipboard contents. Those would require separate interaction or style checks.

Safe for the shared engine?

Recorded assessment: safe_for_shared_engine: true.

Receipt reason, verbatim:

Only existing code blocks change; the theme pair and background setting are reversible configuration.

A true verdict does not authorize a shared-engine change. Any requirement to modify /home/loca/dev/quartz/quartz must be reported as a BLOCKER, not performed as an action. Reversible configuration is still a change requiring authorization when it affects the engine shared by 51 wikis.

Try it in the sandbox

After editing only authorized sandbox content or configuration, rebuild through the isolated wrapper:

cd /home/loca/dev/quartz-sandbox/sandbox && ./build.sh

The wrapper /home/loca/dev/quartz-sandbox/sandbox/build.sh pins the isolated engine to commit 3dff48b5df6d84c9544a5ae19c8f2cbb01dc44e5 and takes a nonblocking .build.lock; a competing build is rejected instead of overlapping. It runs install-plugins before bootstrap-cli.mjs build, with --directory pointing to /home/loca/dev/quartz-sandbox/sandbox/vault and --output pointing to a new timestamped /home/loca/dev/quartz-sandbox/sandbox/dist-<timestamp> directory. It checks for index.html before atomically replacing current. The origin sees the new release on the next request without a restart.

Recorded runtime invocation from sandbox-runtime.json, reference only:

PATH=/usr/bin:/bin PORT=51947 SANDBOX_ROOT=/home/loca/dev/quartz-sandbox/sandbox/current NODE_ENV=production /usr/bin/node /home/loca/dev/quartz-sandbox/sandbox/serve.mjs

The production service already owns port 51947. Do not start a second process or restart the service. The runtime receipt describes an earlier supervised process and release-swap proof, not an instruction to launch another server. No sandbox rebuild or service change was performed to author this documentation.

index