mb-run 0.0.3 → 0.0.4-dev-20260708-2b76926

package/CHANGELOG.md

@@ -21,6 +21,18 @@ If you like this project and find it useful, please consider giving it a star on
 
 <a href="https://www.buymeacoffee.com/luligugithub"><img src="https://matterbridge.io/assets/bmc-button.svg" alt="Buy me a coffee" width="120"></a>
 
+## [0.0.4] - Dev branch
+
+### Changed
+
+- [package]: Update agents instructions.
+- [package]: Update dependencies.
+- [package]: Upgrade package.
+- [codex]: Update codex configuration.
+- [vscode]: Update vscode extensions.
+
+<a href="https://www.buymeacoffee.com/luligugithub"><img src="https://matterbridge.io/assets/bmc-button.svg" alt="Buy me a coffee" width="80"></a>
+
 ## [0.0.3] - 2026-07-06
 
 ### Added

package/dist/upgrade.js

@@ -27,7 +27,7 @@ export async function runUpgrade(opts) {
     for (const pkgPath of workspacePackageJsonPaths) {
         dstDir = path.dirname(pkgPath);
         const pkgJson = await parsePackageJson(dstDir);
-        await runPackageJsonUpgrade(opts, dstDir, pkgJson, false, true, false, false);
+        await runPackageJsonUpgrade(opts, path.join(dstDir, 'package.json'), pkgJson, false, true, false, false);
     }
     if (commandFailures.length > 0) {
         log(`${red('Failed commands:')}${reset()}\n${inspect(commandFailures, false, 2, true)}`);
@@ -343,8 +343,10 @@ export async function runPackageJsonUpgrade(opts, pkgPath, pkgJson, isMonorepo =
     fileReplace('CHANGELOG.md', '(https://github.com/prettier/prettier)', '(https://prettier.io/)');
     fileReplace('CHANGELOG.md', '(https://github.com/eslint/eslint)', '(https://eslint.org/)');
     fileReplace('CHANGELOG.md', '(https://nodejs.org/api/esm.html)', '(https://nodejs.org/)');
-    if (isMonorepo)
+    if (isMonorepo) {
+        log(magenta('Monorepo detected, skipping script setup for the root package.json.'));
         return;
+    }
     const scripts = pkgJson.scripts;
     const startScript = scripts?.start ?? `node ${pkgJson.main ?? 'dist/module.js'}`;
     log(magenta(`Start script: ${cyan(startScript)}`));
@@ -478,13 +480,19 @@ export async function runPackageJsonUpgrade(opts, pkgPath, pkgJson, isMonorepo =
     delete devDeps?.['@vitest/eslint-plugin'];
     delete devDeps?.['esbuild'];
     delete devDeps?.['javascript-obfuscator'];
+    log(magenta(`Changing package.json "${pkgPath}" scripts and devDependencies...`));
     const packageJson = JSON.parse(readFileSync(pkgPath, 'utf8'));
     writeFileSync(pkgPath, JSON.stringify({
         ...packageJson,
         scripts: pkgJson.scripts,
         devDependencies: pkgJson.devDependencies,
     }, null, 2) + '\n', 'utf8');
+    log(magenta(`Emptying node_modules "${dstDir}"...`));
     await emptyDir('node_modules', { rootDir: dstDir, dryRun: false });
+    if (isWorkspace) {
+        log(magenta('Monorepo workspace detected, skipping install dependencies...'));
+        return;
+    }
     log(green('Installing devDependencies...'));
     const commands = [
         `npm pkg delete overrides`,

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "mb-run",
-  "version": "0.0.3",
+  "version": "0.0.4-dev-20260708-2b76926",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "mb-run",
-      "version": "0.0.3",
+      "version": "0.0.4-dev-20260708-2b76926",
       "license": "Apache-2.0",
       "dependencies": {
         "cross-spawn": "7.0.6",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mb-run",
-  "version": "0.0.3",
+  "version": "0.0.4-dev-20260708-2b76926",
   "description": "Matterbridge command line executor",
   "author": "https://github.com/Luligu",
   "license": "Apache-2.0",

package/vendor/.agents/matterbridge.md

@@ -1,4 +1,4 @@
-# Matterbridge Endpoint Guide
+# Matterbridge Endpoint Guide (v.1.0.0)
 
 Use this guide when writing Matterbridge code in this repository or when authoring a plugin that consumes Matterbridge.
 
@@ -299,7 +299,7 @@ For most plugins, follow this order:
 2. Create the endpoint or single-class device.
 3. Set device identity with one of the Basic Information helpers if you are using a raw `MatterbridgeEndpoint`.
 4. Add explicit cluster servers you need.
-5. Call `addRequiredClusterServers()` last.
+5. Call `addRequiredClusters()` last.
 6. Register the device with `await this.registerDevice(device)`.
 7. Optionally add UI metadata with `setSelectDevice()` and `setSelectEntity()`.
 

package/vendor/.agents/testing.md

@@ -1,4 +1,4 @@
-# Testing Standards for Unit Tests
+# Testing Standards for Unit Tests (v.1.0.0)
 
 ## 1. Test Framework
 
@@ -7,12 +7,12 @@
 - Bun test is available in the repository when the file `bunfig.toml` exists.
 - Jest tests live in `test` folders. Follow the existing convention in the repository for test file placement.
 - Vitest tests live in `vitest` folders. Follow the existing convention in the repository for test file placement.
-- Bun test tests live in `buntest` folders. Follow the existing convention in the repository for test file placement.
+- Bun tests live in `buntest` folders. Follow the existing convention in the repository for test file placement.
 - Ensure that tests are written in TypeScript and follow the ESM module format.
 
 ## 2. Test Structure
 
-- Organize tests in file name `*.test.ts` in the `test`, `vitest`, or `buntest` folders.
+- Organize tests in file named `*.test.ts` in the `test`, `vitest`, or `buntest` folders.
 - Use `describe` blocks to group related tests and `test` blocks for individual test cases.
 
 ## 3. Test Naming

package/vendor/.codex/config.toml

@@ -1,23 +1,25 @@
-# Codex config v. 1.0.1
+# Codex config v.1.0.2
 
 approval_policy = "on-request"
 approvals_reviewer = "user"
-default_permissions = "matterbridge_safe"
+
 web_search = "live"
 
+default_permissions = "matterbridge_safe"
+
 [shell_environment_policy]
 inherit = "core"
 
 [windows]
 sandbox = "elevated"
 
-[permissions.matterbridge_safe.network]
-enabled = false
-
 [permissions.matterbridge_safe]
 description = "Workspace access with sensitive files denied and network disabled."
 extends = ":workspace"
 
+[permissions.matterbridge_safe.network]
+enabled = false
+
 [permissions.matterbridge_safe.filesystem]
 glob_scan_max_depth = 4
 

package/vendor/.codex/rules/default.rules

@@ -1,4 +1,4 @@
-# Codex rules v. 1.0.1
+# Codex rules v.1.0.1
 
 # Git mutations
 prefix_rule(pattern = ["git", "pull"], decision = "forbidden", justification = "Do not change local refs without explicit manual control.")

package/vendor/.github/copilot-instructions.md

@@ -1,17 +1,34 @@
-# Matterbridge Workspace Instructions (v.1.0.1)
+# Matterbridge Workspace Instructions (v.1.0.2)
+
+## Style And Formatting
 
 - Follow [STYLEGUIDE.md](../STYLEGUIDE.md) for code style, naming, JSDoc, validation, logging, and formatting expectations.
 - JSDoc requirements are enforced by the configured linter. Treat missing or incomplete JSDoc on required APIs as a real lint issue, not optional documentation.
 - Import and export ordering are enforced by the formatter. Preserve the existing grouped and sorted order unless a change requires updating it.
 - Formatting is enforced by oxfmt. Follow the existing formatting and do not fight the formatter.
+
+## Scope And Safety
+
 - Keep changes minimal and scoped to the request. Avoid unrelated refactors or broad cleanup.
 - Do not modify production code only to make a test pass. If a failing test points to a likely source issue, explain the issue and change behavior only when required by the task.
 - Preserve cross-platform behavior. Changes must work on Windows, macOS, and Linux, especially for paths, shell commands, environment variables, and networking behavior.
 - Maintain compatibility with the supported Node.js versions in this repository: 20.19, 22.13, 24.0, and 26.0.
+
+## Project Architecture
+
 - This repository uses TypeScript and ESM. Follow existing project patterns for imports, exports, build configuration, and test setup.
+
+## Testing And Validation
+
 - Prefer the existing npm scripts in [package.json](../package.json) and the VS Code tasks in [tasks.json](../.vscode/tasks.json) for building, linting, and testing.
 - Keep tests deterministic and simple. Prefer small data sets and straightforward setup.
 - Some tests are intentionally multi-step flows. State may persist across successive steps within a single test flow, but each test unit must remain isolated from other tests.
 - For validation, run the relevant full test file or the matching suite/task for the touched area rather than assuming arbitrary isolated single-test execution is reliable.
+
+## Documentation
+
 - When behavior changes, update the relevant tests and documentation.
+
+## Additional Agent Guidance
+
 - Use dedicated instruction files under [.github/instructions](instructions/) when a rule applies only to specific file types or workflows.

package/vendor/.github-plugin/copilot-instructions.md

@@ -1,17 +1,34 @@
-# Matterbridge Workspace Instructions (v.1.0.1)
+# Matterbridge Workspace Instructions (v.1.0.2)
+
+## Style And Formatting
 
 - Follow [STYLEGUIDE.md](../STYLEGUIDE.md) for code style, naming, JSDoc, validation, logging, and formatting expectations.
 - JSDoc requirements are enforced by the configured linter. Treat missing or incomplete JSDoc on required APIs as a real lint issue, not optional documentation.
 - Import and export ordering are enforced by the formatter. Preserve the existing grouped and sorted order unless a change requires updating it.
 - Formatting is enforced by oxfmt. Follow the existing formatting and do not fight the formatter.
+
+## Scope And Safety
+
 - Keep changes minimal and scoped to the request. Avoid unrelated refactors or broad cleanup.
 - Do not modify production code only to make a test pass. If a failing test points to a likely source issue, explain the issue and change behavior only when required by the task.
 - Preserve cross-platform behavior. Changes must work on Windows, macOS, and Linux, especially for paths, shell commands, environment variables, and networking behavior.
 - Maintain compatibility with the supported Node.js versions in this repository: 20, 22, 24, and 26.
+
+## Project Architecture
+
 - This repository uses TypeScript and ESM. Follow existing project patterns for imports, exports, build configuration, and test setup.
+
+## Testing And Validation
+
 - Prefer the existing npm scripts in [package.json](../package.json) and the VS Code tasks in [tasks.json](../.vscode/tasks.json) for building, linting, and testing.
 - Keep tests deterministic and simple. Prefer small data sets and straightforward setup.
 - Some tests are intentionally multi-step flows. State may persist across successive steps within a single test flow, but each test unit must remain isolated from other tests.
 - For validation, run the relevant full test file or the matching suite/task for the touched area rather than assuming arbitrary isolated single-test execution is reliable.
+
+## Documentation
+
 - When behavior changes, update the relevant tests and documentation.
+
+## Additional Agent Guidance
+
 - Use dedicated instruction files under [.github/instructions](instructions/) when a rule applies only to specific file types or workflows.

package/vendor/.vscode/extensions.native.json

@@ -1,10 +1,9 @@
-// VS Code extensions native v. 1.0.4
+// VS Code extensions native v. 1.0.5
 {
   "recommendations": [
     "typescriptteam.native-preview",
     "oxc.oxc-vscode",
     "vitest.explorer",
-    "firsttris.vscode-jest-runner",
     "ms-azuretools.vscode-containers",
     "anthropic.claude-code",
     "github.copilot-chat",
@@ -12,5 +11,5 @@
     "github.vscode-pull-request-github",
     "openai.chatgpt"
   ],
-  "unwantedRecommendations": ["dbaeumer.vscode-eslint", "esbenp.prettier-vscode"]
+  "unwantedRecommendations": ["dbaeumer.vscode-eslint", "esbenp.prettier-vscode", "firsttris.vscode-jest-runner"]
 }

package/vendor/AGENTS.md

@@ -1,10 +1,10 @@
-# Matterbridge Agents Instructions (v.1.0.0)
+# Matterbridge Agents Instructions (v.1.0.2)
 
 ## Style And Formatting
 
 - Follow [STYLEGUIDE.md](./STYLEGUIDE.md) for code style, naming, JSDoc, validation, logging, and formatting expectations.
 - JSDoc requirements are enforced by the linter. Treat missing or incomplete JSDoc on required APIs as a real lint issue, not optional documentation.
-- Import and export ordering are enforced by the linter or by theformater. Preserve the existing grouped and sorted order unless a change requires updating it.
+- Import and export ordering are enforced by the linter or by the formatter. Preserve the existing grouped and sorted order unless a change requires updating it.
 - Follow the existing formatting and do not fight the formatter.
 
 ## Scope And Safety
@@ -27,11 +27,11 @@
 
 ## Documentation
 
-- When behavior changes, update the relevant tests and documentation.
+- When behavior changes, update the relevant tests and documentation in the README.md files.
 
 ## Additional Agent Guidance
 
-For task-specific guidance, read relevant files in `.agents/`:
+For task-specific guidance, read relevant files in [.agents](./.agents/):
 
-- `.agents/testing.md` for testing and validation expectations
-- `.agents/matterbridge.md` for instruction about using matterbridge in a plugin
+- `.agents/testing.md` for testing and validation expectations;
+- `.agents/matterbridge.md` for instruction about using matterbridge in a plugin.

package/vendor/CLAUDE.md

@@ -1,17 +1,34 @@
-# Matterbridge Claude Instructions (v.1.0.1)
+# Matterbridge Claude Instructions (v.1.0.2)
+
+## Style And Formatting
 
 - Follow [STYLEGUIDE.md](./STYLEGUIDE.md) for code style, naming, JSDoc, validation, logging, and formatting expectations.
 - JSDoc requirements are enforced by the configured linter. Treat missing or incomplete JSDoc on required APIs as a real lint issue, not optional documentation.
 - Import and export ordering are enforced by the formatter. Preserve the existing grouped and sorted order unless a change requires updating it.
 - Formatting is enforced by oxfmt. Follow the existing formatting and do not fight the formatter.
+
+## Scope And Safety
+
 - Keep changes minimal and scoped to the request. Avoid unrelated refactors or broad cleanup.
 - Do not modify production code only to make a test pass. If a failing test points to a likely source issue, explain the issue and change behavior only when required by the task.
 - Preserve cross-platform behavior. Changes must work on Windows, macOS, and Linux, especially for paths, shell commands, environment variables, and networking behavior.
 - Maintain compatibility with the supported Node.js versions in this repository: 20.19, 22.13, 24.0 and 26.0.
+
+## Project Architecture
+
 - This repository uses TypeScript and ESM. Follow existing project patterns for imports, exports, build configuration, and test setup.
+
+## Testing And Validation
+
 - Prefer the existing npm scripts in [package.json](./package.json) and the VS Code tasks in [tasks.json](./.vscode/tasks.json) for building, linting, and testing.
 - Keep tests deterministic and simple. Prefer small data sets and straightforward setup.
 - Some tests are intentionally multi-step flows. State may persist across successive steps within a single test flow, but each test unit must remain isolated from other tests.
 - For validation, run the relevant full test file or the matching suite/task for the touched area rather than assuming arbitrary isolated single-test execution is reliable.
+
+## Documentation
+
 - When behavior changes, update the relevant tests and documentation.
+
+## Additional Agent Guidance
+
 - Use dedicated instruction files under [.claude/rules](.claude/rules/) when a rule applies only to specific file types or workflows.