@yemi33/minions 0.1.2159 → 0.1.2160

package/docs/distribution.md

@@ -7,7 +7,7 @@ Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized pa
 | Remote (local name on `D:/squad`) | URL | Role |
 |-----------------------------------|-----|------|
 | `origin` | `https://github.com/yemi33/minions` | **Authoring source of truth.** All normal code changes (engine, dashboard, playbooks, agents, etc.) land here first. Triggers npm publish + downstream mirror. |
-| `opg` | `https://github.com/opg-microsoft/minions` | **Compliant store** under the `opg-microsoft` org. Automated mirror to a sync branch via `.github/workflows/mirror-to-opg.yml`; `main` is reconciled by a maintainer PR because it carries enterprise/compliance-only commits (see below). |
+| `opg` | `https://github.com/opg-microsoft/minions` | **Enterprise/compliance flavor.** Carries opg-only commits (compliance files, enterprise workflows). Sync from yemi33 is a manual cherry-pick PR onto `opg/main`; opg → yemi33 backports are handled by `backport-to-yemi33.yml` running on opg. |
 
 ### Port direction
 
@@ -17,9 +17,9 @@ Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized pa
 - **Direct pushes to `opg-microsoft/minions` are allowed for enterprise/compliance-specific changes only.** Examples: editing `.github/policies/jit.yml`, updating `.github/acl/access.yml`, modifying `.github/compliance/inventory.yml`. These changes stay on `opg` and are not backported.
 - Other teams (Microsoft infra, compliance review) may also push to `opg-microsoft/minions` directly. Treat its `main` as potentially ahead of `yemi33` on policy files.
 
-### Why opg uses a sync-branch + reviewed-PR pattern
+### Why opg uses a manual sync-PR pattern
 
-`opg-microsoft/minions`'s `main` carries enterprise-only commits that don't exist on `yemi33/master`, so a force-push to `opg/main` would destroy them. Instead, `mirror-to-opg.yml` force-pushes `yemi33/master` to `opg/sync/yemi33-master` (a dedicated bot-owned branch), and a maintainer opens or updates a PR from `sync/yemi33-master` → `main` for review. The first such PR uses `--allow-unrelated-histories` to bridge the initial divergence; subsequent ones merge incrementally.
+The two repos are peers. To bring yemi33 changes onto `opg/main`, a maintainer opens a manual sync PR (cherry-picking the commits needed; example: PR #96). To bring opg changes onto `yemi33/master`, the opg-side `backport-to-yemi33.yml` workflow files PRs against `yemi33/master`. Neither direction is automatic — drift between the two repos is expected and reconciled on demand.
 
 ### Required secrets on `yemi33/minions`
 
@@ -27,9 +27,8 @@ Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized pa
 |--------|---------|----------|
 | `NPM_TOKEN` | npm publish | `publish.yml` |
 | `EMU_PACKAGES_TOKEN` | Publish to `@yemishin_microsoft` internal registry | `publish-internal-github-packages.yml` |
-| `OPG_PUSH_TOKEN` | Push to `opg-microsoft/minions` sync branch | `mirror-to-opg.yml` |
 
-Each mirror workflow gracefully skips with a warning if its token secret is unset, so unconfigured downstreams never block the primary publish path.
+Each downstream publish workflow gracefully skips with a warning if its token secret is unset, so unconfigured downstreams never block the primary publish path.
 
 ## Distribution Boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.2159",
+  "version": "0.1.2160",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"