Profile delivery

Profiles are prebuilt by default on every site. On a PHP-served site, turn off Static profile pages in Tools → Feature flags to skip profile HTML during builds. The equivalent environment override is FORUM_STATIC_PROFILE_PAGES_ENABLED=false; use the same setting for the builder and PHP frontend. Canonical site settings persist across commands; a command-only environment override does not configure the web process.

Run your usual full ./v3 build-static command with the same repository, database, destination and other arguments after switching. Profile links continue to work through PHP, and profile, identity, approval and history data remain available. This setting is independent of Static detail pages, which controls threads and posts.

The PHP frontend bypasses old profile artifacts immediately when disabled. A shared refresh drops copied profile artifacts but does not regenerate them when enabling; a full build restores them. Direct single-route refreshes also skip disabled profiles. Keep this control enabled for static-only hosting, which cannot supply the runtime route. Direct requests to old physical .html files are outside PHP routing; retire old public-root exports when changing a static-only deployment to PHP.

A failed candidate leaves the current release active. Correct the reported error and rerun the same full build. To return to prebuilt profiles, enable the control (or remove the false environment override), then complete a full build. Existing profile access rules still apply.

For the QDB replay at /home/qdb/v3, use the same command and arguments that produced release-20261030201011-af62aa46; only change the profile setting intentionally. The original argument list was not supplied in the timing report, so it is not reconstructed here. Record the application commit, canonical repository HEAD, PHP version and effective setting before running. Preserve the complete output, including the new Rendering profile pages complete (...) timing when enabled, the skip message when disabled, phase timings, artifact counts, activation path and time output. Compare against 314.961 seconds total, 39.1605 seconds indexing commits and 44.503 seconds indexing activity evidence, noting corpus/configuration/cache differences. After success, follow an author link to a profile and inspect Activity and a commit/source view. Production access, deployment and replay have not been performed in the local implementation cycle.