[GH-ISSUE #8334] [Docs] Put WASM interface comparison under the WASM guidance section #6547

New issue

Open

opened 2026-11-01 21:12:08 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:12:08 +00:00

Owner

Originally created by @morluto on GitHub (Oct 31, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/8334

Before submitting

I searched the existing issues for a related documentation report.
I removed credentials, tokens, private paths, and sensitive target data.

Documentation location

references/native-and-artifacts.md: Offline PE and ELF export tables, installed REA guidance rea-agents@6.8.0.

Problem

The PE/ELF export section ends with instructions for compare_wasm_interfaces and core WebAssembly modules. That paragraph is about a different format but appears under the native export heading, so an agent reading this section to compare native exports can encounter an inapplicable follow-up. The paragraph itself says “core-module”; it does not explicitly claim the tool supports ELF.

Expected content

Move the WASM comparison paragraph to the existing Offline WASM section, preserving its explicit scope and Evidence requirements. Keep the PE/ELF section limited to native export workflows. Do not substitute a different comparison tool without verifying its supported input and semantics.

Supporting evidence

In a built a989c0e stdio MCP server, search_guidance({query:"native exports"}) returned the “Offline PE and ELF export tables” locator; read_guidance_section returned both the native paragraph and the WASM comparison paragraph in one section. As a boundary control, two actual ELF inspect_native_exports records passed by retained reference to compare_wasm_interfaces returned invalid_request with Expected complete inspect_wasm_artifact Evidence, matching the tool's advertised contract. The rejection is correct; the documentation placement is the issue. No autonomous-agent behavior was measured and neither ELF target was executed or modified.

Additional context

This is separate from #8333's missing IFUNC guidance and #8290's search-ranking discussion. An appropriately scoped documentation check could verify the packaged guidance section after regeneration.

@gensokyo-dev @kaoru0822-kitauji @N0zoM1z0

Originally created by @morluto on GitHub (Oct 31, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8334 ### Before submitting - [x] I searched the existing issues for a related documentation report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Documentation location [`references/native-and-artifacts.md`: Offline PE and ELF export tables](https://github.com/morluto/rea/blob/a989c0e458c91af177e097abd7be0fd021b0401d/.agents/skills/reverse-engineer-anything/references/native-and-artifacts.md#L660), installed REA guidance `rea-agents@6.8.0`. ### Problem The PE/ELF export section ends with instructions for `compare_wasm_interfaces` and core WebAssembly modules. That paragraph is about a different format but appears under the native export heading, so an agent reading this section to compare native exports can encounter an inapplicable follow-up. The paragraph itself says “core-module”; it does not explicitly claim the tool supports ELF. ### Expected content Move the WASM comparison paragraph to the existing [Offline WASM section](https://github.com/morluto/rea/blob/a989c0e458c91af177e097abd7be0fd021b0401d/.agents/skills/reverse-engineer-anything/references/native-and-artifacts.md#L261), preserving its explicit scope and Evidence requirements. Keep the PE/ELF section limited to native export workflows. Do not substitute a different comparison tool without verifying its supported input and semantics. ### Supporting evidence In a built `a989c0e` stdio MCP server, `search_guidance({query:"native exports"})` returned the “Offline PE and ELF export tables” locator; `read_guidance_section` returned both the native paragraph and the WASM comparison paragraph in one section. As a boundary control, two actual ELF `inspect_native_exports` records passed by retained reference to `compare_wasm_interfaces` returned `invalid_request` with `Expected complete inspect_wasm_artifact Evidence`, matching the tool's advertised contract. The rejection is correct; the documentation placement is the issue. No autonomous-agent behavior was measured and neither ELF target was executed or modified. ### Additional context This is separate from #8333's missing IFUNC guidance and #8290's search-ranking discussion. An appropriately scoped documentation check could verify the packaged guidance section after regeneration. @gensokyo-dev @kaoru0822-kitauji @N0zoM1z0

bsakaguchi added the

documentation

triage

labels

2026-11-01 21:12:08 +00:00

No milestone

No project

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#6547

No description provided.

Rows
Columns