docs: refresh source-verified engineering runbooks

[cursor]

Summary

• Updated setup/configuration docs for explicit Prisma generation, PRODUCTION truthiness, and command registration guild IDs.
• Corrected feature and command docs for current JTC, ticket, and rank-card behavior.
• Refreshed engineering, architecture, database, and contributing notes for event-loader registration, release automation, interaction cooldown paths, and current test coverage.

Codepaths Covered

• src/example.config.js, src/events/ready/registerCommands.js, src/events/ready/registerContextMenus.js, src/handlers/deploy.js
• src/commands/slash/Management/setup.js, src/events/Guild/jointocreate.js, prisma/schema.prisma
• src/commands/slash/General/rank.js, src/utils/rankCardPresenceStatus.js
• src/handlers/events.js, src/events/Guild/interactionCreate.js, .github/workflows/release.yml, tests/*.test.js

Key Knowledge Gaps Addressed

• Local development should leave PRODUCTION unset/empty because PRODUCTION=false still selects MONGODB_URI for runtime Prisma.
• Ready-time slash/context menu registration always uses DEV_GUILD_ID; developer commands use config.handler.guildId.
• JTC runtime code exists but setup UI is not shipped, and UserLimit is read by the handler but absent from the Prisma schema.
• Rank commands manage stored rank data manually; there is no verified automatic chat XP writer, and /rank info requires a user.
• Release automation is gated by missing v<package.version> tag, not a latest-commit version-line diff.

Validation

• git diff --check HEAD~1..HEAD
• npm test (37 tests passed)