Jamie BruntonandClaude Opus 5
14d92e14ee
Stopping the bot previously halted conversation syncing too. On the
multi-account path the run-flag check sat above both the reply-sync and
response-check branches, so a stop left only MediaSyncService's coarse
30-minute chat refresh. The legacy single-account path did the opposite
and kept syncing while stopped — one boolean meaning two things.
Replace the boolean with an explicit three-way mode:
running — discover, screen, send, automate replies
scan — refresh chats, detect replies, check responses; send nothing
and discover nothing; actionable replies surface as backlog
stopped — everything halts, including background media sync
scan differs from browser.dryRun, which still discovers and pays for AI
screening before suppressing the send.
The mode persists in runtime_state.bot_mode; a migration backfills it
from bot_running, and rows written by an older build still read
correctly. Both loops now gate on the mode, the account runtime loop
reconciles background media sync on transitions only, and the dashboard
and agent API expose all three states.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
30 lines
1.4 KiB
TypeScript
30 lines
1.4 KiB
TypeScript
import { describe, expect, it } from 'vitest';
|
|
import { deriveShellStatus } from '../../apps/dashboard/src/app/shell-status.js';
|
|
|
|
describe('global shell status', () => {
|
|
it('derives safety-critical labels from authoritative snapshots', () => {
|
|
expect(deriveShellStatus({
|
|
stats: { mode: 'running', dryRunMode: true, invitationCooldown: { reason: 'Reddit cooldown' } },
|
|
reddit: { ready: true, loggedIn: true, status: 'authenticated' },
|
|
realtime: { status: 'reconnecting', isStale: true },
|
|
sync: { syncing: true, syncingKind: 'full' },
|
|
})).toEqual({
|
|
bot: 'Running (dry run)', reddit: 'Reddit authenticated', realtime: 'Realtime reconnecting (stale)',
|
|
cooldown: 'Reddit cooldown', sync: 'Full sync active', controlAction: 'stopped', controlDisabled: false,
|
|
});
|
|
});
|
|
|
|
it('labels scan mode and offers a full start as the next step', () => {
|
|
expect(deriveShellStatus({
|
|
stats: { mode: 'scan', dryRunMode: false, invitationCooldown: null },
|
|
realtime: { status: 'connected', isStale: false },
|
|
})).toMatchObject({ bot: 'Scanning', controlAction: 'running' });
|
|
});
|
|
|
|
it('guards bot controls until the authoritative bot state is available', () => {
|
|
expect(deriveShellStatus({ realtime: { status: 'idle', isStale: true } })).toMatchObject({
|
|
bot: 'Bot state unavailable', controlDisabled: true,
|
|
});
|
|
});
|
|
});
|