From 9e6a1f8c3ec57539f4d937ca8c56d626cf4ff10e Mon Sep 17 00:00:00 2001 From: govin Date: Thu, 24 Sep 2026 10:55:06 +0800 Subject: [PATCH] docs: put the figure and the derived sentence fields in the MCP table --- docs/OVERVIEW.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/OVERVIEW.md b/docs/OVERVIEW.md index 9927a79..fbf1133 100644 --- a/docs/OVERVIEW.md +++ b/docs/OVERVIEW.md @@ -595,7 +595,7 @@ written by an agent is indistinguishable from one written by hand. What | Addition | Why the REST shape is wrong for a model | |---|---| -| 41 tools with `paper_` / `paragraph_` / `sentence_` / `template_` / `field_` / `reference_` / `reference_tag_` prefixes | a model picks a tool out of a list by its name, not by reading 41 descriptions | +| 42 tools with `paper_` / `paragraph_` / `sentence_` / `template_` / `field_` / `reference_` / `reference_tag_` / `image_` prefixes | a model picks a tool out of a list by its name, not by reading 42 descriptions | | JSON strings, `None`-free, no pagination envelope on reads | a tool result is paid for in context tokens | | `paragraph_write` addressed by **heading** as well as position | nobody writing "1. Introduction" knows the template places it at `sort = 20` | | `paper_write` / `paper_write_text` | "generate the paper, then put it in" is one intention, not thirty round trips | @@ -603,7 +603,9 @@ written by an agent is indistinguishable from one written by hand. What | `sentence_search` across papers | the job is consistency — one paper says 洪水损失, the next must not say GUL | | `reference_*` and `reference_tag_*` | the reference library is what makes a citation mean something; an agent that can cite id 42 but cannot look up what 42 *is* is writing blind | | `reference_import` | "here are the twenty references I cited" is one intention, and twenty round trips would spend twenty schemas on it | -| `line_break_before` on a sentence, and the display-formula rule in `document_text` | a paragraph is its sentences run together, so a formula, a list or an author line needs a way to say where the line starts — and the text an agent reads back has to break lines where the paper view breaks them, or the two disagree about what the manuscript looks like | +| `line_break_before` on a sentence, and the display-formula and figure rules in `document_text` | a paragraph is its sentences run together, so a formula, a list, an author line or a 插图 needs a way to say where the line starts — and the text an agent reads back has to break lines where the paper view breaks them, or the two disagree about what the manuscript looks like | +| `image_upload` taking base64 | the upload route is `multipart/form-data`, which a model cannot send; it has bytes and a tool argument, and it gets back the same Markdown and the same sentence the editor would have written | +| the sentence's own columns read from `SentenceInput` rather than listed | `line_break_before` and `formula_align` were each added to the domain, used by the editor and the API, and silently dropped by every MCP write path; the field set is now derived, and `smoke_mcp.py` fails if `specs.py` lags behind | Two transports are served from one build: `stdio`, which is what a client spawns, and `streamable-http`, which is what a client on another machine @@ -1108,7 +1110,10 @@ builds from a Dockerfile — so `deploy/build-mcp-image.sh` builds inside a throwaway privileged docker-in-docker pod, with the working tree mounted in through a hostPath so the build context is what you are actually looking at. The database is the in-cluster TiDB Service (`tidb-tidb.tidb:4000`), not the -NodePort the host uses. `deploy/README.md` has the commands, the two traps +NodePort the host uses, and the object store is the in-cluster MinIO Service +(`minio.minio.svc.cluster.local:9000`) rather than the host's `:30090` — the +same bucket either way, and neither address changes when the node's does. +`deploy/README.md` has the commands, the two traps worth knowing (a reused image tag silently keeps the cached image; `COPY` carries the working tree's `0600` file mode into the image and a non-root container then cannot read its own code), and how to add the REST API to the