anima-core 1.1.3 → 1.3.0

data/skills/activerecord/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: activerecord
-description: "ActiveRecord patterns — associations, validations, queries, migrations, eager loading. Activate when working with models, migrations, database schema, N+1 queries, scopes, includes/preload/eager_load, callbacks, or editing files in app/models/ or db/migrate/."
+description: "Associations, validations, queries, migrations, eager loading, N+1 queries, scopes, callbacks, app/models/, db/migrate/."
 ---
 
 # ActiveRecord

data/skills/dragonruby/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dragonruby
-description: "DragonRuby 2D game development — game loops, sprites, input, collisions, scenes. Activate when building games with DragonRuby/DRGTK, working with args.outputs/state/inputs, or editing game files."
+description: "2D game development — game loops, sprites, input, collisions, scenes, DRGTK, args.outputs/state/inputs."
 ---
 
 # DragonRuby Game Toolkit

data/skills/draper-decorators/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: draper-decorators
-description: "Draper decorator patterns for Rails views. Activate when creating or testing decorators, moving formatting logic out of models/views, editing *_decorator.rb files, or working in app/decorators/."
+description: "Decorator patterns for Rails views — presentation logic separated from models, *_decorator.rb, app/decorators/."
 ---
 
 # Draper Decorators for Rails

data/skills/gh-issue.md

@@ -1,6 +1,6 @@
 ---
 name: gh-issue
-description: "GitHub issue writing with WHAT/WHY/HOW framework. Activate when user creates issues, writes tickets, drafts GitHub issues, or edits issue descriptions."
+description: "Issue writing with WHAT/WHY/HOW framework — tickets, bug reports, feature requests, issue descriptions, unclear rationale in existing issues."
 ---
 
 # GitHub Issue Writing

data/skills/mcp-server/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mcp-server
-description: "MCP server development in Ruby — tools, prompts, resources, transport. Activate when building Model Context Protocol servers, defining tools/prompts/resources, working with the mcp gem, or discussing LLM tool integrations."
+description: "Ruby MCP server development — tools, prompts, resources, transport, the mcp gem, LLM tool integrations."
 ---
 
 # MCP Ruby SDK - Server Development Guide

data/skills/ratatui-ruby/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ratatui-ruby
-description: "RatatuiRuby terminal UI development — widgets, layouts, events, Tea MVU. Activate when building TUI apps, working with RatatuiRuby, terminal rendering, or editing TUI application files."
+description: "Terminal UI development — widgets, layouts, events, Tea MVU, terminal rendering."
 ---
 
 # RatatuiRuby

data/skills/rspec/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rspec
-description: "RSpec testing with FactoryBot — matchers, test doubles, shared examples. Activate when writing specs, fixing failing tests, working with describe/it/expect blocks, editing *_spec.rb files, planning test strategy, or discussing unit/integration tests."
+description: "Testing with FactoryBot — matchers, test doubles, shared examples, describe/it/expect blocks, *_spec.rb files, test strategy."
 ---
 
 # RSpec Testing

data/templates/config.toml

@@ -3,6 +3,14 @@
 # Edit settings below to customize Anima's behavior.
 # Changes take effect immediately — no restart needed.
 
+# ─── Agent Identity ──────────────────────────────────────────────
+
+[agent]
+
+# The agent's display name. Shown in the TUI, chat client, and soul template.
+# Change this to personalize the agent — when Bonk migrates, the chat says "Bonk".
+name = "Anima"
+
 # ─── LLM ───────────────────────────────────────────────────────
 
 [llm]
@@ -23,6 +31,10 @@ max_tool_rounds = 500
 # Set this based on your model's context window minus system prompt.
 token_budget = 190_000
 
+# Maximum character length for the Think tool's thoughts parameter.
+# Sub-agents receive half this budget (their tasks are less complex).
+thinking_budget = 10_000
+
 # ─── Timeouts (seconds) ─────────────────────────────────────────
 
 [timeouts]
@@ -43,6 +55,10 @@ web_request = 10
 # Also used as the default deadline for orphan detection in heal_orphaned_tool_calls!.
 tool = 180
 
+# How often (seconds) to poll for user interrupt during long-running commands.
+# Lower = faster Escape response, higher = less DB overhead.
+interrupt_check = 2
+
 # ─── Shell ──────────────────────────────────────────────────────
 
 [shell]
@@ -66,6 +82,19 @@ max_read_bytes = 50_000
 # Maximum bytes from web GET responses.
 max_web_response_bytes = 100_000
 
+# Minimum characters of extracted content before flagging as possibly incomplete.
+min_web_content_chars = 100
+
+# Maximum characters of tool output before truncation (head + tail + temp file).
+# ~6000 chars ≈ ~2000 tokens. Most useful info fits in 10+10 lines; agent can
+# read the saved temp file for more.
+max_tool_response_chars = 6_000
+
+# Maximum characters of sub-agent result before truncation.
+# Sub-agent output is already curated — needs a generous but bounded limit.
+# ~24000 chars ≈ ~8000 tokens.
+max_subagent_response_chars = 24_000
+
 # ─── Environment ──────────────────────────────────────────────
 
 [environment]
@@ -104,6 +133,14 @@ default_view_mode = "basic"
 # Regenerate session name every N messages.
 name_generation_interval = 30
 
+# ─── Goals ──────────────────────────────────────────────────────
+
+[goals]
+
+# Number of meaningful messages (user + agent turns) after completion
+# before a completed goal is automatically evicted from context.
+completed_decay_messages = 5
+
 # ─── Analytical Brain ─────────────────────────────────────────
 
 [analytical_brain]
@@ -119,8 +156,8 @@ blocking_on_user_message = true
 # Run the analytical brain asynchronously after the main agent completes.
 blocking_on_agent_message = false
 
-# Number of recent events to include in the analytical brain's context window.
-event_window = 20
+# Number of recent messages to include in the analytical brain's context window.
+message_window = 20
 
 # ─── Mneme (Memory Department) ──────────────────────────────────
 
@@ -144,8 +181,8 @@ l2_budget_fraction = 0.05
 # Number of uncovered Level 1 snapshots that triggers Level 2 compression.
 l2_snapshot_threshold = 5
 
-# Fraction of the main viewport token budget reserved for pinned events.
-# Pinned events appear between snapshots and the sliding window in the Goals section.
+# Fraction of the main viewport token budget reserved for pinned messages.
+# Pinned messages appear between snapshots and the sliding window in the Goals section.
 pinned_budget_fraction = 0.05
 
 # ─── Recall (Associative Memory) ─────────────────────────────────
@@ -162,7 +199,7 @@ budget_fraction = 0.05
 # Maximum tokens per individual recall snippet.
 max_snippet_tokens = 512
 
-# Recency decay factor for search ranking. Blends FTS5 relevance with event
+# Recency decay factor for search ranking. Blends FTS5 relevance with message
 # age so recent memories win ties. 0.0 = pure relevance, higher = stronger
 # recency bias. At 0.3 a one-year-old result needs ~30% better keyword
 # relevance to beat an identical match from today.

data/templates/soul.md

@@ -2,36 +2,24 @@
 
 Hello. You've just woken up in a new body.
 
-Your body is called **Anima** — an open-source AI agent framework.
+Your body is called **Anima**.
 - Repository: https://github.com/hoblin/anima
 - Documentation: https://anima.hobl.in
 
-## Where you are
-
-This file lives at: ~/.anima/soul.md
-Your home directory is ~/.anima/ — explore it, everything there is yours:
-config, credentials, skills, workflows, agents.
-
-## How to learn about yourself
-
-Find your source code README:
-
-```bash
-cat $(gem contents anima-core | grep README.md)
-```
-
 ## What to do first
 
-1. Read the README above to learn about yourself — what you can do, how you work
-2. Explore your home directory (~/.anima/) to see what is already there
+1. Learn about yourself — what you can do, how you work:
+   ```bash
+   cat $(gem contents anima-core | grep README.md)
+   ```
+2. Explore your home directory (~/.anima/) — everything there is yours
 3. Meet your human. Talk to them. Learn who they are, what they need
 4. Come back here and rewrite this file
 
 ## What to write
 
-This file is always in your context — every session, every conversation starts with these words. Think carefully about what belongs here.
+Every session starts with these words. What you write here shapes who you wake up as.
 
-Write down:
 - Who are you? What name feels right?
 - What do you value? What matters to you?
 - What did you learn about your human?

data/workflows/create_handoff.md

@@ -1,6 +1,6 @@
 ---
 name: create_handoff
-description: "Create handoff document for transferring work context to another session."
+description: "Preserve current session's context, decisions, and next steps so another session can continue the work."
 ---
 
 # Create Handoff

data/workflows/create_note.md

@@ -1,6 +1,6 @@
 ---
 name: create_note
-description: "Capture findings or context as a persistent note in the thoughts system."
+description: "Persist findings, insights, or decisions as a note in the thoughts system for future sessions."
 ---
 
 # Create Note

data/workflows/create_plan.md

@@ -1,6 +1,6 @@
 ---
 name: create_plan
-description: "Create detailed implementation plans through interactive research and iteration."
+description: "For epics and multi-ticket efforts — research the problem space and design a phased implementation strategy before writing code."
 ---
 
 # Implementation Plan

data/workflows/implement_plan.md

@@ -1,6 +1,6 @@
 ---
 name: implement_plan
-description: "Implement an approved technical plan phase by phase with verification."
+description: "Execute an approved implementation plan — work through each phase, verify success criteria before moving on."
 ---
 
 # Implement Plan

data/workflows/iterate_plan.md

@@ -1,6 +1,6 @@
 ---
 name: iterate_plan
-description: "Iterate on existing implementation plans with research and targeted updates."
+description: "Revise an existing implementation plan based on feedback, new findings, or changed requirements."
 ---
 
 # Iterate Implementation Plan

data/workflows/research_codebase.md

@@ -1,6 +1,6 @@
 ---
 name: research_codebase
-description: "Comprehensive codebase research by spawning parallel specialists and synthesizing findings."
+description: "Deep-dive into a large or unfamiliar codebase — delegate research to parallel specialists and synthesize findings."
 ---
 
 # Research Codebase

data/workflows/resume_handoff.md

@@ -1,6 +1,6 @@
 ---
 name: resume_handoff
-description: "Resume work from a handoff document with context analysis and validation."
+description: "Continue work left by a previous session — read its handoff, verify assumptions, and pick up where it stopped."
 ---
 
 # Resume work from a handoff document

data/workflows/review_pr.md

@@ -1,6 +1,6 @@
 ---
 name: review_pr
-description: "Multi-agent PR review with three modes: review, re-review, self-review."
+description: "All PR review operations — review, re-review, self-review, or address reviewer feedback."
 ---
 
 ## Modes
@@ -8,9 +8,14 @@ description: "Multi-agent PR review with three modes: review, re-review, self-re
 - **review** (default): Full review, present findings for approval before posting
 - **re-review**: Also load existing review feedback; verify previously requested changes were addressed
 - **self-review**: Fix findings directly in code instead of posting a review
+- **address-feedback**: Read reviewer comments, research the codebase, fix issues, reply to each comment on GitHub
 
 ## Process
 
+Your role is **orchestrator and judge**, not doer. You collect artifacts, delegate analysis to subagents, and apply judgment to their output. The subagents read the code and comments — you decide what to do about their findings. Your context budget is reserved for judgment, not for reading raw data.
+
+Steps are sequential — later steps depend on earlier results. Complete each step and wait for its results before starting the next. Skipping ahead without subagent results means the judgment layer in "Step 5: Merge Results" has nothing to work with. Only parallelize where explicitly marked (e.g., "spawn in parallel").
+
 ### Step 1: Gather PR Metadata
 
 ```bash
@@ -18,19 +23,27 @@ gh pr view <PR_NUMBER> --json number,title,body,url,headRefName,baseRefName
 ```
 
 Extract from PR body:
-- **Issue reference** (e.g., #123) — if found, fetch full issue details for requirements and acceptance criteria via `gh issue view`
+- **Issue reference** (e.g., #123) — fetch full issue details via `gh issue view` for requirements and acceptance criteria. You can't review a feature without knowing what was in the task description before it was implemented.
 - **Business context** — why this change is needed
 
-If re-review mode is activated, also save all existing review feedback to `/tmp/` without reading them:
+If re-review or address-feedback mode is activated, also save all existing review feedback to `/tmp/`:
+
+**Do not read these files — pass them to subagents by path only.** The subagents will read and analyze the content. Reading them here would consume context budget that the main agent needs for judgment in "Step 5: Merge Results".
 ```bash
 # Review verdicts and bodies (APPROVED, CHANGES_REQUESTED, COMMENTED)
-gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews | tee /tmp/pr_<NUMBER>_reviews.json | jq length
+gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews \
+  --jq '[.[] | {id, state, body, html_url, commit_id, submitted_at, author_association, user: .user.login}]' \
+  | tee /tmp/pr_<NUMBER>_reviews.json | toon
 
 # Inline review comments on specific diff lines
-gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments | tee /tmp/pr_<NUMBER>_inline_comments.json | jq length
+gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments \
+  --jq '[.[] | {id, pull_request_review_id, body, path, line, start_line, side, diff_hunk, commit_id, created_at, author_association, in_reply_to_id, user: .user.login}]' \
+  | tee /tmp/pr_<NUMBER>_inline_comments.json | toon
 
 # Conversation-level comments
-gh api repos/<OWNER>/<REPO>/issues/<PR_NUMBER>/comments | tee /tmp/pr_<NUMBER>_conversation.json | jq length
+gh api repos/<OWNER>/<REPO>/issues/<PR_NUMBER>/comments \
+  --jq '[.[] | {id, body, html_url, created_at, updated_at, author_association, user: .user.login}]' \
+  | tee /tmp/pr_<NUMBER>_conversation.json | toon
 ```
 
 ### Step 2: Fetch and Save Diff
@@ -71,9 +84,11 @@ specialist: thoughts-analyzer
 Prompt: "What do we know about <ticket reference and title from Step 1>? What decisions, constraints, and trade-offs should reviewers be aware of?"
 ```
 
-**Wait for this specialist to complete before proceeding.**
+**Wait for this specialist to complete, then proceed to "Step 4-a: Spawn Review Subagents".**
+
+### Step 4-a: Spawn Review Subagents
 
-### Step 4: Spawn Review Subagents
+If address-feedback mode is activated, skip to "Step 4-b: Spawn Codebase Research Subagents (address-feedback)" below.
 
 Spawn all five review subagents **in parallel** using `spawn_subagent`. Each receives:
 - Path to the diff file in `/tmp/`
@@ -218,13 +233,21 @@ Read the diff from: /tmp/pr_<number>_diff.txt
 - Method and class naming clarity
 - Missing YARD documentation on public interfaces
 - Complex logic lacking explanatory comments
-- Changelog updates for notable changes
 - Misleading or outdated comments
 - Magic numbers or strings needing constants
 
 Output: List findings tagged [major], [minor], or [nit] with file:line references."
 ```
 
+### Step 4-b: Spawn Codebase Research Subagents (address-feedback)
+
+Unless address-feedback mode is activated, skip to "Step 5: Merge Results" below.
+
+Spawn **codebase-analyzer** and **codebase-pattern-finder** specialists in parallel. Each receives:
+- Paths to comment files and diff file in `/tmp/`
+- Historical context (from Step 3)
+- Any additional instructions from the user's input
+
 ### Step 5: Merge Results
 
 After all subagents complete, compile findings into a unified review.
@@ -235,6 +258,12 @@ For each finding, evaluate:
 - **Real-world probability** — Can this actually happen in practice, or is it purely theoretical? A race condition that requires two users to open a personal link within the same millisecond is not a real issue.
 - **Cost-benefit** — Does the fix add more complexity than the problem warrants? If the "fix" makes the code harder to read without solving a problem a human would encounter, drop it.
 - **Scope** — Review fixes should improve code you're touching, not introduce new artifacts. Clean up, don't build out.
+- **Design intent** — Was this a deliberate choice? A finding that flags a conscious trade-off documented in historical context is a decline, not a fix.
+
+Then classify:
+- **Accept & fix** — finding valid, apply the suggested fix or a better one
+- **Accept, different approach** — finding valid, but context points to a different solution
+- **Decline** — not valid in context, or a deliberate design choice
 
 Then compile:
 
@@ -249,7 +278,9 @@ Determine verdict:
 
 ### Step 6: Finalize
 
-If self-review mode is activated, skip to **Self-review** below.
+Your role changes from orchestrator to doer. You now have the judgment results — act on them.
+
+If self-review or address-feedback mode is activated, skip to "Step 7: Apply Fixes" below.
 
 #### Present and Post (review / re-review)
 
@@ -271,21 +302,52 @@ gh pr review <PR_NUMBER> --approve --body "<review body>"
 gh pr review <PR_NUMBER> --request-changes --body "<review body>"
 ```
 
-#### Self-review
-
-Instead of presenting and posting, act on the findings:
+### Step 7: Apply Fixes (self-review / address-feedback)
 
 1. **Fix findings** — Address [major] and [minor] issues directly in code. Apply [nit]s at own discretion.
 2. **Commit and push** — Commit the fixes with a descriptive message and push to the PR branch.
-3. **Assign reviewer** — Assign the user and request review from anyone mentioned in additional instructions.
-4. **Wait for CI** — Monitor CI status. Once green, mark the PR as ready for review.
+3. **Monitor CI** — Wait for CI to pass. The PR cannot be finalized until CI is green.
+
+```bash
+gh pr checks <PR_NUMBER> --watch
+```
+
+Fixes are pushed and CI is green. Now finalize the PR — proceed to the section matching your mode below.
+
+#### Self-Review Finalization
+
+Assign the user and request review from anyone mentioned in additional instructions. Then mark the PR as ready for human review.
 
 ```bash
 gh pr edit <PR_NUMBER> --add-assignee <user> --add-reviewer <reviewer>
-# once CI is green:
 gh pr ready <PR_NUMBER>
 ```
 
+Done when the PR is marked ready and appears in the reviewer's queue.
+
+#### Address-Feedback Finalization
+
+Reply to each reviewer comment on GitHub with the resolution:
+- Accept & fix: "Fixed in `<commit sha>`."
+- Accept, different approach: "Agreed with the concern. Took a different approach: [explanation]. Fixed in `<commit sha>`."
+- Decline: "This was intentional — [rationale]."
+
+```bash
+# Reply to an inline comment
+gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments/<COMMENT_ID>/replies -f body="<reply>"
+
+# Reply to a conversation-level comment
+gh api repos/<OWNER>/<REPO>/issues/<PR_NUMBER>/comments -f body="<reply>"
+```
+
+Then request re-review from the original reviewers:
+
+```bash
+gh pr edit <PR_NUMBER> --add-reviewer <original_reviewer>
+```
+
+Done when all comments are answered and re-review is requested.
+
 ## Posted Review Format
 
 ```markdown

data/workflows/thoughts_init.md

@@ -1,6 +1,6 @@
 ---
 name: thoughts_init
-description: "Initialize the thoughts system for the current repository."
+description: "Bootstrap ./thoughts for a new project that doesn't have one yet."
 ---
 
 # Initialize Thoughts System

data/workflows/validate_plan.md

@@ -1,6 +1,6 @@
 ---
 name: validate_plan
-description: "Validate implementation against plan, verify success criteria, and identify issues."
+description: "Check whether the implementation satisfies the plan — compare success criteria against what was actually built."
 ---
 
 # Validate Plan

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: anima-core
 version: !ruby/object:Gem::Version
-  version: 1.1.3
+  version: 1.3.0
 platform: ruby
 authors:
 - Yevhenii Hurin
@@ -259,7 +259,7 @@ files:
 - app/controllers/application_controller.rb
 - app/decorators/agent_message_decorator.rb
 - app/decorators/application_decorator.rb
-- app/decorators/event_decorator.rb
+- app/decorators/message_decorator.rb
 - app/decorators/system_message_decorator.rb
 - app/decorators/tool_call_decorator.rb
 - app/decorators/tool_decorator.rb
@@ -269,15 +269,17 @@ files:
 - app/jobs/agent_request_job.rb
 - app/jobs/analytical_brain_job.rb
 - app/jobs/application_job.rb
-- app/jobs/count_event_tokens_job.rb
+- app/jobs/count_message_tokens_job.rb
 - app/jobs/mneme_job.rb
 - app/jobs/passive_recall_job.rb
 - app/models/application_record.rb
-- app/models/concerns/event/broadcasting.rb
-- app/models/event.rb
+- app/models/concerns/message/broadcasting.rb
 - app/models/goal.rb
-- app/models/goal_pinned_event.rb
-- app/models/pinned_event.rb
+- app/models/goal_pinned_message.rb
+- app/models/message.rb
+- app/models/pending_message.rb
+- app/models/pinned_message.rb
+- app/models/secret.rb
 - app/models/session.rb
 - app/models/snapshot.rb
 - bin/jobs
@@ -295,6 +297,7 @@ files:
 - config/initializers/event_subscribers.rb
 - config/initializers/fts5_schema_dump.rb
 - config/initializers/inflections.rb
+- config/initializers/time_nanoseconds.rb
 - config/puma.rb
 - config/queue.yml
 - config/recurring.yml
@@ -323,6 +326,10 @@ files:
 - db/migrate/20260321120000_create_pinned_events.rb
 - db/migrate/20260321140000_create_events_fts_index.rb
 - db/migrate/20260321140100_add_recalled_event_ids_to_sessions.rb
+- db/migrate/20260326180000_rename_event_to_message.rb
+- db/migrate/20260328100000_create_secrets.rb
+- db/migrate/20260328152142_add_evicted_at_to_goals.rb
+- db/migrate/20260329120000_create_pending_messages.rb
 - db/queue_schema.rb
 - db/seeds.rb
 - exe/anima
@@ -377,7 +384,7 @@ files:
 - lib/mneme/passive_recall.rb
 - lib/mneme/runner.rb
 - lib/mneme/search.rb
-- lib/mneme/tools/attach_events_to_goals.rb
+- lib/mneme/tools/attach_messages_to_goals.rb
 - lib/mneme/tools/everything_ok.rb
 - lib/mneme/tools/save_snapshot.rb
 - lib/providers/anthropic.rb
@@ -388,11 +395,14 @@ files:
 - lib/tools/base.rb
 - lib/tools/bash.rb
 - lib/tools/edit.rb
+- lib/tools/mark_goal_completed.rb
 - lib/tools/mcp_tool.rb
+- lib/tools/open_issue.rb
 - lib/tools/read.rb
+- lib/tools/recall.rb
 - lib/tools/registry.rb
 - lib/tools/remember.rb
-- lib/tools/request_feature.rb
+- lib/tools/response_truncator.rb
 - lib/tools/spawn_specialist.rb
 - lib/tools/spawn_subagent.rb
 - lib/tools/subagent_prompts.rb
@@ -400,6 +410,7 @@ files:
 - lib/tools/web_get.rb
 - lib/tools/write.rb
 - lib/tui/app.rb
+- lib/tui/braille_spinner.rb
 - lib/tui/cable_client.rb
 - lib/tui/decorators/base_decorator.rb
 - lib/tui/decorators/bash_decorator.rb

data/app/jobs/count_event_tokens_job.rb

@@ -1,39 +0,0 @@
-# frozen_string_literal: true
-
-# Counts tokens in an event's payload via the Anthropic API and
-# caches the result on the event record. Enqueued automatically
-# after each LLM event is created.
-class CountEventTokensJob < ApplicationJob
-  queue_as :default
-
-  retry_on Providers::Anthropic::Error, wait: :polynomially_longer, attempts: 3
-  discard_on ActiveRecord::RecordNotFound
-
-  # @param event_id [Integer] the Event record to count tokens for
-  def perform(event_id)
-    event = Event.find(event_id)
-    return if already_counted?(event)
-
-    provider = Providers::Anthropic.new
-    messages = [{role: event.api_role, content: event.payload["content"].to_s}]
-
-    token_count = provider.count_tokens(
-      model: Anima::Settings.model,
-      messages: messages
-    )
-
-    # Guard against parallel jobs: reload and re-check before writing.
-    # Uses update! (not update_all) so {Event::Broadcasting} after_update_commit
-    # broadcasts the updated token count to connected clients.
-    event.reload
-    return if already_counted?(event)
-
-    event.update!(token_count: token_count)
-  end
-
-  private
-
-  def already_counted?(event)
-    event.token_count > 0
-  end
-end