Release 2026.04.06.04 to main

[alexphillips-dev]

What changed

• add curated override notes for 2026.04.06.04
• make the main release publish cumulative notes since v2026.04.05.13 instead of only the top manifest block

Why

release-on-main builds GitHub release notes from the current version block or docs/releases/<version>.md.
Without an override, publishing 2026.04.06.04 from main would only describe the latest manifest slice instead of the full set of changes shipped after the last main release.

Impact

• GitHub release notes for v2026.04.06.04 will include the full delta since the last main release
• no package, source, or runtime behavior changes are introduced in this PR

Validation

• bash scripts/ensure_plg_changes_entry.sh --check-only --require-explicit --version 2026.04.06.04
• bash scripts/build_release_notes.sh --version 2026.04.06.04 --output ...
• bash scripts/release_notes_consistency_guard.sh
• pre-push hook suite passed

[chatgpt-codex-connector]

💡 Codex Review

FolderView-Plus/scripts/run_ci_suite.sh

Lines 157 to 158 in 51124f8

	local default_required="0"
	export FVPLUS_BROWSER_SMOKE_REQUIRED="${FVPLUS_BROWSER_SMOKE_REQUIRED:-${default_required}}"

Honor --release for browser smoke enforcement

When run_ci_suite.sh is invoked with --release, this function now always defaults FVPLUS_BROWSER_SMOKE_REQUIRED to 0 unless callers set it explicitly, so release runs can skip browser smoke validation entirely when FVPLUS_BROWSER_SMOKE_URL is unset. That breaks the script’s documented --release contract (“Enforce required browser and theme smoke configuration”) and can let release preparation pass without the intended smoke gate.

---

FolderView-Plus/scripts/run_ci_suite.sh

Lines 169 to 170 in 51124f8

	local default_required="0"
	export FVPLUS_THEME_MATRIX_REQUIRED="${FVPLUS_THEME_MATRIX_REQUIRED:-${default_required}}"

Honor --release for theme matrix enforcement

This path also now defaults FVPLUS_THEME_MATRIX_REQUIRED to 0 regardless of --release, which allows theme-matrix smoke checks to be skipped in release mode unless external env wiring sets the variable first. In practical terms, bash scripts/run_ci_suite.sh --release no longer guarantees this required release-time validation, weakening the release gate.

ℹ️ 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".