@mutmutco/codex-plugin 4.5.43 → 4.5.44

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 (4) hide show
  1. package/.codex-plugin/plugin.json +1 -1
  2. package/package.json +1 -1
  3. package/skills/bootstrap/SKILL.md +6 -1
  4. package/skills/bootstrap/seeds/gate.template.yml +2 -2
package/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mmi",
3
- "version": "4.5.43",
3
+ "version": "4.5.44",
4
4
  "mmiCompat": "4.x",
5
5
  "description": "MMI workflow skills and org gates delivery.",
6
6
  "author": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/codex-plugin",
3
- "version": "4.5.43",
3
+ "version": "4.5.44",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
package/skills/bootstrap/SKILL.md CHANGED
@@ -376,7 +376,12 @@ collaborator list + the per-branch allowlist are the record — no separate rost
376
376
  under the org **wall-clock budget** (#3178): the render pins `run-with-budget` to the CLI's blessed SHA
377
377
  with `--var GATE_MAX_SECONDS=` (300s onboarding default — tighten once the gate is measured, via
378
378
  `--var` or `org project set <repo> --var gate={"maxSeconds":N}`); `ci audit` and the release train
379
- both enforce the step, so do not remove it. Every trigger runs the full `GATE_CMD`. `bootstrap apply --execute` installs that JSON as the
379
+ both enforce the step, so do not remove it. Every trigger runs the full `GATE_CMD`. A repo whose checks
380
+ need a service container or an extra budgeted step declares them in its registry gate config, never by
381
+ hand-editing the rendered gate (#7407): `gate.services` is keyed by service name with `image`, `env`,
382
+ `ports`, one-line `options` and `tmpfs` paths; `gate.steps` is a list of `{name, command, env,
383
+ maxSeconds}` run after the main check under the same budget wrapper. Invalid declarations fail the
384
+ render by field name; a repo that declares neither renders exactly as before. `bootstrap apply --execute` installs that JSON as the
380
385
  repository ruleset itself (#6070) and reports one `product-ruleset` row: `PARK` (the gate file is not on
381
386
  the base branch yet — installed disabled), `WAIT` (the gate exists but has not emitted a proven-green
382
387
  `gate` context — kept disabled; re-run apply after the gate passes), `ACTIVATE` (gate green — enforcement
package/skills/bootstrap/seeds/gate.template.yml CHANGED
@@ -57,7 +57,7 @@ jobs:
57
57
  if: ${{ github.event_name != 'push' || github.ref_name == '{{GATE_FULL_RUN_BRANCH}}' || github.ref_name == 'main' || github.ref_type == 'tag' }}
58
58
  runs-on: [self-hosted, linux, x64, mmi-live]
59
59
  defaults:
60
- run: { working-directory: {{GATE_WORKDIR}} }
60
+ run: { working-directory: {{GATE_WORKDIR}} }{{GATE_SERVICES_YAML}}
61
61
  steps:
62
62
  - uses: mutmutco/MMI-Hub/.github/actions/runner-checkout@{{GATE_RUNNER_SHA}}
63
63
  with:
@@ -123,4 +123,4 @@ jobs:
123
123
  with:
124
124
  command: {{GATE_CMD}}
125
125
  max-seconds: {{GATE_MAX_SECONDS}}
126
- working-directory: {{GATE_WORKDIR}}
126
+ working-directory: {{GATE_WORKDIR}}{{GATE_EXTRA_STEPS_YAML}}