Repository navigation
fix: remove the worldwide token counter - #4322
Open
ScriptedAlchemy wants to merge 5 commits into
Open
ScriptedAlchemy wants to merge 5 commits into
ScriptedAlchemy wants to merge 5 commits into
Conversation
|
ScriptedAlchemy
enabled auto-merge
October 18, 2026 16:46
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3619
What was broken. The worldwide token counter was still live: the CLI and MCP server uploaded pending token amounts to the hosted Cloudflare Worker (
/increment,/total), the doctor probed it, anduser.upload_enabled.v1,enable-upload-counteranddisable-upload-counteradvertised it.Fix. The counter is removed end to end and local accounting is untouched.
cloud.rs,global::try_flush, startup and shutdown flushes, MCP pending-delta scheduling and persistence inledger.rs, and the doctor reachability probe.user.upload_enabled.v1andupload_enabledfrom the configuration registry, API patch, dashboard settings and observatory controls. A patch or read that names them is refused.embedded/server.mjsare unaffected.upload_enabled,pending_upload,last_upload_atandlast_worldwide_*in an oldconfig.toml, and the storeduser.upload_enabled.v1row, load normally. The next write drops them. The pending amount is never uploaded.current-counter,reset-counter,gain,cost, the monitor, savings ledger persistence, and the independent release callback in the dashboard cloud bridge.docs/USER-GUIDE.mdanddocs/REBRAND-COMPATIBILITY-POLICY.md(A5). The Worker and its Upstash Redis store are not in this repository, so shutting them down is a maintainer action.Evidence.
git grepfinds no worker host, no/incrementor/totalcall, and none of the removed names outside retired-feature tests, docs and the changelog.Bazel, all passing:
unit_testfor tracedecay, tracedecay-api, tracedecay-cli, tracedecay-configuration, tracedecay-dashboard-api, tracedecay-domain, tracedecay-global-db and tracedecay-session-memory, pluscore_cli_suite,mcp_suite,dashboard_api_testandruntime_acceptance_suite. Clippy andrustfmt_check_2024are clean for those crates,gen_builds.py --checkis current,dashboard contracts:checkis up to date,tsc --noEmitis clean, and the observatory, settings and fixture vitest files pass (296 tests).Legacy-state regression tests: global-db persistence (old enabled opt-in converges), session-memory
user_config(old keys ignored and dropped), dashboard settings API (patch refused, field not served), CLIconfiguration getof the retired key, and a doctor test that asserts no counter probe.