Files
rea/docs/user-visible-errors.csv

31 KiB

1harm_ranklocationtriggercurrent_copyuser_riskproposed_replacementimplementation_statusverification_result
21src/domain/errors.ts:AnalysisCapabilityUnavailableErrorRequested analysis unavailableProvider {providerId} cannot execute {operation}: {reason}Exposes provider and internal operation/reasonThis analysis is unavailable for the current target. Choose another analysis or target.implementedfocused assertions passed; full `npm run check` passed
32src/domain/errors.ts:ProviderAdapterErrorProvider adapter failsProvider {providerId} adapter failed during {operation}Exposes provider and implementation boundaryAnalysis could not complete. Retry once; if it continues, run `rea doctor`.implementedfocused assertions passed; full `npm run check` passed
43src/domain/errors.ts:HopperRemoteErrorRemote analysis request failsHopper request failed ({code}): {safeMessage}Exposes provider name code and upstream textAnalysis could not complete. Retry once; if it continues, run `rea doctor`.implementedfocused assertions passed; full `npm run check` passed
54src/domain/errors.ts:HopperProtocolErrorMalformed provider protocol resultRaw constructor messageCan expose provider protocol and implementation detailsAnalysis returned an unreadable result. Retry once; if it continues, run `rea doctor`.implementedfocused assertions passed; full `npm run check` passed
65src/domain/errors.ts:AnalysisOutputErrorAnalysis output fails parsingInvalid analysis output for {operation}: {reason}Exposes internal operation and parser reasonAnalysis returned an unreadable result. Retry once; if it continues, run `rea doctor`.implementedfocused assertions passed; full `npm run check` passed
76src/domain/errors.ts:AnalysisProtocolErrorApplication protocol failsRaw constructor messageCan expose protocol internalsAnalysis returned an unreadable result. Retry once; if it continues, run `rea doctor`.implementedfocused assertions passed; full `npm run check` passed
87src/domain/errors.ts:HopperProcessErrorAnalysis subprocess stopsHopper bridge stopped unexpectedly with code {exitCode}Exposes provider bridge and process codeAnalysis could not start or stopped unexpectedly. Run `rea doctor`, then try again.implementedfocused assertions passed; full `npm run check` passed
98src/domain/errors.ts:HopperStartErrorAnalysis subprocess cannot startHopper application bridge could not be startedExposes provider and bridge implementationAnalysis could not start or stopped unexpectedly. Run `rea doctor`, then try again.implementedfocused assertions passed; full `npm run check` passed
109src/domain/errors.ts:BinaryTargetErrorTarget cannot openCannot open artifact: {reason}May expose raw reason and lacks checksPreserve the target admission reason; directories name analyze_javascript_application and rea analyze as available alternatives.implementedfocused assertions passed; full `npm run check` passed
1110src/domain/errors.ts:ConfigurationErrorEnvironment configuration invalidRaw constructor messageMay expose provider-specific variables and lacks recoveryREA configuration is invalid. Run `rea doctor` and fix the reported setting.implementedfocused assertions passed; full `npm run check` passed
1211src/domain/errors.ts:ArtifactOperationErrorArtifact inventory or extraction failsArtifact {operation} failed: {reason} at {logicalPath} (declared_sha256=...)Exposes paths hashes and internal reasonReason-specific plain message with safe recovery step.implementedfocused assertions passed; full `npm run check` passed
1312src/domain/errors.ts:EvidenceFileErrorEvidence file operation failsEvidence bundle {operation} failed: {reason}Internal reason token gives weak recoveryReason-specific plain message with safe recovery step.implementedfocused assertions passed; full `npm run check` passed
1413src/domain/errors.ts:EvidenceIntegrityErrorEvidence validation failsRaw constructor messageMay expose validation internals and lacks recoveryEvidence is invalid or has changed. Recreate or re-import it, then try again.implementedfocused assertions passed; full `npm run check` passed
1514src/domain/errors.ts:UnknownRegistryErrorEvidence-state mutation failsResidual unknown registry mutation failed: {reason}Exposes internal subsystem and state tokenMissing IDs identify the session and retry; concurrent revision conflicts refresh current state.implementedfocused assertions passed; full `npm run check` passed
1615src/domain/errors.ts:ProcessCaptureErrorProcess capture failsRaw constructor messageMay expose process and cleanup internalsProcess capture could not complete. Check command access and limits, then try again.implementedfocused assertions passed; full `npm run check` passed
1716src/domain/errors.ts:AnalysisTimeoutErrorAnalysis deadline expiresAnalysis operation timed out after {timeoutMs}ms: {operation}Exposes internal deadline and operation; weak recoveryAnalysis took too long. Try a smaller request, then run `rea doctor` if it continues.implementedfocused assertions passed; full `npm run check` passed
1817src/domain/errors.ts:HopperTimeoutErrorProvider deadline expiresHopper did not respond within {timeoutMs}msExposes provider and internal deadlineAnalysis took too long. Try a smaller request, then run `rea doctor` if it continues.implementedfocused assertions passed; full `npm run check` passed
1918src/domain/errors.ts:ProviderSelectionErrorDeep-provider selection failsAnalysis provider selection failed ({reason}) for {requestedProviderId}; candidates: {candidateIds}Retains non-secret local selection context that needs a safe structured projectionReason-specific guidance with stable candidate IDs and actionable rejection diagnosticsimplementedfocused registry/CLI/MCP assertions passed; full `npm run check` passed
2020src/domain/errors.ts:AnalysisInputErrorParsed analysis input invalidInvalid analysis input for {operation}Exposes operation identifier and lacks correctionAnalysis input is invalid. Check the arguments and try again.implementedfocused assertions passed; full `npm run check` passed
2121src/domain/errors.ts:AnalysisCancelledErrorCaller cancels analysisAnalysis operation was cancelled: {operation}Exposes operation identifierAnalysis was cancelled. Start it again when ready.implementedfocused assertions passed; full `npm run check` passed
2222src/domain/errors.ts:HopperCancelledErrorCaller cancels provider requestHopper operation was cancelledExposes provider nameAnalysis was cancelled. Start it again when ready.implementedfocused assertions passed; full `npm run check` passed
2323src/domain/errors.ts:NoBinaryOpenErrorAnalysis requested without targetNo app is open. Ask the user which app to investigate, then call open_binary with its local path.Low risk; already supplies agent recoveryKeep current copyimplementedfocused assertions passed; full `npm run check` passed
2424src/server/toolResult.ts:successResultSuccessful value violates public output schemaAnalysisOutputError: Analysis output does not match the tool contractExposes internal error tag and contract implementationAnalysis returned an unreadable result. Retry once; if it continues, run `rea doctor`.implementedfocused assertions passed; full `npm run check` passed
2524.5src/server/registerOfficialTools.ts:capability unknownApproved unknown tracking records an unavailable analysisTOOL_NAME is unavailable: PROVIDER_REASONExposes an internal tool identifier and provider diagnostic in persistent user-visible evidenceThe requested analysis is unavailable for the current target.implementedverified by focused MCP integration test
2624.6src/application/ReferenceSourceImportEntries.ts:failed entryA partial reference import contains an unreadable entryLow-level reader diagnostic stored in entry limitationsCan persist filesystem or reader implementation detailsCode- and entry-specific safe guidance with a retry, limit, exclusion, or platform recovery step.implementedverified by exhaustive focused projection test
2724.7src/server/registerSessionTools.ts:process residualCapture records a residual unknown linked to capture EvidenceSCOPE: RAW_REASONPersists adapter diagnostic and implementation wordingWas SCOPE behavior fully observed during capture?implementedverified by focused session MCP test
2824.8src/server/registerInvestigationTools.ts:changed behavior unknownChanged-behavior workflow remains incompleteChanged behavior result EVIDENCE_ID remains STATUSPersists internal evidence identifierDid both versions behave the same under a complete controlled replay?implementedverified by focused investigation MCP test
2924.9src/server/registerInvestigationTools.ts:call path unknownCall-path workflow remains incompleteCall path START_ADDRESS → GOAL_ADDRESS is STATUSPersists binary addresses and internal status wordingCan the requested call path be established from complete analysis?implementedverified by focused unresolved call-path MCP test
3024.91src/server/registerInvestigationTools.ts:static runtime unknownStatic/runtime correlation remains incompleteStatic/runtime correlation result EVIDENCE_ID is STATUSPersists internal evidence identifierDoes runtime behavior match the available static analysis?implementedverified by focused unresolved static/runtime MCP test
3124.92src/server/registerInvestigationTools.ts:reconstruction unknownReconstruction verification retains unknown claimsReconstruction SPECIFICATION_HASH has unknown claimsPersists internal hashDoes the reconstruction satisfy every declared claim?implementedverified by focused unknown reconstruction MCP test
3224.93src/server/registerFunctionComparisonTool.ts:probe rationaleFunction comparison is incompleteCapture complete dossiers with equal providers and analysis limits.Exposes provider architecture and gives ambiguous equality guidanceCapture complete dossiers for both functions under the same target context and analysis limits.implementedverified by focused function-comparison MCP test
3324.95incur:CLI argument validationCaller omits or mistypes a command argumentVALIDATION_ERROR with raw Zod Details and fieldErrors including code/path/expected/receivedExposes validator representation and buries the useful correctionREA could not read the command arguments. Check the named argument and its expected type, then try again.implementedverified by sanitizer unit tests and real dispatcher missing-argument test
3425src/application/ReferenceSourceImport.ts:cancelledReference-source import is cancelledReference source import cancelledNo recovery timing guidanceReference source import was cancelled. Start it again when ready.implementedfocused assertions passed
3526src/application/ReferenceSourceImportPolicy.ts:invalid-limitsConfigured import limits are not positive integersImport limits must be positive integersFixed importer ceilings prevented full source importsRemoved fixed byteentrydepthand path limits.removedverified by greater-than-10000 entry and greater-than-16-MiB regressions
3627src/application/ReferenceSourceImportPolicy.ts:invalid-rootSource path cannot resolve or is not a directoryReference source root could not be resolved / Reference source root is not a directoryMultiple low-level copies and no complete path checkReference source directory could not be opened. Check that the path exists, is readable, and points to a directory.implementedfocused assertions passed
3728src/application/ReferenceSourceImportPolicy.ts:policyNo approved root exists or requested root is outside policyNo approved reference source roots / Reference source root is outside approved rootsApproval friction duplicates direct caller path selectionRemoved the configured root allowlist and permission gate; caller-selected directories are validated and traversed directly.removedverified by source search and focused import tests
3829src/application/ReferenceSourceImport.ts:ioReader fails during traversalRaw reader error messageMay expose filesystem details and inconsistent recoveryReference source files could not be read. Check directory permissions and try again.implementedfocused assertions passed
3930src/application/ReferenceSourceImport.ts:parseHistorical graph validation failsRaw thrown graph validation messageCan expose internal graph invariantsReference source could not be indexed. Check that the source tree is readable, then try again.implementedfocused assertions passed
4031src/application/ReferenceSourceImportTypes.ts:limitImport reports terminal limit failureNo reachable constructor foundDeclared state may be unreachable; false verification riskRemove unreachable top-level limit variant; per-entry limit guidance remains caller-visible.removedverified by typecheck, exhaustive projection test, and source search
4132src/application/Setup.ts:configureDetectedClients(backup)Agent configuration backup fails{clientName} configuration backup verification failed; no successful configuration was reported.Exposes machine client key and obscures no-write guaranteeAgent configuration could not be backed up, so no change was made. Check file permissions, then rerun setup.implementedfocused assertions passed
4233src/application/Setup.ts:configureDetectedClients(write)Agent configuration write fails{clientName} configuration write verification failed; no successful configuration was reported.Exposes machine client key and gives no recoveryAgent configuration could not be updated. Check file permissions, then rerun setup.implementedfocused assertions passed
4334src/application/Setup.ts:configureDetectedClients(readback)Written agent configuration cannot be verified{clientName} configuration readback verification failed; no successful configuration was reported.Exposes machine client key and omits backup recoveryAgent configuration could not be verified after writing. Repair the configuration file or restore its `.rea.backup`, then rerun setup.implementedfocused assertions passed
4435src/application/Setup.ts:installSkillSkill install or semantic readback failsAgent skill installation or readback failed.No useful recovery actionREA analysis skill could not be installed or verified. Check permissions for `~/.agents/skills`, then rerun setup.implementedfocused assertions passed
4536src/main.ts:serveStdio.onerrorEstablished MCP client connection reports an errorMCP stdio transport errorExposes transport implementation and gives no recoveryREA lost its MCP client connection. Restart REA from your MCP client.implementedverified by injected transport onerror runtime test
4637src/main.ts:serveStdio throwMCP connection cannot be createdFailed to start MCP stdio transportExposes transport implementation and gives no recoveryREA could not start its MCP connection. Restart REA from your MCP client; run `rea doctor` if it fails again.implementedverified by injected transport startup-throw runtime test
4738src/main.ts:requestShutdown catchConnection or analysis session close rejectsFailed to shut down cleanlyDoes not explain duplicate-process risk or recoveryREA could not close cleanly. End the REA process before starting it again.implementedverified by injected handle-close rejection runtime test
4839src/main.ts:entrypoint catchUnhandled rejection escapes run()Unexpected server startup failureVague and lacks diagnostic recoveryREA could not start. Run `rea doctor`, then restart REA from your MCP client.implementedverified by injected entrypoint rejection test
4940src/application/Upgrade.ts:unknown-install-methodRunning package is not owned by detectable global npm installationUpdate manually with: npm install --global rea-agents@latestAlready gives exact safe recoveryKeep current copyunchangedexisting focused assertion passed
5041src/application/Upgrade.ts:installnpm global install subprocess exits unsuccessfullynpm install --global rea-agents@latest failed.Does not identify bounded likely checks before retryREA could not update through npm. Check npm registry access and global install permissions, then run: npm install --global rea-agents@latestimplementedfocused assertion passed
5142src/application/Uninstall.ts:removeClient readExisting agent configuration cannot be readConfiguration could not be read.No recovery stepConfiguration could not be read. Check file permissions, then rerun uninstall.implementedverified by injected filesystem read failure test
5243src/application/Uninstall.ts:removeClient parseAgent configuration is malformedMalformed configuration was preserved without mutation.Does not name required repair format or retryConfiguration is not valid JSON/TOML and was not changed. Repair it, then rerun uninstall.implementedfocused JSON assertion passed; TOML path uses same branch
5344src/application/Uninstall.ts:removeClient backupConfiguration backup copy failsConfiguration backup failed; no mutation was attempted.No recovery stepConfiguration could not be backed up, so no change was made. Check file permissions, then rerun uninstall.implementedverified by injected filesystem backup failure test
5445src/application/Uninstall.ts:removeClient updateWrite or semantic readback failsConfiguration update failed; the original was restored and {backupPath} was retained.Exposes local path and lacks clear next sequenceReport whether the original was restored; if restoration also fails, direct the user to the retained backup.implementedverified by injected update and restoration failure tests
5545.5src/application/Uninstall.ts:removeClient restoreConfiguration update fails and restoring the original also failsConfiguration could not be updated or restored. Restore its `.rea.backup` manually, then rerun uninstall.High risk; persistent configuration may be damaged, but retained backup is authoritativeKeep new recovery copyimplementedverified by injected restoration failure test
5646src/application/Uninstall.ts:removeManagedPath symlinkManaged cache/state/skill path is a symbolic linkRefused to follow symlink {path}.Exposes local path and does not explain manual safety checkREA did not remove this item because its managed path is a symbolic link. Verify the link target before removing it manually.implementedfocused assertion passed
5747src/application/Uninstall.ts:removeManagedPath failureManaged item removal fails{path} could not be removed.Exposes local path and gives no recoveryThis item could not be removed. Check file permissions, then rerun uninstall.implementedverified by injected managed-path removal failure test
5848src/application/DoctorDiagnostics.ts:nodeRuntime version is outside supported rangesInstall Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+.Low risk; exact dependency recoveryKeep current copyunchangedverified by doctor unit test
5949src/application/Doctor.ts:hostHost OS/distribution is unsupportedREA supports macOS 12+, Ubuntu 24.04+, Fedora 41+, Nobara 44+, 64-bit Arch Linux, and CachyOS.Low risk; clearly states supported choicesKeep current copyunchangedverified by doctor unit tests
6050src/application/Doctor.ts:analysis engineOptional deep-analysis executable cannot be foundRun rea setup to install Hopper, or set HOPPER_LAUNCHER_PATH.Low risk in setup-specific diagnostic; exact recovery pathsKeep current copyunchangedverified by doctor unit tests
6151src/application/Doctor.ts:targetOptional target path fails shared validationSupply a readable local app or program path.Low risk; tells caller valid target classKeep current copyunchangedverified by doctor unit test
6252src/application/Setup.ts:approvalSetup plan lacks approvalReview the setup plan, then rerun interactively or with --yes.Low risk; exact authorization recoveryKeep current copyunchangedverified by setup unit tests
6353src/application/Setup.ts:engine installApproved analysis-engine installation returns no launcherHopper installation failed; install Hopper manually or rerun setup after resolving the reported system error.Mentions component intentionally being installed and offers two bounded recovery pathsKeep current copyunchangedverified by setup unit test
6454src/application/Setup.ts:first-run choiceNew macOS analysis-engine install requires a first-run choiceOpen Hopper, choose its demo mode or activate a license, then rerun rea doctor --json.Low risk; exact demo-or-license choice and verification commandKeep current copyunchangedverified by setup unit test
6555src/application/Setup.ts:optional engineSetup completes without optional deep-analysis engineHopper is optional for non-Hopper providers. Rerun with --yes --install-hopper for deep native analysis.Exposes provider terminology but this is an explanatory setup status rather than an error; recovery command is exactKeep current copyunchangedverified by setup unit test
6656src/application/Setup.ts:doctor fallbackPost-setup diagnostics remain unhealthyRun rea doctor and apply each reported remediation.Low risk; delegates to structured per-check recoveryKeep current copyunchangedverified by exact setup unit test
6757src/application/Setup.ts:unsupported platformPlatform is neither macOS nor LinuxREA supports Hopper on macOS and selected 64-bit Linux distributions.Low risk; states support boundaryKeep current copyunchangedverified by setup unit test
6858src/application/SetupHost.ts:unsupported NodeRuntime version cannot run setupInstall Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+ and rerun setup.Low risk; exact dependency and retryKeep current copyunchangedverified by setup host tests
6959src/application/Setup.ts:unsupported macOSmacOS version is missing or older than 12Upgrade to macOS 12 or newer.Low risk; exact support floorKeep current copyunchangedverified by setup host tests
7060src/application/Setup.ts:unsupported LinuxLinux distribution is outside supported setREA supports Hopper on Ubuntu 24.04+, Fedora 41+, Nobara 44+, 64-bit Arch Linux, and CachyOS.Low risk; exact supported alternativesKeep current copyunchangedverified by setup unit test
7161src/application/process/ProcessCli.ts:readJson readProcess scenario or evidence file cannot be readRaw filesystem exception through CLI frameworkCan expose local paths/codes and no recoveryProcess input file could not be read. Check that the path exists and is readable.implementedverified by focused CLI test
7262src/application/process/ProcessCli.ts:readJson sizeProcess scenario or evidence file exceeds 64 MiBProcess JSON input exceeds byte limitDoes not state limit or recoveryProcess input file is too large. Reduce it below 64 MiB, then try again.implementedverified by focused sparse-file CLI test
7363src/application/process/ProcessCli.ts:readJson parseProcess scenario or evidence file is malformed JSONRaw JSON parser exception through CLI frameworkCan expose parser implementation and lacks recoveryProcess input file is not valid JSON. Repair the file, then try again.implementedverified by focused CLI test
7464src/application/process/ProcessCli.ts:capture scenario parseScenario fails Process Capture schemaRaw Zod validation exception through CLI frameworkExposes schema internals and field paths without stable recoveryProcess scenario is invalid. Check its required fields and limits, then try again.implementedverified by focused CLI test
7566src/application/process/ProcessCli.ts:wrong evidenceComparison receives valid Evidence from another workflowExpected REA process capture EvidenceUses internal schema name and does not explain recoveryCapture evidence is not from the current process-capture workflow. Create new capture evidence, then try again.implementedverified by focused CLI test
7667src/application/process/ProcessCli.ts:unexpectedUnexpected parser/comparison/canonicalization failure escapes expected classificationsRaw thrown exception through CLI frameworkCan expose stack or internal invariantProcess command could not complete. Check the input files and run `rea doctor`, then try again.implementedverified by direct unexpected-cause projection test
7768src/server/registerEvidenceTools.ts:object guardValidated provider-tool input is unexpectedly not an objectProvider tool input was not an objectExposes provider architecture and implies caller can fix impossible stateRemove the impossible duplicate guard and parse through the declared JSON-object schema.removedverified by typecheck and MCP integration tests
7869src/server/registerEnhancedTools.ts:object guardValidated enhanced-tool input is unexpectedly not an objectValidated enhanced input was not a JSON objectExposes validation/JSON implementation detailRemove the impossible duplicate guard and parse through the declared JSON-object schema.removedverified by typecheck and enhanced MCP integration tests
7970src/server/registerOfficialTools.ts:object guardValidated direct-tool input is unexpectedly not an objectValidated MCP tool input was not a JSON objectExposes MCP validation implementation detailRemove the impossible duplicate guard and parse through the declared JSON-object schema.removedverified by typecheck and official MCP integration tests
8071src/server/registerProcessComparisonTool.ts:canonical guardProcess comparison value cannot become canonical JSONProcess capture could not be canonicalizedNames internal serialization invariant and gives no recoveryRemove the impossible canonicalization error branch; compare schema-validated values directly.removedverified by process-comparison MCP tests and source search
8172src/server/sessionEvidence.ts:canonical guardRecorded Evidence cannot become canonical JSONEvidence could not be canonicalizedNames internal serialization invariant and gives no recoveryRemove the impossible canonicalization error branch; compare parsed Evidence directly.removedverified by session Evidence integrity tests and source search
8273install.sh:--version value--version has no following value--version requires a value.Low risk; identifies correctionKeep current copyunchangedverified by shell branch inspection
8374install.sh:unknown optionInstaller receives an unsupported flagunknown option with caller-provided flagLow risk; identifies offending inputKeep current copyunchangedverified by shell branch inspection
8475install.sh:platformInstaller runs outside macOS or supported LinuxREA supports macOS and selected 64-bit Linux distributions.Low risk; states support boundaryKeep current copyunchangedverified by shell branch inspection
8576install.sh:curl missingcurl is absentcurl is required.No recovery instructioncurl is required. Install curl, then rerun this installer.implementedverified by exact missing-curl installer test
8677install.sh:node missingnode is absentNode.js 22.x (>=22.19), 24.x (>=24.11), or 26+ is required; install it from nodejs.org and retry.Low risk; exact versions and recoveryKeep current copyunchangedverified by shell branch inspection
8778install.sh:npm missingnpm is absentnpm is required; install it with Node.js and retry.Low risk; exact recoveryKeep current copyunchangedverified by shell branch inspection
8879install.sh:node unreadablenode exists but does not report a parseable versioncould not determine the active Node.js version.No cause-local recoveryThe active Node.js version could not be read. Check that node works and is on PATH, then retry.implementedverified by exact unreadable-Node-version installer test
8980install.sh:Node 22 floorNode 22 minor version is below 19Node.js VERSION is unsupported; use Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+.Low risk; exact detected version and supported alternativesKeep current copyunchangedverified by exact installer test using Node 20 and branch inspection
9081install.sh:Node 24 floorNode 24 minor version is below 11Node.js VERSION is unsupported; use Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+.Low risk; exact detected version and floorKeep current copyunchangedverified by shell branch inspection
9182install.sh:version syntaxExplicit version is not exact semantic versionversion must be an exact semantic version.Low risk; exact correctionKeep current copyunchangedverified by shell branch inspection
9283install.sh:release lookupLatest GitHub release request failscould not resolve the latest GitHub release.No fallback despite supporting pinned versionsThe latest REA release could not be resolved. Check network access or pass --version VERSION, then retry.implementedverified by exact release-lookup installer test
9384install.sh:release responseLatest release response is not valid expected JSONNode JSON parser stack followed by the safe release-response messageLeaks a parser stack and buries recovery guidanceThe release response was invalid. Retry later or pass --version VERSION.implementedverified by exact malformed-release test with parser stderr suppressed
9485install.sh:release tagLatest release tag does not match REA release conventionlatest release tag is not a valid rea-agents release.Exposes package naming detail and omits fallbackThe latest release tag was invalid. Retry later or pass --version VERSION.implementedverified by exact invalid-release-tag installer test
9586install.sh:npm prefixnpm cannot return its global prefixcould not determine the npm global prefix.No recovery instructionThe npm global prefix could not be read. Repair the npm configuration, then retry.implementedverified by exact macOS npm-prefix installer test
9687install.sh:npm installnpm global installation exits nonzeronpm package installation failed.No likely causes or recoverynpm could not install REA. Check registry access and npm permissions, then retry.implementedverified by exact installer test
9788install.sh:binary absentnpm exits successfully without executablethe rea command was not installed at local pathLeaks local path and no recoverynpm completed without installing the rea command. Check the npm global bin directory and PATH, then retry.implementedverified by exact absent-installed-command test
9889install.sh:version readInstalled rea executable cannot report its versioncould not read the installed REA version.No recovery instructionThe installed REA version could not be read. Reinstall the requested version, then retry.implementedverified by exact unreadable-installed-version test
9990install.sh:version mismatchInstalled rea reports a different versioninstalled version ACTUAL does not match EXPECTED.Low risk; gives exact integrity mismatchKeep current copyunchangedverified by exact installer test
10090.5@modelcontextprotocol/server:tool input validationCaller sends arguments that violate a declared tool schemaInput validation error: Invalid arguments for tool TOOL: FIELD: Invalid input: expected TYPE, received TYPELow risk; public tool and field names plus exact type correctionKeep SDK-generated copyunchangedverified by real in-memory MCP client/server call with wrong argument type
10190.6incur:unknown CLI commandCaller enters an unknown REA command'COMMAND' is not a command for 'rea'. Suggested command: rea --helpLow risk; identifies input and exact discovery actionKeep framework-generated copyunchangedverified by real packaged dispatcher invocation