✨ Changed comments to be enabled by default

[ErisDS]

Summary

• Flip comments_enabled default from off to all so new sites allow members to comment without staff having to find the setting first.
• Hide the Admin sidebar Comments item when comments are explicitly disabled, so navigation reflects the disabled state.
• Update fixture, integrity hash, and the snapshots that captured the old default (settings responses, pages/posts Content API, email previews, email card rendering, the two portal/stripe e2e tests that need to opt-out).

Carved out of #27653 to ship the default-flip independently of the pinning work.

Test plan

• Backend unit + e2e suites green after snapshot regen (some byte-count drift expected from main moving since the original commit was authored — verify locally)
• Fresh install: confirm new sites have comments_enabled = "all"
• Existing install: confirm settings already persisted in DB are untouched
• Admin: with comments off, Comments nav item is hidden; with comments on, visible

🤖 Generated with Claude Code

[github-actions]

It looks like this PR contains a migration 👀
Here's the checklist for reviewing migrations:

General requirements

• ⚠️ Tested performance on staging database servers, as performance on local machines is not comparable to a production environment
• Satisfies idempotency requirement (both up() and down())
• Does not reference models
• Filename is in the correct format (and correctly ordered)
• Targets the next minor version
• All code paths have appropriate log messages
• Uses the correct utils
• Contains a minimal changeset
• Does not mix DDL/DML operations
• Tested in MySQL and SQLite

Schema changes

• Both schema change and related migration have been implemented
• For index changes: has been performance tested for large tables
• For new tables/columns: fields use the appropriate predefined field lengths
• For new tables/columns: field names follow the appropriate conventions
• Does not drop a non-alpha table outside of a major version

Data changes

• Mass updates/inserts are batched appropriately
• Does not loop over large tables/datasets
• Defends against missing or invalid data
• For settings updates: follows the appropriate guidelines

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• ghost/core/test/e2e-api/admin/__snapshots__/email-previews.test.js.snap is excluded by !**/*.snap

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: aaddba85-b546-4f92-b6ee-878d4de46956

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

This PR changes the default value of the comments_enabled setting from "off" to "all", updates the admin sidebar navigation to fetch and conditionally display the Comments menu item based on this setting, and adjusts e2e tests to explicitly control comment settings during test execution. The admin UI now computes visibility by combining membership access, the commentModeration feature flag, and the comments_enabled setting value, replacing a simpler direct membership check.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: enabling comments by default, which is the primary objective of the PR.
Description check	✅ Passed	The description is directly related to the changeset, providing clear details about the default change, UI updates, and test plan for the implementation.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch enable-comments-by-default

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}