Skip to content

chore: move repo config under .dz/ - #81

Closed
developerz-ai[bot] wants to merge 9 commits into
mainfrom
dz/config-migrate
Closed

developerz-ai[bot] wants to merge 9 commits into
mainfrom
dz/config-migrate

Conversation

@developerz-ai

@developerz-ai developerz-ai Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Moves the maintainer-agent config under .dz/ so the repo root stays readable:

  • .dz/briefs/health.md → .dz/schedules/health.md
  • .dz/briefs/improve.md → .dz/schedules/improve.md
  • .dz/briefs/release-due.md → .dz/schedules/release-due.md
  • .dz/briefs/security-release.md → .dz/schedules/security-release.md
  • .dz/maintainer/maintainer.yml: every brief_file: under .dz/briefs/ now points at .dz/schedules/, the one brief home

A moved file keeps identical content; only the path changes.
The Contents API returned a new blob sha for each write and the consumer asserted it is
exactly the planned one before opening this PR, so nothing was re-encoded.

Not interested? Just close this PR.


🤖 Opened automatically by developerz.ai (developerz-ai[bot]), an automated agent, not a human. Not interested? Just close this PR. What is this?

@developerz-ai
developerz-ai Bot marked this pull request as ready for review November 17, 2026 08:58
@developerz-ai

developerz-ai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor Author

✅ 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

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

@developerz-ai developerz-ai Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Updates four schedule brief paths from .dz/briefs/ to .dz/schedules/. No concrete defect is established by the provided diff.

  • 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?

@developerz-ai

developerz-ai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor Author

The developerz.ai bot is closing this pull request: it also changes gate files the merge check cannot machine-prove safe, and a fix round may not revert them.

It changes .dz/maintainer/maintainer.yml.

The merge check refused it (gate_path_widens): .dz/maintainer/maintainer.yml: the edit grants more than the base policy on schedules for #81.

The platform's setup template owns those files, so a fix round may not edit them and the revert cannot be made here. No goal is re-filed for it. The branch dz/config-migrate is kept; nothing was deleted or reverted. To take this pull request as it is, reopen it and merge it by hand: it is not closed a second time.

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

@developerz-ai developerz-ai Bot closed this Nov 17, 2026
@developerz-ai
developerz-ai Bot deleted the dz/config-migrate branch November 17, 2026 11:02
developerz-ai Bot pushed a commit that referenced this pull request Nov 18, 2026
#82)

## What

Moves the four scheduled briefs from `.dz/briefs/` to `.dz/schedules/`,
names the monthly `improve` cadence in the policy, and rewords one
stub-shaped line in the onboarding base audit.

## Why

- `.dz/schedules/` is the one brief home the platform template writes;
two homes made the layout drift. The platform's own move PR (#81) was
closed by its merge gate, so this lands it by hand.
- The `improve` brief faked a monthly cadence with `[ "$(date -u +%-d)"
-le 7 ]`, firing every Tuesday to do nothing three weeks in four. The
schema now has `weeks_of_month`, so the policy says it directly.
- `.dz/onboarding/base-audit.md` had one line opening with
`TODO(setup)`, which the `.dz` contract reads as an unfilled setup slot.
It is a historical audit sentence, so it is reworded, not deleted.

## Changes

- `git mv .dz/briefs/{release-due,security-release,health,improve}.md
.dz/schedules/`; every `brief_file` and every in-repo reference
(`.dz/README.md`, `README.md`, the two `.dz/schedules/` steering files,
`security-release.md`, the policy comment) follows.
- `.dz/maintainer/maintainer.yml`: `improve` gains `weeks_of_month:
[1]`; nothing else in the policy changes.
- `.dz/schedules/improve.md`: drops the date check.
- `.dz/onboarding/base-audit.md`: "TODO(setup) placeholders" becomes
"unfilled setup placeholders".

## Verification

- `.dz` contract (`bun run dz-contract <clone> --repo
developerz-ai/mcp-ssh`): before, 1 finding (`setup_todo` in
base-audit.md); after, `ok`.
- Policy validates against the current schema (`policy-cli`): `ok`.
- `cargo test --locked --test public_tree --test module_map`: 11 passed.
No Rust source changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants