[PR #1512] [MERGED] docs: align the Indonesian README with the other translations #2932

Closed
opened 2026-10-17 21:11:58 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1512
Author: @morluto
Created: 10/10/2026
Status: ✅ Merged
Merged: 10/10/2026
Merged by: @morluto

Base: main ← Head: cursor/fix-indonesian-readme-formatting-a75d


📝 Commits (1)

  • bb01002 docs: align the Indonesian README with the other translations

📊 Changes

19 files changed (+325 additions, -17 deletions)

View changed files

📝 README.md (+1 -1)
📝 README_ar.md (+1 -1)
📝 README_de.md (+1 -1)
📝 README_es.md (+1 -1)
📝 README_fa.md (+1 -1)
📝 README_fr.md (+1 -1)
➕ README_id.md (+307 -0)
📝 README_ja.md (+1 -1)
📝 README_ko.md (+1 -1)
📝 README_pl.md (+1 -1)
📝 README_pt-BR.md (+1 -1)
📝 README_ru.md (+1 -1)
📝 README_th.md (+1 -1)
📝 README_tr.md (+1 -1)
📝 README_uk.md (+1 -1)
📝 README_vi.md (+1 -1)
📝 README_zh-TW.md (+1 -1)
📝 README_zh.md (+1 -1)
📝 tests/conformance/readmeConsistency.test.ts (+1 -0)

📄 Description

Summary

Lands the Bahasa Indonesia README from #1508 and fixes the formatting that kept it out of the shared README layout.

Problem and expected behavior

#1508 adds README_id.md, but the file does not match the other translations:

  • The file starts with a leading space before <div align="center">.
  • The language selector puts Bahasa Indonesia second and is not linked from the other READMEs.
  • The Node.js badge and table of contents point at English heading slugs (#what-you-can-analyze, #quick-start, #showcases, #update-rea) that the translated headings do not generate.
  • The analysis table is not column-aligned like the other READMEs.
  • Onboarding shell examples are not registered in the README consistency check.

Translated READMEs should use the same selector order, the same non-anchor links and shell commands as README.md, and in-page links that resolve to their own headings.

Change and scope

  • Keeps the contributed Indonesian prose.
  • Moves Bahasa Indonesia to the end of every language selector, matching how later translations were added.
  • Points the badge, contents, and FAQ links at #current-status and the translated heading slugs.
  • Aligns the analysis table.
  • Registers README_id.md in tests/conformance/readmeConsistency.test.ts.

Documentation links other than README selectors and in-page anchors stay identical to README.md, so the documentation-fact check still passes.

Contract and boundary impact

  • Semantic owner and earliest changed stage: onboarding documentation only.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Process execution, authorization, cleanup, or containment impact: none.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. README_id.md is repository documentation and is not added to the published package file list.

Evidence and regression coverage

  • Tests added or updated: tests/conformance/readmeConsistency.test.ts now includes README_id.md.
  • Base reproduction or other evidence: compared non-anchor, non-README link targets and bash examples with README.md; both lists match. Checked that every in-page anchor is a translated heading slug or the existing current-status id.
  • User-visible CLI/MCP output (if applicable): not applicable.
  • Remaining proof gaps: full npm run docs:check was not run. The README link comparison covers the documentation-fact rule this change can affect.

Validation performed

  • Link-target and bash-example comparison against README.md — lists match.
  • In-page anchor check — every # link resolves to a heading slug or current-status.
  • npm run test:local -- tests/conformance/readmeConsistency.test.ts — 2 tests passed.

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: none.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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.
Open in Web Open in Cursor 

🔄 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/1512 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/10/2026 **Status:** ✅ Merged **Merged:** 10/10/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `cursor/fix-indonesian-readme-formatting-a75d` --- ### 📝 Commits (1) - [`bb01002`](https://github.com/morluto/rea/commit/bb01002777db8f577b1d7bf1578124d42210c0d6) docs: align the Indonesian README with the other translations ### 📊 Changes **19 files changed** (+325 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) 📝 `README_ar.md` (+1 -1) 📝 `README_de.md` (+1 -1) 📝 `README_es.md` (+1 -1) 📝 `README_fa.md` (+1 -1) 📝 `README_fr.md` (+1 -1) ➕ `README_id.md` (+307 -0) 📝 `README_ja.md` (+1 -1) 📝 `README_ko.md` (+1 -1) 📝 `README_pl.md` (+1 -1) 📝 `README_pt-BR.md` (+1 -1) 📝 `README_ru.md` (+1 -1) 📝 `README_th.md` (+1 -1) 📝 `README_tr.md` (+1 -1) 📝 `README_uk.md` (+1 -1) 📝 `README_vi.md` (+1 -1) 📝 `README_zh-TW.md` (+1 -1) 📝 `README_zh.md` (+1 -1) 📝 `tests/conformance/readmeConsistency.test.ts` (+1 -0) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Summary Lands the Bahasa Indonesia README from #1508 and fixes the formatting that kept it out of the shared README layout. ## Problem and expected behavior #1508 adds `README_id.md`, but the file does not match the other translations: - The file starts with a leading space before `<div align="center">`. - The language selector puts **Bahasa Indonesia** second and is not linked from the other READMEs. - The Node.js badge and table of contents point at English heading slugs (`#what-you-can-analyze`, `#quick-start`, `#showcases`, `#update-rea`) that the translated headings do not generate. - The analysis table is not column-aligned like the other READMEs. - Onboarding shell examples are not registered in the README consistency check. Translated READMEs should use the same selector order, the same non-anchor links and shell commands as `README.md`, and in-page links that resolve to their own headings. ## Change and scope - Keeps the contributed Indonesian prose. - Moves **Bahasa Indonesia** to the end of every language selector, matching how later translations were added. - Points the badge, contents, and FAQ links at `#current-status` and the translated heading slugs. - Aligns the analysis table. - Registers `README_id.md` in `tests/conformance/readmeConsistency.test.ts`. Documentation links other than README selectors and in-page anchors stay identical to `README.md`, so the documentation-fact check still passes. ## Contract and boundary impact - Semantic owner and earliest changed stage: onboarding documentation only. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Process execution, authorization, cleanup, or containment impact: none. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. `README_id.md` is repository documentation and is not added to the published package file list. ## Evidence and regression coverage - Tests added or updated: `tests/conformance/readmeConsistency.test.ts` now includes `README_id.md`. - Base reproduction or other evidence: compared non-anchor, non-README link targets and bash examples with `README.md`; both lists match. Checked that every in-page anchor is a translated heading slug or the existing `current-status` id. - User-visible CLI/MCP output (if applicable): not applicable. - Remaining proof gaps: full `npm run docs:check` was not run. The README link comparison covers the documentation-fact rule this change can affect. ## Validation performed - Link-target and bash-example comparison against `README.md` — lists match. - In-page anchor check — every `#` link resolves to a heading slug or `current-status`. - `npm run test:local -- tests/conformance/readmeConsistency.test.ts` — 2 tests passed. ## 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: none. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-9a32b5fb-61ec-48c0-a9d2-629dfff6a75d?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-9a32b5fb-61ec-48c0-a9d2-629dfff6a75d&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-17 21:11:58 +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#2932
No description provided.