chore(gui): mission work logs — cordis design finalization, tool-card wire archive, incident records chore: missions chore: missions chore(gui): mission ledger — batch-2 answers, parallel dispatch state, jsdom coverage re-scope chore(gui): ledger — night-mode standing orders (self-commit small, no push, 5-min refresh) chore(gui): ledger — jsdom batches 2-4 landed (233 green), coverage probe next chore(gui): ledger — web-ui coverage probe 65%, four-tier fill plan approved chore(gui): ledger — cordis-impl B1 state after third API drop, decisions on file chore(gui): ledger — 01:32 patrol snapshot (jsdom tier-1 landed, coverage-fixer probed) chore(gui): ledger — 01:37 patrol (peer src trio landed, coverage-fixer still silent) chore(gui): ledger — 01:42 patrol (jsdom tier-2 landed, peer committed x2, coverage-fixer 2nd probe) chore(gui): ledger — coverage diagnosis complete (6-file gap list), web-ui at 91.4% chore(gui): ledger — 01:46 patrol (B1 done, jsdom tier-3 landed, coverage fix batch running) chore(gui): ledger — 01:51 patrol (jsdom tails x2 landed, B2 underway) chore(gui): ledger — 01:56 patrol (gateway.ts 337 lines, checkpoint T-7min) chore(gui): ledger — hold/pending split ruling, coverage-fixer externalize-or-restart ultimatum chore(gui): ledger — 02:01 patrol (B2 done, jsdom final arms, coverage ultimatum pending) chore(gui): ledger — 02:03 checkpoint executed (fixer2 respawn, four lanes released, three owners cold-started) chore(gui): ledger — all six lanes acked, type isolation first live proof (client closure clean) chore(gui): ledger — 02:08 patrol (all seven lanes active, wire carrier assembled) docs(gui): respond-design task checkpoint — apiproxy wire-layer recon done chore(gui): ledger — P0-2 contributor AGENTS.md landed (dd28a5019) docs(gui): respond-design checkpoint 2 — host-side recon (stub respond, frame types, approval seam, ACP answerer precedent) docs(gui): OOP debt inventory — seven territories, 2 real debts (createApiProxy, createFixtureApi), rest ruled keep-as-is docs(gui): disambiguation note on the archived i18n design task chore(gui): ledger — 02:12 patrol (exclude removed, mixed-knife incident under reconciliation) chore(gui): ledger — 02:15 wave (jsdom mission closed, OOP audit done, B3 isolation proof, mixed-knife resolved) chore(gui): ledger — 02:17 patrol (attribution reversal filed, arch-session probed) chore(gui): ledger — 02:22 patrol (B4 done, B5+B6 merged batch, arch-session deadline set) docs(gui): respond-design checkpoint 3 — client-side recon (pending map, PendingCard onRespond stub, AbstractApiClient.respond ready, bootHost missing approval mounts) docs(gui): peer carrier territory review — 2 fixes (SSE cancel leak, route-reservation guard), 1 ruling ask (RPC-log visibility), compliance ledger chore(gui): ledger — 02:27 (arch-shell respawn, territory review verdicts routed, ask-deny finding flagged) docs(gui): P1-5 respond design page complete — pending registry, wire answerer, client state machine, first-wins arbitration chore(gui): ledger — 02:31 patrol (respond design complete, B5 wire smoke green, shell knife 1 underway) docs(gui): respond design — add §0 status warning (web host ask defaults to deny), mount-behavior delta, no-timeout ruling with Config discipline chore(gui): ledger — 02:42 patrol (respond line closed pending review, B7 last piece underway) docs(gui): respond design contract review — direction pass, 2 doc fixes (settle-order contradiction, answering-state race), A/B/C compliance ledger docs(gui): respond design — contract review fixes (R1 verify-before-delete arbitration, R2 answering+resolved-frame transition, ask dual-source wording, rejected-is-ok-value note) chore(gui): ledger — 02:46 patrol (respond line final, two user decisions distilled, arch-shell deadline) docs(gui): respond review addendum — contract-gap ruling: approve plan A (ApprovalRequest.id), wire unchanged, drop plan B backscan chore(gui): ledger — cordis B7 summit: real-browser 10/10 green, user acceptance criterion proven docs(gui): respond design — contract gap #4 approved as plan A (ApprovalRequest.id), backscan fallback retired, blade 0 prepended docs(gui): respond design — final polish (owner-approval vs user-go-ahead wording, implementation handoff notes) chore(gui): ledger — 02:51 (shell-exec third respawn with operational script, respond line 4-knife final) chore(gui): ledger — 02:53 wave (respond five-knife true final, B7 closed 12/12, client.ts green) chore(gui): ledger — 02:56 patrol (cordis closeout bounced pending R1/R2/N1, shell-exec first sign of life) chore(gui): ledger — 03:01 patrol (R1/R2/N1 remediation in flight across four files) chore(gui): ledger — cordis line officially closed and archived, verified on disk (24 knives, 12/12, reviews closed) chore(gui): ledger — 03:06 patrol (shell-exec final window, lowered first-knife bar) chore(gui): ledger — 03:11 patrol (shell line iced-broken: three registries on disk) chore(gui): ledger — 03:15 patrol (quiet window, both active lanes within threshold) chore(gui): ledger — 03:20 patrol (shell five files up, api-proxy plan reported) chore(gui): ledger — 03:25 patrol (shell migration in flight with history-preserving moves, webserver green) chore(gui): ledger — 03:30 patrol (shell knife-1 in verification, api-proxy patching) chore(gui): ledger — shell knife 1 accepted (694cecc53), knife 2 released chore(gui): ledger — 03:40 patrol (knife 2 pre-move stage, cold-list spec appears) chore(gui): ledger — 03:45 patrol (rpclog moves staged, api-proxy two specs in flight) chore(gui): ledger — 03:54 patrol (knife-2 code done, coverage full-run final check) docs(gui): coverage-fixer task ledger — fixer2 takeover, per-file fix log, isolated reportsDirectory pitfall chore(gui): ledger — coverage lane closed and accepted (a19f069a5), the PR #443 CI fix knife chore(gui): ledger — 04:04 patrol (knife-2 calibration, sole active lane) chore(gui): ledger — shell knife 2 accepted (f8fb77b95), knife 3 released as final night task chore(gui): ledger — 04:19 patrol (knife-3 past half: callback chain through, ToolCallDetail up) chore(gui): ledger — night closeout summary: seven lanes closed, wake-up decision sheet chore: missions chore: missions chore: missions chore(gui): mission-local browser/probe verify scripts under missions/scripts/ The six acceptance/probe scripts move here as mission-side working material (headers and relative imports adjusted for the new location): carrier-errors, rpclog-panel, session, session-real, webserver-backpressure, webserver-hardening. chore(gui): verify-relocate mission log chore(gui): verify-relocate mission log — R1 guard addendum chore(gui): gates-continue mission log — CI-equivalent sequence all green chore(gui): VS Code 扩展体系双边设计调研报告 chore(gui): 调研追加 4.5 节——git 扩展数据面与 scope 绑定 docs(gui): web plugin system RFC — walkthrough + design notes docs(gui): RFC — restore existing SSE/POST as the v1 transport; envelope rides on it (D16) docs(gui): RFC — envelope demoted to chan-dispatch, scope out of envelope, rpc-log cut, peer deferred, scope tree is native cordis (D17-D21) docs(gui): RFC — hooks re-derived from component needs: useWatch/useAction only, useService removed; sessionHub cut, projections user-space, router rename, loader-only root (D22-D25) docs(gui): RFC — drop stale fork vocabulary (vendored cordis has Fiber only; scope = mintScope pattern), hook idempotence contract (D26-D27) docs(gui): RFC — session precision seam: plugins read scope key (host paradigm), React gets it from tree position via SlotOutlet (D28) docs(gui): RFC — domain hooks owned by plugins over framework primitives; useConversation paradigm carried over (D29) docs(gui): RFC — ctx services are the inter-plugin API (cordis proper); declarations are wire-only; get(id) returns scoped ctx (D30) docs(gui): RFC — full ctx.conversation walkthrough: root-singleton scope-sensitive service, caller-ctx scope key, get(key) as scoped ctx (D31) docs(gui): RFC — no client-side agents collection: session state machine already expresses the duality; agent resolution stays host authority (D32) docs(gui): RFC — v1 stays session-precision, no agent-level isolation; incarnation/agent-axis designs archived in ledger (D33) docs(gui): RFC walkthrough — full rewrite to final state (D16-D33 consolidated), end-to-end chain restored docs(gui): RFC — apiproxy demoted to generic channel routing; domain RPCs dissolve into owner plugins (D34) docs(gui): RFC — TS-interface-first wire contract (zod internal), conversation owns the dialogue frame with pluggable views (D35) docs(gui): RFC — page skeleton (sidebar+conversation), projects as plugin not service, nested slots via owner registries (D36) docs(gui): RFC — SlotMap declaration-merging slot model: single register API, inject-as-ownership, FC-typed registration, typed outlets (D37) docs(gui): RFC — slot props whitelist: identity, display params, materialized snapshot slices, stable UI callbacks (D38) docs(gui): RFC — end-to-end data flow: three transforms, equality protocol table, immer placement; i18n/theme kept standard (D39-D40) docs(gui): RFC — full external-injection model: props carry values + stable injected hooks; shared/client/react example rewritten (D41-D43) docs(gui): RFC final trio — modules.md (agent implementation spec), architecture.md (human walkthrough), plugins.md (business plugin inventory) docs(gui): RFC — props three-source merge (scope-standard useSession auto-injected); keyed key vs list id disambiguated (D44) docs(gui): RFC — inject comment says what it is (the React-facing props bundle); SessionHandle rename; snapshot-production story unified on buildSnapshot docs(gui): RFC architecture — full React component tree walkthrough: props three sources, slot vs plain children, hook taxonomy per node docs(gui): RFC — module map finalized (ui-slots/web-react/connection/runtime/ui-*/web); slots onChange replaced by cordis events; toolcall dimension; detail sidebar default-collapsed with toolName-keyed routing docs(gui): RFC plugins — openDetail relay chain: toolcard calls chat-view injected action, chat-view relays to conversation sidebar chore(gui): progress ledger — full archive rewrite: RFC outcome digest, open gaps, dispatch plan, cold-start entry docs(gui): RFC grill pass 1 — SlotScope axis (root/session) on declares, Gate dependency inversion, inject handle by scope, W5 acceptance list, gantt relay chain fixed docs(gui): figma analysis — sidebar/projects/sessions 区域交互视觉理解报告 docs(gui): figma 解析报告 — details 面板/多视图 tabs/未来功能区盘点 + slot 需求清单 docs(gui): figma 对话主区解析报告 — 消息流/tool calls 变体/审批接管输入框/Header tabs/视觉 token docs(gui): plugins.md rewritten from figma analysis — three-column layout, full slot reservation table, selection channel, composer-takeover approvals, phased scope docs(gui): layout dynamics ruled (drag+collapse both rails, details yields first, composer swap-panel, same-component transition); toolviews promoted to named scope-aware registry docs(gui): P-I scope locked (details minimal, dual theme, chat-view, custom toolview sample); teammate dispatch plan — 6 owners by package, dependency-driven waves, contract arbitration docs(gui): P-I api-contracts (full inter-package API spec) + dispatch plan (T0 skeleton knife, 7-dev roster, task briefs, milestones) docs(gui): api-contracts v2 — scope tree in P-I, bundle loader + per-plugin CSS isolation in P-I, agent-scoped toolviews live, zustand engine, renames (SessionProvider/ObservableSnapshot/SessionBinding), router owns all shell view-state docs(gui): services roster + progressive loading (no blocking loadAll), SlotsService as real cordis Service, renderSlot/renderSuspenseSlot duo, ui-traj teammate docs(gui): loading-chain gaps ruled — dev=rebundle no HMR, ui-primitives package, externals on globals (no import map), host injects __DSH_BOOT__ into HTML (zero round-trip) docs(gui): api-contracts v3 + dispatch v2 final — 12 packages, services merged in, progressive loader, global externals, __DSH_BOOT__ injection, 8-dev roster with convo split and ui-traj docs(gui): v3 amendments — router renamed ctx.layout, ui-trajectory has no service (pure consumer sample), wait-for-settled loading (no Suspense in P-I, ledger 6b) chore(gui): progress — pre-compact final state: v3 revision chain, 8-dev roster, T0 procedure, doc authority order docs(gui): authority banners — modules/architecture get v3 term-mapping headers, walkthrough marked as archived process doc docs(gui): cssdesign token set is THE theme source (--dsw-* variables, data-ds-dark-theme switch); recorded in contracts + progress docs(gui): architecture.md full v3 rewrite — loading chain, 12-package map, service roster, slot/inject/toolviews, data flow, component tree, perf model, all current docs(gui): contracts — UI plugins are dual-entry host plugins (node half serves client asset via ctx.webPlugins; __DSH_BOOT__ derives from it; client-closure gate back in scope) docs(gui): contracts — closure-factory bundles with DI require (no globals), package.json dshWeb declarative discovery (no serve ritual), create-then-send empty state with project picker, ancestry() for breadcrumb, unload stubbed until HMR, props.renderSlot confirmed docs(gui): dshClient declaration (inject/platform/immediately, exports./client), closure-DI require loading — synced across contracts/dispatch/modules/architecture/walkthrough chore(gui): progress — record final loading-chain rulings (dshClient declaration, closure-DI require, startSession) before compact docs(gui): architecture.md — developer-facing whole-web architecture on master baseline 6b16a67cb: what exists, what is new, no process narrative docs(gui): architecture.md — self-contained whole-web architecture: absorbs still-valid substance from the branch RFCs (host layering, four-quadrant RPC, object layer, testing tiers) under the new plugin system as the override chore(gui): progress — final pre-compact snapshot: contracts digest, apiproxy purity ruling, T0 procedure with first-action list docs(gui): api-contracts v3 §3.1 — apiproxy purity principle with three-way existing-code verdicts docs(gui): api-contracts v3 — immediately reinterpreted as static-infra group (8-package dshClient scope, boot manifest reconciliation) docs(gui): api-contracts v3 — immediately corrected to early-load dynamic group (prod shell must not rebundle); loader shell-held; bundles register their export surface into module table docs(gui): architecture — align with immediately=early-load dynamic group ruling; loader shell-held; module-table registration of loaded bundles docs(gui): T0 checklist — 12-package skeleton table, 4-cut sequence, mv/attic/rewire rules (pre-drafted, awaiting go) docs(gui): t0-checklist — pin figma-flows findings (missing font-family base vars, three alias vars behind upstream) docs(gui): dispatch v2.1 — drop cordis-web salvage wording, two-wave staffing, loader/immediately boundary updates docs(gui): progress + t0-checklist ledger — T0 landed, staffing status, execution accounting docs(gui): api-contracts v3 — arbitration round 1: renderBody deps, RootBindingProvider, flush default sync, prune current, loader subpath, config-source P-I bar docs(gui): v3 §3.2 connection 导出清单附录(rt-core 对账)+ rt-core 实现计划档案 docs(gui): progress — T1 milestone, arbitration round 1 ledger, fw-react timeout escalation docs(gui): progress rolling update — per-line battlefield state at 00:2x, mailbox-vs-contract lesson, small-batch discipline reinforced docs(gui): fw-react notes — v3 §2 complete, seven knives, T1/T2 follow-ups docs(fw-slots): archive — four packages landed, open tails logged docs(gui): progress — framework layer complete (web-react five, fw-slots four packages), T2 gated on rt-core runtime knife only docs: api-contracts docs: style-spec docs docs(gui): tsconfig convergence ruling — no host.json, root resumes host-aggregate duty, typecheck = root + client aggregates docs(gui): missions 根三份 07-18 世代档案加「已被取代」头注——指向 web-plugin-rfc 现行权威并注明新旧对应 missions docs(gui): progress rewritten for post-closeout state — wave ledger, architecture finale, teammate roster with handover notes, pending-user-command queue
6.1 KiB
全仓 package.json exports 形态盘点(2026-07-20)
调研输入:cordis-spike 的双端 exports 条件(customConditions)调研 + 后续「三入口规范」。只读盘点,零改动。范围:packages//(78)+ apps(2)+ vendor(9)+ python(1)= 108 个 manifest,以当前树为准。构型批(pr-gates)在途:client/* 两包与 host/apiproxy 的 src 指向预计会变,标注于表。
聚类总览
| 形态 | 数量 | 说明 |
|---|---|---|
A. 标准形:lib 入口 + ./src/* 透传 |
90 | .={types:lib/types, default:lib/index.js} + ./src/* + ./package.json。harness 绝对主流,vendor 8 包同形 |
| B. src 直入口(无 lib) | 2 | client/web-runtime、client/web-ui(GUI 期产物,构型批在改) |
| C. lib 入口 + 指向 src 的具名子路径 | 2 | core/session(./surface→src)、host/apiproxy(./api ./api/* ./client→src) |
| D. lib 入口 + 额外 lib 子路径(无 src 透传) | 3 | code-runtime-worker(./worker)、sdk/scripts(./dev/tsdown-config,bin)、apps/web(./dist/*) |
| E. lib 入口干净形(无 src 透传、无子路径) | 3 | core/agent-loop、sdk/create-sdk(bin)、sdk/helper |
| F. A 形 + 额外子路径 | 5 | 四个 examples demo(./bin,bin 包)+ workflow-workerthread(./worker) |
| G. 无 exports 无 main | 2 | apps/dsc(纯 bin)、python/sdk-runtime(pnpm 占位) |
| H. 只有 main 无 exports | 1 | vendor/schemastery(main=lib/index.cjs,唯一 CJS 主入口) |
① 导出 src 的包(用户点名)
./src/* 通配透传:95 包(A 形 90 + F 形 5)——即除 B/C 之外几乎全仓都留着 "./src/*": "./src/*" 后门。这是模板化产物(所有包同一份样板),不是逐包决策。
入口/具名子路径指向 src(比通配更实质的 src 导出):
| 包 | 指向 src 的座位 | 消费者(grep 实证) |
|---|---|---|
| client/web-runtime | main/types/. = src/index.ts |
apps/web、client/web-ui(构型批在改) |
| client/web-ui | main/types/. = src/index.tsx |
apps/web(构型批在改) |
| host/apiproxy | ./api→src/api/index.ts、./api/*→src/api/*.ts、./client→src/fetch/client.ts |
见 ③ |
| core/session | ./surface→src/surface.ts |
client/web-runtime/src/session/fold-adapter.ts(1 处) |
② GUI 新五包 + apps 现状
| 包 | main | exports 形态 | 备注 |
|---|---|---|---|
| client/web-runtime | src/index.ts | B(src 直入口) | 构型批在途→lib |
| client/web-ui | src/index.tsx | B(src 直入口) | 构型批在途→lib |
| host/apiproxy | lib/index.js | C(lib 入口+3 个 src 具名子路径) | src 子路径是「为 client 专门导出」的那部分,见 ③ |
| host/runtime | lib/index.js | A 标准形 | 已合规 |
| host/webserver | lib/index.js | A 标准形 | 已合规 |
| apps/dsc | (无,bin=lib/bin.js) | G | 纯 CLI,无库面 |
| apps/web | (无) | D(./dist/* 透传) |
唯一消费者 apps/dsc web.ts 的 require.resolve('@deepseek-ai/dsc-web/dist/index.html') |
③ apiproxy 子路径导出(「为 client 专门导出」部分)
| 子路径 | 指向 | 消费者(product 源码,grep 实证) |
|---|---|---|
./api |
src/api/index.ts | host/runtime(api-proxy.ts、start.ts)、client/web-runtime(api.ts、fixture.ts)、apps/dsc(headless.ts) |
./api/* |
src/api/*.ts | host/runtime(api/rpc)、client/web-runtime(api/rpc)、apps/dsc(api/rpc) |
./client |
src/fetch/client.ts | client/web-runtime/src/api.ts(re-export AbstractApiClient/IApiClient,仅此 1 文件) |
特征:三个子路径都指 src/*.ts 而非 lib——即使主入口已是 lib,双端共享的契约面走的还是 TS 源直连。这正是 cordis-spike customConditions 调研要解决的形态(browser 侧 vite 吃 TS 源没问题,node 侧要么 tsx 要么得走 lib)。「三入口规范」落地时 apiproxy 是首要改造对象。
④ src 路径 import 违例清单(「代码上尽量别再用」)
product 源码(src→src 跨包):0 处——干净。 测试代码:13 处,全部是「本包 tests/ import 本包 src/」(白盒测试形态,不跨包):
| 文件 | import |
|---|---|
| mcp-client/tests/mcp-client.spec.ts | 本包 src/tools.ts、src/transport.ts |
| mcp-client/tests/mcp-client.e2e.ts | 本包 src/index.ts、src/tools.ts |
| mcp-client/tests/apply.spec.ts | 本包 src/index.ts |
| hooks-codex/tests/config.spec.ts | 本包 src/config.ts |
| hooks-claude/tests/config.spec.ts | 本包 src/config.ts |
| core/tools/tests/ts-types.spec.ts | 本包 src/ts-types.ts |
| bash-sandbox/tests/bwrap.e2e.ts + seatbelt.e2e.ts | dsh-sandbox-local/src/profiles.ts(唯一真跨包×2) |
| compact-basic/tests/compact-basic.spec.ts | 本包 src/region.ts、src/config.ts |
| web-search-deepseek/tests/deepseek.spec.ts | 本包 src/types.ts |
vendor src import:全仓 0 处。结论:./src/* 通配的真实消费=测试白盒(且 11/13 是本包),砍掉通配对 product 代码零破坏,只需处理 bash-sandbox 两个 e2e 的跨包 src import + 本包白盒改相对路径(或规范豁免测试)。
⑤ 其他值得记录的形态
./worker子路径(workerthread、code-runtime-worker):指 lib/worker.cjs(CJS!worker 线程入口)。运行时自身不经包名消费(host.ts 用相对new URL('./worker.cjs', import.meta.url),dev 态 fallback./worker.ts),子路径是给外部/测试的正式座位。三入口规范时这类「非 index 的运行时资产」要单独归类。./bin子路径(4 examples):bin 包同时把 bin 入口暴露为库子路径(types+default 双条件,规范形),源码 @module 注释自证。- sdk/scripts
./dev/tsdown-config:构建工具链自消费(各包 tsdown.config.ts),lib 指向,规范形。 - vendor/logger-console:全仓唯一用 条件分支 exports 的包(
node:lib/index.js vsdefault:lib/browser.js)——cordis-spike 双端条件调研的现成 in-repo 先例。 - vendor/schemastery:全仓唯一无 exports 字段包(main=lib/index.cjs);上游原状,NodeNext 下靠 main 回退。
- core/agent-loop、sdk/helper、sdk/create-sdk:仅有的三个「无
./src/*」的 dsh 包——agent-loop 疑似有意收紧(核心循环不给后门),可作三入口规范的目标形参照。
附:原始数据
/tmp/exports-survey.json(本机,重跑 survey 脚本可再生;脚本一次性,未入库)。