[PR #906] [MERGED] feat(website): introduce REA and the DX-Ball reconstruction #2335

New issue

Closed

opened 2026-10-16 21:17:28 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:17:28 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/906
Author: @N0zoM1z0
Created: 10/7/2026
Status: ✅ Merged
Merged: 10/7/2026
Merged by: @N0zoM1z0

Base: main ← Head: feat/website

📝 Commits (3)

ca76d79 feat(website): add local introduction and DX-Ball showcase
be4d36e feat(website): illustrate REA and DX-Ball reconstruction
74582b9 docs(website): show the REA queries behind source recovery

📊 Changes

12 files changed (+2487 additions, -0 deletions)

View changed files

➕ .github/workflows/website-pages.yml (+44 -0)
➕ website/README.md (+63 -0)
➕ website/evidence/dx-ball-sound-pan.md (+116 -0)
➕ website/figures.md (+99 -0)
➕ website/public/assets/favicon.svg (+1 -0)
➕ website/public/assets/figures/dx-ball-sound-pan-investigation.svg (+58 -0)
➕ website/public/assets/figures/rea-investigation-flow.svg (+43 -0)
➕ website/public/assets/main.js (+57 -0)
➕ website/public/assets/styles.css (+857 -0)
➕ website/public/get-started/index.html (+310 -0)
➕ website/public/index.html (+232 -0)
➕ website/public/showcase/dx-ball/index.html (+607 -0)

📄 Description

Summary

Add an English website for REA with a product introduction, onboarding guide and DX-Ball case study. Two SVG figures show the investigation flow. Compact recorded REA requests show how the agent obtained function, caller and byte-read evidence, and an interactive comparison connects x86 instructions to maintained C.

Problem and expected behavior

Readers currently learn about REA through repository documentation. The website introduces the workflow, provides setup commands and lets readers follow one concrete reconstruction from executable evidence to checked source. This is a standalone website addition; no issue is linked.

Change and scope

Serve three static pages from website/public, with relative navigation and assets for the /rea/ Pages path.
Present the DX-Ball sound-pan input, arithmetic, caller and constant reads alongside the maintained function. Retain the complete instruction listing and source provenance.
Add a manual GitHub Pages workflow restricted to main, with separate artifact preparation and deployment jobs. Ordinary pushes and PRs do not publish.
Maintain diagrams as SVG source, preserving the reviewed visual layout. Keep contributor notes for the initial image-generation prompts, content sources and local preview.
Use REA in the product overview and case narrative; configuration guides and provenance retain provider details.

Contract and boundary impact

Semantic owner and earliest changed stage: website presentation only.
CLI and MCP/tool-catalog contract: unchanged.
Provider, bridge, target-format, or platform compatibility: unchanged.
Evidence, artifact, provenance, or reconstruction contract: existing recorded REA/Ghidra results are presented with their artifact identity and pinned public reconstruction checkpoint.
Process execution, authorization, cleanup, or containment impact: the manually invoked workflow publishes website/public to GitHub Pages.
Generated metadata, package, or installation impact: none.

Evidence and regression coverage

Tests added or updated: none; static pages and their browser interactions were checked directly.
Base reproduction or other evidence: assembly matches the saved REA dossier; maintained C matches the pinned public DX-Ball source; byte reads decode to the displayed constants.
User-visible CLI/MCP output: unchanged.
Remaining proof gaps: the case study cites the reconstruction project's recorded execution/compiler checks; this website update does not rerun them.
Observed, derived, and inferred claims remain distinguishable.
Artifact identity and source provenance remain preserved.
Function-level validation and ongoing game integration are described at their actual scope.

Validation performed

npm run check:fast — passed in the pre-push hook.
Website JavaScript syntax and Oxfmt checks — passed.
Chrome browser preview at the root and /rea/ — six routes and 22 clipboard checks passed; five comparison steps, keyboard interaction and responsive widths 1440/768/390/320 passed without browser errors or page overflow.
HTML links and evidence provenance checks — 41 local links/assets valid; full 23-instruction listing and eight-instruction excerpt match saved Evidence; C matches pinned source.

Compatibility, safety, and release

Breaking changes or migration steps: none.
Real Hopper/Ghidra, browser, or OS coverage: real Chrome website checks; saved REA 4.1.0 / Ghidra 12.1.4 evidence reused, with no new native-provider run.
Package or release metadata impact: none.
Security, privacy, process, or containment review: only static website assets are published. Original executables, complete private dossiers and compiler products remain outside the website.

Review checklist

One focused outcome and Conventional Commit title.
Issue-link scope explained above.
Changed browser behavior checked directly.
Website documentation and evidence provenance updated.
No CLI/MCP contract changes.
Final diff checked for unrelated files and unsupported claims.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/906 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 10/7/2026 **Status:** ✅ Merged **Merged:** 10/7/2026 **Merged by:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Base:** `main` ← **Head:** `feat/website` --- ### 📝 Commits (3) - [`ca76d79`](https://github.com/morluto/rea/commit/ca76d790367a94b0fcad60bb2035a5b53a282ee7) feat(website): add local introduction and DX-Ball showcase - [`be4d36e`](https://github.com/morluto/rea/commit/be4d36e4869436fb64f531b57543b948c088741e) feat(website): illustrate REA and DX-Ball reconstruction - [`74582b9`](https://github.com/morluto/rea/commit/74582b9ce0c0a442580376bd7992e4b4be9d67a3) docs(website): show the REA queries behind source recovery ### 📊 Changes **12 files changed** (+2487 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/website-pages.yml` (+44 -0) ➕ `website/README.md` (+63 -0) ➕ `website/evidence/dx-ball-sound-pan.md` (+116 -0) ➕ `website/figures.md` (+99 -0) ➕ `website/public/assets/favicon.svg` (+1 -0) ➕ `website/public/assets/figures/dx-ball-sound-pan-investigation.svg` (+58 -0) ➕ `website/public/assets/figures/rea-investigation-flow.svg` (+43 -0) ➕ `website/public/assets/main.js` (+57 -0) ➕ `website/public/assets/styles.css` (+857 -0) ➕ `website/public/get-started/index.html` (+310 -0) ➕ `website/public/index.html` (+232 -0) ➕ `website/public/showcase/dx-ball/index.html` (+607 -0) </details> ### 📄 Description ## Summary Add an English website for REA with a product introduction, onboarding guide and DX-Ball case study. Two SVG figures show the investigation flow. Compact recorded REA requests show how the agent obtained function, caller and byte-read evidence, and an interactive comparison connects x86 instructions to maintained C. ## Problem and expected behavior Readers currently learn about REA through repository documentation. The website introduces the workflow, provides setup commands and lets readers follow one concrete reconstruction from executable evidence to checked source. This is a standalone website addition; no issue is linked. ## Change and scope - Serve three static pages from `website/public`, with relative navigation and assets for the `/rea/` Pages path. - Present the DX-Ball sound-pan input, arithmetic, caller and constant reads alongside the maintained function. Retain the complete instruction listing and source provenance. - Add a manual GitHub Pages workflow restricted to `main`, with separate artifact preparation and deployment jobs. Ordinary pushes and PRs do not publish. - Maintain diagrams as SVG source, preserving the reviewed visual layout. Keep contributor notes for the initial image-generation prompts, content sources and local preview. - Use REA in the product overview and case narrative; configuration guides and provenance retain provider details. ## Contract and boundary impact - Semantic owner and earliest changed stage: website presentation only. - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: unchanged. - Evidence, artifact, provenance, or reconstruction contract: existing recorded REA/Ghidra results are presented with their artifact identity and pinned public reconstruction checkpoint. - Process execution, authorization, cleanup, or containment impact: the manually invoked workflow publishes `website/public` to GitHub Pages. - Generated metadata, package, or installation impact: none. ## Evidence and regression coverage - Tests added or updated: none; static pages and their browser interactions were checked directly. - Base reproduction or other evidence: assembly matches the saved REA dossier; maintained C matches the pinned public DX-Ball source; byte reads decode to the displayed constants. - User-visible CLI/MCP output: unchanged. - Remaining proof gaps: the case study cites the reconstruction project's recorded execution/compiler checks; this website update does not rerun them. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity and source provenance remain preserved. - [x] Function-level validation and ongoing game integration are described at their actual scope. ## Validation performed - `npm run check:fast` — passed in the pre-push hook. - Website JavaScript syntax and Oxfmt checks — passed. - Chrome browser preview at the root and `/rea/` — six routes and 22 clipboard checks passed; five comparison steps, keyboard interaction and responsive widths 1440/768/390/320 passed without browser errors or page overflow. - HTML links and evidence provenance checks — 41 local links/assets valid; full 23-instruction listing and eight-instruction excerpt match saved Evidence; C matches pinned source. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: real Chrome website checks; saved REA 4.1.0 / Ghidra 12.1.4 evidence reused, with no new native-provider run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: only static website assets are published. Original executables, complete private dossiers and compiler products remain outside the website. ## Review checklist - [x] One focused outcome and Conventional Commit title. - [x] Issue-link scope explained above. - [x] Changed browser behavior checked directly. - [x] Website documentation and evidence provenance updated. - [x] No CLI/MCP contract changes. - [x] Final diff checked for unrelated files and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-16 21:17:28 +00:00