@mutmutco/pi-plugin 4.6.35 → 4.6.36
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.
package/package.json
CHANGED
|
@@ -2,4 +2,7 @@
|
|
|
2
2
|
## MMI developer environment
|
|
3
3
|
|
|
4
4
|
Use the [canonical MMI developer-environment guide](https://github.com/mutmutco/MMI-Hub/blob/main/docs/Architecture/agentic-dev-environment.md) for shared setup and daily agent work.
|
|
5
|
+
|
|
6
|
+
Daily loop: `mmi-cli oracle issue create` → `mmi-cli oracle board claim <n>` (stamps the mmi-claim lease) → `mmi-cli devops pr create` → `mmi-cli devops pr land <pr>`.
|
|
7
|
+
Any org member with repository write (developer) or repository admin (project admin) can run it, with no vault access; release trains stay org-owner only.
|
|
5
8
|
<!-- mmi-developer-environment:end -->
|
|
@@ -6,5 +6,9 @@
|
|
|
6
6
|
"scripts/next-version.mjs": {
|
|
7
7
|
"blob": "2c1985b59edc779695479559074e7654c1574a11",
|
|
8
8
|
"reason": "comment-only note that rc/release modes are unused in dev-only MM suite repos (#8282), no runtime or operator behaviour change"
|
|
9
|
+
},
|
|
10
|
+
"README.md": {
|
|
11
|
+
"blob": "768c5e35cdb48849c77bce6b334658adefe6a5d8",
|
|
12
|
+
"reason": "the developer-environment seed block now states the concrete mmi-cli loop (issue create, board claim, PR create, PR land) and who may run it — the README propagation is intended (#9987); no runbook step changes"
|
|
9
13
|
}
|
|
10
14
|
}
|
|
@@ -13,6 +13,23 @@ our self-hosted runners, dispatched by an org owner, never on a workstation (#91
|
|
|
13
13
|
A 503 `github-rate-limited` answer means the org App's hourly GitHub allowance is used up. It is
|
|
14
14
|
not a denial: wait for the reset time it names, then retry.
|
|
15
15
|
|
|
16
|
+
## Developer and project-admin access
|
|
17
|
+
|
|
18
|
+
A developer is an org member with GitHub write on a product repository. A project admin is that
|
|
19
|
+
repository's admin. Both run the full loop with mmi-cli and need no MMI-Hub vault access:
|
|
20
|
+
|
|
21
|
+
```sh
|
|
22
|
+
mmi-cli oracle issue create --title "<title>" --body-file <path> # files and attaches the board card
|
|
23
|
+
mmi-cli oracle board claim <n> # stamps the mmi-claim lease
|
|
24
|
+
mmi-cli devops pr create --title "<title>" --base development
|
|
25
|
+
mmi-cli devops pr land <pr-number>
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
Board writes (attach, claim stamp, status move) gate on org owner, repo admin or repository write, so
|
|
29
|
+
these roles pass. Where the GitHub App route is absent the writes go as the person's own GitHub login
|
|
30
|
+
(one note says so); an agent host with the App route writes as the App. MMI-Hub's own merges and all
|
|
31
|
+
release trains stay org-owner only.
|
|
32
|
+
|
|
16
33
|
Start with `mmi-cli onboard` and the [board skill](../../board/SKILL.md).
|
|
17
34
|
Reading or discussing the board is read-only until the developer authorizes work.
|
|
18
35
|
Claim approved work with `mmi-cli oracle board claim <issue>`, then prepare an isolated task
|