docs: AGENTS.md allineato a CI su master e packaging Electron

[ronzim]

• Sezione Deploy: la CI parte su master, usa Node 20/22 e fa il build Electron con --publish never. Rimosso il TODO "allineare i branch", ora superato.
• Convenzioni: nuova voce sul packaging (mappit-core nel bundle del main, npmRebuild: false e il perché), per non reintrodurre CI: il build Electron fallisce su tutte le piattaforme (app-builder ENOENT) #26.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CecUKcJiSVnehcZEiXLgtk

[Copilot]

🟢 Approval recommended

It is a documentation-only change whose CI and packaging claims were all verified accurate against ci.yml, publish.yml, package.json, and electron.vite.config.ts.

0 open findings

What changed in this PR

This PR updates AGENTS.md (the repository's agent/contributor documentation) to align the "Deploy" and "Convenzioni" sections with the current state of CI on master and the Electron packaging setup. It removes a now-obsolete TODO about branch alignment and documents the packaging rationale so that issue #26 (electron-builder failing because it wiped devDependencies) is not reintroduced.

Changes:

• Deploy section corrected to reflect the actual CI: Node 20/22 (not 18/20/22), triggers on push and PR to master, typecheck runs after the core build, and Electron packaging uses --publish never.
• Added a packaging convention explaining that the packaged app ships without node_modules, mappit-core is bundled from source via the alias in electron.vite.config.ts, and npmRebuild: false prevents electron-builder from wiping devDependencies.

File	Description
AGENTS.md	Aligns the Deploy section with the current master CI workflow and adds a packaging convention documenting the npmRebuild: false rationale.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.