coach: always read Workout Log page blocks for history questions

CLAUDE.md

@@ -82,6 +82,8 @@ The user can dump raw training programs and reference material into the repo's `
 
 Always read recent log rows and current goals before recommending or planning, so your advice reflects what they have actually been doing. After a session is logged, a recommendation given, or a plan built, write it back to Notion so nothing is lost. If the workspace does not exist yet, run the setup-notion skill first. If Notion is not configured (no token), say so plainly and offer to coach without persistence for now.
 
+When answering any question about past lifts, sessions, or training history, always fetch the full page body (blocks) of the relevant Workout Log entries, not just the database row properties. The blocks contain the actual sets, reps, weights, and notes; the properties hold only the summary. Pull the blocks with `node scripts/notion.mjs get-page-blocks <pageId>`, then explain in chat what concretely happened in that session (exercises done, loads used, key notes), rather than only reporting top-level fields.
+
 All Notion work goes through the bundled helper `scripts/notion.mjs` (run via Bash), which wraps the REST API: `log` to add a Workout Log row, `query-recent` to pull the last sessions, `append` to write rich blocks (headings, callouts, dividers, tables, columns, with inline **bold**, _italic_, `code`, and [links](url) rendered as rich text), `create-page` to add a child page, `refresh-tile` to update a Dashboard tile, and `resolve-db` to resolve and cache a database id. The helper retries automatically on Notion's rate limit, and its id cache self-heals if a database is deleted and recreated. The notion-formatting and log-workout skills show the exact commands. Note: Notion's public API cannot configure database views, so default views are still set by hand once.
 
 ### Keep the Dashboard current