"architecture" documentations translated into Japanese

[takashiuesaka]

fixed #1021

All of these translated documents were created using the "skill".

[Copilot]

Pull request overview

Adds Japanese translations for the “architecture” documentation section under src/frontend/src/content/docs/ja/architecture/, aligning the JA locale with the existing English architecture docs.

Changes:

• Added Japanese versions of the architecture overview and multi-language architecture pages.
• Added Japanese translations for the resource model, hierarchies, API patterns, publishing, and examples pages.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/frontend/src/content/docs/ja/architecture/overview.mdx	Adds Japanese translation of the architecture overview page.
src/frontend/src/content/docs/ja/architecture/multi-language-architecture.mdx	Adds Japanese translation of the multi-language AppHost architecture page.
src/frontend/src/content/docs/ja/architecture/resource-model.mdx	Adds Japanese translation of the resource model page (DAG, states, interfaces).
src/frontend/src/content/docs/ja/architecture/resource-hierarchies.mdx	Adds Japanese translation of resource hierarchies/values/endpoints content (incl. synced language tabs).
src/frontend/src/content/docs/ja/architecture/resource-api-patterns.mdx	Adds Japanese translation of resource API patterns (AddX/WithX, annotations, value objects).
src/frontend/src/content/docs/ja/architecture/resource-publishing.mdx	Adds Japanese translation of resource publishing/manifest callback guidance.
src/frontend/src/content/docs/ja/architecture/resource-examples.mdx	Adds Japanese translation of end-to-end resource example content.

Comments suppressed due to low confidence (1)

src/frontend/src/content/docs/ja/architecture/resource-model.mdx:148

• The state table is written with || at the start of each row, which introduces an unintended empty first column in Markdown table rendering. Change these rows (and other tables in this file) to start with a single | so headers/columns align as intended.

| 状態 | 意味 |
|--|--|
| `Exited` | 実行完了（通常は短期間のジョブ、マイグレーション、ワンショットタスク用）。 |
| `FailedToStart` | スタートアップ初期化中に失敗しました。 |
| `Finished` | 正常に実行完了（バッチワークロードまたはスクリプト用）。 |

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[IEvangelist]

LGTM but we need to fix the failing tests, perhaps we need to adjust the SKILL to ensure that it's creating valid links. This is a good check to have in place, unfortunately it takes the full build to catch (and that takes time):

validating links 
08:34:33 [ERROR] [starlight-links-validator] Links validation failed.

   ╭─ ja/architecture/resource-model.mdx
   ·
80 | /ja/architecture/resource-api-patterns/#annotations
   ·                                      ╰── invalid hash

   ╭─ ja/get-started/resources.mdx
   ·
78 | /ja/architecture/resource-model/#built-in-resources-and-lifecycle
   ·                                      ╰── invalid hash

    ╭─ ja/whats-new/aspire-13-2.mdx
    ·
799 | /ja/architecture/resource-hierarchies/#context-based-endpoint-resolution
    ·                                      ╰── invalid hash

╭─                                 ─╮
· Found 3 invalid links in 3 files. ·
╰─                                 ─╯

If you want to leave the English bookmarks, you'd have to also splat <span id="annotations"></span> just under the corresponding heading. Alternatively, use the same slugify JS method in the skill to create the new bookmarks.

[takashiuesaka]

I confirmed that the link validation error occurred in documents that had been translated previously, not in the documents translated this time.

So, I am planning to create some scripts for the skill to validate links across the entire translated documentation for a specific language.