morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #4567] docs: add a game movement walkthrough #6312

New issue
Open
opened 2026-10-31 01:13:29 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:13:29 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4567
Author: @TheDesignFounder
Created: 10/16/2026
Status: 🔄 Open

Base: main ← Head: docs/relay-garden-community-20261016

📝 Commits (1)

  • 817b054 docs: add a game movement walkthrough

📊 Changes

4 files changed (+400 additions, -0 deletions)

View changed files

📝 docs/index.md (+4 -0)
📝 docs/javascript-application-workflows.md (+4 -0)
➕ docs/relay-garden-movement.md (+190 -0)
➕ docs/relay-garden-verification.md (+202 -0)

📄 Description

Summary

Add a playable example built around one question: does moving diagonally make
the player faster?

The walkthrough shows how we used REA to find the movement function in a small
JavaScript reference we wrote. Reading the function explains the movement rule;
comparing a separate implementation with the reference across 2,000 inputs
checks the result.

Play the game ·
Read the article ·
Get the source

Watch the gameplay ·
Watch the guided investigation ·
Read the recording transcript

Related to #778. This adds one example alongside #1704 and leaves the broader
demo collection open.

Problem and expected behavior

Readers of the JavaScript guide would get a small example they can follow from
question to result. It includes the command-line and MCP steps, the source REA
points to, and checks they can run themselves.

It also shows an incomplete result: a search misses a number that is present in
the code. The walkthrough explains why that result does not mean the number is
absent.

Change and scope

Four Markdown files: a walkthrough, a verification record, and links from the
JavaScript guide and documentation index. The example uses existing REA tools.

We wrote the reference and knew its code before the investigation. The example
checks a movement rule; the drones, collectibles and other game rules were added
separately. We added original artwork using Dreamlayer.

Contract and boundary impact

  • Semantic owner and earliest changed stage: documentation; helps readers find
    and follow an example.

  • Contribution scope fit and linked maintainer decision: documentation of
    existing JavaScript analysis tools, related to #778. A new-capability scope
    decision is not applicable.

  • CLI and MCP/tool-catalog contract: unchanged.

  • Provider, bridge, target-format, or platform compatibility: unchanged. The
    verification record names the versions and computer used.

  • Evidence, artifact, provenance, or reconstruction contract: unchanged. The
    displayed responses are labeled as excerpts; full local records are retained.

  • Target selection, authority, upstream behavior, and cleanup details: REA reads
    our version-pinned reference. Separate tests run the reference and game code.
    The MCP server process exited after the connection was closed.

  • Generated metadata, package, or installation impact: none.

  • Documentation or usability only; no target interaction introduced by this PR.

Evidence and regression coverage

  • Tests added or updated: none in this documentation PR. A separate local fix
    makes the game's browser tests advance time only when instructed.

  • Base reproduction or other evidence: real REA 6.5.0 command-line and MCP runs.
    The caller trace found one relationship and reported eight unresolved facts.
    The search for 180 found no match and reported partial coverage.

  • User-visible CLI/MCP output: the verification record includes exact requests,
    selected responses, and the source location checked against the reference.

  • Remaining proof gaps: the investigation was guided and used a local SDK client.
    Native agent registration, other operating systems, and autonomous discovery
    were not tested. Matching these inputs does not prove a match for every input.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Checks recorded on 16 October 2026:

  • npm ci and npm run investigate: passed with the locked dependencies.
  • npm test: all eight tests passed, including 2,000 movement comparisons.
  • npm run validate:assets: all ten file checksums matched.
  • One MCP connection: analysis and both follow-up queries completed; the queries
    reused the first analysis result. Server shutdown was verified.
  • Browser checks: the original suite failed once, then passed unchanged. A later
    controlled test reproduced a timing problem in the test itself. With the
    separate local fix, all seven browser checks passed; removing the fix made the
    new timing check fail. The public example pinned at b0627c5 does not yet
    contain this fix. The original failure lacked enough timing data to prove its
    exact cause.
  • The four documentation files passed the scoped Oxfmt check, whitespace checks,
    and source, JSON and local-link checks. These checks were repeated after applying
    the documentation changes to the current upstream branch. Both uploaded videos
    were downloaded without authentication and matched the local file checksums.

The full REA runtime and provider suites were not run for these documentation
changes. Website templates and translations are unchanged.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS 13.1 x86_64, Node 22.23.3,
    REA 6.5.0 and Chrome 155.0.8059.82. No native analysis engine was used.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: public excerpts use generic
    paths and are labeled as excerpts. Raw local records are kept outside the docs.

Author readiness

Human owner: @TheDesignFounder

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, 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/4567 **Author:** [@TheDesignFounder](https://github.com/TheDesignFounder) **Created:** 10/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/relay-garden-community-20261016` --- ### 📝 Commits (1) - [`817b054`](https://github.com/morluto/rea/commit/817b054d2edd321b54a7d453003bf1bb9e9cb6e7) docs: add a game movement walkthrough ### 📊 Changes **4 files changed** (+400 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/index.md` (+4 -0) 📝 `docs/javascript-application-workflows.md` (+4 -0) ➕ `docs/relay-garden-movement.md` (+190 -0) ➕ `docs/relay-garden-verification.md` (+202 -0) </details> ### 📄 Description ## Summary Add a playable example built around one question: **does moving diagonally make the player faster?** The walkthrough shows how we used REA to find the movement function in a small JavaScript reference we wrote. Reading the function explains the movement rule; comparing a separate implementation with the reference across 2,000 inputs checks the result. [Play the game](https://thedesignfounder.github.io/dreamlayer-game-assets/demo/) · [Read the article](https://dreamlayer.io/blog/rea-game-assets) · [Get the source](https://github.com/TheDesignFounder/dreamlayer-game-assets) [Watch the gameplay](https://github.com/user-attachments/assets/155db219-8f74-47af-9079-94cac8a6d77e) · [Watch the guided investigation](https://github.com/user-attachments/assets/6a79bb7e-a246-4a77-b272-339116e5dd93) · [Read the recording transcript](https://github.com/TheDesignFounder/dreamlayer-game-assets/releases/download/relay-garden-videos-20261016/rea-investigation-transcript.md) Related to #778. This adds one example alongside #1704 and leaves the broader demo collection open. ## Problem and expected behavior Readers of the JavaScript guide would get a small example they can follow from question to result. It includes the command-line and MCP steps, the source REA points to, and checks they can run themselves. It also shows an incomplete result: a search misses a number that is present in the code. The walkthrough explains why that result does not mean the number is absent. ## Change and scope Four Markdown files: a walkthrough, a verification record, and links from the JavaScript guide and documentation index. The example uses existing REA tools. We wrote the reference and knew its code before the investigation. The example checks a movement rule; the drones, collectibles and other game rules were added separately. We added original artwork using Dreamlayer. ## Contract and boundary impact - Semantic owner and earliest changed stage: documentation; helps readers find and follow an example. - Contribution scope fit and linked maintainer decision: documentation of existing JavaScript analysis tools, related to #778. A new-capability scope decision is not applicable. - CLI and MCP/tool-catalog contract: unchanged. - Provider, bridge, target-format, or platform compatibility: unchanged. The verification record names the versions and computer used. - Evidence, artifact, provenance, or reconstruction contract: unchanged. The displayed responses are labeled as excerpts; full local records are retained. - Target selection, authority, upstream behavior, and cleanup details: REA reads our version-pinned reference. Separate tests run the reference and game code. The MCP server process exited after the connection was closed. - Generated metadata, package, or installation impact: none. - [x] Documentation or usability only; no target interaction introduced by this PR. ## Evidence and regression coverage - Tests added or updated: none in this documentation PR. A separate local fix makes the game's browser tests advance time only when instructed. - Base reproduction or other evidence: real REA 6.5.0 command-line and MCP runs. The caller trace found one relationship and reported eight unresolved facts. The search for `180` found no match and reported partial coverage. - User-visible CLI/MCP output: the verification record includes exact requests, selected responses, and the source location checked against the reference. - Remaining proof gaps: the investigation was guided and used a local SDK client. Native agent registration, other operating systems, and autonomous discovery were not tested. Matching these inputs does not prove a match for every input. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed Checks recorded on 16 October 2026: - `npm ci` and `npm run investigate`: passed with the locked dependencies. - `npm test`: all eight tests passed, including 2,000 movement comparisons. - `npm run validate:assets`: all ten file checksums matched. - One MCP connection: analysis and both follow-up queries completed; the queries reused the first analysis result. Server shutdown was verified. - Browser checks: the original suite failed once, then passed unchanged. A later controlled test reproduced a timing problem in the test itself. With the separate local fix, all seven browser checks passed; removing the fix made the new timing check fail. The public example pinned at `b0627c5` does not yet contain this fix. The original failure lacked enough timing data to prove its exact cause. - The four documentation files passed the scoped Oxfmt check, whitespace checks, and source, JSON and local-link checks. These checks were repeated after applying the documentation changes to the current upstream branch. Both uploaded videos were downloaded without authentication and matched the local file checksums. The full REA runtime and provider suites were not run for these documentation changes. Website templates and translations are unchanged. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: macOS 13.1 x86_64, Node 22.23.3, REA 6.5.0 and Chrome 155.0.8059.82. No native analysis engine was used. - Package or release metadata impact: none. - Security, privacy, process, or containment review: public excerpts use generic paths and are labeled as excerpts. Raw local records are kept outside the docs. ## Author readiness Human owner: @TheDesignFounder - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6312
No description provided.