[logicwu0]

Describe what this PR does / why we need it

Disabling Nacos Prompt, including leaving it disabled by default, currently sets the JVM system property spring.nacos.config.enabled to false. This overwrites an explicitly enabled Nacos Config setting and affects other application contexts in the same JVM.

This PR keeps the Prompt condition scoped to its own auto-configuration without changing the application's global Nacos Config setting.

Does this pull request fix one issue?

Fixes #68

Describe how you did it

• Remove the system-property mutation from PromptTemplateNacosConfigCondition; retain the default-disabled behavior and existing bean backoff conditions.
• Add regression coverage for all nine combinations of Prompt and global Config settings (true, false, unset), concurrent application contexts, context recreation, and application-provided beans.
• Restore system properties after each test and serialize access to system properties within the test class.
• Document the independent switches and migration from the former implicit global disablement.

Describe how to verify it

mvn -B -ntp -pl auto-configurations/prompt/argi-autoconfigure-nacos-prompt -am -Dcheckstyle.skip=false test

Verified locally with JDK 21:

• Before the production fix, the expanded auto-configuration suite ran 14 tests with 6 failures, reproducing global values changing from true or unset to false.
• After the fix, all 35 tests across the Prompt and Prompt auto-configuration modules passed with no failures or skips.
• Checkstyle reported zero violations.

Special notes for reviews

Only three files change: the condition, its auto-configuration tests, and a module README with migration notes.

Applications that depended on disabling Prompt to disable Nacos Config must now explicitly configure spring.nacos.config.enabled=false. Applications using Nacos Config retain responsibility for their connection configuration; disabling Prompt should not suppress genuine Nacos Config errors.

These are offline auto-configuration and unit tests, not a live Nacos-server connectivity verification.

[yuluo-yx]

I’m not entirely clear on the context here; I’ll need to look into it. As the comment explains, this fixes an issue.