mellos-mapping 0.20.2 → 0.20.3

package/README.md

@@ -556,9 +556,7 @@ npm install
 npm run verify
 ```
 
-`verify` is five steps, in this order: `typecheck` (the repo's own sources),
-`typecheck:packages` (the dsh plugin packages' framework-free modules, with
-`mellos-mapping/*` pointed at these sources), `test`, `build` (bundles
+`verify` is four steps, in this order: `typecheck`, `test`, `build` (bundles
 `dist/`, emits `lib/` with declarations, cleaning both first), and
 `check:package` — which packs the tarball through the real `prepack`
 lifecycle and fails if any `exports` or `bin` target is missing from it.
@@ -576,27 +574,12 @@ The repo is itself layered bottom-up, and each layer has its spec:
 | 4 render | `src/render/` | `render.test.ts`, `routing.test.ts` | the ASCII renderer and its wire routing |
 | 4 pane | `src/watch/` | `watch.test.ts`, `pane-state.test.ts`, `input.test.ts` | the polling pane: page set, input parsing, panel and chrome |
 | — launchers | `scripts/` | `open-pane.test.mjs`, `codex-register.test.mjs` | plain-node entry points |
-| — packaging | `package.json`, `packages/` | `tests/lockfile.test.ts`, `tests/packages.test.ts`, `browser-safe.test.ts` | what ships, and to whom |
+| — packaging | `package.json` | `tests/lockfile.test.ts`, `browser-safe.test.ts` | what ships, and to whom |
 
 `dist/` is committed deliberately: plugin installation clones this repo and
 runs nothing, so entry points ship bundled. CI diffs the committed `dist/`
 against a fresh build, so a source change that forgets the rebuild fails.
 
-### The dsh packages
-
-`packages/dsh` and `packages/dsh-client` are the DeepSeek Harness surface: a
-host plugin that reads and watches a workspace's `.mellos/` store, and the
-browser map panel that draws it with these same semantics. They are
-*developed* inside a dsh workspace checkout (its toolchain builds them) and
-*published* from here — sources, specs and `lib/` committed, refreshed by
-`node scripts/sync-dsh-plugin.mjs <path-to-deepseek-harness>`, which rewrites
-the dsh-internal package names to the published ones. This repo cannot build
-them, so it proves what it can: `typecheck:packages` and the framework-free
-specs run in CI, and `tests/packages.test.ts` guards the src↔lib structure,
-the shared version line, and the MCP row's spawn form. Specs that need the
-`@deepseek-ai` framework or a DOM are named, with their reason, in
-`vitest.config.ts`. See [`packages/dsh/README.md`](packages/dsh/README.md).
-
 ### Library
 
 The lower layers are also a library (`npm run build` emits `lib/` with type
@@ -615,7 +598,7 @@ declarations; npm packs it). Subpath exports mirror the source:
 **Browser-safe** means no Node builtins anywhere in the import closure, gated
 by a test, so a graphical client (a web panel, an editor view) can parse state
 files and reuse the exact aggregation, zoom and glyph semantics the terminal
-pane draws with. `packages/dsh-client` is that client.
+pane draws with.
 
 ## License
 

package/README.zh-CN.md

@@ -493,9 +493,7 @@ npm install
 npm run verify
 ```
 
-`verify` 是按顺序的五步：`typecheck`（本仓库自己的源码）、
-`typecheck:packages`（dsh 插件包里不依赖框架的模块，且把 `mellos-mapping/*`
-指向本仓库源码）、`test`、`build`（打包 `dist/`、产出带声明的 `lib/`，两个
+`verify` 是按顺序的四步：`typecheck`、`test`、`build`（打包 `dist/`、产出带声明的 `lib/`，两个
 目录都先清空），以及 `check:package`——它按真实的 `prepack` 生命周期打出
 tarball，只要 `exports` 或 `bin` 里有任何目标没被打进去就失败。
 
@@ -512,26 +510,12 @@ tarball，只要 `exports` 或 `bin` 里有任何目标没被打进去就失败
 | 4 render | `src/render/` | `render.test.ts`、`routing.test.ts` | ASCII 渲染器与它的走线 |
 | 4 pane | `src/watch/` | `watch.test.ts`、`pane-state.test.ts`、`input.test.ts` | 轮询面板：页集、输入解析、详情面板与外框 |
 | — 启动脚本 | `scripts/` | `open-pane.test.mjs`、`codex-register.test.mjs` | 纯 node 的入口 |
-| — 打包 | `package.json`、`packages/` | `tests/lockfile.test.ts`、`tests/packages.test.ts`、`browser-safe.test.ts` | 发出去的是什么、发给谁 |
+| — 打包 | `package.json` | `tests/lockfile.test.ts`、`browser-safe.test.ts` | 发出去的是什么、发给谁 |
 
 `dist/` 是刻意提交的：插件安装就是克隆本仓库、不运行任何东西，所以入口
 文件以打包形式随仓库分发。CI 会把提交的 `dist/` 和一次全新构建做 diff，
 所以改了源码却忘了重新构建会直接失败。
 
-### dsh 插件包
-
-`packages/dsh` 与 `packages/dsh-client` 是 DeepSeek Harness 的那一面：一个
-读取并监视工作区 `.mellos/` 存储的宿主插件，加上用同一套语义作画的浏览器
-地图面板。它们在 dsh workspace 检出里*开发*（由那边的工具链构建），从这里
-*发布*——源码、规格测试和 `lib/` 都提交在这儿，用
-`node scripts/sync-dsh-plugin.mjs <deepseek-harness 检出路径>` 刷新，该脚本
-会把 dsh 内部包名改写成发布用的名字。本仓库构建不了它们，所以只证明它能
-证明的：`typecheck:packages` 和不依赖框架的规格测试在 CI 里跑，
-`tests/packages.test.ts` 守住 src↔lib 的结构、共享版本线和 MCP 行的拉起
-方式。需要 `@deepseek-ai` 框架或 DOM 的规格测试连同理由一起写在
-`vitest.config.ts` 里。详见
-[`packages/dsh/README.md`](packages/dsh/README.md)。
-
 ### 库
 
 底部各层同时是一个库（`npm run build` 产出带类型声明的 `lib/`，npm 打包
@@ -549,8 +533,7 @@ tarball，只要 `exports` 或 `bin` 里有任何目标没被打进去就失败
 
 **浏览器安全**的意思是 import 闭包里没有任何 Node 内建模块，由测试门禁
 守护——图形客户端（web 面板、编辑器视图）可以直接解析状态文件，并复用与
-终端面板完全一致的聚合、缩放与字形语义。`packages/dsh-client` 就是这样一个
-客户端。
+终端面板完全一致的聚合、缩放与字形语义。
 
 ## 许可证
 

package/dist/server.mjs

@@ -21237,7 +21237,7 @@ function describeMapError(e) {
     case "layer-holds-group":
       return `layer "${e.id}" still holds group "${e.occupant}"; remove its groups (removeGroup) first`;
     case "edge-not-downward":
-      return `edge ${e.from} (rank ${e.fromRank}) -> ${e.to} (rank ${e.toRank}) is not strictly downward; dependencies may only point to a lower layer`;
+      return `edge ${e.from} (rank ${e.fromRank}) -> ${e.to} (rank ${e.toRank}) is not strictly downward; ` + (e.fromRank === e.toRank ? `same-band siblings may not depend on each other \u2014 either "${e.to}" is really a lower concept (declare it on a lower band) or "${e.from}" and "${e.to}" are one node (merge them)` : `"${e.from}" would USE "${e.to}" from a lower band \u2014 reverse the edge if "${e.to}" is the user, otherwise move or re-rank so "${e.from}" sits above "${e.to}"`);
   }
 }
 
@@ -23145,7 +23145,7 @@ function summarize(map) {
 
 // src/server/server.ts
 var SERVER_NAME = "mellos-mapping";
-var SERVER_VERSION = "0.20.2";
+var SERVER_VERSION = "0.20.3";
 var TITLE_MAX = 120;
 var LABEL_MAX = 60;
 var DETAIL_MAX = 600;

package/dist/watch.mjs

@@ -87,7 +87,7 @@ function describeMapError(e) {
     case "layer-holds-group":
       return `layer "${e.id}" still holds group "${e.occupant}"; remove its groups (removeGroup) first`;
     case "edge-not-downward":
-      return `edge ${e.from} (rank ${e.fromRank}) -> ${e.to} (rank ${e.toRank}) is not strictly downward; dependencies may only point to a lower layer`;
+      return `edge ${e.from} (rank ${e.fromRank}) -> ${e.to} (rank ${e.toRank}) is not strictly downward; ` + (e.fromRank === e.toRank ? `same-band siblings may not depend on each other \u2014 either "${e.to}" is really a lower concept (declare it on a lower band) or "${e.from}" and "${e.to}" are one node (merge them)` : `"${e.from}" would USE "${e.to}" from a lower band \u2014 reverse the edge if "${e.to}" is the user, otherwise move or re-rank so "${e.from}" sits above "${e.to}"`);
   }
 }
 

package/lib/domain/types.js

@@ -147,7 +147,16 @@ export function describeMapError(e) {
         case 'layer-holds-group':
             return `layer "${e.id}" still holds group "${e.occupant}"; remove its groups (removeGroup) first`;
         case 'edge-not-downward':
+            // The fault is one invariant (I4) but the remedy is not: a same-band
+            // edge is a modeling error the caller fixes by restructuring, an
+            // upward edge is usually a reversed arrow. The refusal is the moment
+            // the caller needs the remedy, so it is spelled out here, not only in
+            // the skill text they read before the batch was composed.
             return (`edge ${e.from} (rank ${e.fromRank}) -> ${e.to} (rank ${e.toRank}) is not strictly downward; ` +
-                `dependencies may only point to a lower layer`);
+                (e.fromRank === e.toRank
+                    ? `same-band siblings may not depend on each other — either "${e.to}" is really a lower concept ` +
+                        `(declare it on a lower band) or "${e.from}" and "${e.to}" are one node (merge them)`
+                    : `"${e.from}" would USE "${e.to}" from a lower band — reverse the edge if "${e.to}" is the user, ` +
+                        `otherwise move or re-rank so "${e.from}" sits above "${e.to}"`));
     }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mellos-mapping",
-  "version": "0.20.2",
+  "version": "0.20.3",
   "mcpName": "io.github.GuangminJu/mellos-mapping",
   "description": "A live layered dependency map for bottom-up development — MCP server + terminal pane. Ghost the design first, then light nodes up from the bottom as they are built and verified.",
   "type": "module",
@@ -75,11 +75,10 @@
   "scripts": {
     "test": "vitest run",
     "typecheck": "tsc --noEmit",
-    "typecheck:packages": "tsc -p tsconfig.packages.json",
     "build": "node build.mjs && tsc -p tsconfig.lib.json",
     "check:package": "node scripts/check-package-surface.mjs",
     "prepack": "npm run build",
-    "verify": "npm run typecheck && npm run typecheck:packages && npm run test && npm run build && npm run check:package"
+    "verify": "npm run typecheck && npm run test && npm run build && npm run check:package"
   },
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.12.0",