An English static website with explanatory figures, worked guides and DX-Ball, Notion, TH04 and CTF investigations. The public files are in website/public/. The site uses HTML, CSS and small scripts for copying code, following code comparisons and playing the dinosaur speed reconstruction. Python packages the downloadable example; there is no frontend bundler or npm dependency.

style-guide.md explains the writing, page structure, figures, visual system and review process. Read it before adding or revising a page.

Local preview

From the repository root:

python3 scripts/prepare-website.py
python3 -m http.server 4173 --bind 127.0.0.1 --directory website/public

Open http://127.0.0.1:4173/. Refresh the browser after editing a file.

Content

Keep the copy direct and specific. Explain the task and the result before listing tool names. Setup commands and runtime requirements should match the released package. Keep the core learning path inside the site. Source, issue and evidence reference links may point to the corresponding repositories.

evidence/guide-examples.md records the published REA package, example digests and observed results behind the guides. The Notes Electron fixture is for static analysis; Electron is not a prerequisite for following that example. The separate Notes browser app runs in the local preview and constructs a CSV download after fetching its JSON data.

The Electron guide offers one ZIP containing the six source files under notes-example/. scripts/prepare-website.py generates this download from an explicit file list, with fixed timestamps and permissions. The ZIP is ignored by Git; website checks and each manual publication regenerate it before checking and uploading the public directory. The verifier checks that its entries match the current source and contain no extra files.

The first-investigation page uses this same ZIP. Its prompt lets the agent download and unpack the target; the download button provides a manual path. The reader follows the static export trace, then runs the CSV formatter with one changed input. This formatter check needs only Node.js. The separate browser Notes example has a different implementation.

Agent terminals show example prompts, not transcripts of previous investigations. All cursors blink continuously with the same CSS animation, respecting reduced-motion preferences. Both the prompt and animation work without JavaScript. The homepage and agent setup section share a copyable installation prompt; setup still presents its plan for approval.

Reading pages share a small ↑ Top link at the bottom right. It appears after scrolling and returns to the page header, with smooth scrolling when reduced motion is disabled. Keyboard activation returns focus to the first navigation link. Without JavaScript, the link stays visible and uses its #top anchor.

The FAQ uses native <details> for its answers. Keep replies short and link to on-site guides for the next step. Individual answers have stable fragment IDs; the shared script opens an answer when its fragment is visited. The questions and disclosure controls remain usable without JavaScript. Check FAQ commands and support statements against the English README and relevant guides when updating them.

DX-Ball figures and findings refer to the linked 7 October 2026 checkpoint, commit a55dca27ec0a07018c1b2c95ae2be027f7d8c3c4. Update those links and figures together when moving to another checkpoint. Case-study source excerpts come from the MIT-licensed DX-Ball reconstruction repository.

The assembly excerpts were transcribed from the project's saved REA/Ghidra Evidence. evidence/dx-ball-sound-pan.md records their provenance and the scope of the validation claims. The original executable and complete private Evidence records are not website assets.

The homepage starts with a short installation prompt and the ordinary setup command, then explains what reverse engineering is and why someone would use it. The manual/agent comparison introduces REA’s role before the examples. Its opening links directly to Showcases and lets experienced readers skip to the analysis guides. Case-study previews live on the Showcases page. A right-side table of contents stays visible at widths of 1440px and above. On narrower screens it becomes a sticky, native disclosure; selecting a link closes the menu and focuses the destination. The homepage script follows the reading position and marks the current link. Without JavaScript, the menu stays open and its fragment links remain usable. The comparison uses the same Calculator question on both sides: three selectable manual steps pair original instructions with an analyst illustration and thought bubbles; the agent side begins with “One prompt.” and a copyable question. Thoughts illustrate the reasoning behind the findings. The shared code-step script selects the initial note on load, so all three notes remain readable when JavaScript is disabled. The original-instruction panel starts expanded on desktop. On narrow screens, the homepage script collapses it; a native disclosure keeps the code available while the thought bubble and agent prompt remain close together. Dinosaur is the first example; Calculator follows as the native example. Both name the goal and the reason to inspect the program before showing the demo. A labeled finding explains what REA returned, and the flow distinguishes REA’s inspection from the agent’s interpretation and implementation. Its game precedes the prompt and code on small screens. Calculator’s excerpt comes from an installed model DLL; Microsoft’s public implementation supplies names and a crosscheck. Its controls apply the percentage rule to generic inputs.

The dinosaur example connects an inspected running script to a new playable mini-game. public/assets/dino-speed.js owns the recovered speed rule and replay; dino-demo.js imports it for automatic acceleration. The slider chooses a fixed speed instead. Drawing, jumping and collision code are newly authored for this teaching game. It starts on input, pauses when hidden or outside the viewport, and retains a static SVG when JavaScript is disabled. The lab links the speed module and complete game source, and replays the rule against recorded original-game values.

evidence/calculator-and-dino.md records both targets, selected findings, attribution and verification scope. Update the speed rule, game, check table and evidence together. The original script excerpt and its BSD license are credited on the pages. Prompt responses are example explanations based on findings.

The general investigation and DX-Ball overview diagrams are maintained as SVG source. Initial layout references were created with the built-in image generation tool; figures.md retains their prompts and the current asset notes. Figures provide an overview; REA requests, assembly and C remain selectable HTML text. On narrow screens, the diagrams scroll horizontally and can also be opened at full size. The worked guides use semantic HTML flows that stack vertically on smaller screens. The Electron teaching example uses CommonJS, matching its preload code; the scoped lint override admits require only in that example directory.

The Notion case follows the same HTML figure style. Its short excerpts explain the packaged clipboard bridge; separate web-cache probes illustrate the rich clipboard format, with Markdown tables available as an additional example in collapsed details. Only selected source details and generic example data belong on the site. Machine paths, account identifiers, local configuration, complete vendor bundles and raw captured results stay outside the website. evidence/notion-clipboard.md records the REA package version, selected findings, source anchors and module-probe scope.

TH04 case study

The TH04 case inspects the original PC-98 DOS angle helper through REA 4.1.0. Its selected instructions are paired with readable C++ and a source SVG of fixed and aimed rings. evidence/th04-bullet-ring.md records the fresh load-image/function evidence and separately credited TH04 source and historical compiler replay. The figure illustrates the calculation; original game assets and executable bytes are not website downloads.

CTF case study

The DownUnderCTF 2023 case follows the official ms_flag_checker handout from prompt references to checking functions, compressed masks, equations and an accepted flag. evidence/ctf-masked-squares.md records the REA analysis, extracted data and positive/negative process captures. The downloadable public/showcase/ctf/solve.py uses Python and z3-solver; its constants come from REA's byte reads. The original executable stays in the organizers' repository and is linked from the page.

The mask SVG is drawn from the seventh decoded mask. It selects zero-based position 21 and compares its character code with 55 (7). Keep the figure, solver constants and evidence notes aligned when changing this case.

Cloudflare Workers

wrangler.toml serves website/public/ through Workers Static Assets. There is no Worker script or frontend build. Before a preview or deployment, Wrangler runs the existing Python scripts to prepare the example ZIP and verify the website. Node.js and Python 3 must be available; the commands below use a pinned Wrangler version without adding it to REA's package dependencies.

Cloudflare documents static-asset requests as free and unlimited, with no additional storage cost. See billing and limitations.

Local and hosted previews

Run these commands from the repository root. --cwd website makes the build paths consistent with the website configuration. Preview locally first:

npx [email protected] dev --cwd website --env ""

If CLOUDFLARE_API_TOKEN is already set in your shell, Wrangler uses it for authentication; skip wrangler login. If you are not using an API token, sign in once with npx [email protected] login. See Cloudflare's authentication commands.

To publish a preview:

npx [email protected] deploy --cwd website --env ""

This creates rea-website-preview at the workers.dev URL printed by Wrangler. It does not attach rea.tools. Check the homepage, a nested guide, case studies, the Notes browser example and the Electron ZIP at that URL.

Connect rea.tools

Serving the custom hostname requires an active Cloudflare zone. When DNS is managed elsewhere:

Add rea.tools to your Cloudflare account and choose the Free plan.
Export or save the current DNS records. Review Cloudflare's imported records against them, including subdomains, MX and TXT records for email and domain verification; the automatic scan can miss records.
If DNSSEC is enabled, follow Cloudflare's instructions to disable it at the registrar before changing nameservers.
At the domain registrar, replace the current nameservers with the two assigned by Cloudflare. The domain can remain registered with the current registrar.
Wait for Cloudflare to report the zone as Active. Re-enable DNSSEC through Cloudflare afterward if required.

See Cloudflare's nameserver setup procedure for the complete migration steps. A CNAME to the preview's workers.dev hostname at the current DNS provider does not configure a Workers Custom Domain.

The production environment creates or updates rea-website, attaches rea.tools, and lets Cloudflare manage its DNS record and HTTPS certificate. Deployment can succeed while the zone is pending; verify public HTTPS after activation and certificate issuance. An existing CNAME at rea.tools must be resolved before adding the Custom Domain. The production Worker also retains its workers.dev address for direct checks. Only rea.tools is attached; www.rea.tools is not configured by this file.

Verify https://rea.tools/, https://rea.tools/guides/javascript/, https://rea.tools/examples/notes-web/ and the Electron ZIP. Unknown paths return 404, and directory pages retain trailing slashes so relative assets and links resolve correctly. The root README and browser guide use https://rea.tools/ as the public website URL.

Production publication uses the synchronized GitHub Actions workflow below. Local Wrangler commands above publish only the separate preview Worker.

Synchronized production publishing

.github/workflows/website-pages.yml prepares website/public once and deploys the same artifact to Cloudflare (rea.tools) and GitHub Pages. It is the sole production publisher, manually triggered and restricted to main; ordinary pushes and pull requests do not publish the site.

Configure these repository Actions secrets before publishing:

CLOUDFLARE_API_TOKEN: a Cloudflare token using the Edit Cloudflare Workers template, scoped to the website's account and zone.
CLOUDFLARE_ACCOUNT_ID: that Cloudflare account's ID.

See Cloudflare's GitHub Actions authentication instructions. The default both target checks that both secrets are present before preparing a release. Cloudflare deploys first; GitHub Pages deploys after that step succeeds.

Preparation adds deployment.json with the workflow's commit SHA. Cloudflare receives the extracted Pages artifact through Wrangler's explicit assets path; the local custom-build output is not the uploaded directory. The workflow then checks the selected public version markers and reports success only when they match that commit. A failed publication remains failed; fix its cause and rerun the workflow to complete both deployments. The two hosts can update at different times while a run is in progress.

Website checks run only for pull requests that change website/, the verification script or workflow definitions. They check local links, HTML fragments, SVG XML and the single Pages publisher without installing npm dependencies. The same checks run before each manual deployment. You can also run them locally:

python3 scripts/prepare-website.py
python3 scripts/verify-website.py

.github/workflows/pages.yml is a separate, manual-only VitePress build. It has no Pages artifact upload, deployment job or deployment permissions. This prevents documentation updates from replacing the public website. The legacy publishing job has been removed, so enabling this build workflow cannot publish the old site.

After the site is approved and merged, select GitHub Actions under the repository's Settings → Pages → Build and deployment. Then run Publish REA website from the Actions tab on main. This publishes both production hosts. The workflow uses the github-pages environment, the official Pages actions and Cloudflare's Wrangler action.

The equivalent CLI command publishes both hosts:

gh workflow run website-pages.yml --repo morluto/rea --ref main

While Cloudflare credentials are being configured, an explicitly requested Pages-only publication uses the same workflow with target=pages:

gh workflow run website-pages.yml --repo morluto/rea --ref main -f target=pages

This mode verifies the Pages commit marker. The default remains both for synchronized production releases.

Local development does not change Pages settings or run the deployment workflow. Any environment protection rules are configured separately when publication is approved.

README.md Unescape Escape

REA website