Area: Engagement (audit p9) · Surface: /projects (+ subroutes), /community-challenge · Dimension: documentation · Severity: minor
Member-hosted Projects (with BOM export, releases, file uploads, comments, cloning) and the founding-member Community Challenge are both real user-facing surfaces guarded behind feature flags, but neither has a mobieusKnow article. Both are POLICY_DISABLED (never auto-enabled), so the missing docs match the never-shipped-to-customers status; severity is minor. The Community Challenge in particular has an attest/request-review member flow with no help content explaining how to qualify.
Evidence
ProjectController.php (50KB) gates every action with `$this->features->require('projects')` (platform/src/Controllers/ProjectController.php:27) and renders projects/index, show, create, edit, releases, etc. CommunityChallengeController.php renders the founding-member challenge (post-5 / tell-5 / mod-approve flow). Wiki has NO coverage: `curl https://support.mobieus.io/know/projects` → HTTP 404; `curl https://support.mobieus.io/know/community-challenge` → HTTP 404; `?q=projects`, `?q=project`, `?q=challenge` all → 'No results'; /know/index link dump has no projects or challenge entries. Both keys are POLICY_DISABLED (platform-admin/src/Domain/FeatureCatalog.php:78 'projects', :85 'community_challenge'), and GameController.php:386 and CommunityChallengeController.php:27 both reference the POLICY_DISABLED gate.
Suggested fix. Treat the same as Games: if these stay POLICY_DISABLED permanently, close as won't-do. If a tenant can opt in, add /know/projects and a /know/community-challenge article (the latter explaining the post-5 / tell-5 / mod-approve qualification flow) and seed via docs/customer-help/.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus