Use English for the public landing page on lmstudio.ai and the root README.md. This is the project's editorial choice for a broad audience, not a claim that the Hub requires English or automatically selects translations.
Every guide starts with links to all five languages. Simplified Chinese is the current Chinese edition; Traditional Chinese can be added as a separate edition if needed. Do not assume automatic language switching on the Hub.
Use absolute Hub file-page URLs for documentation navigation: https://lmstudio.ai/yuanjumay/analyze-images-advanced/files/<path>. This applies to the language selector, links to this policy, and links back to the guides. The same README appears on the project landing page and individual file pages, where relative paths resolve differently. Checking that local files exist is not sufficient. After publishing, check the rendered links from the landing page, a translated guide and the nested policy page. If the owner or project name changes, update the base URL in all six documents together.
Text and naming
Keep the public name Analyze Images Advanced and plugin ID yuanjumay/analyze-images-advanced stable.
Use English for the public short description and release summary, with the language selector near the top of the README. Describe the release as local image discovery, single/joint analysis, optional automatic attachment, and local/Strata backends.
Release preparation
Check the source and package version against all five guides. Review the title, first paragraph and short description for the final feature scope.
Check language links, Markdown fences, commands and setting labels. Require absolute Hub file-page URLs and confirm the target pages contain the expected document, not just HTTP 200. Run the documented checks when code has changed; documentation-only edits do not require model inference tests.
This policy does not change runtime UI languages or translate tool schemas. The release's behavior is shared across all README languages.
Publication and language policy
Main language
Use English for the public landing page on lmstudio.ai and the root README.md. This is the project's editorial choice for a broad audience, not a claim that the Hub requires English or automatically selects translations.
Every guide starts with links to all five languages. Simplified Chinese is the current Chinese edition; Traditional Chinese can be added as a separate edition if needed. Do not assume automatic language switching on the Hub.
Use absolute Hub file-page URLs for documentation navigation: https://lmstudio.ai/yuanjumay/analyze-images-advanced/files/<path>. This applies to the language selector, links to this policy, and links back to the guides. The same README appears on the project landing page and individual file pages, where relative paths resolve differently. Checking that local files exist is not sufficient. After publishing, check the rendered links from the landing page, a translated guide and the nested policy page. If the owner or project name changes, update the base URL in all six documents together.
Text and naming
Keep the public name Analyze Images Advanced and plugin ID yuanjumay/analyze-images-advanced stable.
Use English for the public short description and release summary, with the language selector near the top of the README. Describe the release as local image discovery, single/joint analysis, optional automatic attachment, and local/Strata backends.
Release preparation
Check the source and package version against all five guides. Review the title, first paragraph and short description for the final feature scope.
Check language links, Markdown fences, commands and setting labels. Require absolute Hub file-page URLs and confirm the target pages contain the expected document, not just HTTP 200. Run the documented checks when code has changed; documentation-only edits do not require model inference tests.
This policy does not change runtime UI languages or translate tool schemas. The release's behavior is shared across all README languages.
Keep actual tool names, UI labels, parameter keys, command lines, filenames and API identifiers unchanged in translations. Translate explanations and example prompts.
English is the reference for published behavior. Changes can be drafted in Japanese, but reconcile the English guide and all four translations in the same documentation update. Do not silently leave translations describing an older release.
Keep versions, defaults, format support, limits, failure behavior, validation scope, credits and license consistent. Claims about model accuracy require actual evidence; mocked tests establish request behavior only.
Keep machine-specific paths, troubleshooting transcripts, private credentials and local development history outside public guides. The previous mixed-language README is preserved in the workspace backup, outside this plugin directory.
Review the files to be included in the upload. Exclude local caches, secrets and machine-specific records according to the actual packaging behavior; do not assume a particular ignore filename is supported.
Read LM Studio's publishing guide and lms push reference when publishing. lms push uploads the plugin and can update an existing project; changing the manifest name creates a different project.
Publishing is a separate action. Preparing these guides does not authorize an upload. After publication, verify the displayed version, main README, language links and installation flow.
Keep actual tool names, UI labels, parameter keys, command lines, filenames and API identifiers unchanged in translations. Translate explanations and example prompts.
English is the reference for published behavior. Changes can be drafted in Japanese, but reconcile the English guide and all four translations in the same documentation update. Do not silently leave translations describing an older release.
Keep versions, defaults, format support, limits, failure behavior, validation scope, credits and license consistent. Claims about model accuracy require actual evidence; mocked tests establish request behavior only.
Keep machine-specific paths, troubleshooting transcripts, private credentials and local development history outside public guides. The previous mixed-language README is preserved in the workspace backup, outside this plugin directory.
Review the files to be included in the upload. Exclude local caches, secrets and machine-specific records according to the actual packaging behavior; do not assume a particular ignore filename is supported.
Read LM Studio's publishing guide and lms push reference when publishing. lms push uploads the plugin and can update an existing project; changing the manifest name creates a different project.
Publishing is a separate action. Preparing these guides does not authorize an upload. After publication, verify the displayed version, main README, language links and installation flow.