@mrrlin-dev/mcp 0.3.26 → 0.3.27
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/dist/bin.cjs +285 -312
- package/package.json +6 -7
- package/dist/prompts/report-issue.md +0 -51
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mrrlin-dev/mcp",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.27",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"bin": {
|
|
6
6
|
"mrrlin-mcp": "dist/bin.cjs"
|
|
@@ -11,7 +11,6 @@
|
|
|
11
11
|
"files": [
|
|
12
12
|
"dist/bin.cjs",
|
|
13
13
|
"dist/consensus/personas",
|
|
14
|
-
"dist/prompts",
|
|
15
14
|
"scripts/postinstall-restart.cjs"
|
|
16
15
|
],
|
|
17
16
|
"devDependencies": {
|
|
@@ -22,12 +21,12 @@
|
|
|
22
21
|
"@types/ws": "^8.18.1",
|
|
23
22
|
"esbuild": "^0.24.0",
|
|
24
23
|
"tsx": "^4.22.3",
|
|
24
|
+
"@mrrlin/codex-client": "0.0.0",
|
|
25
|
+
"@mrrlin/client": "0.0.0",
|
|
26
|
+
"@mrrlin/director-e2e": "0.0.0",
|
|
25
27
|
"@mrrlin/schemas": "0.0.0",
|
|
26
28
|
"@mrrlin/wiki": "0.0.0",
|
|
27
|
-
"@mrrlin/
|
|
28
|
-
"@mrrlin/tsconfig": "0.0.0",
|
|
29
|
-
"@mrrlin/client": "0.0.0",
|
|
30
|
-
"@mrrlin/codex-client": "0.0.0"
|
|
29
|
+
"@mrrlin/tsconfig": "0.0.0"
|
|
31
30
|
},
|
|
32
31
|
"dependencies": {
|
|
33
32
|
"@iarna/toml": "^2.2.5",
|
|
@@ -43,7 +42,7 @@
|
|
|
43
42
|
"scripts": {
|
|
44
43
|
"build": "node scripts/write-version.mjs && tsc -p tsconfig.json && pnpm run bundle && chmod +x dist/bin.cjs",
|
|
45
44
|
"postinstall": "node scripts/postinstall-restart.cjs",
|
|
46
|
-
"bundle": "node scripts/write-version.mjs && esbuild src/bin.ts --bundle --platform=node --format=cjs --target=node20 --outfile=dist/bin.cjs --banner:js='#!/usr/bin/env node' && mkdir -p dist/consensus/personas && cp src/consensus/personas/*.md dist/consensus/personas/
|
|
45
|
+
"bundle": "node scripts/write-version.mjs && esbuild src/bin.ts --bundle --platform=node --format=cjs --target=node20 --outfile=dist/bin.cjs --banner:js='#!/usr/bin/env node' && mkdir -p dist/consensus/personas && cp src/consensus/personas/*.md dist/consensus/personas/",
|
|
47
46
|
"dev": "tsx watch src/bin.ts serve",
|
|
48
47
|
"lint": "eslint .",
|
|
49
48
|
"start": "node dist/bin.cjs serve",
|
|
@@ -1,51 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: report-issue
|
|
3
|
-
description: Deprecated shell helper. Use the in-app Director `/report-issue` flow or the web header's `Report issue` entry; both file GitHub issues in fnnzzz/mrrlin.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Report issue
|
|
7
|
-
|
|
8
|
-
This slash-command prompt is kept only as a compatibility shim for operators who
|
|
9
|
-
already installed `/report-issue` into Codex.
|
|
10
|
-
|
|
11
|
-
## Preferred flows
|
|
12
|
-
|
|
13
|
-
Use one of the in-app flows instead of this shell prompt:
|
|
14
|
-
|
|
15
|
-
1. In the Director chat, run `/report-issue <what broke>`.
|
|
16
|
-
The app will package:
|
|
17
|
-
- your free-text description
|
|
18
|
-
- screenshots from the current Director turn
|
|
19
|
-
- the recent Director transcript
|
|
20
|
-
- the local Director bridge logs
|
|
21
|
-
- the active project slug and current route
|
|
22
|
-
|
|
23
|
-
2. In the top-right user menu, choose `Report issue`.
|
|
24
|
-
That modal lets you describe the problem in free text and attach screenshots.
|
|
25
|
-
It also packages recent Director context when available.
|
|
26
|
-
|
|
27
|
-
Both flows rationalize the evidence locally and create a GitHub issue in
|
|
28
|
-
`fnnzzz/mrrlin` through the operator's local `gh` CLI. The issue is labelled as
|
|
29
|
-
`bug`, includes bridge-log excerpts, transcript context, screenshots, and the
|
|
30
|
-
customer-facing description.
|
|
31
|
-
|
|
32
|
-
## What this legacy prompt should do
|
|
33
|
-
|
|
34
|
-
If an operator still invokes `/report-issue` from Codex directly:
|
|
35
|
-
|
|
36
|
-
- Tell them this flow is deprecated.
|
|
37
|
-
- Point them to the two in-app entry points above.
|
|
38
|
-
- Do not mention Telegram or any legacy support-bot flow.
|
|
39
|
-
- Do not invent a separate reporting pipeline.
|
|
40
|
-
|
|
41
|
-
Use concise wording. Example:
|
|
42
|
-
|
|
43
|
-
```text
|
|
44
|
-
Issue reporting moved into the Mrrlin UI.
|
|
45
|
-
|
|
46
|
-
- Director chat: `/report-issue <what broke>`
|
|
47
|
-
- Header menu: `Report issue`
|
|
48
|
-
|
|
49
|
-
Both flows attach bridge logs, transcript context, screenshots, and file a GitHub
|
|
50
|
-
issue in fnnzzz/mrrlin via your local gh CLI.
|
|
51
|
-
```
|