Summary

Add per-department ceremony policy override support to the template schema and department configuration. This enables the 3-level config resolution: project default + department override + per-ceremony override.

Design Reference

See Ceremony Scheduling design page -- "3-Level Resolution" section.

Requirements

• Extend TemplateDepartmentConfig (or the runtime department config) with an optional ceremony_policy: CeremonyPolicyConfig | None field
• When None, the department inherits the project-level policy
• When set, its fields override the project-level policy field-by-field
• Per-ceremony overrides still take precedence over department-level
• Template YAML files can optionally declare department-level ceremony policies
• resolve_ceremony_policy() from feat: sprint ceremony runtime scheduler with task-driven cadence support #961 handles the 3-level merge

Example

departments:
  engineering:
    # inherits project default (task_driven)
  marketing:
    ceremony_policy:
      strategy: calendar  # marketing uses calendar
  design:
    ceremony_policy:
      strategy: event_driven
      transition_threshold: 0.8  # auto-transition at 80%

Implementation

• Modify: src/synthorg/templates/schema.py -- add ceremony_policy to TemplateDepartmentConfig
• Modify: template renderer to pass department policy to config resolution
• Update tests for department-level policy resolution

Dependencies

• feat: sprint ceremony runtime scheduler with task-driven cadence support #961 (CeremonyPolicyConfig model, resolve_ceremony_policy function)