[GH-ISSUE #1633] [Question] Track Hermes first-run config being reported as a legacy installation #552

New issue

Open

opened 2026-10-15 18:26:06 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:26:06 +00:00

Owner

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

Before submitting

Searched related Hermes/setup reports, including #1521 and #1587.
Removed credentials, private paths and target data.

Area

First-run Hermes configuration / onboarding.

Observed behavior

After REA creates an additive Hermes MCP config in an otherwise fresh home, Hermes warns that the config predates version 12 and is about two years old. The config was just created. Two independent real Codex-backed bundle analyses and two missing-target runs completed correctly despite the warning.

Reduced controls and reproduction

At Hermes source revision 66605471, run its actual hermes_cli.post_update.step_migrate_config() boundary in independent homes. No REA, MCP registration, skill or model is needed:

Fresh on-disk config	Repeats	Raw stamp	Boot result	File rewritten
Missing file	2	50	up-to-date	no
Empty YAML mapping `{}`	2	absent	below-support-floor warning	no
Empty file	2	absent	below-support-floor warning	no

read_config_version_stamp() preserves the absent stamp as None; check_config_version() projects it to zero; step_migrate_config() then compares zero with the legacy support floor. In contrast, migrate_config() explicitly distinguishes an absent stamp from an explicit old version and documents the absent case as first-run state.

Expected behavior

A fresh additive configuration is recognized as unversioned first-run state rather than an ancient installation.

REA version / environment

REA source head 1bba5545, skill 37. Hermes 66605471, Python 3.14.7; Linux x64. Source package metadata says 6.3.0, but this is not the published npm 6.3.0 build (which has no Hermes setup client).

Ownership and follow-up

The warning is reproduced without REA, so it is not evidence that REA writes invalid config. This is a client boot-maintenance boundary observation; do not stamp a hardcoded Hermes schema version in REA or migrate user configuration on its behalf. Track the compatibility concern and reduce it for upstream Hermes if needed. The most useful REA guidance can be decided after upstream behavior is known. No REA production fix is proposed.

Verification limits

Both positive live bundle runs answered the fixture questions and distinguished static Evidence from runtime execution. Both missing-target runs clarified with zero REA operations. Other model providers, native engines and Windows/macOS first-use onboarding remain unverified.

Refs #1587, #1627.

Originally created by @N0zoM1z0 on GitHub (Oct 10, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1633 ### Before submitting - [x] Searched related Hermes/setup reports, including #1521 and #1587. - [x] Removed credentials, private paths and target data. ### Area First-run Hermes configuration / onboarding. ### Observed behavior After REA creates an additive Hermes MCP config in an otherwise fresh home, Hermes warns that the config predates version 12 and is about two years old. The config was just created. Two independent real Codex-backed bundle analyses and two missing-target runs completed correctly despite the warning. ### Reduced controls and reproduction At Hermes source revision 66605471, run its actual `hermes_cli.post_update.step_migrate_config()` boundary in independent homes. No REA, MCP registration, skill or model is needed: | Fresh on-disk config | Repeats | Raw stamp | Boot result | File rewritten | | --- | --- | --- | --- | --- | | Missing file | 2 | 50 | up-to-date | no | | Empty YAML mapping `{}` | 2 | absent | below-support-floor warning | no | | Empty file | 2 | absent | below-support-floor warning | no | `read_config_version_stamp()` preserves the absent stamp as `None`; `check_config_version()` projects it to zero; `step_migrate_config()` then compares zero with the legacy support floor. In contrast, `migrate_config()` explicitly distinguishes an absent stamp from an explicit old version and documents the absent case as first-run state. ### Expected behavior A fresh additive configuration is recognized as unversioned first-run state rather than an ancient installation. ### REA version / environment REA source head 1bba5545, skill 37. Hermes 66605471, Python 3.14.7; Linux x64. Source package metadata says 6.3.0, but this is not the published npm 6.3.0 build (which has no Hermes setup client). ### Ownership and follow-up The warning is reproduced without REA, so it is not evidence that REA writes invalid config. This is a client boot-maintenance boundary observation; do not stamp a hardcoded Hermes schema version in REA or migrate user configuration on its behalf. Track the compatibility concern and reduce it for upstream Hermes if needed. The most useful REA guidance can be decided after upstream behavior is known. No REA production fix is proposed. ### Verification limits Both positive live bundle runs answered the fixture questions and distinguished static Evidence from runtime execution. Both missing-target runs clarified with zero REA operations. Other model providers, native engines and Windows/macOS first-use onboarding remain unverified. Refs #1587, #1627.

bsakaguchi added the

question

area: setup

P2: medium

labels

2026-10-15 18:26:06 +00:00

bsakaguchi referenced this issue

2026-10-16 21:13:54 +00:00

[PR #552] [MERGED] fix(platform): accept absolute paths for any host and stop blaming the ceiling for a missing grant #2068