From 64c7d3cd8aeff56d39a08fcbe173432b5c8bf85a Mon Sep 17 00:00:00 2001 From: mashfromband Date: Mon, 12 Oct 2026 13:40:47 +0900 Subject: [PATCH 1/3] docs: scope fork operations to owner-authorized AI assignees --- AGENTS.md | 19 ++++++++- CONTRIBUTING.md | 7 ++-- MAINTAINERS.md | 41 +++++++++++-------- docs-site/src/content/docs/contributing.md | 9 ++-- docs-site/src/content/docs/fr/contributing.md | 3 ++ docs-site/src/content/docs/ja/contributing.md | 3 ++ docs-site/src/content/docs/ko/contributing.md | 3 ++ docs-site/src/content/docs/ru/contributing.md | 3 ++ docs-site/src/content/docs/tr/contributing.md | 3 ++ .../src/content/docs/zh-cn/contributing.md | 3 ++ .../src/content/docs/zh-tw/contributing.md | 3 ++ 11 files changed, 69 insertions(+), 28 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4e81205b92b..758c93458e5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,3 +1,18 @@ +## この所有者の開発運用（2026-10-12） + +この規則は GitHub の実所有者が mashfromband の場合に適用する。オーナーの2026-10-12の直接指示（共有ToDo2458/2465）が、古い一般的な人手レビュー・マージ・日常操作・再承認の前提に優先する。他の所有者や顧客固有の契約には適用しない。 + +人は要件を決め、本人だけが決められる質問に答える。AI担当は設計・実装・検査・失敗の修正・別モデルレビュー・Must解消・同じ最終HEADのCI確認・PRマージ・必要な既存Prdへの反映・後片付けまで行う。PRを作っただけ、委譲を受け付けただけでは完了にしない。日常操作や技術的な選択について、人のレビューや再承認を待たない。 + +既存のDiscord回答は元ToDo・質問・本人ID・対象・範囲と照合し、同じ判断を再質問しない。未指定の製品要件、新費用、権利、顧客との新しい約束、公開、取り消せない操作など本人だけが決める点は、PCのSkill discord-owner-askに従って具体的な選択肢を1回送る。その項目だけ共有ToDoのblockにし、独立した作業を続ける。他ToDoの完了待ちはwait --onで記録する。 + +プロジェクト固有の検査・受入条件・秘密保護・顧客固有の人によるレビュー要求・既存Prd限定の制約は維持する。新費用・新APIキーは使わない。Vercel/Railwayのオーナーアカウント内はソロ運用とし、他メンバーがいることだけで承認待ちにしない。他OrgのGitHub環境は変更しない。ドメイン管理はRakkoだけを使う。コマンドは窓を出さず担当が実行する。 + +既存checkoutでは実remoteとGitHub ownerを再照合し、読み書き前にscrub391 --guard-pathで保護判定する。保護対象には触らず名前・パスを報告しない。専用branchで作業し、他担当の未コミットを巻き込まない。稼働中担当を止めず、元要件を保持した保存specまたは正式配送で次の区切りから反映させる。受付・読取・実反映を区別する。 + +完了時は変更・確認済み・未確認・残作業を件数で記録し、PR URL、固定HEAD、検査、CI、別モデルレビュー、マージ、Prd反映の結果を元の共有ToDoへ残す。一時データと自作ChromeタブはPCの所有記録に従って片付ける。 + + # AGENTS.md Guidance for AI agents (and humans) working on or reviewing this repository. @@ -291,7 +306,7 @@ than nudged. ## Branch policy - `dev` — the single integration branch and the target for every pull request. -- `main` — release branch. It only moves by maintainer-controlled promotion +- `main` — release branch. It only moves by assignee-controlled, independently reviewed promotion from `dev` (releases, docs deploys). Do not open feature PRs against `main`. - `preview` — prerelease train (`x.y.z-preview.*` versions). @@ -341,7 +356,7 @@ The bypass is PR-only, so a direct push to `dev` remains rejected regardless of [`MAINTAINERS.md`](./MAINTAINERS.md) is authoritative for review and merge policy (approvals, CI requirements, security review, promotion). This file -summarizes; it never overrides it. +summarizes; it never overrides it. In this mashfromband fork, the owner-authorized policy in MAINTAINERS.md replaces general human-maintainer approval requirements; inherited upstream roles do not grant or require approvals here. ## Review guidelines diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 08db5a6bbbf..9f4834dcf7b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,6 +2,8 @@ Thanks for helping with opencodex. +For this mashfromband fork, [AGENTS.md](AGENTS.md) and [MAINTAINERS.md](MAINTAINERS.md) apply the owner's 2026-10-12 directive: the AI assignee completes independent model review, fixes, exact-head checks and merge. The hosted guides describe upstream contribution; upstream maintainers do not supply or require approval for this fork. Customer-specific human review contracts remain in force. + - Start with the canonical guide: [Contributing](https://opencodex.me/contributing/) - Pull-request quality contract: [Review readiness and author responsibility](https://opencodex.me/contributing/pr-quality/) - Public user docs live in [`docs-site/`](./docs-site) @@ -13,7 +15,7 @@ Thanks for helping with opencodex. ## Branches - `dev` — the only integration target for pull requests. -- `main` — releases only; moves by maintainer-controlled promotion from `dev`. +- `main` — releases only; moves by independently reviewed AI-assignee promotion from `dev`. - `preview` — prerelease train. The `dev2-go` Go native-port line has been retired. Its history is archived at @@ -49,8 +51,7 @@ A ready-for-review PR is the author's claim that the change is complete, underst checks this mechanically, and its failures are deterministic — read the message and you know what to change. - Authentication, workflow, release automation, and dependency-installation - surfaces need a maintainer to sponsor the change (`maintainer-sponsored`) - before merge. Those are the places where a bad merge is expensive and hard to + surfaces require independent security review before merge in this fork. The upstream `maintainer-sponsored` convention remains an upstream requirement. Those are the places where a bad merge is expensive and hard to unwind, which is why they are the only pre-approved surfaces here. - A PR that stalls with unresolved review feedback may be closed, with the reason stated. A closed PR can be reopened once the stated reason is resolved, or diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 4d047649567..e6ffed7a675 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -1,9 +1,8 @@ # Maintainers -This document lists the people responsible for maintaining opencodex and defines the project's -review and merge policy. +This document defines the review and merge policy of the mashfromband fork. The 2026-10-12 owner directive below replaces general human-maintainer approval and operational handoff requirements in this fork. Upstream roster and historical governance entries below are attribution/reference only; they do not describe this fork's permissions or require an upstream person's approval. -## Current maintainers +## Upstream maintainers (reference only) | GitHub account | Project role | Responsibilities | | --- | --- | --- | @@ -16,7 +15,7 @@ through GitHub repository settings. `dev` is the only integration line. The former `dev2-go` carry duty is retired; see [The retired `dev2-go` line](#the-retired-dev2-go-line). -## Former maintainers +## Former upstream maintainers (history) | GitHub account | Project role | Period | | --- | --- | --- | @@ -54,17 +53,9 @@ when a maintainer steps down. Authors with repository push permission skip the ancestry heuristic only. As with the approval requirement above, this part is enforced by convention; the ruleset does not check ancestry (see the note under the change log). -- Pull requests require successful required CI checks before merge. Contributor pull requests - normally require approval from at least one maintainer other than the author. -- A current maintainer with GitHub `maintain` or `admin` access may explicitly integrate a pull - request into `dev` without another maintainer's approval, including their own pull request. - Record that choice and the exact-head verification in the pull-request description or comment. - This is maintainer integration, not a self-approval or an independent review. Outstanding - maintainer change requests must still be resolved or explicitly withdrawn. Technical review, - attribution, documentation and security-review duties remain in force. -- The maintainer-integration exception applies only to `dev`. It does not change review rules - for `main` or `preview`, grant contributor authors approval authority, or permit direct pushes, - force-pushes or branch deletion. Authors do not submit approving reviews of their own work. +- In this mashfromband fork, AI assignees own design, implementation, checks, fixes, independent model review, resolution of Must findings, successful required CI for the exact final head, merge, necessary existing-production reflection and cleanup. They do not wait for a human maintainer's review or merge. +- Authors do not submit approving GitHub reviews of their own work. Independent model review is recorded with the fixed head and evidence; an author attestation alone is not independent review. Outstanding substantiated review findings must be resolved. +- Integration still targets `dev`; release and preview promotion retain their technical, security and verification gates. The AI assignee performs authorized promotion instead of handing it to a human. New publication, costs, rights or unspecified product requirements remain owner-only decisions under AGENTS.md. Upstream promotion and maintainer requirements apply only upstream. - Authentication, credential handling, GitHub Actions, release automation, dependency installation, and other security-boundary changes require explicit security review. - A new or promoted provider preset is a credential-destination change. Before merge it needs the @@ -76,12 +67,12 @@ when a maintainer steps down. with the service is disclosed, not disqualifying, and it does not lower the evidence bar. When the evidence is incomplete, prefer an inert `src/providers/free-directory.ts` reference row over a canonical registry entry. -- Security-sensitive and release-related changes should be reviewed by both maintainers when +- Security-sensitive and release-related changes should receive an additional independent security review when practical. - Integration uses pull requests, including urgent maintainer repairs. The PR-only ruleset bypass does not authorize direct pushes; incident changes to branch protection require a separate owner decision. -- Promotion from `dev` to `main` and npm releases is maintainer-controlled. +- Promotion from `dev` to `main` is performed by the AI assignee after required verification. npm publication requires existing owner authorization; this policy creates no new publication permission. - **Opening a release starts by moving `dev`'s version line forward.** Before cutting a release, `dev` must already outrank the version being released; `release.yml` asserts this and refuses to publish otherwise. Dispatch @@ -128,7 +119,7 @@ defects. Bun-native TypeScript on `dev` is the single runtime line again. (Rust via N-API is the current candidate), not a second integration branch. Reopening a parallel runtime line is an owner decision. -## Maintainer changes +## Upstream maintainer changes (reference and history only) Adding or removing a maintainer requires: @@ -208,3 +199,17 @@ Adding or removing a maintainer requires: Private vulnerability reports are handled by the current maintainers according to [`SECURITY.md`](./SECURITY.md). Do not disclose secrets or exploit details in a public issue. + +## この所有者の開発運用（2026-10-12） + +この規則は GitHub の実所有者が mashfromband の場合に適用する。オーナーの2026-10-12の直接指示（共有ToDo2458/2465）が、古い一般的な人手レビュー・マージ・日常操作・再承認の前提に優先する。他の所有者や顧客固有の契約には適用しない。 + +人は要件を決め、本人だけが決められる質問に答える。AI担当は設計・実装・検査・失敗の修正・別モデルレビュー・Must解消・同じ最終HEADのCI確認・PRマージ・必要な既存Prdへの反映・後片付けまで行う。PRを作っただけ、委譲を受け付けただけでは完了にしない。日常操作や技術的な選択について、人のレビューや再承認を待たない。 + +既存のDiscord回答は元ToDo・質問・本人ID・対象・範囲と照合し、同じ判断を再質問しない。未指定の製品要件、新費用、権利、顧客との新しい約束、公開、取り消せない操作など本人だけが決める点は、PCのSkill discord-owner-askに従って具体的な選択肢を1回送る。その項目だけ共有ToDoのblockにし、独立した作業を続ける。他ToDoの完了待ちはwait --onで記録する。 + +プロジェクト固有の検査・受入条件・秘密保護・顧客固有の人によるレビュー要求・既存Prd限定の制約は維持する。新費用・新APIキーは使わない。Vercel/Railwayのオーナーアカウント内はソロ運用とし、他メンバーがいることだけで承認待ちにしない。他OrgのGitHub環境は変更しない。ドメイン管理はRakkoだけを使う。コマンドは窓を出さず担当が実行する。 + +既存checkoutでは実remoteとGitHub ownerを再照合し、読み書き前にscrub391 --guard-pathで保護判定する。保護対象には触らず名前・パスを報告しない。専用branchで作業し、他担当の未コミットを巻き込まない。稼働中担当を止めず、元要件を保持した保存specまたは正式配送で次の区切りから反映させる。受付・読取・実反映を区別する。 + +完了時は変更・確認済み・未確認・残作業を件数で記録し、PR URL、固定HEAD、検査、CI、別モデルレビュー、マージ、Prd反映の結果を元の共有ToDoへ残す。一時データと自作ChromeタブはPCの所有記録に従って片付ける。 diff --git a/docs-site/src/content/docs/contributing.md b/docs-site/src/content/docs/contributing.md index 19f694d3ebd..6ac06309b7a 100644 --- a/docs-site/src/content/docs/contributing.md +++ b/docs-site/src/content/docs/contributing.md @@ -3,6 +3,9 @@ title: Contributing description: Develop opencodex — setup, layout, conventions, and how to add a provider or adapter. --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## Setup Source development requires the `bun` CLI on your `PATH`. The published npm package bundles its own @@ -147,11 +150,7 @@ The current maintainers, their responsibilities, and the review and merge policy [`MAINTAINERS.md`](https://github.com/lidge-jun/opencodex/blob/main/MAINTAINERS.md). GitHub review ownership for the repository and security-sensitive paths is declared in `.github/CODEOWNERS`. -Contributor pull requests normally need a maintainer's approval. A current maintainer with -GitHub `maintain` or `admin` access may explicitly integrate a PR into `dev`, including their -own, without a second maintainer approval. The decision and exact-head verification must be -recorded; CI, security review and outstanding maintainer objections still apply. This exception -does not change `main`/`preview` review rules or allow direct pushes, force-pushes or deletion. +In this fork, AI assignees integrate after independent model review, Must resolution and successful exact-head CI; no human-maintainer approval is required. The upstream integration exception, roster and GitHub permissions described in the hosted guide apply only upstream. ## Conventions diff --git a/docs-site/src/content/docs/fr/contributing.md b/docs-site/src/content/docs/fr/contributing.md index 34d6548d778..baf9fd0e9c3 100644 --- a/docs-site/src/content/docs/fr/contributing.md +++ b/docs-site/src/content/docs/fr/contributing.md @@ -3,6 +3,9 @@ title: Contribuer description: Développez opencodex — installation, structure, conventions et ajout d’un fournisseur ou d’un adaptateur. --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## Configuration Le développement depuis les sources exige la CLI `bun` dans votre `PATH`. Le paquet npm publié fournit son propre diff --git a/docs-site/src/content/docs/ja/contributing.md b/docs-site/src/content/docs/ja/contributing.md index ebada118d04..67f05eb3bd2 100644 --- a/docs-site/src/content/docs/ja/contributing.md +++ b/docs-site/src/content/docs/ja/contributing.md @@ -3,6 +3,9 @@ title: コントリビュート description: opencodex の開発環境、構成、規約、プロバイダーとアダプターの追加方法。 --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## セットアップ ```bash diff --git a/docs-site/src/content/docs/ko/contributing.md b/docs-site/src/content/docs/ko/contributing.md index 24642bdf81e..d52df980285 100644 --- a/docs-site/src/content/docs/ko/contributing.md +++ b/docs-site/src/content/docs/ko/contributing.md @@ -3,6 +3,9 @@ title: 기여하기 description: opencodex 개발 환경, 구조, 컨벤션, 프로바이더와 어댑터 추가 방법. --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## 설정 ```bash diff --git a/docs-site/src/content/docs/ru/contributing.md b/docs-site/src/content/docs/ru/contributing.md index b926b32e04b..0d8c6204b2f 100644 --- a/docs-site/src/content/docs/ru/contributing.md +++ b/docs-site/src/content/docs/ru/contributing.md @@ -3,6 +3,9 @@ title: Участие в разработке description: Разработка opencodex — настройка окружения, структура, конвенции и добавление провайдера или адаптера. --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## Настройка окружения ```bash diff --git a/docs-site/src/content/docs/tr/contributing.md b/docs-site/src/content/docs/tr/contributing.md index 66eb9293b94..82079c29f5a 100644 --- a/docs-site/src/content/docs/tr/contributing.md +++ b/docs-site/src/content/docs/tr/contributing.md @@ -3,6 +3,9 @@ title: Katkıda Bulunma description: opencodex geliştirme — kurulum, düzen, kurallar ve yeni bir sağlayıcı veya adaptör ekleme. --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## Kurulum Kaynak kod üzerinde geliştirme yapmak için `PATH` ortam değişkeninizde `bun` CLI diff --git a/docs-site/src/content/docs/zh-cn/contributing.md b/docs-site/src/content/docs/zh-cn/contributing.md index 7adccef6918..ac85e16fcbf 100644 --- a/docs-site/src/content/docs/zh-cn/contributing.md +++ b/docs-site/src/content/docs/zh-cn/contributing.md @@ -3,6 +3,9 @@ title: 贡献指南 description: opencodex 的开发环境、结构、约定，以及添加 provider 或 adapter 的方法。 --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## 环境搭建 ```bash diff --git a/docs-site/src/content/docs/zh-tw/contributing.md b/docs-site/src/content/docs/zh-tw/contributing.md index 97880fe4f28..a1688a38491 100644 --- a/docs-site/src/content/docs/zh-tw/contributing.md +++ b/docs-site/src/content/docs/zh-tw/contributing.md @@ -3,6 +3,9 @@ title: 貢獻指南 description: opencodex 的開發環境、結構、約定，以及新增 provider 或 adapter 的方法。 --- +For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. + + ## 環境搭建 ```bash From 2d31bec28858cf5863ceb89830cb6d0f0e33e367 Mon Sep 17 00:00:00 2001 From: mashfromband Date: Mon, 12 Oct 2026 13:46:44 +0900 Subject: [PATCH 2/3] docs: remove residual maintainer handoff and clarify Japanese guidance --- AGENTS.md | 21 ++++++++----------- docs-site/src/content/docs/ja/contributing.md | 2 +- 2 files changed, 10 insertions(+), 13 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 758c93458e5..bfff4968e7a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -339,20 +339,17 @@ and asks the author to test and tick the boxes again against the latest code. Before a completion is accepted, the gate verifies the checklist claims it can check itself: the branch must be on the latest `dev` commit or at most 10 commits behind it, and Codex/CodeRabbit findings must be resolved. The -local-CI box is an author attestation only — fork contributors cannot start -repository CI; a maintainer has to — so the gate never disproves it; a new +local-CI box is an author attestation only — contributors without repository permission cannot start +repository CI; the AI assignee with the required fork permission starts it — so the gate never disproves it; a new push still resets every box. A disproved claim unticks the matching box and keeps the PR a draft. -Authors with repository push permission skip the ancestry heuristic only. As with approval requirements in -[`MAINTAINERS.md`](./MAINTAINERS.md), the ancestry heuristic is a CI check -rather than a branch rule. The branches themselves are protected: `dev`, -`main`, and `preview` each require a pull request and block force-pushes and deletion. -For `dev` only, a current maintainer with GitHub `maintain` or `admin` access may -explicitly integrate through a PR without another maintainer approval, including -their own PR, under the policy in `MAINTAINERS.md`. Record the decision and exact-head -CI evidence; keep outstanding maintainer objections and security review separate. -The bypass is PR-only, so a direct push to `dev` remains rejected regardless of -`--no-verify`. Contributor review and `main`/`preview` rules remain unchanged. +In this mashfromband fork, the AI assignee completes independent model review, +resolves Must findings, verifies successful required CI for the exact final head, +and integrates the PR under MAINTAINERS.md. Integration targets `dev`; authorized +release/preview promotions retain their technical and security gates. Human +maintainer approval and upstream rosters apply only upstream. Inspect this fork's +actual GitHub rules and permissions rather than assuming upstream protection is +inherited; do not weaken configured checks or bypass an execution rejection. [`MAINTAINERS.md`](./MAINTAINERS.md) is authoritative for review and merge policy (approvals, CI requirements, security review, promotion). This file diff --git a/docs-site/src/content/docs/ja/contributing.md b/docs-site/src/content/docs/ja/contributing.md index 67f05eb3bd2..0c804cf2040 100644 --- a/docs-site/src/content/docs/ja/contributing.md +++ b/docs-site/src/content/docs/ja/contributing.md @@ -3,7 +3,7 @@ title: コントリビュート description: opencodex の開発環境、構成、規約、プロバイダーとアダプターの追加方法。 --- -For work in the mashfromband fork, use its [AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) and [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md). The fork's 2026-10-12 owner directive replaces general human approval and operational handoff; AI assignees complete independent review, exact-head checks, merge and existing-production reflection. Upstream roster, permissions and contribution requirements in this guide apply only upstream. Customer-specific human review contracts remain in force. +この mashfromband フォークの開発では、[AGENTS.md](https://github.com/mashfromband/opencodex/blob/dev/AGENTS.md) と [MAINTAINERS.md](https://github.com/mashfromband/opencodex/blob/dev/MAINTAINERS.md) に従います。2026-10-12のオーナー指示により、AI担当が別モデルレビュー・同じ最終HEADの検査・マージ・必要な既存Prd反映まで行います。このガイドの上流担当者・権限・人による一般的な承認要件は上流だけに適用します。顧客固有の人によるレビュー契約は維持します。 ## セットアップ From ebfe59d4e615f1add54fc5b8d6c169fcf8290c36 Mon Sep 17 00:00:00 2001 From: mashfromband Date: Mon, 12 Oct 2026 13:59:36 +0900 Subject: [PATCH 3/3] docs: assign CI startup consistently to authorized AI assignees --- MAINTAINERS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index e6ffed7a675..0add12cfe26 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -46,8 +46,8 @@ when a maintainer steps down. Before a completion is accepted, the gate verifies the checklist claims it can check itself: the branch must be on the latest `dev` commit or at most 10 commits behind it, and Codex/CodeRabbit findings must be resolved. - The local-CI box is an author attestation only — fork contributors cannot - start repository CI; a maintainer has to — so the gate never disproves it; + The local-CI box is an author attestation only — contributors without repository permission cannot + start repository CI; the AI assignee with the required fork permission starts it — so the gate never disproves it; a new push still resets every box. A disproved claim unticks the matching box and keeps the PR a draft. Authors with repository push permission skip the ancestry heuristic only. As