perf(server): skip full thread loads on projection and ingestion

[leoisadev1]

Problem

Thread shell refresh, client snapshots, and provider reactors decoded every persisted message, plan, and activity payload to compute a few summary fields. Large tool outputs made those reads cost more memory than the result required.

Adaptation

Ported the remaining narrow projection and ingestion lookups from T3 Code, keeping Akeru bot, group, channel, author, reaction, and delegation fields.

• Shell refresh uses SQL for latest user-message time, pending approval count, and actionable-plan status, plus user-input lifecycle rows only.
• Client snapshots load activity payloads in 25-row primary-key batches and project each batch before the next read.
• Metadata commands read the thread shell. Turn start reads one message and an existence check for other non-compaction user messages.
• Runtime ingestion uses a joined thread context, including Akeru ownership fields, and keyed message, plan, and task-activity lookups.
• Controller helpers now take the shell ownership fields they actually read (id, botId, groupId, respondingBotId, interactionMode) instead of a full OrchestrationThread.
• Task-title fallback reads projection activity kind and payload, so records keyed by activityId compile.
• Live thread.activity-appended stays O(1) when the current array was produced by the reducer and is already sorted.
• upsertMany exists for projector cursors. Runtime projectEvent still commits each projector separately because attachment cleanup runs after each projector transaction. Combining those commits is shared with checkpoint attachment-transaction work and is not in this PR.

Upstream

Adapted from pingdotgg/t3code:

• #9000 bound snapshot activity payload memory
• #8988 skip unused tool payloads
• #9152 incremental message-sent and activity appends
• #9662 SQL latest user-message time and pending approval count
• #9671 cursor upsertMany API only
• #9706 joined thread runtime context
• #9758 shell reads for metadata commands
• #10108 turn-start message query
• #10120 keyed completion lookups
• #10341 plan-status metadata without markdown bodies

Scope

This PR is projection and ingestion query narrowing only. Logging (pingdotgg#8187 remaining) is #240. Incremental transcript scans (pingdotgg#9024) are still separate. Checkpoint attachment cleanup after outer command commit is owned by the checkpoint-safety work.

Verification

Focused tests:

• 154 tests across ProviderCommandReactor and ProviderRuntimeIngestion after the helper-contract repair, including shell-only identity and projection activityId title lookup
• Server typecheck: no error TS on akeru-bot after the repair
• Targeted lint and format

Isolated browser on a354e64f2, home /tmp/akeru-ui.cGmS1M, web 6836 / server 14876:

• Scout history rendered from projected messages, then a live send projected the user line and a completed error reply into the thread and roster preview
• Thumbs-up reaction persisted on the user message and survived reconnect
• Group Projection check (Scout boss, Relay specialist) rendered from the roster; a live send showed Scout is working, then a completed Scout error reply
• Reconnect via /bots/ui-scout restored Scout history plus the reaction; opening the group from the roster restored group history
• Hard navigation straight to /groups/... before the roster store is populated still crashes GroupThreadLanding (useReplyPlaybackThread after if (!group) return null). That hook-order bug is pre-existing and not introduced here
• Live successful provider streaming and delegation cards were not available: this isolated fixture has no working provider credentials, so turns complete with the local failure reply instead of a provider stream or a delegation record

Implemented and verified by Grok 4.6 High in Grok Build via Orca.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
akeru-bot-landing	Building	Preview	Sep 10, 2026 6:01pm UTC

[greptile-apps]

Greptile Summary

This PR replaces full thread-history decoding in projection and provider-ingestion paths with bounded, purpose-specific persistence queries while preserving client snapshot and runtime behavior.

• Computes shell summary fields through narrow message, plan, approval, and activity lifecycle queries.
• Loads and projects client activity payloads in bounded batches within the snapshot transaction.
• Uses joined runtime context and keyed message, plan, and task-activity lookups during provider ingestion.
• Narrows controller helper contracts to the shell ownership fields they consume.
• Adds an indexed fast path for already-sorted live activity appends.
• The earlier activity-identifier type issue is fixed.

Confidence Score: 5/5

Safe to merge; no outstanding blocking issues remain.

The prior activity-identifier finding was resolved by greptile-apps[bot] without explanation. The current code passes the repository's full projected activity shape to the task-title helper, which only requires its kind and payload fields.

_{Reviews (4): Last reviewed commit: "Merge branch 'main' into perf/narrow-pro..." | Re-trigger Greptile}