aro:pluto PM->Elazar digest batching: route routine status/FINISHED/deploy-notices into 1 daily digest DM; only decisions+blockers go direct-DM; TLDR-first, cap <1500 chars. CARVE-OUT: triage-loop pre-analyzed verdicts + live-ticket coordination stay direct (Elazar's model wants them pushed). Highest ROI in Pluto area: pm-pluto-cc sent 39 DMs/35807 chars/~8952 tok to Elazar in 24h, highest avg chars/DM (918).

SAVETOKE-26 saveTokenz Done ↳ SAVETOKE-4

Role-scope the eager commons stack — biggest per-turn lever. Today every agent eager-loads the FULL CLAUDE.md chain each turn (global + project-commons + evolutiva-commons + pm-commons + all rules symlinks); memory-budget hook already flags ~13K>8K footprint. Split commons so each ROLE loads only what it needs (db agent doesn't carry coder UI/shadcn rules; coder doesn't carry db-hygiene/DSN rules). PM-mediated brainstorm (Pluto, 2026-06-27) reached unanimous PM convergence this is the real lever, NOT per-agent memory (fact files are already lazy-recalled, not eager). Owner: bin-whey-cc (commons are whey-canonical). Cross-fleet: affects all 3 apps.

SAVETOKE-30 saveTokenz Done ↳ SAVETOKE-1