Repository navigation
chore(dz): briefs to .dz/schedules, monthly improve via weeks_of_month - #82
Merged
Merged
Conversation
…a weeks_of_month The four scheduled briefs move from .dz/briefs/ to .dz/schedules/, the one brief home the platform template writes, and every reference follows. The improve schedule names its cadence in the policy (weeks_of_month: [1]) instead of a date check inside the brief. The base audit's one stub-shaped line is reworded so the .dz contract stops reading it as an unfilled setup slot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
✅ Reviewed — nothing blocking0 actionable comment(s) · grounded on your code |
Contributor
There was a problem hiding this comment.
Review summary — 10 file(s), 0 finding(s).
Consolidates scheduled briefs under .dz/schedules/, moves the monthly improve cadence into policy, and updates references and audit wording. No concrete defects are established by the supplied diff; changes are confined to maintenance configuration and documentation.
- 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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves the four scheduled briefs from
.dz/briefs/to.dz/schedules/, names the monthlyimprovecadence 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 (chore: move repo config under .dz/ #81) was closed by its merge gate, so this lands it by hand.improvebrief faked a monthly cadence with[ "$(date -u +%-d)" -le 7 ], firing every Tuesday to do nothing three weeks in four. The schema now hasweeks_of_month, so the policy says it directly..dz/onboarding/base-audit.mdhad one line opening withTODO(setup), which the.dzcontract 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/; everybrief_fileand 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:improvegainsweeks_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
.dzcontract (bun run dz-contract <clone> --repo developerz-ai/mcp-ssh): before, 1 finding (setup_todoin base-audit.md); after,ok.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