New-feature checklist
Run through this for every feature or fix:
- Implement in the cog; add tests (note: no test files are currently in the repo — restore them before treating the suite as a gate); run the full suite.
- Dependencies: any new package goes in
requirements.txt(setup.pypicks it up automatically — no other changes needed). - README: update the command tables and feature docs (standing rule — every push updates the README).
- This handbook: update the relevant page if the architecture or a pattern changed. Every page has an Edit this page link.
- Push only when Emily says so (local-first: she tests locally and
asks for the push). README and handbook pushes are the exception and
may go anytime. Push from her PC over SSH with files staged
explicitly by path — never
git add -A(runtime files likebot.db— a frozen legacy copy — anddata/backups/are tracked and must stay out) — then verify local HEAD matchesgit ls-remote origin main. - Tell the user the exact local steps: which files to update, whether
to
pip install, and to restart the bot.