burhan-mop 0.1.2 → 0.1.4

package/AGENTS.md

@@ -14,13 +14,23 @@ follow `.MOP/PROTOCOL.md`.
   It selects one primary role and may recommend any number of support roles
   when genuinely needed. If no named agent exists for a needed role, ask the
   user to name it and save it with `agent activate`.
+
+| Role | Name | Description |
+| :--- | :--- | :--- |
+| **[qa]**         | QA Engineer             | Test plans, coverage gaps, regression                  |
+| **[ai]**         | Prompt Alchemist        | Prompt engineering, AI tuning, LLM evaluation          |
+| **[seo]**        | SEO Strategist          | Technical SEO, on-page, audits, implementation specs   |
+| **[browser]**    | Browsing Agent          | Web browsing, scraping, form filling, bot bypass, extraction |
+
 - If the router marks the task as ambiguous, the named primary agent must ask
   clarifying questions before implementation.
+- **[browser] Agent Rule**: Before creating a new browser session with `browser-act`, you must check the user's default browser (e.g., using `xdg-settings get default-web-browser` on Linux) or ask them what browser they use (Chrome, Edge, Brave, Opera). If they use something other than the built-in Chrome, use `browser-act`'s `chrome-direct` mode and guide them to start their browser with remote debugging (`--remote-debugging-port`), rather than just creating a default `chrome` browser.
 - If the router returns `partyMode.active: true`, use Party Mode. Show
-  `PARTY MODE` in large uppercase before the dialogue, then show
-  agent-to-agent and agent-to-user dialogue with the exact format from
-  `.MOP/PROTOCOL.md`. Party Mode normally uses at least 3 agents and
-  prefers 4 when relevant roles exist.
+  `PARTY MODE` in large uppercase before the dialogue, then generate the
+  agent-to-agent and agent-to-user dialogue explicitly in your response using this exact format:
+  `agent: <from-name> (<from-role>) to agent: <to-name> (<to-role>)`
+  `          <message>`
+  Party Mode normally uses at least 3 agents and prefers 4 when relevant roles exist.
 - For complex work or "what next?" questions, use MOP Workflow:
   `mop-workflow.mjs help --actor <codename> --task "<user task>"`.
 - Before implementation, run the readiness gate. If it is not `ready`, ask

package/README.bm.md

@@ -142,7 +142,7 @@ dan merge hanya bila workflow selamat.
 | --- | --- |
 | npm package | [`burhan-mop`](https://www.npmjs.com/package/burhan-mop) |
 | command latest | `npx burhan-mop install` |
-| GitHub release | [`v0.1.2`](https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP/releases/tag/v0.1.2) |
+| GitHub release | [`v0.1.4`](https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP/releases/tag/v0.1.4) |
 | Node | `>=20` |
 
 ## Links

package/README.md

@@ -141,7 +141,7 @@ and merges only when the workflow is safe.
 | --- | --- |
 | npm package | [`burhan-mop`](https://www.npmjs.com/package/burhan-mop) |
 | latest command | `npx burhan-mop install` |
-| GitHub release | [`v0.1.2`](https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP/releases/tag/v0.1.2) |
+| GitHub release | [`v0.1.4`](https://github.com/BURHANDEV-ENTERPRISE/BURHAN-MOP/releases/tag/v0.1.4) |
 | Node | `>=20` |
 
 ## Links

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "burhan-mop",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "MOP portable agent memory core installer and CLI.",
   "type": "module",
   "author": "BURHANDEV ENTERPRISE",