feat: let the operator set the daily comment limit per account

The allowance was derived from the adaptive trust level with no way to
change it, which made the dashboard's "1 / 2 today" unexplainable and
left no way to slow an account down or push one along.

`dailyLimit` is null by default, keeping today's adaptive behaviour. A
whole number between 1 and 50 overrides it and is enforced verbatim in
either direction — it can raise an account above what it has earned or
hold it below. The trust level keeps being tracked underneath and is
reported as `adaptiveAllowance`, so the earned figure stays visible next
to the override, and clearing the field hands pacing back to the ladder.

Raising the limit above the earned allowance does remove the adaptive
backoff after a bad comment, so the dashboard says exactly that where the
limit is set. It does not touch the pause on two consecutive removals, a
comment the public cannot see, or a captcha challenge: those are safety
stops rather than rate controls and no limit setting can disable them.

Also correct two things the page was saying badly. The allowance is now
labelled "used in last 24h" with the trust level shown as what it earns,
because it is a rolling window and not a midnight reset. And a
per-community cap above the account allowance now states how much of it
is actually reachable — "1 of 10 today" beside an account limit of 2 read
as far more headroom than existed, since caps distribute the allowance
rather than adding to it.

Verified against a local instance: override above and below the earned
allowance, unrelated saves preserving it, clearing it through the UI,
rejection of 0/51/2.5/non-numeric, and a limit failing to clear a pause.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/database/growth-repository.ts

@@ -24,6 +24,12 @@ export interface GrowthSettingsRecord {
   enabled: boolean;
   /** Rung on the adaptive allowance ladder. Higher means more comments per day. */
   trustLevel: number;
+  /**
+   * Operator override for comments per day. Null leaves the allowance to the
+   * adaptive ladder. A value is enforced verbatim — the ladder keeps tracking
+   * the account underneath, and the removal/shadowban pause still applies.
+   */
+  dailyLimit: number | null;
   levelChangedAt: number | null;
   consecutiveRemovals: number;
   /** Non-null means growth is hard-paused until an operator clears it. */
@@ -38,6 +44,8 @@ export interface GrowthSettingsRecord {
 
 export interface GrowthSettingsPatch {
   enabled?: boolean;
+  /** Pass null to hand the allowance back to the adaptive ladder. */
+  dailyLimit?: number | null;
   minDelayMs?: number;
   jitterMs?: number;
   quietHours?: GrowthQuietHours;
@@ -158,6 +166,7 @@ export class AccountGrowthRepository {
         accountId,
         enabled: false,
         trustLevel: 0,
+        dailyLimit: null,
         levelChangedAt: null,
         consecutiveRemovals: 0,
         pausedReason: null,
@@ -184,26 +193,34 @@ export class AccountGrowthRepository {
     if (patch.jitterMs !== undefined && (!Number.isInteger(patch.jitterMs) || patch.jitterMs < 0)) {
       throw new Error('Growth jitter must be a non-negative integer');
     }
+    if (patch.dailyLimit !== undefined && patch.dailyLimit !== null
+      && (!Number.isInteger(patch.dailyLimit) || patch.dailyLimit < 1 || patch.dailyLimit > 50)) {
+      throw new Error('Daily comment limit must be a whole number between 1 and 50');
+    }
     if (patch.quietHours) validateQuietHours(patch.quietHours);
     const current = this.getSettings(accountId, now);
     const merged: GrowthSettingsRecord = {
       ...current,
       ...patch,
       quietHours: patch.quietHours ?? current.quietHours,
+      // `null` is a meaningful value here — it hands the allowance back to the
+      // adaptive ladder — so only an explicitly present key may change it.
+      dailyLimit: 'dailyLimit' in patch ? patch.dailyLimit ?? null : current.dailyLimit,
       updatedAt: now,
     };
     this.db.prepare(`
       INSERT INTO account_growth_settings (
-        account_id, enabled, trust_level, level_changed_at, consecutive_removals,
+        account_id, enabled, trust_level, daily_limit, level_changed_at, consecutive_removals,
         paused_reason, paused_at, min_delay_ms, jitter_ms, quiet_hours_json,
         allow_nsfw, updated_at
       ) VALUES (
-        @accountId, @enabled, @trustLevel, @levelChangedAt, @consecutiveRemovals,
+        @accountId, @enabled, @trustLevel, @dailyLimit, @levelChangedAt, @consecutiveRemovals,
         @pausedReason, @pausedAt, @minDelayMs, @jitterMs, @quietHoursJson,
         @allowNsfw, @updatedAt
       )
       ON CONFLICT(account_id) DO UPDATE SET
         enabled = excluded.enabled,
+        daily_limit = excluded.daily_limit,
         min_delay_ms = excluded.min_delay_ms,
         jitter_ms = excluded.jitter_ms,
         quiet_hours_json = excluded.quiet_hours_json,
@@ -213,6 +230,7 @@ export class AccountGrowthRepository {
       accountId,
       enabled: merged.enabled ? 1 : 0,
       trustLevel: merged.trustLevel,
+      dailyLimit: merged.dailyLimit,
       levelChangedAt: merged.levelChangedAt,
       consecutiveRemovals: merged.consecutiveRemovals,
       pausedReason: merged.pausedReason,
@@ -718,6 +736,7 @@ function mapSettings(row: Record<string, unknown>): GrowthSettingsRecord {
     accountId: row.account_id as string,
     enabled: row.enabled === 1,
     trustLevel: row.trust_level as number,
+    dailyLimit: (row.daily_limit as number | null) ?? null,
     levelChangedAt: (row.level_changed_at as number | null) ?? null,
     consecutiveRemovals: row.consecutive_removals as number,
     pausedReason: (row.paused_reason as string | null) ?? null,