Investigate + close the config-as-code gap for cultureProfile

[JSONbored]

Part of #4092.

Confirmed finding (was originally filed as an open investigation — now resolved by direct code-check)

src/queue/processors.ts (~lines 7160, 9289): isRepoCultureProfileEnabled(env) && args.reviewCultureProfile === true — review.cultureProfile IS already consulted for the real on/off decision, but only as a REQUIRED additional AND-gate alongside GITTENSORY_REVIEW_CULTURE_PROFILE, same pattern as inlineComments/fixHandoff (#4099), reviewMemory (#4101), and impactMap (#4102). A repo can restrict via config but can't fully replace the env var.

Fix

Same shape as #4099/#4101/#4102: apply src/review/feature-activation.ts's existing precedence so review.cultureProfile: true can turn the feature on for a repo even without the env var/allowlist, and false forces it off. Follow whatever namespace decision #4099 makes for consistency.

Deliverables

• isRepoCultureProfileEnabled's real gate (both call sites) migrated to the resolver's full precedence
• Regression test: unset config preserves exact current behavior
• Tests mirroring the feature-activation pattern

Expected outcome

review.cultureProfile fully controls the feature per-repo, consistent with #4099/#4101/#4102.

Effort

S — confirmed, well-defined fix; no further investigation needed.

[linear-code]

JSO-3153

[JSONbored]

Closing as investigated, no code change warranted — same finding as #4101/#4102 (see #4101's closing comment for the full evidence), which applies identically here.

Both processors.ts call sites — isRepoCultureProfileEnabled(env) && args.reviewCultureProfile === true and isRepoCultureProfileEnabled(env) && reviewCultureProfile === true — were never a "required-AND-because-allowlist" shape like inlineComments/fixHandoff's pre-#4116 code; there is no isConvergenceRepoAllowed term anywhere in cultureProfile's history (absent from feature-activation.ts's FEATURE_GLOBAL_FLAG map). reviewCultureProfile is already a definite boolean by the time it reaches either AND-gate (resolveReviewPromptOverrides's cultureProfile: manifest?.review.cultureProfile === true), so envFlag && definiteBoolean is algebraically identical to any "kill-switch, then let the manifest decide" rewrite. review.cultureProfile already fully controls this feature today (subject to the operator kill-switch) — there was nothing to bypass.

No PR was opened against this issue (implementation work stayed local/uncommitted); closing without shipping a fix for a gap that doesn't exist, consistent with #4101/#4102's disposition.