feat: add weapons catalog and expand fun text

.gitignore

@@ -7,6 +7,7 @@ data/*
 !data/cars.txt
 !data/fun/
 !data/fun/*.txt
+!data/weapons.txt
 .env
 .env.bak
 .act-runner/

README.md

@@ -77,7 +77,8 @@ cmd/irc-bot/       application entrypoint
 bot/               IRC connection, config, queue, stats, and interfaces
 plugins/           built-in plugins and tests
 data/foods/        local food, cuisine, and beer suggestion lists
-data/fun/          local family-friendly joke, pun, and wisdom catalogs
+data/fun/          local joke, pun, one-liner, and wisdom catalogs
+data/weapons.txt   local high-level firearm and weapons-name catalog
 data/sports.txt    local sports suggestion list
 data/cars.txt      local car make/model suggestion list
 storage/           BoltDB wrapper used by stateful plugins

config.yaml

@@ -83,8 +83,10 @@ plugins:
   status: {enabled: true}
   define: {enabled: true, timeout_seconds: 8, max_length: 240}
   calc: {enabled: true}
-  # Local, family-friendly text catalogs; one line per entry under data/fun.
+  # Local, operator-editable text catalogs; one line per entry under data/fun.
   fun: {enabled: true, data_dir: "data/fun", max_length: 240}
+  # High-level local firearm/weapons catalog; identification only, no instructions.
+  weapons: {enabled: true, data_file: "data/weapons.txt", max_length: 240}
   # Public GitHub lookups; token is optional and should be supplied out-of-band.
   github: {enabled: true, timeout_seconds: 8, max_length: 360, token: ""}
   reddit: {enabled: true, timeout_seconds: 8, max_length: 360}

data/fun/wisdom.txt

@@ -60,3 +60,105 @@ Do not optimize a process that should be removed.
 Good humor opens a door; good judgment knows when not to walk through it.
 Choose a sustainable pace before urgency chooses one for you.
 A clear “no” can protect a better “yes.”
+Begin with the smallest honest description of the problem.
+The best habit is one that still works on an ordinary day.
+Write down the decision while the reasons are still fresh.
+A kind correction is easier to remember than a sharp one.
+Ask what would make the next step safer and simpler.
+Good preparation reduces drama without reducing ambition.
+The person closest to the work often knows where the friction is.
+An idea becomes useful when someone can try it.
+Leave enough margin for the plan to survive reality.
+When a rule creates confusion, explain its purpose before repeating it.
+Attention is a resource; spend it where it changes something.
+Small acts of maintenance are how good things stay good.
+The fastest way to improve a draft is to let another person read it.
+Trust grows when promises are precise and follow-through is visible.
+Do not make a permanent decision to solve a temporary mood.
+A reliable process should be understandable by someone new.
+If the same question returns, the answer may need a better home.
+Good tools amplify care; they do not replace it.
+The clearest boundary is one that can be stated without anger.
+Make the important path easy to find.
+Patience is not passivity; it is room for better information.
+An error report is an invitation to improve the system.
+When a plan changes, preserve the goal and update the route.
+You can be firm without making someone feel small.
+The useful version of certainty includes what could change your mind.
+A good archive is a gift to the future.
+Do not let a full calendar hide an empty priority list.
+The most helpful answer may be a question that reveals the missing fact.
+Clarity is a form of kindness.
+If the first solution is fragile, keep looking for the one that is boringly stable.
+Make room for rest before exhaustion makes the decision for you.
+The quality of a conversation is measured by what becomes possible afterward.
+A simple checklist can protect attention for harder thinking.
+The best lesson is the one that changes the next attempt.
+If you want a different result, change the repeated part of the process.
+Good leadership makes it easier for others to do good work.
+The right pace is fast enough to learn and slow enough to notice.
+Do not confuse a loud opinion with a complete argument.
+The strongest plan can explain its assumptions.
+If a task has no owner, it has no reliable future.
+Make feedback actionable, timely, and humane.
+The smallest useful measurement is better than the largest unused dashboard.
+Protect the relationship while solving the problem.
+An honest limit is more useful than an impressive promise.
+You do not need to win every argument to improve the outcome.
+When something works, make it repeatable before making it fancy.
+The best question is often “what are we optimizing for?”
+Keep a record of what you learned, not only what you finished.
+A pause can be a decision to think, not a decision to avoid.
+The future benefits from notes written in the present tense.
+Good systems make recovery normal instead of heroic.
+An explanation should reduce confusion, not display vocabulary.
+Do not spend tomorrow fixing what a five-minute check could catch today.
+The best standards leave room for judgment and responsibility.
+When people feel safe to ask, problems surface earlier.
+Build habits that make the right action convenient.
+The goal of a disagreement is understanding before resolution.
+If you cannot say why a shortcut is safe, it may not be one.
+Kindness is not a lack of standards; it is a better way to hold them.
+Let evidence change the plan before pride makes the plan expensive.
+The work is easier to share when the context is written down.
+A small improvement repeated is a quiet revolution.
+Give new ideas a small experiment before demanding a grand proof.
+The best apology changes the conditions that caused the harm.
+An open question can be more productive than a fast conclusion.
+Make it easy to stop a process that is causing damage.
+Progress is not invalidated by needing a second attempt.
+The safest default is the one you have tested in normal conditions.
+Good documentation answers the question a tired person will ask.
+If the plan depends on everyone remembering, write it down.
+The strongest teams share credit and surface risk.
+Do not confuse familiarity with truth.
+The right tool is the one that solves the problem without creating a larger one.
+Leave a little energy for tomorrow's work.
+A clear example can teach what a paragraph leaves abstract.
+When the result matters, verify it independently.
+Make the easy thing the ethical thing whenever you can.
+The best time to define success is before the work begins.
+Small reliable signals beat dramatic guesses.
+If you are stuck, describe the obstacle to someone who is not inside it.
+Good questions are reusable tools.
+The most durable confidence comes from knowing how to check.
+Do not make a person carry a system's missing memory.
+A healthy process can survive one busy day.
+Use precision for important facts and generosity for imperfect people.
+The next good step is still good even when it is not the final one.
+If a task keeps growing, define its smallest acceptable finish.
+The best improvements are visible in the ordinary moments.
+Take responsibility for the effect, not only the intention.
+An idea that welcomes questions is stronger than one that fears them.
+When you teach, leave behind a method, not just an answer.
+Good judgment includes knowing when to ask for help.
+The shortest path to trust is consistent, observable care.
+Choose a standard you can maintain when nobody is watching.
+If the system is confusing, the confusion is data.
+Make the next person’s first experience easier than your own.
+The best correction preserves dignity and improves accuracy.
+Leave a little room for delight in a serious plan.
+The most valuable resource may be the attention you return to someone.
+Do not wait for perfect conditions to practice a good habit.
+An accurate small promise is better than an inspiring vague one.
+You can change direction without declaring the earlier road worthless.