There are two suggestions. However, since each of these issues is quite minor, I am condensing both into one issue.

1. All commands do not print any text when a council does not exist yet.
   Expected Behavior:
   Input: !motion newTextHere
   Input: !config reason.required.no true
   Input: !CouncilStats

Expected Output:

A council does not exist for this channel.

Observed Output:

No Output

2. archive command truncates motion description without a visual queue to signal the truncation.
   Expected Behavior:
   Input: !motion "this is a long string of motion text which exceeds 45 characters long and therefore should be truncated."
   Input: !motion "this is not a long string."
   Input: !archive #1-#2

Expected Output:

#1 Passed | this is a long string of motion text which...
#2 Passed | this is not a long string.
To view a full motion, run archive #1 where 1 is the number of the motion you want to view.

Observed Behavior:

#1 Passed | this is a long string of motion text which ex
#2 Passed | this is not a long string.
To view a full motion, run !archive #1 where 1 is the number of the motion you want to view.```