Skip to content

chore(main): release rea-agents 6.6.0 - #1

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--rea-agents
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--rea-agents

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

This release is too large to preview in the pull request body. View the full release notes here: https://github.com/CloudEngineHub/rea/blob/release-please--branches--main--components--rea-agents--release-notes/release-notes.md

@github-actions github-actions Bot changed the title chore(main): release rea-agents 6.4.0 chore(main): release rea-agents 6.5.0 Oct 12, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--rea-agents branch 3 times, most recently from 27690bf to 661822d Compare October 14, 2026 04:18
@github-actions github-actions Bot changed the title chore(main): release rea-agents 6.5.0 chore(main): release rea-agents 6.6.0 Oct 15, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--rea-agents branch 2 times, most recently from 1919fb0 to 5266a6d Compare October 16, 2026 03:12
JadeCong pushed a commit that referenced this pull request Oct 17, 2026
* feat(ghidra): support raw big-endian m68k analysis

Admit `m68k` for headerless raw-binary targets. Admission requires a
2-byte aligned entry and a mapping within 0x0..0xffffffff, and Ghidra
imports with BinaryLoader using 68000:BE:32:default, the default compiler
specification, and the `ram` default address space.

`6502` and `m68k` now share one RAW_ONLY_ARCHITECTURES owner, so detected
targets, Evidence subjects, snapshots, and lifecycle output contracts
exclude both instead of repeating a 6502 literal.

Ghidra's default 68000 language decodes the 68040 superset; separate
68020/68030/CPU32/ColdFire variants, Amiga/Atari containers, and reset
vector discovery remain unsupported. Windows Ghidra P0 still admits raw
6502 only.

Verified with Ghidra 12.1.4 on macOS against an 8-byte self-built fixture
(nop; nop; moveq #1,d0; rts at 0x1000): load image verified in `ram`,
entry decompiles to `return 1`.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* test(ghidra): verify raw m68k analysis with real Ghidra

Add npm run verify:ghidra:m68k. The verifier loads a source-owned 22-byte
68000 fixture (annotated hex, no assembler) at 0x1000 and checks, through
the compiled CLI and stdio MCP server: the 68000:BE:32:default BinaryLoader
import, load-image parity, exact mapped bytes, both functions, the bsr.b
call reference, decompilation by address and file offset, rejection of a
misaligned entry and of a mapping past 0xffffffff without replacing the
active session, unchanged source bytes, and runtime cleanup.

Run with Ghidra 12.1.4 and JDK 21 on macOS arm64. Linux has not been
exercised; Windows Ghidra P0 does not admit m68k.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--rea-agents branch from 5266a6d to 6861714 Compare October 17, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants