Kaoru0822andClaude Opus 5.5 0a0244db42 fix(config): name the rejected setting and its constraint in configuration errors ...

Every configuration failure projected the same message, "REA configuration
is invalid. Run `rea doctor` and fix the reported setting.", with no
details. The environment parser discarded the issue that names the variable
(for example `REA_GHIDRA_NATIVEAOT_JAR must be absolute`), and doctor can
report healthy for that environment, so neither the CLI, the MCP startup
message, nor doctor told callers which setting to correct.

ConfigurationError now carries the rejected settings and their constraints
(never their values). The projection names them in its message, lists them
in `details.settings`, and asks the caller to correct those settings where
REA is started. Errors without a named setting keep the previous message.

Fixes #1184

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-09 04:08:43 +00:00

..

environment.ts

fix(config): name the rejected setting and its constraint in configuration errors

2026-10-09 04:08:43 +00:00

ghidraStartupTimeout.ts

feat(ghidra): make the startup deadline configurable (#974)

2026-10-09 07:21:36 +08:00

mcpResponseBudget.ts

fix(config): name the rejected setting and its constraint in configuration errors

2026-10-09 04:08:43 +00:00

parseConfig.ts

feat(ghidra): make the startup deadline configurable (#974)

2026-10-09 07:21:36 +08:00

parsers.ts

fix(config): name the rejected setting and its constraint in configuration errors

2026-10-09 04:08:43 +00:00

types.ts

feat(ghidra): make the startup deadline configurable (#974)

2026-10-09 07:21:36 +08:00