Krzysztof kuhy Rudnicki 28c243d066 Coach toolbox, clusters, cold re-tests and property cards (TODO-coach 9-12) ... - toolbox.json: 20 entries over a fixed 40-property vocabulary; no entry's property set nests in another's, so every property card has one answer. - clusters.json: decision 10's six clusters, ids plus slugs. - progress.py (stdlib only): solved = code + postmortem, re-tests due at +3/+10 days, cluster progress, all derived from the session logs. - leetcode due / --cluster <name> / --retest <slug> (cluster_cli.py): due re-tests of the cluster first, then the next problem with no code event, skipping LeetCode-Accepted ones (live check fails open). A cold re-test logs `retest` only once the session reached a post-mortem. - Post-mortem cards are property -> operation only, generated by toolbox_cards (shared slug `toolbox`); `add` appends an entry only after kuhy confirms its properties. The local client accepts {"toolbox": [...]}. - _coach_log publishes retests_due and clusters from the coach. - requirements-sync treats sibling repo packages as first-party. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PjvF5DZG9JduSBYKxqyysi		2026-10-23 15:39:52 +02:00
leetcode_coach/leetcode_coach	Coach toolbox, clusters, cold re-tests and property cards (TODO-coach 9-12)	2026-10-23 15:39:52 +02:00