feat(points): show early finish and expected points on questions

Core pays 10 early points for an unproven Steam finish. The rest
comes with proof. Show this in the toast and the game line.
Questions cards show the full value from GET /api/rewards/expected.

README.md

@@ -56,7 +56,10 @@ To Be Played is split into three repositories:
   Play Next "Start", Questions, add game) `usePointsCheck` asks Core `GET /api/rewards/games/{appid}`, reloads the wallet
   when the balance moved and shows a toast ("+N points", "Already paid on ...", "No points yet: reason"). The game page
   shows the paid rows and the reason per missing kind (`GamePointsLine`); `pointsNotice` in `utils/rewards.js` picks the
-  toast, the reason codes come from Core and `POINTS.REASONS` only maps them to texts.
+  toast, the reason codes come from Core and `POINTS.REASONS` only maps them to texts. A finish without proof pays 10
+  early points (toast "+10 points; the rest comes with proof", game line "The rest of the finish points: play once on
+  Steam after finishing"), and the rest once Steam play proves it. A "Finished?" card on the Questions page shows
+  "Up to N points" from `GET /api/rewards/expected`; when that call fails the card shows no line.
 
 ```mermaid
 flowchart LR
@@ -65,6 +68,7 @@ flowchart LR
     Check --> Toast["Toast"]
     Check -->|balance moved| Wallet["reloadWallet: header"]
     Core --> Line["GamePointsLine on the game page"]
+    Questions["Questions page"] -->|"GET /api/rewards/expected"| CoreExpected["Core /api/rewards/expected"]
 ```
 - **Landing page**: next to the community numbers and the top games, three blocks: games per platform, top genres and
   finished games per year of all users.