Add a single global switch that controls whether Article Guidance is available on a wiki, and expose it through Community Configuration.

When Article Guidance is globally disabled, the wiki should behave as if the Article Guidance user-facing feature were not enabled.

Expected behavior

Introduce an ArticleGuidanceEnabled configuration value.

The effective value should come from Community Configuration when an on-wiki value has been explicitly set. Otherwise, it must fall back to the state that would have applied before this setting was introduced.

When ArticleGuidanceEnabled is false:

• red links do not redirect to Article Guidance, regardless of ArticleGuidanceRedirectEnabled;
• Special:NewArticle does not expose the Article Guidance workflow when accessed directly;
• the articleguidance-enable user preference is not offered;
• Article Guidance client-side functionality must not expose another way to enter the disabled feature.

When ArticleGuidanceEnabled is true, existing Article Guidance behavior is unchanged and the more specific configuration values, such as ArticleGuidanceRedirectEnabled and the junior-editor restriction, continue to determine redirect behavior.

Implementation notes

T437586: Allow configuring redirects via Community Configuration introduced the Article Guidance Community Configuration provider. Extend that provider/schema.

Add the global setting to the extension configuration and make the effective Community Configuration value available to the places that decide whether Article Guidance is exposed.

Check the global switch as early as practical in the relevant paths, in particular:

• RedLinkRedirectHandler
• SpecialNewArticle
• the user preference
• parser hooks
• any client-side entry path that can expose Article Guidance independently

Avoid duplicating the Community Configuration lookup or global-enabled logic throughout the extension; prefer a shared way of obtaining the effective feature state.

The global switch should take precedence over the redirect settings. For example:

Dependencies and prerequisites

• T437586: Allow configuring redirects via Community Configuration provides the Article Guidance Community Configuration provider and should be deployed before this feature is enabled for communities.
• T437643: Remove ArticleGuidanceRedirectEntryPointTitles may remove the legacy entry-point redirect independently; this task should not add new handling for that path.

No design work is required beyond defining the Community Configuration label/help text for the new global checkbox.

No data migration or schema migration is expected, but the introduction of the new setting may require a configuration/fallback strategy to preserve existing wiki enablement state.

Acceptance criteria

• Community Configuration exposes a global Article Guidance enable/disable setting.
• Introducing the new setting does not change existing Article Guidance availability:
  • Article Guidance stays enabled on every wiki where it is currently enabled.
  • Article Guidance does not become enabled on any wiki where it is currently disabled.
• With no explicit on-wiki value configured, the effective Article Guidance state remains the same as before this setting was introduced.
• Changing the value through Community Configuration takes effect without a deployment.
• When globally disabled:
  • red links never redirect into Article Guidance;
  • direct access to Special:NewArticle does not expose the Article Guidance workflow;
  • the Article Guidance user preference is not shown.
• ArticleGuidanceRedirectEnabled=true cannot override a globally disabled feature.
• When globally enabled, existing redirect, eligibility and direct-access behavior continues to work.
• The existing Community Configuration redirect settings introduced in T437586: Allow configuring redirects via Community Configuration continue to work.

QA plan

Risks and affected areas

The main risks are:

• accidentally disabling Article Guidance on wikis where it is currently enabled;
• accidentally enabling Article Guidance on wikis where it is currently disabled;
• applying the switch to one entry path but leaving Article Guidance accessible through another;
• getting precedence wrong between the global switch and ArticleGuidanceRedirectEnabled;
• failing to preserve the existing state when no Community Configuration value has been set.

The affected areas are wiki-level feature enablement, the red-link redirect, direct Special:NewArticle access, the user preference, and Community Configuration.

Automated testing

Consider automated coverage for:

• existing enabled configuration + no Community Configuration override → Article Guidance remains enabled;
• existing disabled configuration + no Community Configuration override → Article Guidance remains disabled;
• globally disabled + redirect enabled → no redirect;
• globally enabled + redirect enabled → existing redirect behavior remains;
• globally enabled + redirect disabled → direct Article Guidance access remains available without automatic redirect;
• the disabled state of Special:NewArticle;
• hiding the user preference while globally disabled;
• Community Configuration override and fallback behavior.

Manual testing

Test on a local wiki or Patch Demo with Article Guidance and Community Configuration installed.

First verify migration/fallback behavior:

1. Configure the wiki as Article Guidance-enabled using the existing deployment configuration, without setting the new Community Configuration value.
   • Article Guidance remains enabled.
2. Configure the wiki as Article Guidance-disabled using the existing deployment configuration, without setting the new Community Configuration value.
   • Article Guidance remains unavailable.

Then test Community Configuration overrides on an enabled wiki:

3. Disable Article Guidance through Special:CommunityConfiguration.
   • An in-scope red link uses the normal editor rather than Article Guidance.
   • Directly visiting Special:NewArticle does not expose the Article Guidance workflow.
   • The Article Guidance user preference is not offered.
4. Re-enable Article Guidance while disabling redirects.
   • Direct Special:NewArticle access works.
   • Red links use the normal editor.
5. Enable both Article Guidance and redirects.
   • An eligible red link redirects to Article Guidance.
   • Direct Special:NewArticle access works.
6. Remove the on-wiki value and verify that behavior returns to the pre-existing deployment-configured state.

The core scenarios should be checked on both desktop and mobile where the affected entry paths are available.

No production-only verification is required; all behavior can be exercised before deployment.