sb-dev-sync-docslisted

# Keep bilingual documentation aligned Public user guides are paired by relative path: ```text docs/en/<relative-path> docs/ja/<relative-path> ``` English is published at `/`; Japanese is published at `/ja/`. Japanese remains the practical authoring source for new product explanations, but an edit in either language must not silently leave its counterpart with different behavior, commands, ownership boundaries, warnings, or navigation. ## Scope Apply this workflow to `index.md` and `guide/**/*.md` below both language roots. `docs/en/reference/` is intentionally English-only. Internal architecture, Decision, repository, contributor, and forward-test documents outside the two language roots are not translation pairs. ## Workflow 1. Inspect the requested change and the current Git diff. Identify every affected public page and its same-relative-path counterpart. 2. Read both complete pages. When Japanese content is created, edited, or reviewed for readability, also read [the Japanese style reference](references/japanese-style.md). When the edit changes product behavior, commands, paths, or ownership, verify the current source or accepted Decision instead of translating an assumption. 3. Preserve meaning, information architecture, examples, warnings, and link destinations, but write natural documentation for each audience rather than translating sentence by sentence. Edit both counterparts when meaning or information structure changes. For a Japanese