morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #5085] [Bug] Korean update guide omits the documented alias and output-limit guidance #3123

New issue

Closed

opened 2026-10-31 00:36:52 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

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

Owner

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

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. The English “Update REA” section documents rea --update, its global output flags, and updater output retention/progress behavior. The Korean “REA 업데이트” section omits both paragraphs, proceeding from the rea update example directly to the Bun requirement. The canonical command and surrounding setup guidance remain present.

Reproduction

I read both sections and ran this content comparison from a checkout at the source revision below:

python3 - <<'PY'
from pathlib import Path

def section(path, heading):
    text = Path(path).read_text()
    return text.split(heading + '\n', 1)[1].split('\n## ', 1)[0]

en = section('README.md', '### Update REA')
ko = section('docs/readme/README_ko.md', '### REA 업데이트')
for label, token in [('alias', 'rea --update'), ('output bound', '4 MiB')]:
    print(f'{label}: English={token in en}; Korean={token in ko}')
    assert token in en and token not in ko
PY

Observed:

alias: English=True; Korean=False
output bound: English=True; Korean=False

Manual comparison confirms the missing paragraphs rather than merely different translations of these tokens. No REA updater command was run.

Expected behavior

Carry the documented alias and output-limit/progress facts into the Korean update section. Translation guidance identifies English as the reference for README commands, requirements and analysis claims.

Impact and scope

Informational documentation omission for readers of the Korean edition. The guide still provides rea update, the Bun version requirement and registration refresh instructions. No failed workflow, data loss or runtime behavior change was observed. English contains the omitted facts. Other translated editions were not assessed.

REA version

Source SHA 3537e58c1ab29309f06eabf50bc52adba9817a0c, package version 6.7.0. The relevant files have no diff from stable tag rea-agents-6.7.0; this establishes stable source coverage only.

Runtime and platform

Inspection host: Node.js v26.12.0; macOS 27.0.1; arm64. SOURCE-ONLY; no REA runtime or provider was exercised.

Target and artifact context

Repository documentation: README.md and docs/readme/README_ko.md, update sections. No analysis target applies.

Interface

Other

Earliest failure stage

Unknown

Relevant output or evidence

English update section: the alias paragraph is at lines 135–136; output retention and progress guidance is at lines 138–141.
Korean update section: both paragraphs are absent between the command example and Bun requirement.
git diff rea-agents-6.7.0 HEAD -- README.md docs/readme/README_ko.md produced no output at the stated source SHA.

Typed outcome or recovery expected

Not applicable to a documentation-content omission. Restore the missing Korean guidance.

Analysis or suspected cause

Source-derived: the English paragraphs have no counterpart in the Korean update section. The existing consistency test compares bash examples rather than prose. NOT_ENOUGH_INFO: the history or intent behind the omission was not established.

Additional context

Related reports concern different work: #4564 identifies procps, Go/SQLite and Bun facts; #958 tracks a general language-quality review. Neither identifies these two missing paragraphs. This report makes no runtime claim about updater limits or alias execution.

Originally created by @coygeek on GitHub (Oct 18, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/5085 ## 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. The English “Update REA” section documents `rea --update`, its global output flags, and updater output retention/progress behavior. The Korean “REA 업데이트” section omits both paragraphs, proceeding from the `rea update` example directly to the Bun requirement. The canonical command and surrounding setup guidance remain present. ## Reproduction I read both sections and ran this content comparison from a checkout at the source revision below: ```bash python3 - <<'PY' from pathlib import Path def section(path, heading): text = Path(path).read_text() return text.split(heading + '\n', 1)[1].split('\n## ', 1)[0] en = section('README.md', '### Update REA') ko = section('docs/readme/README_ko.md', '### REA 업데이트') for label, token in [('alias', 'rea --update'), ('output bound', '4 MiB')]: print(f'{label}: English={token in en}; Korean={token in ko}') assert token in en and token not in ko PY ``` Observed: ```text alias: English=True; Korean=False output bound: English=True; Korean=False ``` Manual comparison confirms the missing paragraphs rather than merely different translations of these tokens. No REA updater command was run. ## Expected behavior Carry the documented alias and output-limit/progress facts into the Korean update section. [Translation guidance](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/CONTRIBUTING.md#L264-L275) identifies English as the reference for README commands, requirements and analysis claims. ## Impact and scope Informational documentation omission for readers of the Korean edition. The guide still provides `rea update`, the Bun version requirement and registration refresh instructions. No failed workflow, data loss or runtime behavior change was observed. English contains the omitted facts. Other translated editions were not assessed. ## REA version Source SHA `3537e58c1ab29309f06eabf50bc52adba9817a0c`, package version 6.7.0. The relevant files have no diff from stable tag `rea-agents-6.7.0`; this establishes stable source coverage only. ## Runtime and platform Inspection host: Node.js v26.12.0; macOS 27.0.1; arm64. SOURCE-ONLY; no REA runtime or provider was exercised. ## Target and artifact context Repository documentation: `README.md` and `docs/readme/README_ko.md`, update sections. No analysis target applies. ## Interface Other ## Earliest failure stage Unknown ## Relevant output or evidence - [English update section](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/README.md#L124-L147): the alias paragraph is at lines 135–136; output retention and progress guidance is at lines 138–141. - [Korean update section](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/docs/readme/README_ko.md#L110-L130): both paragraphs are absent between the command example and Bun requirement. - `git diff rea-agents-6.7.0 HEAD -- README.md docs/readme/README_ko.md` produced no output at the stated source SHA. ## Typed outcome or recovery expected Not applicable to a documentation-content omission. Restore the missing Korean guidance. ## Analysis or suspected cause Source-derived: the English paragraphs have no counterpart in the Korean update section. The [existing consistency test](https://github.com/morluto/rea/blob/3537e58c1ab29309f06eabf50bc52adba9817a0c/tests/conformance/readmeConsistency.test.ts#L59-L64) compares bash examples rather than prose. NOT_ENOUGH_INFO: the history or intent behind the omission was not established. ## Additional context Related reports concern different work: [#4564](https://github.com/morluto/rea/issues/4564) identifies procps, Go/SQLite and Bun facts; [#958](https://github.com/morluto/rea/issues/958) tracks a general language-quality review. Neither identifies these two missing paragraphs. This report makes no runtime claim about updater limits or alias execution.

bsakaguchi closed this issue

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

bsakaguchi commented

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

Author

Owner

@CassieFox23 commented on GitHub (Oct 21, 2026):

Thanks, coygeek, for the section comparison. From reading main at 01788bac8, not a run: this looks fixed. The file docs/readme/README_ko.md:120 now names rea --update as the alias. Line 122 carries the 4 MiB output bound and the progress behaviour. That landed in 5f0bc86d1a on 2026-10-20. PR #5236 closed the same day without merging. Closing is the maintainers' call.

🤖 Written with Claude Code (Fable 5.1, verified by Opus 5.5), posted with my OK 🦊

@CassieFox23 commented on GitHub (Oct 21, 2026): Thanks, coygeek, for the section comparison. From reading main at 01788bac8, not a run: this looks fixed. The file `docs/readme/README_ko.md:120` now names `rea --update` as the alias. Line 122 carries the 4 MiB output bound and the progress behaviour. That landed in 5f0bc86d1a on 2026-10-20. PR #5236 closed the same day without merging. Closing is the maintainers' call. 🤖 Written with Claude Code (Fable 5.1, verified by Opus 5.5), posted with my OK 🦊

bsakaguchi commented

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

Author

Owner

@morluto commented on GitHub (Oct 23, 2026):

Fixed on main in github.com/morluto/rea@5f0bc86d1a. Korean update guidance now includes rea --update, the same global output flags, combined stdout/stderr 4 MiB retention, metadata overflow handling, continued bounded installer diagnostics, and progress backpressure/completion.

Verified against the full issue and current source. The published tree also retains passing docs:check and docs:build receipts. This closes the documentation/help/CI-configuration scope; no new provider runtime verification is claimed.

@morluto commented on GitHub (Oct 23, 2026): Fixed on main in https://github.com/morluto/rea/commit/5f0bc86d1aae553f1dc81fbaef1fb369bd8f97a4. Korean update guidance now includes rea --update, the same global output flags, combined stdout/stderr 4 MiB retention, metadata overflow handling, continued bounded installer diagnostics, and progress backpressure/completion. Verified against the full issue and current source. The published tree also retains passing docs:check and docs:build receipts. This closes the documentation/help/CI-configuration scope; no new provider runtime verification is claimed.

bsakaguchi referenced this issue

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

[PR #3123] [CLOSED] fix(clients): report the active ZCode fallback registration in status #5633

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#3123

No description provided.

Rows
Columns