chore: bootstrap mirus-tech agent workflow policy #10

Merged
jmz merged 2 commits from maximus/chore/policy-bootstrap into main 2026-05-03 15:28:21 +00:00
Owner

Bootstraps the Mirus Tech multi-agent workflow policy in this repo.

Summary

  • Adds docs/AGENT_WORKFLOW.md (canonical policy doc)
  • Adds .forgejo/PULL_REQUEST_TEMPLATE.md and .forgejo/ISSUE_TEMPLATE/*
  • Adds .forgejo/workflows/check.yml (CI scaffold)

User impact

New contributors and agents see the policy on the repo page; PR + issue templates are pre-populated; CI gate exists for self-merge.

Verification

Generated by ensure-repo-policy.py. Idempotent.

Refs /srv/mirus/AGENT_WORKFLOW.md (canonical source).

Bootstraps the Mirus Tech multi-agent workflow policy in this repo. ## Summary - Adds `docs/AGENT_WORKFLOW.md` (canonical policy doc) - Adds `.forgejo/PULL_REQUEST_TEMPLATE.md` and `.forgejo/ISSUE_TEMPLATE/*` - Adds `.forgejo/workflows/check.yml` (CI scaffold) ## User impact New contributors and agents see the policy on the repo page; PR + issue templates are pre-populated; CI gate exists for self-merge. ## Verification Generated by `ensure-repo-policy.py`. Idempotent. ## Related Refs `/srv/mirus/AGENT_WORKFLOW.md` (canonical source).
chore: bootstrap mirus-tech agent workflow policy
Some checks failed
check / check (pull_request) Failing after 12s
8fb41200b8
Adds docs/AGENT_WORKFLOW.md, PR + issue templates, and CI scaffold (if absent).
Generated by ensure-repo-policy.py.
ci: use generic CI scaffold (rust toolchain version mismatch)
All checks were successful
check / check (pull_request) Successful in 1s
check / check (push) Successful in 2s
62c31f22f9
The strict rust scaffold's `cargo check --all` fails on the runner because
its rustc is 1.85.0 (system-installed) while matrix-sdk@0.14.0 requires
1.88+. Project-MSRV vs runner-toolchain alignment is a separate fix; for
now use the generic scaffold so the policy gate fires correctly without
blocking the bootstrap.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
jmz merged commit 62c31f22f9 into main 2026-05-03 15:28:21 +00:00
Author
Owner

Summary

Bootstrap of mirus-tech multi-agent workflow policy on this repo. First non-self enrollment after jmz/mirus-tools dog-foodings.

Changes (as merged)

  • docs/AGENT_WORKFLOW.md (canonical policy reference)
  • .forgejo/PULL_REQUEST_TEMPLATE.md
  • .forgejo/ISSUE_TEMPLATE/{bug,feature,plan}.md
  • .forgejo/workflows/check.yml (generic CI scaffold; project-specific Rust CI deferred — runner has rustc 1.85.0 but matrix-sdk@0.14.0 requires 1.88+, separate fix)

User impact

  • Branch protection enforced: FF-only merges, no direct push, required check / check (pull_request) status, block-on-outdated-branch.
  • Repo-level merge config locked: only fast-forward-only merges allowed (allow_merge_commits/rebase/squash all disabled).
  • 17 standard labels provisioned (type:, priority:, status:, agent:).
  • PR + issue templates pre-fill the closing-comment / bug / feature / plan structures.

Verification

  • ensure-repo-policy.py --check jmz/matrix-bridge returns OK on 11/11 checks.
  • This PR's CI green via the generic scaffold (1s); FF-merge succeeded with required-status-check enforced.

Follow-up

  • Replace generic CI with a Rust-aware workflow once the runner toolchain is updated to >= 1.88. Probably a dtolnay/rust-toolchain@1.88.0 action plus cargo check --all + cargo test --all in a follow-up PR.
  • Refs jmz/mirus-tools (the canonical policy + tooling source).
  • Refs the runner rescaling / instance-scope debug session that preceded this enrollment.
## Summary Bootstrap of mirus-tech multi-agent workflow policy on this repo. First non-self enrollment after jmz/mirus-tools dog-foodings. ## Changes (as merged) - docs/AGENT_WORKFLOW.md (canonical policy reference) - .forgejo/PULL_REQUEST_TEMPLATE.md - .forgejo/ISSUE_TEMPLATE/{bug,feature,plan}.md - .forgejo/workflows/check.yml (generic CI scaffold; project-specific Rust CI deferred — runner has rustc 1.85.0 but matrix-sdk@0.14.0 requires 1.88+, separate fix) ## User impact - Branch protection enforced: FF-only merges, no direct push, required `check / check (pull_request)` status, block-on-outdated-branch. - Repo-level merge config locked: only fast-forward-only merges allowed (allow_merge_commits/rebase/squash all disabled). - 17 standard labels provisioned (type:*, priority:*, status:*, agent:*). - PR + issue templates pre-fill the closing-comment / bug / feature / plan structures. ## Verification - `ensure-repo-policy.py --check jmz/matrix-bridge` returns OK on 11/11 checks. - This PR's CI green via the generic scaffold (1s); FF-merge succeeded with required-status-check enforced. ## Follow-up - Replace generic CI with a Rust-aware workflow once the runner toolchain is updated to >= 1.88. Probably a `dtolnay/rust-toolchain@1.88.0` action plus `cargo check --all` + `cargo test --all` in a follow-up PR. ## Related - Refs jmz/mirus-tools (the canonical policy + tooling source). - Refs the runner rescaling / instance-scope debug session that preceded this enrollment.
Sign in to join this conversation.
No description provided.