Skip to content

User Story: Station Bot nomination anti-abuse runtime controls #252

@GitAddRemote

Description

@GitAddRemote

User Story

As a Station super admin, I need to manage nomination anti-abuse runtime controls so that I can tune cooldowns and daily limits without editing bot environment files directly.

Definition of Done

  • Station exposes NOMINATION_USER_COOLDOWN_SECONDS, NOMINATION_TARGET_MAX_PER_DAY, and NOMINATION_USER_MAX_PER_DAY
  • Positive-integer validation and save/reload flows are covered by tests
  • Guild owners/admins cannot access these controls
  • pnpm typecheck passes

Acceptance Criteria

  • A station_super_admin can update nomination anti-abuse values from Station
  • Invalid numeric values are rejected with field-level validation
  • Guild-scoped admins cannot access or mutate these controls

Technical Elaboration

This ticket covers the anti-abuse runtime settings only. It is separate from nomination digest, delegated access, audit history, and worker tuning.

Design Elaboration

This UI should feel like a safety control surface. Limits and cooldowns should be grouped and clearly explained in operational terms.


Parent Epic: #231
Depends on: #232, #233, #242

Metadata

Metadata

Assignees

Labels

backendBackend services and logicconfigConfiguration and feature flagsenhancementNew feature or requestfrontendFrontend app and dashboardsecuritySecurity, auth, and permissionsuser-storyEnd-user facing feature story

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions