-• Inspect the CloudWatch logs for our Turbot AWS Lambda during the time
- period of the active hunt, (October 24-31), find and diagnose any
- errors that occurred during that period. Users reported seeing
- "Trouble connecting" (probably during new-puzzle dialog submission)
- as well as "dispatch_failed during /state command (perhaps due to a
- state string that was very long).
+• Think about writing some custom solving tools, (like Qat, or
+ Nutrimatic, or Snap2, etc.)
+
+• Fix slash commands to pass off processing to a separate Lambda and
+ then return immediately (removing the annoying "operation timeout"
+ complaints from Slack even when the command works exactly as it
+ should).
+
+Round management
+----------------
+
+• Select round fields by default based on the round of the puzzle for
+ the channel in which `/puzzle` is invoked.
+
+• Consider putting a round prefix into the channel name to group a
+ round's puzzles in the channel list.
+
+Hunt overview commands and filters
+----------------------------------
+
+• On the Turbot home screen allow a dropdown for Unsolved/Solved/All
+ puzzles
+
+• On the Turbot home screen add a text box for a search hstring (to
+ work like the search string now available in "/hunt").
+
+File uploads
+------------