[Enhancement] Engagement: Removal candidate (policy-disabled): Founding-Member Community Challenge (public + admin controllers + templates)

Area: Engagement (audit p9) · Surface: src/Controllers/CommunityChallengeController.php + src/Controllers/AdminCommunityChallengeController.php · Dimension: dead-code · Severity: enhancement

The Founding-Member community challenge (attest / request-review + admin approve/reject) is POLICY_DISABLED — present but opt-in only, so off for every tenant by default. Reporting as removal/opt-in candidate per the policy-disabled rule, not as orphaned/broken code.

Evidence

FeatureCatalog.php:85 lists 'community_challenge' in POLICY_DISABLED with the comment that it surfaces a hardcoded post-5/tell-5/mod-approve flow that 'doesn't suit every tenant... POLICY_DISABLED so each tenant opts in explicitly.' CommunityChallengeController.php:32-35 gateFeature() calls `Container::get(Features::class)->require('community_challenge');` and is invoked at the top of show/attest/requestReview (lines 39,60,76). Routes /community-challenge* (426-428) and admin /community-challenge* (1518-1520). Templates community-challenge.php and admin/community-challenge/index.php rendered only here.

Suggested fix. This one is explicitly designed for per-tenant opt-in, so it is best left in place. No action unless the challenge concept is being permanently dropped.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.