set_threshold.buckets does not declare its key set, though the validator already knows it #449

buckets is { type: 'object' } (src/mcp-tools.js:324), so the valid bucket names reach the model only through a refusal message, while set_route.bucket publishes enum: WEEKLY_BUCKET_KEYS right in the schema.

setBucketThresholds in src/config-ops.js already rejects an unknown bucket against QUOTA_BUCKETS, so propertyNames: { enum: QUOTA_BUCKETS } would advertise a constraint that is actually enforced rather than a decorative one.