From 693dd3638375a3093de52aafac1e32830e6e9e81 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:35 +0000 Subject: [PATCH 1/7] chore: move repo config under .dz/ --- .dz/maintainer/maintainer.yml | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/.dz/maintainer/maintainer.yml b/.dz/maintainer/maintainer.yml index 9e4e493..cfd95e3 100644 --- a/.dz/maintainer/maintainer.yml +++ b/.dz/maintainer/maintainer.yml @@ -59,12 +59,26 @@ schedules: - name: release-due days: [mon, tue, wed, thu, fri] hours_utc: [6] - brief_file: .dz/briefs/release-due.md + brief_file: .dz/schedules/release-due.md - name: health days: [mon, tue, wed, thu, fri, sat, sun] hours_utc: [7] - brief_file: .dz/briefs/health.md + brief_file: .dz/schedules/health.md - name: improve days: [mon] hours_utc: [8] - brief_file: .dz/briefs/improve.md + brief_file: .dz/schedules/improve.md + +# Added by the developerz.ai maintainer agent: blocks from the current template this file did not have. Each states the value already in effect; edit it like any other key. + +# branches: on at 60 because this file exists. A branch with no new commit +# this long is tagged archive// at its last commit, then deleted. +# false keeps every branch. See /docs/maintainer-yml. +branches: + close_inactive_after_days: 60 + +# scout: the platform's daily survey of this repo files only what is already BROKEN +# (red CI, failing tests, a security advisory, a broken build or link) — never an +# improvement idea. `full` lets it file ideas too; `off` stops the survey. +scout: + survey: broken_only From 4a58318c3926d36429a284906f29264c156c3def Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:37 +0000 Subject: [PATCH 2/7] chore: move repo config under .dz/ --- .dz/schedules/health.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 .dz/schedules/health.md diff --git a/.dz/schedules/health.md b/.dz/schedules/health.md new file mode 100644 index 0000000..d578836 --- /dev/null +++ b/.dz/schedules/health.md @@ -0,0 +1,27 @@ +# Brief: is the project healthy? + +Daily checkup fired by `schedules: health`: the failures no issue or PR announces. + +| Signal | Command | Healthy | +|---|---|---| +| `main` is green | `gh run list --workflow ci.yml --branch main --event push --limit 1 --json conclusion,headSha,url`, then `git rev-parse origin/main` | `success` on the `origin/main` tip; a null conclusion or another sha is no verdict | +| the last release published | `t=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main); gh run list --workflow release.yml --limit 5 --json conclusion,headSha,url` against `git rev-parse "$t^{commit}"` | `success` on that sha; no run on that sha is no verdict | +| npm serves the tree | `npm view @developerz.ai/aitm version` and `npm view @developerz.ai/ai-claude-compat version`, against `jq -r .version packages/*/package.json` | all equal, or an open release PR or in-flight run explains it | +| the GitHub Release exists | `gh release view "$t" --json isDraft,publishedAt` | not a draft, published | +| Dependabot is not stuck | `gh pr list --app dependabot --state open --limit 100 --json number,updatedAt,statusCheckRollup` | no PR with failed checks and more than 7 days since `updatedAt` | + +## What to file + +For each unhealthy signal, one ask, unless an open issue already carries its exact title +(`gh issue list --state open --search " in:title" --json number,title`, then compare byte for byte). +Titles are stable: nothing that changes run to run (sha, run URL, version) goes in one; that goes in the body, +with the command and its output. Unreadable evidence is no verdict: re-run it, never file it as a defect. +A red `main` comes first: nothing releases from it. + +## Rows + +- `main-green`: Main CI succeeds on the `origin/main` tip; a null conclusion or another sha is no verdict. +- `release-published`: The release workflow succeeds on the latest matching release tag's commit; no run on that sha is no verdict. +- `npm-tree`: Both published npm package versions equal the tree versions, or an open release PR or in-flight run explains the difference. +- `github-release`: The GitHub Release for that tag is published and is not a draft. +- `dependabot-stuck`: No open Dependabot PR has failed checks and more than 7 days since `updatedAt`. From 17c146a5ca5973ec377b90165b04284bb0362372 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:39 +0000 Subject: [PATCH 3/7] chore: move repo config under .dz/ --- .dz/briefs/health.md | 27 --------------------------- 1 file changed, 27 deletions(-) delete mode 100644 .dz/briefs/health.md diff --git a/.dz/briefs/health.md b/.dz/briefs/health.md deleted file mode 100644 index d578836..0000000 --- a/.dz/briefs/health.md +++ /dev/null @@ -1,27 +0,0 @@ -# Brief: is the project healthy? - -Daily checkup fired by `schedules: health`: the failures no issue or PR announces. - -| Signal | Command | Healthy | -|---|---|---| -| `main` is green | `gh run list --workflow ci.yml --branch main --event push --limit 1 --json conclusion,headSha,url`, then `git rev-parse origin/main` | `success` on the `origin/main` tip; a null conclusion or another sha is no verdict | -| the last release published | `t=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main); gh run list --workflow release.yml --limit 5 --json conclusion,headSha,url` against `git rev-parse "$t^{commit}"` | `success` on that sha; no run on that sha is no verdict | -| npm serves the tree | `npm view @developerz.ai/aitm version` and `npm view @developerz.ai/ai-claude-compat version`, against `jq -r .version packages/*/package.json` | all equal, or an open release PR or in-flight run explains it | -| the GitHub Release exists | `gh release view "$t" --json isDraft,publishedAt` | not a draft, published | -| Dependabot is not stuck | `gh pr list --app dependabot --state open --limit 100 --json number,updatedAt,statusCheckRollup` | no PR with failed checks and more than 7 days since `updatedAt` | - -## What to file - -For each unhealthy signal, one ask, unless an open issue already carries its exact title -(`gh issue list --state open --search "<title> in:title" --json number,title`, then compare byte for byte). -Titles are stable: nothing that changes run to run (sha, run URL, version) goes in one; that goes in the body, -with the command and its output. Unreadable evidence is no verdict: re-run it, never file it as a defect. -A red `main` comes first: nothing releases from it. - -## Rows - -- `main-green`: Main CI succeeds on the `origin/main` tip; a null conclusion or another sha is no verdict. -- `release-published`: The release workflow succeeds on the latest matching release tag's commit; no run on that sha is no verdict. -- `npm-tree`: Both published npm package versions equal the tree versions, or an open release PR or in-flight run explains the difference. -- `github-release`: The GitHub Release for that tag is published and is not a draft. -- `dependabot-stuck`: No open Dependabot PR has failed checks and more than 7 days since `updatedAt`. From 0a583132a519f1c191075c22e7ce7766d8d0a35c Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:40 +0000 Subject: [PATCH 4/7] chore: move repo config under .dz/ --- .dz/schedules/improve.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 .dz/schedules/improve.md diff --git a/.dz/schedules/improve.md b/.dz/schedules/improve.md new file mode 100644 index 0000000..a84a8bf --- /dev/null +++ b/.dz/schedules/improve.md @@ -0,0 +1,38 @@ +# Brief: monthly improvement + +Fired every Monday by `schedules: improve`. **Act only on the first Monday of the month:** +`[ "$(date -u +%-d)" -le 7 ]`. On any other Monday stop here, file nothing, open nothing. + +Once a month, leave aitm measurably better. `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`. + +## Signals + +| Signal | Command | +|---|---| +| the gate on fresh `main` | `bun run lint && bun run typecheck && bun run typecheck:tests && bun run test:node` | +| dependency majors | `bun outdated` | +| open bugs | `gh issue list --state open --label bug --json number,title,url` | + +## Pick at most three, in this order + +1. Anything the gate found broken or flaky: the root cause, never a retry or a skip. +2. Dependency majors. A `bun.lock` resync is its own PR, never inside a release (`CLAUDE.md`). +3. Open bugs, each starting from a test that fails on `main`. +4. README claims that no longer match the code, then dead code. + +## Ship + +One small PR per improvement, its evidence in the body, `bun run lint && bun run typecheck && bun run typecheck:tests && bun run test:node` green first. Never bump the version or touch release automation here. No co-author trailers (`CLAUDE.md`). +Check no open PR or issue already covers it. If nothing is worth changing, do nothing: no empty PRs, no churn. + +## Rows + +- `first-monday-only`: Act only on the first Monday of the month; on any other Monday stop here, file nothing, open nothing. +- `gate-on-main`: The gate on fresh `main` (`bun run lint && bun run typecheck && bun run typecheck:tests && bun run test:node`) is green; anything it found broken or flaky is picked first — the root cause, never a retry or a skip. +- `dependency-majors`: Dependency majors exist per `bun outdated`; a `bun.lock` resync is its own PR, never inside a release. +- `open-bugs`: Open bugs exist per `gh issue list --state open --label bug --json number,title,url`; each is picked starting from a test that fails on `main`. +- `readme-drift`: README claims that no longer match the code. +- `dead-code`: Dead code, after the README claims that no longer match the code. +- `already-covered`: No open PR or issue already covers the improvement. +- `nothing-worth-changing`: Nothing is worth changing: do nothing, no empty PRs, no churn. From 6c4bbc679c2479785d7045f997b4dc162b094c83 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:41 +0000 Subject: [PATCH 5/7] chore: move repo config under .dz/ --- .dz/briefs/improve.md | 38 -------------------------------------- 1 file changed, 38 deletions(-) delete mode 100644 .dz/briefs/improve.md diff --git a/.dz/briefs/improve.md b/.dz/briefs/improve.md deleted file mode 100644 index a84a8bf..0000000 --- a/.dz/briefs/improve.md +++ /dev/null @@ -1,38 +0,0 @@ -# Brief: monthly improvement - -Fired every Monday by `schedules: improve`. **Act only on the first Monday of the month:** -`[ "$(date -u +%-d)" -le 7 ]`. On any other Monday stop here, file nothing, open nothing. - -Once a month, leave aitm measurably better. `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`. - -## Signals - -| Signal | Command | -|---|---| -| the gate on fresh `main` | `bun run lint && bun run typecheck && bun run typecheck:tests && bun run test:node` | -| dependency majors | `bun outdated` | -| open bugs | `gh issue list --state open --label bug --json number,title,url` | - -## Pick at most three, in this order - -1. Anything the gate found broken or flaky: the root cause, never a retry or a skip. -2. Dependency majors. A `bun.lock` resync is its own PR, never inside a release (`CLAUDE.md`). -3. Open bugs, each starting from a test that fails on `main`. -4. README claims that no longer match the code, then dead code. - -## Ship - -One small PR per improvement, its evidence in the body, `bun run lint && bun run typecheck && bun run typecheck:tests && bun run test:node` green first. Never bump the version or touch release automation here. No co-author trailers (`CLAUDE.md`). -Check no open PR or issue already covers it. If nothing is worth changing, do nothing: no empty PRs, no churn. - -## Rows - -- `first-monday-only`: Act only on the first Monday of the month; on any other Monday stop here, file nothing, open nothing. -- `gate-on-main`: The gate on fresh `main` (`bun run lint && bun run typecheck && bun run typecheck:tests && bun run test:node`) is green; anything it found broken or flaky is picked first — the root cause, never a retry or a skip. -- `dependency-majors`: Dependency majors exist per `bun outdated`; a `bun.lock` resync is its own PR, never inside a release. -- `open-bugs`: Open bugs exist per `gh issue list --state open --label bug --json number,title,url`; each is picked starting from a test that fails on `main`. -- `readme-drift`: README claims that no longer match the code. -- `dead-code`: Dead code, after the README claims that no longer match the code. -- `already-covered`: No open PR or issue already covers the improvement. -- `nothing-worth-changing`: Nothing is worth changing: do nothing, no empty PRs, no churn. From ea0841f09358d7182369baac5d71480824b29a82 Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:42 +0000 Subject: [PATCH 6/7] chore: move repo config under .dz/ --- .dz/schedules/release-due.md | 48 ++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 .dz/schedules/release-due.md diff --git a/.dz/schedules/release-due.md b/.dz/schedules/release-due.md new file mode 100644 index 0000000..4f02e24 --- /dev/null +++ b/.dz/schedules/release-due.md @@ -0,0 +1,48 @@ +# Brief: is a release due? + +Weekday checkup fired by `schedules: release-due`. This brief decides *when*; the steps below are the *how*. + +## Decide + +```bash +git fetch --tags --unshallow origin 2>/dev/null || git fetch --tags origin +last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) +git log --format='%h %cI %s' "$last"..origin/main -- packages/aitm/src packages/ai-claude-compat/src packages/aitm/package.json packages/ai-claude-compat/package.json bun.lock +jq -r .version packages/*/package.json +``` + +The pathspec names what reaches users. Prose, tests, CI and docs ship nothing. + +| Window | Do | +|---|---| +| a command above failed | no verdict: surface it, file nothing | +| empty | nothing | +| the stamped version is already ahead of `$last` | nothing: a release is in flight, watch `release.yml` | +| the oldest shipping commit is under 24 h old | nothing: its author may still release it | +| `main`'s latest `ci.yml` push run is not `success` | nothing: `health` owns a red `main` | +| a breaking change in the window | no release ask. If no open issue titled `Major release pending` exists, file one for a maintainer, with no release steps | +| otherwise | one ask, **Release `<next>`**, listing the commits | + +`<next>`: a `feat` subject in the window is a minor, anything else a patch. + +## Rows + +- `decide-commands-failed` — a command above failed: no verdict, surface it, file nothing. +- `shipping-window-empty` — empty: nothing. +- `version-ahead-of-last-tag` — the stamped version is already ahead of `$last`: nothing, a release is in flight, watch `release.yml`. +- `oldest-shipping-commit-under-24h` — the oldest shipping commit is under 24 h old: nothing, its author may still release it. +- `main-ci-run-not-success` — `main`'s latest `ci.yml` push run is not `success`: nothing, `health` owns a red `main`. +- `breaking-change-in-window` — a breaking change in the window: no release ask. If no open issue titled `Major release pending` exists, file one for a maintainer, with no release steps. +- `release-due` — otherwise: one ask, **Release `<next>`**, listing the commits. + +## The ask + +File nothing if an open issue title is exactly `Release <next>`, or an open PR is already that release. Body, for the box that takes it: + +1. Re-run Decide on fresh `main`; still due, or stop. +2. Bump the three version lines: both package `version` fields and aitm's exact `@developerz.ai/ai-claude-compat` pin. Run `bun install`. Never regenerate `bun.lock` for a release (`CLAUDE.md`). +3. Run the gate, then one PR titled `chore(release): <next>`, nothing else in the diff. It merges on green like any PR. +4. After it merges: `gh release create v<next> --target <merge sha> --title "v<next>" --generate-notes`, only after `git show <merge sha>:packages/aitm/package.json` shows `<next>`. Publishing the Release is what runs `release.yml` (`PUBLISHING.md`). +5. Watch `release.yml` to the end. A failure is an issue for a maintainer. + +Never re-tag, move or delete a tag, and never publish by hand. A failed publish is an issue for a maintainer; the fix ships as the next patch. From 4178b52e7981d956233b86f94a5168136b5215bf Mon Sep 17 00:00:00 2001 From: "developerz-ai[bot]" <286432749+developerz-ai[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 20:59:44 +0000 Subject: [PATCH 7/7] chore: move repo config under .dz/ --- .dz/briefs/release-due.md | 48 --------------------------------------- 1 file changed, 48 deletions(-) delete mode 100644 .dz/briefs/release-due.md diff --git a/.dz/briefs/release-due.md b/.dz/briefs/release-due.md deleted file mode 100644 index 4f02e24..0000000 --- a/.dz/briefs/release-due.md +++ /dev/null @@ -1,48 +0,0 @@ -# Brief: is a release due? - -Weekday checkup fired by `schedules: release-due`. This brief decides *when*; the steps below are the *how*. - -## Decide - -```bash -git fetch --tags --unshallow origin 2>/dev/null || git fetch --tags origin -last=$(git describe --tags --abbrev=0 --match 'v[0-9]*' origin/main) -git log --format='%h %cI %s' "$last"..origin/main -- packages/aitm/src packages/ai-claude-compat/src packages/aitm/package.json packages/ai-claude-compat/package.json bun.lock -jq -r .version packages/*/package.json -``` - -The pathspec names what reaches users. Prose, tests, CI and docs ship nothing. - -| Window | Do | -|---|---| -| a command above failed | no verdict: surface it, file nothing | -| empty | nothing | -| the stamped version is already ahead of `$last` | nothing: a release is in flight, watch `release.yml` | -| the oldest shipping commit is under 24 h old | nothing: its author may still release it | -| `main`'s latest `ci.yml` push run is not `success` | nothing: `health` owns a red `main` | -| a breaking change in the window | no release ask. If no open issue titled `Major release pending` exists, file one for a maintainer, with no release steps | -| otherwise | one ask, **Release `<next>`**, listing the commits | - -`<next>`: a `feat` subject in the window is a minor, anything else a patch. - -## Rows - -- `decide-commands-failed` — a command above failed: no verdict, surface it, file nothing. -- `shipping-window-empty` — empty: nothing. -- `version-ahead-of-last-tag` — the stamped version is already ahead of `$last`: nothing, a release is in flight, watch `release.yml`. -- `oldest-shipping-commit-under-24h` — the oldest shipping commit is under 24 h old: nothing, its author may still release it. -- `main-ci-run-not-success` — `main`'s latest `ci.yml` push run is not `success`: nothing, `health` owns a red `main`. -- `breaking-change-in-window` — a breaking change in the window: no release ask. If no open issue titled `Major release pending` exists, file one for a maintainer, with no release steps. -- `release-due` — otherwise: one ask, **Release `<next>`**, listing the commits. - -## The ask - -File nothing if an open issue title is exactly `Release <next>`, or an open PR is already that release. Body, for the box that takes it: - -1. Re-run Decide on fresh `main`; still due, or stop. -2. Bump the three version lines: both package `version` fields and aitm's exact `@developerz.ai/ai-claude-compat` pin. Run `bun install`. Never regenerate `bun.lock` for a release (`CLAUDE.md`). -3. Run the gate, then one PR titled `chore(release): <next>`, nothing else in the diff. It merges on green like any PR. -4. After it merges: `gh release create v<next> --target <merge sha> --title "v<next>" --generate-notes`, only after `git show <merge sha>:packages/aitm/package.json` shows `<next>`. Publishing the Release is what runs `release.yml` (`PUBLISHING.md`). -5. Watch `release.yml` to the end. A failure is an issue for a maintainer. - -Never re-tag, move or delete a tag, and never publish by hand. A failed publish is an issue for a maintainer; the fix ships as the next patch.