side-quest 2.4.0 → 2.5.0 (recovery: landed on the GitHub mirror by mistake) #3
Loading…
Reference in a new issue
No description provided.
Delete branch "side-quest-2.4-2.5-recovery"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
These three commits were merged via PRs against the
githubmirror by mistake and never reached canonicalmainhere; the mirror sync then reset GitHub'smainback, orphaning them. Nothing was lost — this bundles them onto Forgejomainwhere they belong. Clean linear chain on top ofa51fce7.XP_BY_CR,RESPONSE_XP_TIERS), level-scaled rewards.broker'sapostrophe in a${VAR:?...}) that stopped the launchd sync daemon on macOS.respondStop hook (extract_turn_features+score_turn, no ML/deps); cap the level-award multiplier at 3x (the uncapped version was a cross-machine inflation runaway); self-echo guard + dedup ring 500→4000 +reconcile/reset-ledgerto stop the shared ledger drifting.112 tests pass, ruff clean, daemon
bash -nclean. Already deployed to the author's machine and verified.See also issues #1 (leaderboard) and #2 (
/side-quest:signup) which build on 2.5.0.Apostrophe in ${XP_MQTT_HOST:?...broker's hostname} inside a double-quoted string aborts bash 3.2 (macOS /bin/bash, used by the launchd plist) with 'unexpected EOF'. zsh -n missed it. Reworded to drop the apostrophe.