Caprock Files

Added

• The weekly report, to your own Telegram bot. What moved this week against your usual, sent Monday morning — or the next day you open the lid, because a timer set for Monday 09:00 fires for nobody whose laptop is shut at weekends.

A repository is only named when it clears both a real change in dollars and twice its usual week, where usual is the median of the preceding four weeks rather than last week: $2 to $6 is three times and is nothing, and a claim in a message is one the reader cannot click into to check. Most weeks it says nothing moved, which is true and worth saying. A week the machine was off is reported as such rather than as a collapse in spending.

The bot token is stored on your machine and is the one thing this API accepts but never returns. The message carries figures only — no prompts, no replies, no tool output, no file names — and goes straight to Telegram; nothing passes our server.

Fixed

• A setting no longer resets when you save a different one. "Set plan keeps resetting" was not a save that failed: the dashboard sent the whole settings object every time, assembled from a cache in the page, so any control could write back a field it had read minutes earlier. Two tabs were enough — change the plan in one, turn on update checks in the other, and the second restated the plan from its own stale copy. Only what changed is sent now.

• Live activity showed a fortnight of history as what just happened. Two causes at once: the feed asked for a session's first sixty events rather than its last, and the store ordered "most recent" by insertion rather than by time. Those agree for a session captured live and diverge for one whose transcript was re-read, because a backfill inserts old events with new ids. On a long session every row was equally stale, which is also why it read as impossible to scroll.

• The new-session dialog cut off the permission label — "Accept edits · asks before com…" hid the consequence, which is the one thing that label exists to state. Wider dialog, shorter labels.

• A stray reconnect no longer crashes a torn-down page. The live socket queues a retry when it cannot connect, and that timer could outlive the document that scheduled it — harmless in a browser, where the page is going away anyway, and enough to fail a release build whose every test had passed. It now gives up quietly instead.

• The premium chip was two controls disguised as one. The label went straight to the checkout while a chevron beside it opened the explanation, in one border with no seam between them — so clicking the word "premium" to find out what premium is took you to a card form. One control now: it opens the dialog, and once you have bought it names your plan and when it ends.