Summary

• Aspire (a live customer) hit two symptoms from the same root cause: seller tasks getting created from post-close CS/onboarding threads a rep was only CC'd on for visibility, and meeting-prep writing full sales talk-tracks (objection handling, pricing) for post-close CS calls.
• Both traced back to the seeded closedStageDefaultInstructions() text's vague "unless acting in a customer success capacity" carve-out , easy for an agent to self-justify just by being present on a thread.
• agent-defaults/next-steps.ts: default "never create tasks for" list now explicitly excludes visibility-only thread presence and closed/terminal-stage deals, with a narrow exception for a genuine new expansion/upsell signal.
• agent-defaults/meeting-prep.ts: default template now checks deal status first and skips sales-mode templates for closed/terminal deals, posting a short recap instead.
• seed-playbook.ts: tightened closedStageDefaultInstructions() itself, and wired it into buildOrgPlaybookTemplate(), which previously never emitted closed-stage <instructions> at all (only the per-user template did).
• Already applied by hand to the live Aspire account (reps with agent execution enabled); this makes it the default for every new account going forward.

Test plan

• pnpm --filter @zero/server exec vitest run on seed-playbook.test.ts, agent-defaults.test.ts, curated-agenda-migration.test.ts, playbook-renderers.test.ts, resolve-playbook-context.test.ts, golden-output-regression.test.ts, playbook-regression-fixtures.test.ts , 227 passed
• pnpm --filter @zero/server run types , clean

🤖 Generated with Claude Code

https://claude.ai/code/session_01CjbZa1VXCaUFrDmUVs7o7Z

Greptile Summary

This PR tightens default playbook behavior so agents avoid sales tasks and full meeting preparation after a deal closes, except for genuine expansion signals.

• Adds explicit post-close handling to meeting-prep and next-steps defaults.
• Strengthens the shared closed-stage instruction text.
• Adds closed-stage instructions to organization playbook seeds.
• Updates the closed-stage regression test.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking prompt duplication issue in newly seeded organization and user playbooks.

The behavioral changes consistently suppress post-close sales work, but new accounts will render the same closed-stage instruction from both playbook levels because runtime resolution concatenates them.

Files Needing Attention: apps/server/src/services/playbook/seed-playbook.ts

Important Files Changed

### Issue 1
apps/server/src/services/playbook/seed-playbook.ts:899-903
**Closed-stage guidance is duplicated**

New accounts seed the same closed-stage instructions into both organization and per-user playbooks, while runtime resolution concatenates both entries. Every closed-stage execution therefore receives the lengthy instruction twice, consuming prompt context and unnecessarily overweighting the duplicated guidance.

---

For each issue above, determine whether it