From da8e0478556006ca0a1c64c40d8a1e5bfa2d61ac Mon Sep 17 00:00:00 2001
From: "developerz-ai[bot]"
 <286432749+developerz-ai[bot]@users.noreply.github.com>
Date: Mon, 9 Nov 2026 13:23:48 +0000
Subject: [PATCH] chore(maintainer): declare scout.survey broken_only in policy

The weekly repo-survey cron expects scout.survey: broken_only, but the policy was silent. Declare it explicitly (it equals the platform schema default) so maintainers can see the filing filter. No schedules entry is added: schedule items require a brief_file and the survey is not a briefed checkup.

Dz-Task-Id: tsk_2b5741a12d7c843b377a6ca6cec294cb
---
 .dz/maintainer/maintainer.yml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/.dz/maintainer/maintainer.yml b/.dz/maintainer/maintainer.yml
index 5b1f863..199fd93 100644
--- a/.dz/maintainer/maintainer.yml
+++ b/.dz/maintainer/maintainer.yml
@@ -51,6 +51,13 @@ escalate:
   # Empty: nothing beyond the platform's hardcoded asks (security, license, CLA).
   ask_before_acting: []
 
+scout:
+  # Declared explicitly so the filing filter of the weekly repo-survey is visible here. It matches
+  # the platform default (broken_only): the survey files findings only for something already broken.
+  # There is no survey entry under `schedules:` on purpose: schedule items require a brief_file and
+  # the survey cron is driven by the platform, not by a repo checkup brief.
+  survey: broken_only
+
 schedules:
   # Weekly (owner, 2026-11-06: routine maintenance weekly, CVE daily). Security has its own lanes.
   - name: health