[PR #3270] [MERGED] docs(readme): add the Linux ps prerequisite to the Korean README #5688

Closed
opened 2026-10-31 01:08:39 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3270
Author: @hachi-008
Created: 10/14/2026
Status: ✅ Merged
Merged: 10/14/2026
Merged by: @morluto

Base: main ← Head: docs/ko-readme-linux-ps


📝 Commits (1)

  • 55f445e docs(readme): add the Linux ps prerequisite to the Korean README

📊 Changes

1 file changed (+3 additions, -1 deletions)

View changed files

📝 docs/readme/README_ko.md (+3 -1)

📄 Description

Summary

The English README now says that Linux needs a procps-compatible ps on REA's PATH, both in the Quick start and in the JavaScript/Electron row. The Korean README was synced right before that change landed (#3046), so it has neither line. This adds both. No issue: it's a translation sync without a scope question.

Problem and expected behavior

A Korean reader on Linux gets no hint about the ps prerequisite, so a missing ps shows up as an unexplained refusal. Expected: the Korean README states the same prerequisite as README.md.

Change and scope

  • Quick start: add the Linux ps paragraph. Like the English text, it points to "Linux owned-process prerequisite" in docs/installation.md.
  • "What you can analyze": add the Linux ps requirement to the JavaScript/Electron row.

Not included: other translations. #3113 covers Simplified Chinese.

Ordinary documentation fix within existing boundaries; scope decision not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: documentation (docs/readme/README_ko.md) only.

  • Contribution scope fit and linked maintainer decision: documentation correction; not applicable.

  • CLI and MCP/tool-catalog contract: none.

  • Provider, bridge, target-format, or platform compatibility: none.

  • Evidence, artifact, provenance, or reconstruction contract: none.

  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.

  • Generated metadata, package, or installation impact: none; no generated files committed.

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Tests added or updated: none (documentation only).
  • Base reproduction or other evidence: compared with README.md at 877d404. No translated README mentions procps yet.
  • User-visible CLI/MCP output: not applicable.
  • Remaining proof gaps: none known.

Validation performed

Linux x64, Node.js 22.22.0, base 877d404:

  • npm run docs:check: passed (includes readmeConsistency.test.ts, 5/5)
  • python3 scripts/website.py check: passed (12 tests)
  • npx oxfmt --check docs/readme/README_ko.md: passed
  • git diff --check: clean

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: not applicable.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/3270 **Author:** [@hachi-008](https://github.com/hachi-008) **Created:** 10/14/2026 **Status:** ✅ Merged **Merged:** 10/14/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `docs/ko-readme-linux-ps` --- ### 📝 Commits (1) - [`55f445e`](https://github.com/morluto/rea/commit/55f445e907f88028a13acdaf2ee6e64be45aa9a5) docs(readme): add the Linux ps prerequisite to the Korean README ### 📊 Changes **1 file changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/readme/README_ko.md` (+3 -1) </details> ### 📄 Description ## Summary The English README now says that Linux needs a procps-compatible `ps` on REA's `PATH`, both in the Quick start and in the JavaScript/Electron row. The Korean README was synced right before that change landed (#3046), so it has neither line. This adds both. No issue: it's a translation sync without a scope question. ## Problem and expected behavior A Korean reader on Linux gets no hint about the `ps` prerequisite, so a missing `ps` shows up as an unexplained refusal. Expected: the Korean README states the same prerequisite as `README.md`. ## Change and scope - Quick start: add the Linux `ps` paragraph. Like the English text, it points to "Linux owned-process prerequisite" in `docs/installation.md`. - "What you can analyze": add the Linux `ps` requirement to the JavaScript/Electron row. Not included: other translations. #3113 covers Simplified Chinese. Ordinary documentation fix within existing boundaries; scope decision not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: documentation (`docs/readme/README_ko.md`) only. - Contribution scope fit and linked maintainer decision: documentation correction; not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata, package, or installation impact: none; no generated files committed. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Tests added or updated: none (documentation only). - Base reproduction or other evidence: compared with `README.md` at 877d404. No translated README mentions `procps` yet. - User-visible CLI/MCP output: not applicable. - Remaining proof gaps: none known. ## Validation performed Linux x64, Node.js 22.22.0, base 877d404: - `npm run docs:check`: passed (includes `readmeConsistency.test.ts`, 5/5) - `python3 scripts/website.py check`: passed (12 tests) - `npx oxfmt --check docs/readme/README_ko.md`: passed - `git diff --check`: clean ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: not applicable. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:08:39 +00:00
Sign in to join this conversation.
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#5688
No description provided.