Restore PC Features through authenticated PCGamingWiki access

[dguay]

What to build

Restore PC Features with a server-side PCGamingWiki integration that authenticates with bot credentials. Keep the credentials out of the Expo application and use the current PCGamingWiki Cargo schema. Both Steam AppID lookup and game-name fallback must return the same typed feature result expected by the game details screen.

PCGamingWiki bot credentials are an external prerequisite for the live smoke check. Store them only as server-side secrets and document the provisioning step. Do not deploy the function or push secrets without explicit approval.

Acceptance criteria

• Cargo requests run only in trusted server-side code and authenticate through the PCGamingWiki bot-password login flow.
• No PCGamingWiki username, bot password, session token, or cookie is included in the Expo bundle or a public environment variable.
• Queries use the current Game table and verified current names for every joined table and requested field.
• Steam AppID lookup and game-name fallback both work through the server-side integration.
• The integration distinguishes an authenticated no-match result from authentication, permission, rate-limit, transport, and schema errors.
• The custom user agent follows the current PCGamingWiki contact-information requirement.
• Tests cover authenticated success, no match, expired login, permission denial, rate limiting, and malformed upstream responses without calling the live service.
• An agent-runnable smoke command confirms that Elden Ring, Steam AppID 1245620, returns a page name and at least one documented PC feature when credentials are configured.
• Setup documentation lists the required secrets, request rate limit, and local verification command.

Blocked by

• Stop PCGamingWiki failures from poisoning the feature cache #10