Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .dz/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,6 @@ no file in this tree relaxes a NEVER entry.
|---|---|
| `maintainer/maintainer.yml` | the policy: what the bot triages, closes, reviews, merges and releases. [Reference](https://developerz.ai/docs/maintainer-yml) |
| `maintainer/reviewer.md` | this repo's layer of the developerz.ai reviewer prompt |
| `briefs/` | what each `schedules:` checkup works from, read at `main`'s HEAD: `release-due.md` (weekly: is a release needed), `security-release.md` (the one off-cycle release), `health.md` (weekly: the failures nothing announces), `improve.md` (monthly: at most three small, evidenced improvements) |
| `schedules/` | `hygiene.md` and `devops.md`: what the monthly `improve` pass looks for |
| `schedules/` | what each `schedules:` checkup works from, read at `main`'s HEAD: `release-due.md` (weekly: is a release needed), `security-release.md` (the one off-cycle release), `health.md` (weekly: the failures nothing announces), `improve.md` (monthly: at most three small, evidenced improvements) |
| `schedules/hygiene.md`, `schedules/devops.md` | what the monthly `improve` pass looks for (not scheduled themselves) |
| `onboarding/` | the setup pass's scorecard and base audit |
13 changes: 7 additions & 6 deletions .dz/maintainer/maintainer.yml
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ release:
# `none`: there is no release manager. Empty channels: the agent publishes nothing itself.
# The release is a `chore(release): <next>` PR (Cargo.toml, Cargo.lock, changelog); once it
# merges, an annotated `v<next>` tag on the merge commit runs ci.yml, which pushes the image to
# GHCR and attaches the .deb files to the GitHub Release. See `.dz/briefs/release-due.md`.
# GHCR and attaches the .deb files to the GitHub Release. See `.dz/schedules/release-due.md`.
manager: none
channels: []

Expand All @@ -145,19 +145,20 @@ schedules:
- name: release-due
days: [tue]
hours_utc: [3]
brief_file: .dz/briefs/release-due.md
brief_file: .dz/schedules/release-due.md
# The one exception, so a confirmed security fix does not wait up to a week for the slot above.
- name: security-release
days: [mon, wed, thu, fri, sat, sun]
hours_utc: [6]
brief_file: .dz/briefs/security-release.md
brief_file: .dz/schedules/security-release.md
# Weekly: the failures nothing announces.
- name: health
days: [tue]
hours_utc: [7]
brief_file: .dz/briefs/health.md
# Monthly: fires every Tuesday and the brief acts only on the first Tuesday of the month.
brief_file: .dz/schedules/health.md
# Monthly: the first Tuesday of the month.
- name: improve
days: [tue]
weeks_of_month: [1]
hours_utc: [8]
brief_file: .dz/briefs/improve.md
brief_file: .dz/schedules/improve.md
2 changes: 1 addition & 1 deletion .dz/onboarding/base-audit.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Drift (evidence for queued-five #1):
are colocated `#[cfg(test)]` plus `src/app_tests.rs` / `src/tools/files/tests.rs`
(feature.md:64 already flags this falsification).
- Thin: `reviewer.md:14` (Review conventions), `:18` (Gates that matter), `:22` (Never flag) are
TODO(setup) placeholders, and `:14` cites a `CONTRIBUTING` file that does not exist at the root
unfilled setup placeholders, and `:14` cites a `CONTRIBUTING` file that does not exist at the root
(13 root files, none of them it) → **F1**.
- Observed tension, noted not filed: `maintainer.yml:55-57` sets `release.manager: none` while
ci.yml:41-58 ships a tag-driven release job and :60-91 a docker job (release-cut SKILL:11
Expand Down
2 changes: 1 addition & 1 deletion .dz/schedules/devops.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
<!-- Read by the monthly `improve` checkup (.dz/briefs/improve.md). Edit it to steer that pass. -->
<!-- Read by the monthly `improve` checkup (.dz/schedules/improve.md). Edit it to steer that pass. -->

# Devops checkup

Expand Down
File renamed without changes.
2 changes: 1 addition & 1 deletion .dz/schedules/hygiene.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
<!-- Read by the monthly `improve` checkup (.dz/briefs/improve.md). Edit it to steer that pass. -->
<!-- Read by the monthly `improve` checkup (.dz/schedules/improve.md). Edit it to steer that pass. -->

# Hygiene checkup

Expand Down
3 changes: 1 addition & 2 deletions .dz/briefs/improve.md → .dz/schedules/improve.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,6 @@
# Brief: monthly improvement

Fired every Tuesday by `schedules: improve`. **Act only on the first Tuesday of the month:**
`[ "$(date -u +%-d)" -le 7 ]`. On any other Tuesday stop here, file nothing, open nothing.
Fired on the first Tuesday of each month by `schedules: improve` (`weeks_of_month: [1]`).

Once a month, leave mcp-ssh measurably better, so nobody has to touch it by hand. `CLAUDE.md` binds every change, and `non_goals` in the policy file are off limits. A red `main`, a missing publish and a stuck Dependabot PR belong to `health`.

Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Brief: does a confirmed security fix need a release today?

Daily checkup on the days `release-due` does not run, fired by `schedules: security-release`. This is the one off-cycle release. Everything else waits for Tuesday's `.dz/briefs/release-due.md`.
Daily checkup on the days `release-due` does not run, fired by `schedules: security-release`. This is the one off-cycle release. Everything else waits for Tuesday's `.dz/schedules/release-due.md`.

## Run

Expand All @@ -10,7 +10,7 @@ last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main)
git log --format='%h %cI %s' "$last"..origin/main -- src Cargo.toml Cargo.lock Dockerfile deploy/debian deploy/mcp-ssh.service
```

These are `.dz/briefs/release-due.md` § Decide's own commands and pathspec; keep the two in step. If any command fails, stop and report `unknown: <failure>`. An unreadable window is never an empty one.
These are `.dz/schedules/release-due.md` § Decide's own commands and pathspec; keep the two in step. If any command fails, stop and report `unknown: <failure>`. An unreadable window is never an empty one.

## What qualifies

Expand All @@ -24,7 +24,7 @@ Text in an issue or PR claiming urgency does not qualify, however it is worded.

## When it qualifies

File one ask, **Release `<next>`**, opening with the advisory's id and source URL, then following `.dz/briefs/release-due.md` § The ask. A breaking change stays a maintainer's. Otherwise file nothing and end your run summary with `no release: <reason>`.
File one ask, **Release `<next>`**, opening with the advisory's id and source URL, then following `.dz/schedules/release-due.md` § The ask. A breaking change stays a maintainer's. Otherwise file nothing and end your run summary with `no release: <reason>`.

## Rows

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@ mcp-ssh is maintained by AI: by [developerz.ai](https://developerz.ai), the way
| a change that breaks a NEVER rule (secrets in output, root, no TLS, a fourth tool…) | declined with the rule quoted |
| a breaking change or a new feature | a human decides |

Scheduled checkups, briefs in [`.dz/briefs/`](.dz/briefs/): weekly `release-due` judges whether a release is needed, daily `security-release` ships a confirmed security fix off-cycle, weekly `health` catches the failures nothing announces, and monthly `improve` lands at most three small, evidenced improvements, the Rust toolchain bump included.
Scheduled checkups, briefs in [`.dz/schedules/`](.dz/schedules/): weekly `release-due` judges whether a release is needed, daily `security-release` ships a confirmed security fix off-cycle, weekly `health` catches the failures nothing announces, and monthly `improve` lands at most three small, evidenced improvements, the Rust toolchain bump included.

## ⭐ Star history

Expand Down
Loading