vertex-palace 0.1.4 → 0.1.6

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.
Files changed (6) hide show
  1. package/BUILD_WEEK.md +79 -0
  2. package/CHANGELOG.md +44 -0
  3. package/README.md +80 -50
  4. package/dist/palace.cjs +35 -31
  5. package/package.json +5 -2
  6. package/plugins/vertex-palace/mcp/server.cjs +23 -23
package/BUILD_WEEK.md ADDED
@@ -0,0 +1,79 @@
1
+ # OpenAI Build Week
2
+
3
+ Vertex Palace is entering the Developer Tools track as a local context-routing and project-memory tool for Codex.
4
+
5
+ ## Eligibility Timeline
6
+
7
+ Vertex Palace existed before the OpenAI Build Week submission period. The pre-existing baseline is:
8
+
9
+ - Tag: `v0.1.4`
10
+ - Commit: `462bf56ad55e1a9394d72f249c2b905ee01e8f45`
11
+ - Baseline capabilities: repository indexing, task routes, context packs, task memory, CLI, MCP, and Codex plugin packaging
12
+
13
+ Only the work added after the submission period began is presented as Build Week work.
14
+
15
+ ## Submission-Period Work
16
+
17
+ ### Routing and indexing reliability
18
+
19
+ Commit `ce26cd66f99019a45e97787ffe1bdfe659541454` added stricter nested-repository ignores, stale room cleanup, more diverse route selection, fixture filtering, task-intent improvements, pitfall relevance changes, and regression tests.
20
+
21
+ ### Measurable route evaluation
22
+
23
+ Version 0.1.5 adds `palace evaluate` and the `palace_evaluate` MCP tool. The evaluator:
24
+
25
+ - compares estimated tokens for all indexed repository text with the actual context pack
26
+ - calculates changed-file coverage and route focus from files supplied after the task
27
+ - compares predicted route confidence with observed coverage
28
+ - labels confidence as well-calibrated, overconfident, underconfident, or unverified
29
+ - saves reproducible Markdown and JSON reports in `.palace/evaluations/`
30
+
31
+ This feature addresses a concrete limitation found during large-project use: a plausible-looking route and a high confidence value do not prove that the route included the files that ultimately mattered.
32
+
33
+ ## Codex And GPT-5.6 Collaboration
34
+
35
+ The submission-period work was developed with Codex using GPT-5.6. Codex was used to:
36
+
37
+ - run Vertex Palace against its own repository before implementation
38
+ - inspect the minimal routed context and expand only when the route omitted required CLI, MCP, and shared contracts
39
+ - translate real large-project feedback into measurable behavior and regression tests
40
+ - identify that the public npm/plugin pin still referenced the pre-submission baseline
41
+ - design the evaluation contract, implement the cross-package feature, and verify CLI and MCP behavior
42
+
43
+ Human product and engineering decisions included:
44
+
45
+ - keeping evaluation deterministic and local instead of adding a remote model or vector database
46
+ - treating changed-file coverage as observed evidence, not as a replacement for tests or runtime verification
47
+ - reporting route focus separately because useful dependency files may be routed without being edited
48
+ - refusing to publish a new plugin pin until the corresponding npm package exists and passes clean-install tests
49
+
50
+ The Devpost submission will include the `/feedback` Session ID from the primary Build Week development task.
51
+
52
+ ## Judge Quick Test
53
+
54
+ Install the public competition release, then run it in the repository you want to evaluate:
55
+
56
+ ```bash
57
+ npm install -g vertex-palace@0.1.6
58
+ palace --version
59
+ palace index
60
+ palace evaluate "improve route confidence calibration" --changed-file packages/core/src/evaluation/evaluate-route.ts
61
+ ```
62
+
63
+ The evaluation command prints a report and saves:
64
+
65
+ ```text
66
+ .palace/evaluations/latest-evaluation.md
67
+ .palace/evaluations/latest-evaluation.json
68
+ ```
69
+
70
+ The Codex plugin is pinned to the same npm release, so judges do not need to rebuild the project.
71
+
72
+ ## Verification Gates
73
+
74
+ - All workspace tests pass.
75
+ - TypeScript no-emit checks pass.
76
+ - The root CLI bundle builds.
77
+ - The bundled MCP server answers framed JSON-RPC `initialize` and `tools/list` requests.
78
+ - The npm tarball is installed and exercised from a clean temporary directory before publishing.
79
+ - The plugin MCP pin matches the published competition release.
package/CHANGELOG.md ADDED
@@ -0,0 +1,44 @@
1
+ # Changelog
2
+
3
+ ## Unreleased
4
+
5
+ ## 0.1.6 - 2026-07-19
6
+
7
+ ### Added
8
+
9
+ - `palace context` / `palace task` as the single task-entry command that initializes, refreshes, routes, and packs context when needed.
10
+ - `palace_context` MCP tool with route and drawer limits for compact agent context.
11
+ - End-to-end tests for one-call context setup on a previously uninitialized repository.
12
+
13
+ ### Changed
14
+
15
+ - Codex plugin, hook, generated guidance, and README now prefer one context call instead of separate status, init, index, route, and pack calls.
16
+ - Context packs produced through the task entry point omit excluded-area narration by default.
17
+ - MCP smoke coverage now requires the new one-call tool.
18
+
19
+ ### Fixed
20
+
21
+ - Reduced repeated agent tool calls and retry opportunities exposed by the A/B benchmark.
22
+ - Prevented routine task startup from spending context on redundant Palace lifecycle output.
23
+
24
+ ## 0.1.5 - 2026-07-18
25
+
26
+ ### Added
27
+
28
+ - `palace evaluate` / `palace eval` command for context-efficiency and route-quality measurement.
29
+ - `palace_evaluate` MCP tool.
30
+ - Persisted Markdown and JSON evaluation reports under `.palace/evaluations/`.
31
+ - Changed-file coverage, route focus, and route-confidence calibration.
32
+ - Build Week development and judging documentation.
33
+ - Windows, macOS, and Linux CI matrix.
34
+ - MCP stdio smoke test using Content-Length framed JSON-RPC messages.
35
+
36
+ ### Changed
37
+
38
+ - Evaluation tasks now route toward the dedicated evaluation subsystem.
39
+ - Scanner and router avoid nested repositories, stale rooms, duplicate source entries, and unrelated fixtures more aggressively.
40
+
41
+ ## 0.1.4
42
+
43
+ - Published the CLI and MCP server through the `vertex-palace` npm package.
44
+ - Added the unique `vertex-palace-mcp-stdio` executable to avoid stale local shim collisions.
package/README.md CHANGED
@@ -2,16 +2,18 @@
2
2
 
3
3
  Memory-palace context routing for Codex.
4
4
 
5
- Vertex Palace turns a repository into a local palace of floors, rooms, cabinets, and drawers. Before a coding task, Codex can ask for a route and receive a compact context pack instead of scanning the whole repository.
5
+ Vertex Palace turns a repository into a local palace of floors, rooms, cabinets, and drawers. Before a coding task, Codex can ask for a route and receive a compact context pack instead of scanning the whole repository.
6
+
7
+ OpenAI Build Week work is documented separately in [BUILD_WEEK.md](./BUILD_WEEK.md), including the pre-existing baseline, submission-period additions, Codex/GPT-5.6 collaboration, and judge verification steps.
6
8
 
7
9
 
8
- Name note: `记忆宫殿工具`, `记忆宫殿`, `memory palace`, `palace tool`, and the old name `Context Palace` all refer to Vertex Palace. The registered MCP tool names are `palace_status`, `palace_init`, `palace_index`, `palace_route`, `palace_pack`, and `palace_write_memory`; the CLI command is `palace`.
10
+ Name note: `记忆宫殿工具`, `记忆宫殿`, `memory palace`, `palace tool`, and the old name `Context Palace` all refer to Vertex Palace. The preferred MCP entry is `palace_context`; the preferred CLI entry is `palace context`. Lower-level `palace_status`, `palace_index`, `palace_route`, and `palace_pack` remain available for diagnosis and manual control.
9
11
 
10
12
  ## English Overview
11
13
 
12
14
  Vertex Palace is a local context-routing tool for Codex coding tasks. It organizes a repository into a memory-palace structure of floors, rooms, cabinets, and drawers, so Codex can find the most relevant files and code snippets before fixing bugs, adding features, or understanding modules.
13
15
 
14
- It is designed for large repositories, multi-client projects, and long-lived codebases. You can run `palace index` to build a local index, use `palace route` to find the task path, generate a compact context pack with `palace pack`, and write task memory after the work is done. By default, everything stays inside the local `.palace/` directory: no source upload, no external API calls, and no remote vector database.
16
+ It is designed for large repositories, multi-client projects, and long-lived codebases. Run `palace context "<task>"` once to initialize or refresh the local index when needed, plan the route, and return a compact context pack with the relevant pitfall board. Write task memory after the work is done. By default, everything stays inside the local `.palace/` directory: no source upload, no external API calls, and no remote vector database.
15
17
 
16
18
  Each route refreshes `.palace/routes/latest-route.json`, `.palace/routes/latest-route.md`, and `.palace/routes/optimized-route.txt`, so the most recent task route does not get stuck on an older task. Each memory write also updates `.palace/memory/latest-task.md`, `.palace/memory/task-log.md`, and `.palace/memory/index.json` while keeping the floor-based archive under `.palace/07-memory/`.
17
19
 
@@ -34,26 +36,26 @@ If you just want the agent to handle it, give your AI coding agent this prompt:
34
36
  ```text
35
37
  Open and read https://github.com/lohchanhin/vertex-palace, install Vertex Palace, then use it in this repository.
36
38
 
37
- Before working, check Vertex Palace status, initialize and index the repository if needed, route my task, generate a minimal context pack, inspect the routed files first, and write task memory after finishing.
39
+ Before working, call palace_context once with my exact task (or run palace context if only the CLI is available), inspect the routed files first, evaluate the route against the files actually changed, and write task memory after finishing.
38
40
  ```
39
41
 
40
42
  The agent should read the repository instructions, install the plugin or use the CLI, then follow this workflow:
41
43
 
42
44
  ```text
43
- status -> init/index if needed -> route -> pack -> inspect routed files -> implement -> test -> memory write
45
+ context (auto init/index/route/pack) -> inspect routed files -> implement -> test -> evaluate -> memory write
44
46
  ```
45
47
 
46
- Before following a route, the agent should read `.palace/00-entrance/pitfall-board.md` when it exists.
48
+ The context pack includes the relevant entries from `.palace/00-entrance/pitfall-board.md` before source drawers.
47
49
 
48
50
  ### Manual Mode: Step By Step
49
51
 
50
52
  1. Install the plugin:
51
53
 
52
54
  ```bash
53
- codex plugin marketplace add lohchanhin/vertex-palace --ref v0.1.4
55
+ codex plugin marketplace add lohchanhin/vertex-palace --ref v0.1.6
54
56
  ```
55
57
 
56
- Use `v0.1.4` or newer. Avoid `v0.1.0` and `v0.1.1`; those early tags had broken MCP install metadata.
58
+ Use `v0.1.6` or newer. Avoid `v0.1.0` and `v0.1.1`; those early tags had broken MCP install metadata.
57
59
 
58
60
  2. Or install the CLI directly from npm:
59
61
 
@@ -70,15 +72,13 @@ npx vertex-palace status
70
72
 
71
73
  3. Open Codex and install Vertex Palace from `/plugins`.
72
74
 
73
- 4. Initialize and index a repository:
75
+ 4. Prepare task context in one call:
74
76
 
75
77
  ```bash
76
- palace init
77
- palace index
78
- palace status
78
+ palace context "fix login refresh token bug" --budget 6000 --route-limit 8 --max-drawers 4 --out .palace/last-pack.md
79
79
  ```
80
80
 
81
- 5. Before each task, create a route and context pack:
81
+ 5. Use the lower-level commands only when diagnosing or manually controlling the route:
82
82
 
83
83
  ```bash
84
84
  palace route "fix login refresh token bug" --limit 8 --compact
@@ -116,21 +116,21 @@ cat .palace/memory/task-log.md
116
116
 
117
117
  ### Troubleshooting: Agent Does Not Recognize The Tool
118
118
 
119
- If a Codex thread says it does not know the "memory palace tool" or `记忆宫殿工具`, it usually means the Vertex Palace plugin or MCP server is not loaded in that thread. The Chinese name is an alias; the actual tool names are `palace_status`, `palace_route`, `palace_pack`, and the other `palace_*` MCP tools.
119
+ If a Codex thread says it does not know the "memory palace tool" or `记忆宫殿工具`, it usually means the Vertex Palace plugin or MCP server is not loaded in that thread. The Chinese name is an alias; the preferred MCP tool is `palace_context`.
120
120
 
121
- Fix it by installing Vertex Palace from `/plugins`, trusting the plugin when prompted, and starting a new Codex thread or restarting Codex so the skill, hooks, and MCP tools reload. If only the CLI is available, ask the agent to use `palace status`, `palace index`, `palace route`, and `palace pack`.
121
+ Fix it by installing Vertex Palace from `/plugins`, trusting the plugin when prompted, and starting a new Codex thread or restarting Codex so the skill, hooks, and MCP tools reload. If only the CLI is available, ask the agent to run `palace context "<task>"`.
122
122
 
123
123
  ## 简体中文说明
124
124
 
125
125
  Vertex Palace 是一个面向 Codex 编程任务的本地上下文路由工具。它会把代码仓库整理成“楼层、房间、柜子、抽屉”的空间结构，让 Codex 在开始修 bug、加功能或理解模块前，先找到最相关的文件与代码片段，而不是每次都从整个仓库重新扫描。
126
126
 
127
- 它适合大型项目、多客户项目和长期维护型项目：你可以先用 `palace index` 建立本地索引，再用 `palace route` 找到任务路径，用 `palace pack` 生成精简上下文包，并在任务结束后写入成功路径、失败路径和决策记忆。所有数据默认保存在本机 `.palace/` 目录中，不上传源码，也不依赖远程向量数据库。
127
+ 它适合大型项目、多客户项目和长期维护型项目：每次任务只要运行一次 `palace context "<任务>"`，工具会在需要时自动初始化或刷新索引、规划路线，并返回包含相关踩坑记录的精简上下文包。任务结束后再写入成功路径、失败路径和决策记忆。所有数据默认保存在本机 `.palace/` 目录中，不上传源码，也不依赖远程向量数据库。
128
128
 
129
129
  每次路由都会刷新 `.palace/routes/latest-route.json`、`.palace/routes/latest-route.md` 和 `.palace/routes/optimized-route.txt`，避免“最近任务路线”停留在旧任务。每次写入记忆也会更新 `.palace/memory/latest-task.md`、`.palace/memory/task-log.md` 和 `.palace/memory/index.json`，同时保留 `.palace/07-memory/` 的楼层归档。
130
130
 
131
131
  第一层入口还会有一个踩坑告示牌：`.palace/00-entrance/pitfall-board.md`。当任务写入 `--pitfall` 或 `--failed-attempt` 时，Vertex Palace 会更新这个告示牌，并在后续 context pack 的前段显示它，让 Codex 在读路线抽屉前先看到之前踩过的坑。
132
132
 
133
- 名称说明：`记忆宫殿工具`、`记忆宫殿`、`memory palace`、`palace tool` 和旧名字 `Context Palace` 都是 Vertex Palace。真正注册到 Codex 的 MCP 工具名是 `palace_status`、`palace_init`、`palace_index`、`palace_route`、`palace_pack` 和 `palace_write_memory`；命令行工具名是 `palace`。
133
+ 名称说明：`记忆宫殿工具`、`记忆宫殿`、`memory palace`、`palace tool` 和旧名字 `Context Palace` 都是 Vertex Palace。建议优先使用 MCP 工具 `palace_context`，命令行对应 `palace context`；status、index、route、pack 等底层命令继续保留给排障和手动控制。
134
134
 
135
135
  ## 设计理念
136
136
 
@@ -149,38 +149,36 @@ Vertex Palace 是一个面向 Codex 编程任务的本地上下文路由工具
149
149
  ```text
150
150
  请打开并阅读 https://github.com/lohchanhin/vertex-palace，安装 Vertex Palace，然后在当前项目使用它。
151
151
 
152
- 开始任务前，请先检查 Vertex Palace 状态；如果还没初始化或索引过，就先 init/index；然后根据我的任务 route，生成最小 context pack，优先阅读路线推荐文件，完成后把改动文件、测试结果、决策和踩坑写入 memory。
152
+ 开始任务前，请针对我的完整任务调用一次 palace_context；如果当前只有命令行，就运行 palace context。优先阅读返回的路线文件，完成后评估路线，并把改动文件、测试结果、决策和踩坑写入 memory。
153
153
  ```
154
154
 
155
155
  它应该照这个流程做：
156
156
 
157
157
  ```text
158
- status -> 需要时 init/index -> route -> pack -> 先读路线文件 -> 执行任务 -> 测试 -> 写入 memory
158
+ context（自动 init/index/route/pack）-> 先读路线文件 -> 执行任务 -> 测试 -> evaluate -> 写入 memory
159
159
  ```
160
160
 
161
- 执行 route 前，agent 应该先读 `.palace/00-entrance/pitfall-board.md`，避免重复踩坑。
161
+ context pack 会在源码抽屉之前带上 `.palace/00-entrance/pitfall-board.md` 中与任务相关的记录，避免重复踩坑。
162
162
 
163
163
  ### 勤劳用法：自己一步一步跑
164
164
 
165
165
  1. 安装插件：
166
166
 
167
167
  ```bash
168
- codex plugin marketplace add lohchanhin/vertex-palace --ref v0.1.4
168
+ codex plugin marketplace add lohchanhin/vertex-palace --ref v0.1.6
169
169
  ```
170
170
 
171
- 请使用 `v0.1.4` 或更新版本。不要再使用 `v0.1.0` 和 `v0.1.1`，这两个早期标签的 MCP 安装元数据有问题。
171
+ 请使用 `v0.1.6` 或更新版本。不要再使用 `v0.1.0` 和 `v0.1.1`，这两个早期标签的 MCP 安装元数据有问题。
172
172
 
173
173
  2. 打开 Codex，输入 `/plugins`，安装 Vertex Palace。
174
174
 
175
- 3. 在项目里初始化并建立索引：
175
+ 3. 每次任务前用一个命令准备上下文：
176
176
 
177
177
  ```bash
178
- palace init
179
- palace index
180
- palace status
178
+ palace context "fix login refresh token bug" --budget 6000 --route-limit 8 --max-drawers 4 --out .palace/last-pack.md
181
179
  ```
182
180
 
183
- 4. 每次任务前先规划路线和上下文包：
181
+ 4. 只有排障或需要手动控制时，才分别执行底层命令：
184
182
 
185
183
  ```bash
186
184
  palace route "fix login refresh token bug" --limit 8 --compact
@@ -218,9 +216,9 @@ cat .palace/memory/task-log.md
218
216
 
219
217
  ### 排障：AI Agent 说不认识“记忆宫殿工具”
220
218
 
221
- 如果某个 Codex 线程说不认识“记忆宫殿工具”，通常不是项目坏了，而是那个线程还没有加载 Vertex Palace 插件或 MCP server。中文叫法只是别名，实际工具名是 `palace_status`、`palace_route`、`palace_pack` 等 `palace_*` 工具。
219
+ 如果某个 Codex 线程说不认识“记忆宫殿工具”，通常不是项目坏了，而是那个线程还没有加载 Vertex Palace 插件或 MCP server。中文叫法只是别名，建议它查找并调用 `palace_context`。
222
220
 
223
- 处理方式：先在 Codex 的 `/plugins` 安装并启用 Vertex Palace，按提示信任插件，然后新开一个 Codex 线程或重启 Codex，让 skill、hooks 和 MCP 工具重新加载。如果当前环境只有命令行可用，就让 agent 改用 `palace status`、`palace index`、`palace route` 和 `palace pack`。
221
+ 处理方式：先在 Codex 的 `/plugins` 安装并启用 Vertex Palace，按提示信任插件，然后新开一个 Codex 线程或重启 Codex，让 skill、hooks 和 MCP 工具重新加载。如果当前环境只有命令行可用，就让 agent 运行 `palace context "<任务>"`。
224
222
 
225
223
  ## Install
226
224
 
@@ -240,15 +238,15 @@ npx vertex-palace status
240
238
  Install the Codex plugin:
241
239
 
242
240
  ```bash
243
- codex plugin marketplace add lohchanhin/vertex-palace --ref v0.1.4
241
+ codex plugin marketplace add lohchanhin/vertex-palace --ref v0.1.6
244
242
  ```
245
243
 
246
- Use `v0.1.4` or newer; `v0.1.0` and `v0.1.1` are obsolete because their MCP install metadata was broken.
244
+ Use `v0.1.6` or newer; `v0.1.0` and `v0.1.1` are obsolete because their MCP install metadata was broken.
247
245
 
248
246
  The plugin launches its MCP server through npm:
249
247
 
250
248
  ```bash
251
- npx -y -p vertex-palace@0.1.4 vertex-palace-mcp-stdio --stdio
249
+ npx -y -p vertex-palace@0.1.6 vertex-palace-mcp-stdio --stdio
252
250
  ```
253
251
 
254
252
  Open Codex:
@@ -282,26 +280,49 @@ This creates:
282
280
  Use Vertex Palace before fixing this bug: fix login refresh token bug
283
281
  ```
284
282
 
285
- Codex should route first, pack only the useful drawers, inspect those files, and write memory after the task.
286
-
287
- ## CLI
283
+ Codex should call `palace_context` once, inspect the returned drawers, and write memory after the task.
288
284
 
289
- ```bash
290
- palace init
291
- palace status
292
- palace index
293
- palace route "fix login refresh token bug"
294
- palace pack "fix login refresh token bug" --budget 12000
295
- palace doctor
296
- ```
285
+ ## CLI
286
+
287
+ ```bash
288
+ palace init
289
+ palace status
290
+ palace index
291
+ palace context "fix login refresh token bug" --budget 6000
292
+ palace route "fix login refresh token bug"
293
+ palace pack "fix login refresh token bug" --budget 12000
294
+ palace evaluate "fix login refresh token bug" \
295
+ --changed-file src/auth/token.service.ts \
296
+ --changed-file tests/auth.test.ts
297
+ palace doctor
298
+ ```
299
+
300
+ ### Route Evaluation
301
+
302
+ Vertex Palace 0.1.5 adds `palace evaluate` (alias: `palace eval`). It measures whether the route was actually useful instead of trusting route confidence alone:
303
+
304
+ - estimated tokens for all indexed repository text versus the generated context pack
305
+ - token reduction and repository-to-pack ratio
306
+ - changed-file coverage and route focus
307
+ - confidence calibration, including explicit overconfidence warnings
308
+ - persisted Markdown and JSON reports under `.palace/evaluations/`
309
+
310
+ Run it after a task and provide the files that were really changed:
311
+
312
+ ```bash
313
+ palace evaluate "fix checkout shipping bug" \
314
+ --changed-file frontend/app/checkout/page.tsx \
315
+ --changed-file backend/src/shipping/quote.service.ts
316
+ ```
317
+
318
+ Without `--changed-file`, the command still measures context efficiency but marks route quality and confidence calibration as `unverified`.
297
319
 
298
320
  ### Token-Saving Workflow
299
321
 
300
- For large repositories, write packs to disk and keep the first pass intentionally small:
322
+ For large repositories, use the one-call compact workflow and keep the first pass intentionally small:
301
323
 
302
324
  ```bash
303
- palace route "fix checkout shipping bug" --limit 8 --compact --out .palace/last-route.txt
304
- palace pack "fix checkout shipping bug" --budget 6000 --route-limit 8 --max-drawers 4 --compact --out .palace/last-pack.md
325
+ palace context "fix checkout shipping bug" --budget 6000 --route-limit 8 --max-drawers 4 --out .palace/last-pack.md
305
326
  ```
306
327
 
307
328
  For multi-client repositories, isolate task memory with a client label:
@@ -318,9 +339,16 @@ palace memory write \
318
339
  --notes "Kept shipping rules configurable."
319
340
  ```
320
341
 
321
- ## Privacy
342
+ ## Privacy
322
343
 
323
- Vertex Palace runs locally by default. It does not upload source code, call external APIs, use embeddings, or create a remote index.
344
+ Vertex Palace runs locally by default. It does not upload source code, call external APIs, use embeddings, or create a remote index.
345
+
346
+ ## Supported Platforms
347
+
348
+ - Node.js 20 or newer
349
+ - Windows, macOS, and Linux are covered by the repository CI matrix
350
+ - Windows is additionally verified through local CLI, npm package, and MCP stdio smoke tests
351
+ - Codex plugin users should start a new task or restart Codex after installing or updating the plugin so its skill and MCP tools reload
324
352
 
325
353
  ## Current Capabilities / 目前能力
326
354
 
@@ -330,8 +358,10 @@ Vertex Palace runs locally by default. It does not upload source code, call exte
330
358
  - Indexes for nodes, edges, rooms, symbols, directory tree, hashes, and routes
331
359
  - Route planner with task classification, confidence, reasons, and excluded areas
332
360
  - Latest route files: `latest-route.json`, `latest-route.md`, and `optimized-route.txt`
333
- - Markdown and JSON context packer
334
- - Task memory ledger: `latest-task.md`, `task-log.md`, and `index.json`
361
+ - Markdown and JSON context packer
362
+ - One-call `palace_context` / `palace context` workflow with automatic initialization, fresh indexing, routing, and compact packing
363
+ - Route evaluation reports with Token reduction, changed-file coverage, route focus, and confidence calibration
364
+ - Task memory ledger: `latest-task.md`, `task-log.md`, and `index.json`
335
365
  - Entrance pitfall board: `.palace/00-entrance/pitfall-board.md`
336
366
  - CLI
337
367
  - MCP stdio server