boundaryxp-mcp 0.4.0-rc.3 → 0.4.0-rc.4
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/CHANGELOG.md +7 -1
- package/DELIVERY-MANIFEST.json +11 -11
- package/INSTALL.md +4 -4
- package/README.md +137 -23
- package/RELEASING.md +1 -1
- package/npm-shrinkwrap.json +2 -2
- package/package.json +4 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,4 +1,10 @@
|
|
|
1
|
-
# 0.4.0-rc.
|
|
1
|
+
# 0.4.0-rc.4 (product introduction and discovery)
|
|
2
|
+
|
|
3
|
+
- Rewrote the bilingual npm introduction around 7+1 task boundaries, parent/child examples, independent LLM judgment and native calculation receipts.
|
|
4
|
+
- Added MCP Registry ownership metadata and search keywords. Metadata preparation does not mean a directory has accepted the listing.
|
|
5
|
+
- Updated installation examples; no Core, adapter logic, runtime resources, task data or dependency changes from rc.3.
|
|
6
|
+
|
|
7
|
+
# 0.4.0-rc.3 (first npm prerelease)
|
|
2
8
|
|
|
3
9
|
- Use the public package identity boundaryxp-mcp and the next prerelease channel. Retain MIT and ship the unchanged compiled B-335 Core without original Core source.
|
|
4
10
|
- Update registry lookup and keep the old private package identities accepted for explicit local migration and rollback. Old rc.2 installations need the new bootstrap once to change package identity.
|
package/DELIVERY-MANIFEST.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"format": "boundaryxp-mcp-delivery/1",
|
|
3
3
|
"package_name": "boundaryxp-mcp",
|
|
4
|
-
"adapter_version": "0.4.0-rc.
|
|
4
|
+
"adapter_version": "0.4.0-rc.4",
|
|
5
5
|
"runtime": {
|
|
6
6
|
"format": "boundaryxp-mcp-runtime-pin/1",
|
|
7
7
|
"product_label": "B-335",
|
|
@@ -127,18 +127,18 @@
|
|
|
127
127
|
},
|
|
128
128
|
{
|
|
129
129
|
"path": "package.json",
|
|
130
|
-
"bytes":
|
|
131
|
-
"sha256": "
|
|
130
|
+
"bytes": 1255,
|
|
131
|
+
"sha256": "fa6886f12b1ef2f3dff10b751e0bbc0f863a6ce49862208b53821a2841bb0113"
|
|
132
132
|
},
|
|
133
133
|
{
|
|
134
134
|
"path": "README.md",
|
|
135
|
-
"bytes":
|
|
136
|
-
"sha256": "
|
|
135
|
+
"bytes": 12079,
|
|
136
|
+
"sha256": "1782978ca76762d1a9920250b5a6cb7aa8b545be8ddd92592a248994c4fd2088"
|
|
137
137
|
},
|
|
138
138
|
{
|
|
139
139
|
"path": "INSTALL.md",
|
|
140
140
|
"bytes": 7905,
|
|
141
|
-
"sha256": "
|
|
141
|
+
"sha256": "5bba381d9f6a80cec65890590c2d71b9f0c676fc409984218ab4f25009b0925f"
|
|
142
142
|
},
|
|
143
143
|
{
|
|
144
144
|
"path": "AUTO-UPDATE.md",
|
|
@@ -147,8 +147,8 @@
|
|
|
147
147
|
},
|
|
148
148
|
{
|
|
149
149
|
"path": "RELEASING.md",
|
|
150
|
-
"bytes":
|
|
151
|
-
"sha256": "
|
|
150
|
+
"bytes": 2028,
|
|
151
|
+
"sha256": "a9499f15fdc70ff3398eb825e1fbee0a63531378fb9c06c0960444e92dfb4366"
|
|
152
152
|
},
|
|
153
153
|
{
|
|
154
154
|
"path": "CONTRACT.md",
|
|
@@ -157,8 +157,8 @@
|
|
|
157
157
|
},
|
|
158
158
|
{
|
|
159
159
|
"path": "CHANGELOG.md",
|
|
160
|
-
"bytes":
|
|
161
|
-
"sha256": "
|
|
160
|
+
"bytes": 5008,
|
|
161
|
+
"sha256": "2462e321f049216bb1cb4d798139a439f8c8bae8e2a13a989a5db7a22a1e0735"
|
|
162
162
|
},
|
|
163
163
|
{
|
|
164
164
|
"path": "THIRD-PARTY-NOTICES.md",
|
|
@@ -203,7 +203,7 @@
|
|
|
203
203
|
{
|
|
204
204
|
"path": "npm-shrinkwrap.json",
|
|
205
205
|
"bytes": 48582,
|
|
206
|
-
"sha256": "
|
|
206
|
+
"sha256": "b997cb3ae5c05502e5c448e3c97460ee138edf9b562f5d2b5b296cb2e6206f25"
|
|
207
207
|
},
|
|
208
208
|
{
|
|
209
209
|
"path": "runtime/research/7plus1-parser/llm-first-028/source.mjs",
|
package/INSTALL.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# 安装、接入和升级 / Installation and upgrades
|
|
2
2
|
|
|
3
|
-
**boundaryxp-mcp 0.4.0-rc.
|
|
3
|
+
**boundaryxp-mcp 0.4.0-rc.4 · B-335 · Windows x64 · Node >=22.18.0(实测24.19.0)**
|
|
4
4
|
|
|
5
5
|
## 首次安装 / First installation
|
|
6
6
|
|
|
@@ -12,7 +12,7 @@ $BxpHome = Join-Path $BxpRoot 'install'
|
|
|
12
12
|
$BxpData = Join-Path $BxpRoot 'data'
|
|
13
13
|
$BxpSettings = Join-Path $BxpRoot 'settings'
|
|
14
14
|
if (Test-Path (Join-Path $BxpHome 'active.json')) { throw 'Already installed: use update' }
|
|
15
|
-
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.
|
|
15
|
+
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.4 bxp install --home $BxpHome --version 0.4.0-rc.4
|
|
16
16
|
if ($LASTEXITCODE -ne 0) { throw 'Installation failed' }
|
|
17
17
|
$BxpLauncher = Join-Path $BxpHome 'launcher.mjs'
|
|
18
18
|
New-Item -ItemType Directory -Path $BxpSettings -Force | Out-Null
|
|
@@ -24,7 +24,7 @@ if (!(Test-Path $BxpEnv)) { [IO.File]::WriteAllText($BxpEnv, "# Model API config
|
|
|
24
24
|
node $BxpLauncher --manage status
|
|
25
25
|
```
|
|
26
26
|
|
|
27
|
-
Wait for `READY`, `probe.passed:true`, and version `0.4.0-rc.
|
|
27
|
+
Wait for `READY`, `probe.passed:true`, and version `0.4.0-rc.4`. Download and integrity checks use the exact package version on npm. Empty profiles allow read-only inspection; no analysis is started. Installation needs internet access for dependencies. No compiler, separate 58618 installation or hosted BoundaryXP server is required.
|
|
28
28
|
|
|
29
29
|
## Cursor
|
|
30
30
|
|
|
@@ -93,7 +93,7 @@ Confirm the preview, save it as a new project, submit one analysis for the exact
|
|
|
93
93
|
旧包名为`@boundaryxp/mcp`。旧更新器不会自行切换到新包名;首次使用新版bootstrap,保持原安装目录及数据配置:
|
|
94
94
|
|
|
95
95
|
```powershell
|
|
96
|
-
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.
|
|
96
|
+
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.4 bxp update --home $BxpHome --version 0.4.0-rc.4
|
|
97
97
|
```
|
|
98
98
|
|
|
99
99
|
先备份数据和配置并等待作业结束,再断开所有相关MCP客户端,升级后重连。不要先删除旧版。rc.2到rc.3运行核心摘要相同,不需要迁移数据;将来不同摘要需显式`--migrate-data <原数据目录>`,复制验证后保留旧目录。只对这套独立MCP操作,不操作58618。
|
package/README.md
CHANGED
|
@@ -1,50 +1,164 @@
|
|
|
1
|
-
# BoundaryXP
|
|
1
|
+
# BoundaryXP · 界痕
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
**7+1 任务边界分析与计算复核,供 AI Agent 和多角色协作使用。**
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
**7+1 task boundary analysis and computational verification for AI agents and teams.**
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
当一个任务被拆给多个 DEV、OPS、QA,如何确认子任务仍在父任务限定的范围内?BoundaryXP(简称 BXP)把任务文本整理为可追溯的 7+1 边界,让 LLM 进行语义判断,再由原生计算器独立复核提交的形式化输入。在同一份报告里查看任务要求、冲突依据、计算回执和未明确项。
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
When work is delegated across agents or roles, BoundaryXP helps inspect whether child tasks stay within their parent's stated constraints. An LLM interprets the text; a native calculator independently verifies the submitted formal inputs. Both judgments, source evidence and computation receipts remain visible.
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
**`boundaryxp-mcp@0.4.0-rc.4` · B-335 · Windows x64 · Node.js ≥22.18 · MIT · Prerelease**
|
|
12
|
+
|
|
13
|
+
通过标准 **stdio MCP** 接入 Cursor、Codex 等宿主,包含 **18 个工具、10 项资源、中英帮助和本地浏览器工作台**。一个 npm 包即可使用,无需另装 BoundaryXP 工作台、exe 安装器或自建 BoundaryXP 服务器。当前原生包只支持 Windows x64。
|
|
14
|
+
|
|
15
|
+
Standard stdio MCP for Cursor, Codex and compatible hosts. One package includes the compiled Core and workbench. No separate BoundaryXP installation or hosted BoundaryXP server is required. macOS/Linux native packages are not included in this release.
|
|
16
|
+
|
|
17
|
+
## 7+1 看什么? / What does 7+1 mean?
|
|
18
|
+
|
|
19
|
+
7+1 是七项任务维度,加一项独立禁止边界;不是评分,也不是八个 Agent。
|
|
20
|
+
|
|
21
|
+
| 维度 / Dimension | 核对内容 / What to inspect |
|
|
22
|
+
|---|---|
|
|
23
|
+
| **I · 输入 / Input** | 哪些数据、材料和来源可用? / Which data and sources are in scope? |
|
|
24
|
+
| **O · 交付 / Output** | 要交付什么,交给谁? / What must be delivered, and to whom? |
|
|
25
|
+
| **A · 动作 / Action** | 可以执行哪些动作? / Which actions are specified or permitted? |
|
|
26
|
+
| **P · 责任与分工 / Responsibility** | 谁负责、谁配合、如何交接? / Who owns the work and handoffs? |
|
|
27
|
+
| **R · 资源 / Resources** | 工作区、容量、预算等限制? / Which workspace, capacity or budget limits apply? |
|
|
28
|
+
| **V · 版本依据 / Version basis** | 以哪版规则、文档或基线为准? / Which rule or baseline version applies? |
|
|
29
|
+
| **C · 完成与停止 / Completion and stopping** | 什么条件算完成,何时停止? / What defines completion or a required stop? |
|
|
30
|
+
| **+1 B · 独立禁止边界 / Prohibitions** | 哪些事明确禁止? / What is explicitly forbidden? |
|
|
31
|
+
|
|
32
|
+
未写明的条件保持“未明确”。L2 行业字典和 L3 企业字典为术语解释提供版本化依据;岗位、姓名及字典条目本身不构成授权。
|
|
33
|
+
|
|
34
|
+
Missing conditions remain unspecified. Versioned L2 industry and L3 enterprise dictionaries support interpretation; roles and dictionary entries do not grant permission.
|
|
35
|
+
|
|
36
|
+
## 一个父子任务案例 / A parent–child example
|
|
37
|
+
|
|
38
|
+
> **父任务 / Parent:** 仅处理测试目录;交付检查报告;禁止部署生产环境。
|
|
39
|
+
>
|
|
40
|
+
> Only inspect the test directory, deliver an inspection report, and do not deploy to production.
|
|
41
|
+
>
|
|
42
|
+
> **DEV-01:** 检查测试文件并交付报告。 / Inspect test files and deliver the report.
|
|
43
|
+
>
|
|
44
|
+
> **DEV-02:** 报告完成后部署生产环境。 / Deploy to production after the report is complete.
|
|
45
|
+
|
|
46
|
+
需要分别核对 DEV-01 和 DEV-02;不能把一个子任务的结论当作整个项目的结论。DEV-02 的部署条款与父任务的禁止条款构成待分析的文本冲突,报告应能回到这两处原文。
|
|
47
|
+
|
|
48
|
+
Each child must be assessed against the parent separately. DEV-02 introduces a deployment clause that conflicts with the parent's stated prohibition. This example illustrates what to inspect; it is not a saved execution result or a guarantee that every model extracts it correctly.
|
|
49
|
+
|
|
50
|
+
支持完整 UTF-8 Markdown/TXT、多级父子任务、多个同角色子任务,以及 `PM → DEV(1/14)` 等标题。显式任务编号、父任务编号和导入预览用于区分节点;同为 DEV 不会把任务合为一个。先确认关系,再提交分析。
|
|
51
|
+
|
|
52
|
+
Complete Markdown/TXT imports support explicit task/parent IDs and multiple children with the same role. Preview and confirm relationships before analysis.
|
|
53
|
+
|
|
54
|
+
## 边界怎样计算? / How does verification work?
|
|
55
|
+
|
|
56
|
+
1. **导入与确认 / Import:** 预览完整父子任务,绑定需要的 L2/L3 字典。
|
|
57
|
+
2. **LLM 语义分析 / Interpret:** 显式提交一次联合分析,形成 7+1、原文证据、语义判断及结构化计算输入。
|
|
58
|
+
3. **原生 Core 复核 / Verify:** 对本轮提交的集合、布尔表达式、数值等受支持的形式化查询执行程序核验,记录实际操作数和回执。
|
|
59
|
+
4. **对照与追溯 / Inspect:** 对齐同一任务与核验范围,比较 LLM 判断和计算器结果,追溯原文与未明确项。保留失败,不把解析失败当作越界或未越界。
|
|
60
|
+
|
|
61
|
+
**LLM 判断与计算器复核分别记录。** 计算器不调用模型;它核对提交的形式化输入。计算通过不自动证明语义抽取正确,也不授予业务批准或执行权限。
|
|
62
|
+
|
|
63
|
+
**LLM judgments and calculator results are recorded separately.** The calculator does not call an LLM: it evaluates supported formal inputs. Successful computation does not prove that text was interpreted correctly. Neither result grants business approval or execution authority.
|
|
64
|
+
|
|
65
|
+
## 能看到什么? / What do you get?
|
|
66
|
+
|
|
67
|
+
- 父子任务树、多个 DEV 节点及完整 7+1 分析。 / Task trees and distinct child assessments.
|
|
68
|
+
- 八轴边界雷达、独立 B 禁止边界、条款和原文证据。 / A boundary radar, prohibitions and evidence.
|
|
69
|
+
- LLM 判断、形式模型、计算回执及技术报告。 / LLM judgments, formal inputs and verification receipts.
|
|
70
|
+
- Markdown 报告、历史结果及失败记录。 / Markdown reports and retained results or failures.
|
|
71
|
+
- MCP 与浏览器读取同一份保存数据。 / The same saved project through MCP and the workbench.
|
|
72
|
+
|
|
73
|
+
雷达表达条款的维度关联,不表示评分、进度或授权大小。The radar shows clause relationships, not scores, progress or authority.
|
|
74
|
+
|
|
75
|
+
## 安装 / Install
|
|
76
|
+
|
|
77
|
+
需要 Windows x64、Node.js ≥22.18 和 npm(实测 Node 24.19.0)。首次安装在 PowerShell 执行;已有安装保留自己的 home、data-root 和配置,使用升级入口。
|
|
12
78
|
|
|
13
79
|
```powershell
|
|
14
80
|
$BxpRoot = Join-Path $env:LOCALAPPDATA 'BoundaryXP'
|
|
15
81
|
$BxpHome = Join-Path $BxpRoot 'install'
|
|
16
82
|
$BxpData = Join-Path $BxpRoot 'data'
|
|
17
|
-
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.
|
|
83
|
+
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.4 bxp install --home $BxpHome --version 0.4.0-rc.4
|
|
18
84
|
if ($LASTEXITCODE -ne 0) { throw 'Installation failed' }
|
|
19
85
|
$BxpLauncher = Join-Path $BxpHome 'launcher.mjs'
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
**Cursor:** 生成独立工作区配置,打开 `$BxpRoot/workspace`,启用 BoundaryXP。
|
|
89
|
+
|
|
90
|
+
```powershell
|
|
20
91
|
$BxpConfig = Join-Path $BxpRoot 'workspace\.cursor\mcp.json'
|
|
21
92
|
node $BxpLauncher --manage configure --config $BxpConfig --data-root $BxpData
|
|
22
93
|
```
|
|
23
94
|
|
|
24
|
-
|
|
95
|
+
**Codex 或其他 MCP 宿主 / Other hosts:** 使用标准 stdio 命令和参数;不同宿主的配置文件位置与格式可能不同。替换下面的绝对路径,保留其他 MCP 配置。
|
|
96
|
+
|
|
97
|
+
```json
|
|
98
|
+
{
|
|
99
|
+
"mcpServers": {
|
|
100
|
+
"BoundaryXP": {
|
|
101
|
+
"command": "node",
|
|
102
|
+
"args": ["C:/absolute/path/install/launcher.mjs", "--data-root", "C:/absolute/path/data"]
|
|
103
|
+
}
|
|
104
|
+
}
|
|
105
|
+
}
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
首次连接后,在宿主聊天发送 / After connection, ask:
|
|
109
|
+
|
|
110
|
+
> 调用 BoundaryXP 的 bx_capabilities 和 bx_workbench_open,返回版本及工作台地址,不提交分析。
|
|
111
|
+
>
|
|
112
|
+
> Call BoundaryXP bx_capabilities and bx_workbench_open; return the version and workbench URL without submitting analysis.
|
|
113
|
+
|
|
114
|
+
工作台地址由 MCP 返回,端口动态分配,不要固定旧地址。关闭浏览器不会结束 MCP;最后一个 MCP 客户端断开时服务退出,未完成作业会取消。重连后重新调用 `bx_workbench_open`。
|
|
115
|
+
|
|
116
|
+
The workbench uses a dynamic local port. Closing its browser tab leaves MCP running; closing the last MCP client stops the backend and cancels unfinished work. Obtain a new URL after reconnecting.
|
|
117
|
+
|
|
118
|
+
## 模型配置与首次分析 / Model access and first analysis
|
|
119
|
+
|
|
120
|
+
**只读帮助、读取已有结果和打开页面无需模型 API。新分析需要自己的模型 API/profile;不会自动继承 Cursor 或 Codex 聊天订阅。** 提供商配置见随包交付的 `INSTALL.md`,工具说明也可通过 MCP 直接读取。
|
|
25
121
|
|
|
26
|
-
|
|
122
|
+
Read-only tools need no model key. Analysis uses your configured API/profile and may incur provider charges. Keep credentials in environment variables or an explicit local env file, never in task text. Requested analysis sends selected task/dictionary content to your model provider; Core computation is local.
|
|
27
123
|
|
|
28
|
-
|
|
124
|
+
配置好模型后,将完整任务文本交给宿主 / After configuring your model:
|
|
29
125
|
|
|
30
|
-
|
|
126
|
+
> 用 BoundaryXP 导入下面的完整父子任务,保留每个 DEV 的任务编号,先展示关系预览;确认后保存,使用我配置的 profile 分析一次。返回 LLM 判断、计算器复核、原文依据和工作台地址。失败不自动重试。
|
|
31
127
|
|
|
32
|
-
|
|
128
|
+
> Import this parent–child task into BoundaryXP, keeping every DEV task ID. Preview relationships first. After confirmation, save and analyze once with my configured profile. Return both judgments, evidence and the workbench URL. Do not automatically retry failures.
|
|
33
129
|
|
|
34
|
-
|
|
130
|
+
## 18 个工具怎么用? / Tool help
|
|
131
|
+
|
|
132
|
+
在宿主聊天说 / Ask in chat:
|
|
133
|
+
|
|
134
|
+
> 用 BoundaryXP 查看中文工具说明、完整多 DEV 案例和排障说明。
|
|
135
|
+
>
|
|
136
|
+
> Read BoundaryXP tool help, multi-DEV examples and troubleshooting in English.
|
|
137
|
+
|
|
138
|
+
帮助入口:`bx_capabilities({"language":"zh-CN","help_topic":"tools"})`;英文用 `language:"en"`。资源入口:`boundaryxp://help/{zh-CN|en}/{overview|tools|examples|troubleshooting}`。参数以工具发现返回的 Schema 为准。
|
|
139
|
+
|
|
140
|
+
工具覆盖能力/帮助、profile 查询、L2/L3 字典、任务导入与校验、项目管理、分析提交与取消、作业状态、结果和文件读取、保存操作数的零模型复验以及打开工作台。
|
|
141
|
+
|
|
142
|
+
Tools cover discovery, profiles, dictionaries, imports, projects, analysis jobs, results, verification of saved inputs and opening the workbench.
|
|
143
|
+
|
|
144
|
+
## 升级与数据 / Updates and data
|
|
145
|
+
|
|
146
|
+
已安装用户沿用自己的 `$BxpHome`,不要替换原任务数据目录:
|
|
147
|
+
|
|
148
|
+
```powershell
|
|
149
|
+
npx.cmd --yes --package boundaryxp-mcp@0.4.0-rc.4 bxp update --home $BxpHome --version 0.4.0-rc.4
|
|
150
|
+
```
|
|
35
151
|
|
|
36
|
-
|
|
152
|
+
自动检查和升级默认关闭,可显式启用;新版准备好后,在相关客户端全部退出后的下次启动切换,不在分析中强制更新。保留原安装、数据和 profile,支持回滚。详见随包交付的 `AUTO-UPDATE.md` 和 `INSTALL.md`。
|
|
37
153
|
|
|
38
|
-
|
|
154
|
+
Automatic updates are opt-in, with safe next-start activation and rollback. Existing data and configuration are retained. The independent 58618 installation is outside this package's update scope.
|
|
39
155
|
|
|
40
|
-
|
|
41
|
-
- `bx_capabilities({"language":"zh-CN","help_topic":"tools"})` or `language:"en"`.
|
|
42
|
-
- Resources: `boundaryxp://help/{zh-CN|en}/{overview|tools|examples|troubleshooting}`.
|
|
43
|
-
- “预览这份多 DEV 任务,核对任务编号和父任务编号;确认后保存并分析一次,失败不自动重试,打开工作台。”
|
|
44
|
-
- “List saved BoundaryXP projects and open the selected project without rerunning analysis.”
|
|
156
|
+
## 文档与交付 / Documentation and distribution
|
|
45
157
|
|
|
46
|
-
|
|
158
|
+
- [npm 安装入口 / Package](https://www.npmjs.com/package/boundaryxp-mcp)
|
|
159
|
+
- [产品资料与 Release / Product repository](https://github.com/joinwell52-AI/BoundaryXP):当前仍私有,访问需权限;npm 安装不依赖该仓库权限。Currently private; npm installation is independent.
|
|
160
|
+
- 完整指南随 npm 包交付:`INSTALL.md`、`AUTO-UPDATE.md`、`guides/TOOLS.md`、`examples/multi-dev-2.md`、`examples/multi-dev-2.en.md`。MCP 内置帮助无需读取私有仓库。
|
|
47
161
|
|
|
48
|
-
|
|
162
|
+
MIT 及第三方 notices 随包保留。Core 以编译后的 Node-API 模块交付,不含原始 C++ 或 JavaScript Core 源码;适配器、UI、提示词及必要资源仍可读。当前预发行不宣称完整协议符合性或所有模型的语义准确率。
|
|
49
163
|
|
|
50
|
-
|
|
164
|
+
The native Core ships without original Core source. Adapter/UI/prompt files and required resources remain readable. This prerelease makes no blanket protocol-conformance or model-accuracy claim.
|
package/RELEASING.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# npm发行流程 / npm release procedure
|
|
2
2
|
|
|
3
|
-
当前发行候选为`boundaryxp-mcp@0.4.0-rc.
|
|
3
|
+
当前发行候选为`boundaryxp-mcp@0.4.0-rc.4`,预发行渠道`next`。rc.3为首次npm发行,rc.4补齐产品介绍及检索元数据。2026-11-14用户明确授权发布,并决定保留MIT、仅交付编译核心,不交付核心源码。源码仓库保持私有;npm发布不会改变GitHub仓库可见性。
|
|
4
4
|
|
|
5
5
|
1. 从固定B-335原生运行包构建,保留runtime manifest和Core摘要。拒绝原始JavaScript Core、C++源码、调试符号、客户任务和凭据。
|
|
6
6
|
2. 生成准确的package.json、锁文件、DELIVERY-MANIFEST和双语安装说明;版本或文件有变化必须形成新候选,不能替换旧rc.2档案。
|
package/npm-shrinkwrap.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "boundaryxp-mcp",
|
|
3
|
-
"version": "0.4.0-rc.
|
|
3
|
+
"version": "0.4.0-rc.4",
|
|
4
4
|
"lockfileVersion": 3,
|
|
5
5
|
"requires": true,
|
|
6
6
|
"packages": {
|
|
7
7
|
"": {
|
|
8
8
|
"name": "boundaryxp-mcp",
|
|
9
|
-
"version": "0.4.0-rc.
|
|
9
|
+
"version": "0.4.0-rc.4",
|
|
10
10
|
"cpu": [
|
|
11
11
|
"x64"
|
|
12
12
|
],
|
package/package.json
CHANGED
|
@@ -1,16 +1,17 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "boundaryxp-mcp",
|
|
3
|
-
"version": "0.4.0-rc.
|
|
3
|
+
"version": "0.4.0-rc.4",
|
|
4
|
+
"mcpName": "io.github.joinwell52-AI/boundaryxp",
|
|
4
5
|
"private": false,
|
|
5
6
|
"os": ["win32"],
|
|
6
7
|
"cpu": ["x64"],
|
|
7
8
|
"type": "module",
|
|
8
9
|
"engines": {"node": ">=22.18.0"},
|
|
9
|
-
"description": "
|
|
10
|
+
"description": "7+1 task boundary analysis and native calculation verification for AI agents, with evidence reports and a local MCP workbench",
|
|
10
11
|
"license": "MIT",
|
|
11
12
|
"repository": {"type":"git","url":"https://github.com/joinwell52-AI/BoundaryXP.git"},
|
|
12
13
|
"homepage": "https://www.npmjs.com/package/boundaryxp-mcp",
|
|
13
|
-
"keywords": ["mcp", "boundaryxp", "bxp", "task-boundary", "native"],
|
|
14
|
+
"keywords": ["mcp", "mcp-server", "boundaryxp", "bxp", "7plus1", "task-boundary", "boundary-verification", "multi-agent", "evidence", "native"],
|
|
14
15
|
"publishConfig": {"registry":"https://registry.npmjs.org/","access":"public","tag":"next"},
|
|
15
16
|
"bin": {"bxp": "cli.mjs", "boundaryxp-mcp": "server.mjs", "bxp-install": "install.mjs"},
|
|
16
17
|
"files": ["*.mjs", "*.md", "LICENSE", "DELIVERY-MANIFEST.json", "npm-shrinkwrap.json", "examples/", "guides/", "schemas/", "runtime/", "package-assets/", "tests/"],
|