Consolidate module system before module development

[RedsTom]

Consolidates the existing module system (core + lib + tooling + docs) before new module development (e.g. Autopin). Stacked per-feature commits, all green (tsc, 144 unit, 36 integration).

Silent killers fixed

• Command registration failures no longer flip the DB to enabled; failed version updates retry next boot
• Missing activatedVersion tolerated instead of throwing; downgrades resync
• Install hooks run before the DB flip (no more “already installed” deadlocks)
• Autocomplete receives the module config, not the core one
• Vanished entities are dropped from config lists instead of crashing consumers
• Explicit guild-id extraction for listeners; commands/autocomplete wrapped in try/catch with DM guards

Boot resilience

• Broken imports and throwing onLoad skip the module instead of aborting boot; onLoad supports async
• Lifecycle hooks optional (example modules de-boilerplated)

Author tooling

• Shared test helpers (#lib/testing.js) + pnpm new-module scaffold (verified end to end)
• Prisma consolidator fails fast on duplicate model names
• requiresAdmin on commands, duplicate customId rejection, publishing checklist, LOG_LEVEL, TS env validator with one shared dev constant

🤖 Generated with Claude Code

[RedsTom]

Review clanker :

Pas mergeable en l-etat, pour raisons process + conflits :

• Draft = true
• mergeable = CONFLICTING (mergeStateStatus DIRTY)
• reviewDecision = REVIEW_REQUIRED (0 review, 1 requise sur master)
• statusCheckRollup vide : aucun check visible sur la PR

Cause racine : la branche est basee sur d0c40fe et origin/master a ~19 commits d-avance, dont du fonctionnel qui touche les memes fichiers. Un rebase sur origin/master est requis, avec au moins ces resolutions :

1. src/core/loaders/listener-loader.ts : conflit extractGuildId (cette PR, exportee + testee) vs findGuildId (master, f680ac8). Suggestion : garder extractGuildId, supprimer findGuildId.
2. src/core/listeners/interaction-create.listener.ts : le hunk handleInteraction lit encore handler.handler.requiresAdmin, qui n-existe plus depuis ad0fce6 (access: InteractionAccess requis) — migrer vers access == admin, sinon ca ne compilera pas apres rebase.
3. src/core/loaders/command-loader.ts : reporter Client -> Client (c52788a) sur les fonctions refactorisees.
4. config.command.ts / module.command.ts : requiresAdmin: true (cette PR) vs check inline requireAdmin (master, 292e028) — le flag central rend l-inline redondant, suggerer de ne garder que le flag.
5. guild-create.listener.ts : guild.client (type Client) passe a installModuleCommandsIn — a ajuster pour Client.

Deux remarques design pour le rebase :

• Cette PR ajoute requiresAdmin optionnel sur Command, alors que les interactions exigent desormais access (requis) depuis ad0fce6 — deux conventions paralleles. Ca vaudrait le coup d-aligner Command sur access.
• onInstall/onUninstall tournent maintenant avant le flip DB : a noter dans la doc du scaffold si un module supposait la ligne d-activation existante.

Cote ordre de merge avec #217 (zones differentes, auto-merge probable dans les deux sens), je recommande de faire passer celle-ci d-abord puisque c-est la fondation annoncee.

Process suggere : rebase -> pnpm build && pnpm test -> sortir du draft -> review. Je ne merge donc pas.

[RedsTom]

Rebase done, PR is now ready and all green. Summary of what changed since the review:

• Rebased onto origin/master (was 19 commits behind). Resolved 2 conflicts:
  • command-loader.ts: kept the shared bulk-PUT helper against the new Client signatures.
  • listener-loader.ts: kept extractGuildId (exported and tested), removed the duplicate findGuildId from master.
• Removed the now-redundant inline requireAdmin checks in /config and /modules (the central dispatcher enforces requiresAdmin; the inline code was unreachable). New fixup commit: 780fb44.
• Fixed the integration test mock (ambient client gains isReady) for the upstream readyClient guard in module-installer.ts.

Verified locally: tsc clean, oxlint clean, 180/180 tests pass. CI is green too (lint, build, docker, CodeQL).

Remaining step: 1 approving review is still required by the master branch policy (auto-merge is enabled, so the PR will merge automatically once approved). Note the pre-existing oxfmt drift across the repo (142 files fail oxfmt --check even on master) — I only formatted the 3 files touched here so the diff stays minimal.

[AntoineJT]

regardé vite fait, pas en détail, ça a l'air pas mal, je merge pour pouvoir regarder la #220 de loic