[developerz-ai]

What

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.

Acceptance

• .dz/maintainer/maintainer.yml has a top-level scout: block containing exactly survey: broken_only
• The existing schedules entries health (days [mon], hour 7) and improve (days [mon], hour 8) are unchanged
• The file stays valid YAML and valid against https://developerz.ai/schemas/maintainer.v1.json (scout.survey enum off|broken_only|full; no unknown keys added)
• A comment in the file states the mode matches the platform default (broken_only) and why no survey schedule entry exists
• bash .github/run-tests.sh and the shell-checks CI job are unaffected and green

Changes

• .dz/maintainer/maintainer.yml (edit) — Add a top-level scout: block with survey: broken_only (schema enum off|broken_only|full; schema default is also broken_only) placed just before schedules: (line 54), with a comment saying it is declared explicitly so the weekly repo-survey cron's filing filter is visible, that it matches the platform default, and that broken_only files only findings for something already broken. Do NOT add a schedules entry: the schema's schedule items require a brief_file and no survey brief exists; the survey cron is platform-driven, not a schedules: checkup. Keep health (mon 7) and improve [trimmed]

Verification

No check command was found for this repository, so no gate ran before the commit.

Notes

Premises of the request the team disproved:

• The request implies the survey needs a schedules entry. The schema (maintainer.v1.json, schedules.items) requires brief_file with additionalProperties false, and no survey brief exists in .dz/briefs/ (health.md, improve.md only), so a schedule entry would be invented; the survey cron is platform-side. The schema default for scout.survey is already broken_only.

---

🤖 Opened by developerz.ai for task tsk_2b5741a12d7c843b377a6ca6cec294cb on developerz-ai/mini.

Raised automatically by the raw_task_triage lane.

🤖 developerz.ai, an automated agent, not a human — this PR is one slice of a stacked plan.
Dispatched automatically by the raw_task_triage lane
Model claude-sonnet-5-5 on router.ai.developerz.ai via native, funded by account_key
Ran on box hv-dedicated-ci-1
Cost unknown: no list price on record for claude-sonnet-5-5 on router.ai.developerz.ai
Run timeline run_983ce4f6b26e41b98fdf9550bbf4ae8d
Part 1/1 of plan rtk_c281c5a62e134756b71912a1177db1c7

[developerz-ai]

Declare the survey/scout mode in the maintainer policy

• Picked up
• Surveying the repo — 2026-11-09 13:23 UTC
• Working — 2026-11-09 13:23 UTC
• Pull request opened — chore(maintainer): declare scout.survey broken_only in policy #37 — 2026-11-09 13:23 UTC
• Done

Work landed on #37 — watching it toward merge.

58s · 10 tool calls

Sessions: coding run

---

🤖 developerz.ai, an automated agent, not a human — hv-dedicated-ci-1 (developerz-ai[bot]) · model claude-sonnet-5-5 on router.ai.developerz.ai

[developerz-ai]

✅ Reviewed — nothing blocking

0 actionable comment(s) · grounded on your code

_{⚠️ 1 config note(s): test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against}

_{⏱ 29s wall clock · deepseek-v4.1-flash via router · 1 model call(s) · 806 output token(s)}

_{🤖 developerz.ai — automated review, running on your model and your box.}

[developerz-ai]

Review summary — 1 file(s), 0 finding(s).

Adds an explicit top-level scout: {survey: broken_only} block with explanatory comments to .dz/maintainer/maintainer.yml, leaving schedules untouched. YAML stays valid and the declared value equals the schema default, so runtime behaviour is unchanged.

• test files were not shown to the reviewer — this diff touched no path recognised as a test, so no assertion was available to read the change against

🤖 developerz.ai review — automated, running on your model and your box. What is this? · Reviewed by router/deepseek-v4.1-flash on box hv-dedicated-ci-0 — 14.4k in / 806 out over 1 call, on your flat-rate plan: no per-token charge (~<$0.01 at list price).

[developerz-ai]

Waiting on the repository owner: this pull request changes a gate file, which the platform does not merge by itself.

It changes .dz/maintainer/maintainer.yml.

The merge check refused the edit: .dz/maintainer/maintainer.yml: a modified policy has no declared transform — only a new one on a repo with none for #37 — proof path: git checkout ef9f7cec1c89410e5f3538e561d3970f36ba32b6 -- .dz/maintainer/maintainer.yml and push — a head that leaves every gate path as the base has it needs no proof, and the rest of the PR merges; or keep only an edit that is exactly a declared transform below. When the gate edit IS the goal, no head of ours proves it: the owner applies it. the PR is re-proved when its head changes, when the platform changes its gate-path transforms or templates, and on the hourly re-check; no .maintainer.yml key and no approval releases it — a workflow edit proves only as a tag pin, a permissions narrowing or a platform template, an added .mcp.json or reviewer prompt only as the platform template, a modified .mcp.json only as the platform adding its managed servers to the base file and touching nothing of the maintainer's, and a policy file only as a NEW .dz/maintainer/maintainer.yml on a repo with none that grants no more than the account's posture default

Every file it changes is one of those files, so there is nothing to re-file without them.

To take it, merge it on GitHub. To have the platform merge it, push a narrower edit: a new head is checked again and merged when the check passes. Nothing here is re-tried or closed automatically, and no email is sent; the pull request is listed with the stuck pull requests.

🤖 Posted by developerz.ai — an automated agent, not a human.