@yemi33/minions 0.1.1978 → 0.1.1980

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/docs/distribution.md +8 -10
  2. package/package.json +1 -1
package/docs/distribution.md CHANGED
@@ -1,33 +1,31 @@
1
1
  # Distribution & Publishing
2
2
 
3
- Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized package boundary. The source lives across three GitHub remotes, with a strict one-way port direction (see [Three-Remote Topology](#three-remote-topology)).
3
+ Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized package boundary. The source lives across two GitHub remotes, with a strict one-way port direction (see [Two-Remote Topology](#two-remote-topology)).
4
4
 
5
- ## Three-Remote Topology
5
+ ## Two-Remote Topology
6
6
 
7
7
  | Remote (local name on `D:/squad`) | URL | Role |
8
8
  |-----------------------------------|-----|------|
9
- | `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 mirrors. |
10
- | `emu` | `https://github.com/yemishin_microsoft/minions` | Microsoft-identity mirror of `yemi33/minions`. Automated via `.github/workflows/mirror-to-emu.yml`. |
9
+ | `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. |
11
10
  | `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). |
12
11
 
13
12
  ### Port direction
14
13
 
15
- **Strictly one-way: `yemi33` → `emu`, `yemi33` → `opg`.**
14
+ **Strictly one-way: `yemi33` → `opg`.**
16
15
 
17
- - **Do NOT port from `emu` or `opg` back into `yemi33`.** Their `main` branches may carry org-specific compliance content (`.github/policies/*`, `.github/acl/*`, `.github/compliance/*`, JIT access policy, internal access lists, MS-org issue templates) that has no business in the personal-fork authoring source.
16
+ - **Do NOT port from `opg` back into `yemi33`.** Its `main` branch may carry org-specific compliance content (`.github/policies/*`, `.github/acl/*`, `.github/compliance/*`, JIT access policy, internal access lists, MS-org issue templates) that has no business in the personal-fork authoring source.
18
17
  - **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.
19
- - Other teams (Microsoft infra, compliance review) may also push to `opg-microsoft/minions` directly. Treat its `main` as potentially ahead of `yemi33`/`emu` on policy files.
18
+ - 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.
20
19
 
21
- ### Why opg can't use the same direct-mirror pattern as emu
20
+ ### Why opg uses a sync-branch + reviewed-PR pattern
22
21
 
23
- `mirror-to-emu.yml` does `git push emu HEAD:master` — direct overwrite, because `emu/master` is meant to be a 1:1 reflection of `yemi33/master`. `opg-microsoft/minions` is different: its `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.
22
+ `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.
24
23
 
25
24
  ### Required secrets on `yemi33/minions`
26
25
 
27
26
  | Secret | Purpose | Workflow |
28
27
  |--------|---------|----------|
29
28
  | `NPM_TOKEN` | npm publish | `publish.yml` |
30
- | `EMU_PUSH_TOKEN` | Push to `yemishin_microsoft/minions` | `mirror-to-emu.yml` |
31
29
  | `EMU_PACKAGES_TOKEN` | Publish to `@yemishin_microsoft` internal registry | `publish-internal-github-packages.yml` |
32
30
  | `OPG_PUSH_TOKEN` | Push to `opg-microsoft/minions` sync branch | `mirror-to-opg.yml` |
33
31
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@yemi33/minions",
3
- "version": "0.1.1978",
3
+ "version": "0.1.1980",
4
4
  "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
5
5
  "bin": {
6
6
  "minions": "bin/minions.js"