[GH-ISSUE #5078] [Bug] Host-support error catalogue omits Omarchy and understates doctor support #3116

New issue

Closed

opened 2026-10-31 00:36:49 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:36:49 +00:00

Owner

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

Before submitting

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

Area

Documentation

Observed behavior

SOURCE-ONLY. In docs/user-visible-errors.csv, the host-support rows with harm ranks 49 and 60 both omit Omarchy, despite being marked unchanged, Keep current copy, and verified by doctor/setup unit tests. The corresponding source messages include Omarchy. Rank 49 also omits the current distinction between broader REA host support and the narrower automated Hopper setup list, including experimental Windows x64 support.

The row locations name Doctor.ts and Setup.ts; the message definitions now reside in DoctorDiagnostics.ts and SetupHost.ts. The former files remain workflow callers.

Reproduction

Source inspection performed at the revision below, from the checkout root:

git rev-parse HEAD
sed -n '60,75p' docs/user-visible-errors.csv
sed -n '110,155p' src/application/SetupHost.ts
sed -n '128,153p' src/application/DoctorDiagnostics.ts

Compare the two CSV rows with hostRemediation and hostCheck. Both source messages contain Omarchy; neither catalogue row does. The doctor source also names recognized apt/dnf/pacman Linux distributions and the experimental Windows x64 Ghidra P0 boundary. A separate CSV-parsing comparison confirmed these mismatches on both main and the stable release tag. No REA command or provider was run.

Expected behavior

Rows explicitly marked as retaining their current copy should describe the current host-support messages and identify their owning definitions. The installation guide already includes Omarchy and distinguishes automated Hopper setup from broader REA host support.

The support lists in these same catalogue rows were previously maintained when Nobara support was added, as shown in commit f0dc233d64de4c215c453c346e516b7622713e95.

Impact and scope

Documentation accuracy only. Readers auditing the host-support error copy receive a stale support list and message location. No runtime rejection of a supported host is established. The current installation guide and source provide the correct information. Reader frequency and reach are NOT_ENOUGH_INFO.

REA version

Main source 3537e58c1ab29309f06eabf50bc52adba9817a0c, package version 6.7.0. The mismatch also exists in source at stable tag rea-agents-6.7.0, commit 27dc42d10249f0410904a75c0997842eb03b931c. No installed stable runtime was tested.

Runtime and platform

Inspection host: Node.js v26.12.0, macOS 27.0.1, arm64. SOURCE-ONLY; no Linux, Windows, Hopper, or Ghidra execution was performed.

Target and artifact context

The error catalogue and its setup/doctor message definitions. No target binary or provider artifact was used.

Interface

Other

Earliest failure stage

Unknown

Relevant output or evidence

Catalogue rows 49 and 60 omit Omarchy while marking the copy unchanged.
Setup message includes Omarchy and explicitly describes automated Hopper setup.
Doctor message and support predicate include the broader host support and Omarchy.
Setup caller and doctor diagnostic collection consume those definitions.

Observed static comparison:

rank=49 status=unchanged catalogue_omarchy=no source_omarchy=yes copy_equal=no
rank=49 catalogue_windows=no source_windows=yes
rank=60 status=unchanged catalogue_omarchy=no source_omarchy=yes copy_equal=no

Existing copy assertions in Setup.recovery.test.ts:319 and Doctor.test.ts:79 agree with the source messages; those tests were read, not executed.

Typed outcome or recovery expected

Not applicable to this documentation mismatch. No change to runtime support or typed outcomes is requested.

Analysis or suspected cause

Source-derived: the catalogue retained the earlier host-support copy after the message definitions changed. The causal change was not isolated.

Additional context

No matching report was found in the complete open-and-closed issue snapshot searched. Issue #3419 concerns automated Hopper installation admitted on an incompatible CPU architecture; this report concerns stale catalogue copy and would require a separate documentation correction.

Originally created by @coygeek on GitHub (Oct 18, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5078 ## Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ## Area Documentation ## Observed behavior SOURCE-ONLY. In `docs/user-visible-errors.csv`, the host-support rows with harm ranks 49 and 60 both omit Omarchy, despite being marked `unchanged`, `Keep current copy`, and verified by doctor/setup unit tests. The corresponding source messages include Omarchy. Rank 49 also omits the current distinction between broader REA host support and the narrower automated Hopper setup list, including experimental Windows x64 support. The row locations name `Doctor.ts` and `Setup.ts`; the message definitions now reside in `DoctorDiagnostics.ts` and `SetupHost.ts`. The former files remain workflow callers. ## Reproduction Source inspection performed at the revision below, from the checkout root: ```sh git rev-parse HEAD sed -n '60,75p' docs/user-visible-errors.csv sed -n '110,155p' src/application/SetupHost.ts sed -n '128,153p' src/application/DoctorDiagnostics.ts ``` Compare the two CSV rows with `hostRemediation` and `hostCheck`. Both source messages contain Omarchy; neither catalogue row does. The doctor source also names recognized apt/dnf/pacman Linux distributions and the experimental Windows x64 Ghidra P0 boundary. A separate CSV-parsing comparison confirmed these mismatches on both main and the stable release tag. No REA command or provider was run. ## Expected behavior Rows explicitly marked as retaining their current copy should describe the current host-support messages and identify their owning definitions. The [installation guide](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/docs/installation.md#L521-L526) already includes Omarchy and distinguishes automated Hopper setup from broader REA host support. The support lists in these same catalogue rows were previously maintained when Nobara support was added, as shown in commit `f0dc233d64de4c215c453c346e516b7622713e95`. ## Impact and scope Documentation accuracy only. Readers auditing the host-support error copy receive a stale support list and message location. No runtime rejection of a supported host is established. The current installation guide and source provide the correct information. Reader frequency and reach are NOT_ENOUGH_INFO. ## REA version Main source `3537e58c1ab29309f06eabf50bc52adba9817a0c`, package version 6.7.0. The mismatch also exists in source at stable tag `rea-agents-6.7.0`, commit `27dc42d10249f0410904a75c0997842eb03b931c`. No installed stable runtime was tested. ## Runtime and platform Inspection host: Node.js v26.12.0, macOS 27.0.1, arm64. SOURCE-ONLY; no Linux, Windows, Hopper, or Ghidra execution was performed. ## Target and artifact context The error catalogue and its setup/doctor message definitions. No target binary or provider artifact was used. ## Interface Other ## Earliest failure stage Unknown ## Relevant output or evidence - [Catalogue rows 49 and 60](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/docs/user-visible-errors.csv#L62-L73) omit Omarchy while marking the copy unchanged. - [Setup message](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/src/application/SetupHost.ts#L124-L142) includes Omarchy and explicitly describes automated Hopper setup. - [Doctor message and support predicate](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/src/application/DoctorDiagnostics.ts#L129-L147) include the broader host support and Omarchy. - [Setup caller](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/src/application/Setup.ts#L229-L233) and [doctor diagnostic collection](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/src/application/DoctorDiagnostics.ts#L28-L34) consume those definitions. Observed static comparison: ```text rank=49 status=unchanged catalogue_omarchy=no source_omarchy=yes copy_equal=no rank=49 catalogue_windows=no source_windows=yes rank=60 status=unchanged catalogue_omarchy=no source_omarchy=yes copy_equal=no ``` Existing copy assertions in `Setup.recovery.test.ts:319` and `Doctor.test.ts:79` agree with the source messages; those tests were read, not executed. ## Typed outcome or recovery expected Not applicable to this documentation mismatch. No change to runtime support or typed outcomes is requested. ## Analysis or suspected cause Source-derived: the catalogue retained the earlier host-support copy after the message definitions changed. The causal change was not isolated. ## Additional context No matching report was found in the complete open-and-closed issue snapshot searched. Issue #3419 concerns automated Hopper installation admitted on an incompatible CPU architecture; this report concerns stale catalogue copy and would require a separate documentation correction.

bsakaguchi closed this issue

2026-10-31 00:36:49 +00:00

bsakaguchi referenced this issue

2026-10-31 01:08:05 +00:00

[PR #3119] [MERGED] fix(ci): check authored documentation code #5626