docs: use latest packages in ordinary install guides

[link1345]

Ordinary installation examples still pinned Gua 1.1.0 after the versioned documentation update. New setups now select the current package release, with explicit guidance to retain the resolved version and match the game integration.

• Update EN/JA NuGet commands to omit --version; explain compatible stable selection, concrete .csproj / Directory.Packages.props versions, and explicit versions for existing setups.
• Use npm @latest for new setup, document package.json / package-lock.json and npm ci, and keep reproducible MCP setups explicitly versioned.
• Link Godot, Unity, and Inspector setup to the latest release; show the real versioned asset naming pattern. Keep CI examples pinned to verified available 1.1.1 assets.
• Base this follow-up on current main after docs: update bilingual guides and v1.1.0 changelog #27. Preserve the historical v1.1.0 changelog and versioned API/source examples.

Validation: Astro check and 60-page build (0 errors/warnings/hints); 4 tests; 2,182 internal links/anchors; 64 desktop/mobile renders across all 32 changed EN/JA pages, plus 16 navigation/readability captures and 8 final renders after the review correction. No browser errors or horizontal overflow. An actual versionless Gua.Core install recorded Version="1.1.1" in a disposable project. Release metadata confirms the 1.1.1 Godot ZIP and Unity TGZ naming. Independent read-only review completed before submission.

No deployment or release operation is included.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-06T00:43:48.683254Z	73405e9	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 73405e9f13

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Pin the MCP server version in persistent client config

This is a persistent MCP-client registration rather than a one-time installation, so @latest can resolve a different gui-mcp release on a new machine or after a cache refresh, independently of the installed game integration; a newer protocol/API release can therefore break an otherwise unchanged setup. The inspected Bun 1.2.14 help states bunx <package><@version> and that it automatically installs into a global shared cache, so this path has no project lockfile to preserve the resolved version. This also contradicts the new /docs/npm-packages/ guidance to use a matching explicit version for reproducible MCP configurations. Keep the concrete compatible version here (and in the Japanese mirror), while reserving @latest for the initial discovery/install command.

Useful? React with 👍 / 👎.