v2.36.0
What's new in v2.36.0
Added
- Backwards compatibility policy — every expert agent and playbook now checks for BC breaks before writing any code. A structured
⚠️ BC BREAKnotice (what changes, who is affected, severity, migration path) is required and blocks implementation until explicitly approved. Defined once inBEST-PRACTICES.md; enforced across all 9 experts, the Critic[BC]dimension, and 5 playbooks (add-feature, bug-fix, api-integration, release, refactor). - Critic
[BC]review dimension — 8th dimension added to the adversarial review. Checks API contract changes, field removals, env/config renames, exported interface changes, auth mechanism changes, and whether the BC notice was issued and approved. Non-migratable break = Critical; undocumented migratable break = High. - Team adoption presentation —
presentation/team-adoption.html(12-slide deck) andpresentation/STORY-PLAN.md(story beats, live demo script, objection handling) for onboarding developer teams.
Changed
- Release playbook BC scan — Step 3b now scans all commits since last tag for BC breaks before semver determination. Any BC break forces a Major bump; blocks if bump is downgraded without explicit approval.
- Cursor multi-model documentation —
.cursor/README.mdandSYNC-POINTS.mdnow document that model switches within Cursor (GPT-4o → Claude → Gemini) are invisible to the platform and should be treated as mini-handoffs: run session-end before switching models mid-task.
Upgrade
npx github:zafrirron/Agent-Platform --mode=upgrade
Your PROJECT sections are never touched. Platform rules update automatically.