rungent v0.5.1
EN中文

rungent更新日志

更新日志

每个 rungent 版本改了什么,最新的在前。npm 包 rungent 与 Python 包 rungent 共用一个版本号。

Unreleased

0.5.1 (2026-11)

  • Release: the PyPI jobs can check out the repository (their id-token permission had dropped contents: read), so rungent and rungent-argos reach PyPI. No code changes.

0.5.0 (2026-11)

Breaking: aidy is now rungent

Every name changes at once, with no aliases: the package, the command, the Python import, the protocol, the environment, the tables, the TypeScript API and the CSS. The repository is https://github.com/rungent/rungent and the site https://rungent.dev. Behavior is unchanged.

What 0.4 (aidy) 0.5 (rungent)
npm package @aidy-dev/aidy rungent (same subpaths: rungent/react, rungent/react/styles.css, rungent/client, rungent/node, rungent/sql/*, rungent/knowledge, rungent/documents, rungent/protocol, rungent/catalog, rungent/delegation, rungent/search, rungent/cli)
Source export condition @aidy-dev/source rungent-source
Command aidy (aidy serve, aidy keys generate, aidy check, aidy brand, …) rungent (npx rungent serve, …)
Built-in CLI prefix aidy:<command> rungent:<command>
CLI login file and cache ~/.config/aidy/hosts.json, ~/.cache/aidy ~/.config/rungent/hosts.json, ~/.cache/rungent (log in again)
Python distribution aidy (saidc index) rungent on PyPI (pip install "rungent[fastapi]")
Python import aidy, aidy.fastapi, aidy.delegation, … rungent, rungent.fastapi, rungent.delegation, …
Python names AidyCall, AidyHost, AidyAssertionError, strip_aidy_headers, request.state.aidy RungentCall, RungentHost, RungentAssertionError, strip_rungent_headers, request.state.rungent
Argos suite aidy-argos, aidy_argos, pack:aidy, AIDY_* target variables rungent-argos on PyPI, rungent_argos, pack:rungent, RUNGENT_*
Server image ghcr.io/aidy-dev/aidy-server ghcr.io/rungent/rungent-server (entrypoint rungent serve)
OpenAPI extension x-aidy (spec/schemas/x-aidy.schema.json) x-rungent (spec/schemas/x-rungent.schema.json)
HTTP API /aidy/v0/* /rungent/v0/* (/mcp, /skill.md, /llms.txt unchanged)
Public keys /.well-known/aidy-keys.json /.well-known/rungent-keys.json
Assertion headers Aidy-Assertion, Aidy-Host-Assertion Rungent-Assertion, Rungent-Host-Assertion
Assertion typ aidy-call+jwt rungent-call+jwt (claim names unchanged)
Error code aidy_assertion_invalid rungent_assertion_invalid
Admin scope aidy:admin rungent:admin
Protocol id aidy/0 rungent/0
AG-UI profile metadata.aidy, MCP _meta.aidy, CUSTOM aidy.*, activity aidy.progress metadata.rungent, _meta.rungent, rungent.*, rungent.progress
Interrupt reasons aidy:approval, aidy:input, aidy:form, aidy:task rungent:approval, rungent:input, rungent:form, rungent:task
Environment AIDY_* (AIDY_URL, AIDY_SECRET, AIDY_SIGNING_KEY, AIDY_DATABASE_URL, AIDY_NAME, AIDY_KNOWLEDGE_DIR, …) and the generic CLI's AIDY_HOST/AIDY_TOKEN RUNGENT_*, the same suffixes (RUNGENT_HOST/RUNGENT_TOKEN); branded CLIs keep their own prefix
Tables aidy_* and aidy_migrations rungent_* and rungent_migrations
TypeScript createAidy, Aidy, AidyConfig, AidyEvent, AidyClient, AidyRequestError, AidyProtocolError, XAidy createRungent, Rungent, RungentConfig, RungentEvent, RungentClient, RungentRequestError, RungentProtocolError, XRungent
React AidyProvider, AidyDock, AidyThread, AidyForm and their *Props RungentProvider, RungentDock, RungentThread, RungentForm and their *Props
Strings askAidy askAssistant
CSS classes .aidy-*, variables --aidy-*, attributes data-aidy-*, SCROLL_CLASS aidy-scroll .rungent-*, --rungent-*, data-rungent-*, rungent-scroll
Browser storage aidy:dock:<origin> rungent:dock:<origin> (the dock opens in its default state once)
Skill https://aidy.acahti.dev/skills/aidy/SKILL.md https://rungent.dev/skills/rungent/SKILL.md
  • The assistant's default name is Assistant. The name users see is the host's setting: name in createRungent, RUNGENT_NAME for rungent serve, the React strings. A product that showed the default "Aidy" sets RUNGENT_NAME=Aidy (or name: 'Aidy') to keep it.
  • Databases migrate themselves. On start, Postgres, SQLite and D1 deployments rename the ledger aidy_migrations to rungent_migrations; migration core/003_rungent renames the aidy_* tables, keys and indexes and rewrites the stored profile names (metadata.aidy, aidy.* events, aidy:* reasons) in events, messages, runs, interrupts and tasks, and knowledge/002_rungent renames the knowledge tables, sequence, FTS index and triggers. Threads, open approvals, feedback, settings and the host's own migrations are kept. Settings sealed by 0.4 open with the same secret.
  • Releases. rungent and rungent-argos publish to pypi.org from the release workflow by trusted publishing; scripts/version.mjs keeps npm, the Python kit and the Argos suite on one version.

0.4.2 (2026-11)

  • Routing never fails a run. The routing call sees the thread's earlier calls, and a model sometimes named one of them (a read it was not offered); that counted as an unusable answer, was retried on every endpoint and ended the run with model_unavailable, so a follow-up such as "it exists, look again" got no answer. Any routing answer is now a choice: a tool it was not offered goes on to the loop like continue. Conformance case forms/routing-ignores-tools-it-was-not-offered; the conformance runner fails a case whose scripted routing answer is retried. Found by TurboMesh's Argos pack.

0.4.1 (2026-11)

  • Dock: a call that did not run says so in the dock's language ("Not run" / "未执行") instead of the English message written for the model.
  • Dock: replayed answers show as they arrive. On a slow connection, history streamed after a reload was revealed like live text again; an answer that began more than 5 s before it mounted is shown as it comes.
  • Runtime: no text before or between tool calls. The system prompt asks for one answer after the last tool result, since the dock shows each call live. Hosts can drop the same rule from their instructions.

0.4.0 (2026-11)

Breaking

  • One npm package. @aidy-dev/aidy replaces the nine @aidy-dev/* packages; each became a subpath. Replace the imports and dependencies:

    Before After
    @aidy-dev/core @aidy-dev/aidy
    @aidy-dev/server @aidy-dev/aidy/node
    @aidy-dev/sql, /postgres, /sqlite, /d1 @aidy-dev/aidy/sql, /sql/postgres, /sql/sqlite, /sql/d1
    @aidy-dev/knowledge @aidy-dev/aidy/knowledge
    @aidy-dev/documents @aidy-dev/aidy/documents
    @aidy-dev/client @aidy-dev/aidy/client
    @aidy-dev/react, @aidy-dev/react/styles.css @aidy-dev/aidy/react, @aidy-dev/aidy/react/styles.css
    @aidy-dev/spec/catalog, /delegation, /protocol, /search @aidy-dev/aidy/catalog, /delegation, /protocol, /search
    @aidy-dev/cli @aidy-dev/aidy/cli (library), bin aidy

    react and react-dom are optional peer dependencies; postgres comes with the package. Branded CLIs depend on @aidy-dev/aidy and import run from @aidy-dev/aidy/cli (rerun aidy brand). The default CLI install line in /skill.md is npm i -g @aidy-dev/aidy.

  • aidy serve replaces aidy-server serve; there is no aidy-server bin. aidy-server keys is gone: aidy keys generate --kid <id> writes the private JWK for AIDY_SIGNING_KEY. aidy --version prints the version.

  • Image: ghcr.io/aidy-dev/aidy-server installs @aidy-dev/aidy and its entrypoint is aidy serve.

  • CLI search is the host's product search (its MCP search tool), as /skill.md says; it no longer lists commands, and there is no aidy:search. aidy tools <words> finds commands.

Runtime

  • The model's reasoning streams to the user. When a model returns reasoning (qwen or Anthropic thinking, OpenAI reasoning summaries), each step emits it before its text and tool calls as AG-UI REASONING_START, REASONING_MESSAGE_START/_CONTENT/_END and REASONING_END, recorded with the thread so replay shows it; the dock renders it as a live reasoning item. It never goes back to the model, nor into MCP, CLI or host job results; encrypted reasoning emits nothing. Conformance cases reasoning/streamed-to-user-only and reasoning/retry-discards-reasoning.

Dock (@aidy-dev/aidy/react)

  • The run shows its work. Each step says what it did, live: the search query, its result count and hit titles; an operation's title, key arguments and item count; approvals and forms waiting; errors with their message; the model's reasoning; and each step's time. A finished run folds to one line (Searched · List servers · 9.4s). ThreadItem gains reasoning items, and items carry startedAt/endedAt. String keys lookups, lookup, thinkingFor, toolRunning and toolSucceeded are replaced by trace* keys.
  • One-card composer. The input grows with its text up to 10 lines, then scrolls, and shrinks after sending; IME composition never sends. The context ring and attach sit on the left under the text, send and stop on the right.
  • Quiet scrollbars. No tracks; a thin thumb shows only while the user scrolls. Hosts can use the same look: SCROLL_CLASS, useScrollbar(ref), watchScrollbar(el), --aidy-scroll-thumb.
  • The open dock stays put across navigation. Open state, width, thread and view live in a store that survives remounts and is read before the first paint; the open animation runs only when the user opens it. Mount AidyProvider and AidyDock once, in the root layout.

Docs

  • The site opens with the problem, what aidy is and the one sentence that installs the new developer skill (/skills/aidy/SKILL.md); 29 pages become 16 per language, and removed pages redirect.

Fixes

  • Role operations default to effect: read, so a role: form operation needs neither effect: read nor approval: never spelled out. Conformance case forms/form-operation-is-a-read.
  • host.fetch takes any handler from Request to Response | Promise<Response>, so Hono's app.fetch fits without a wrapper (type HostFetch).

0.3.2 (2026-11)

  • Workers: no promise shared between requests. The runtime kept the in-flight promise of its first migration (and of two key derivations) and let later requests await it. workerd cancels a promise when the request that created it ends, so on Cloudflare Workers one early-ending first request could fail every later request of the isolate. Only settled results are kept now; concurrent first requests each migrate (migrations lock and skip what is applied). Found in Pipetil's production; the homepage's Worker had the same pattern.
  • Hosts on the Workers Free plan should run aidy in a Durable Object: a run takes more than the plan's 10 ms of CPU per request (Pipetil measured 144 ms for a staff run).

0.3.1 (2026-11)

  • Routing sees every write. It offered only the operations with a form, so with a required choice a smaller model sent "stop the server gpu-train-01" to the create form. It now offers every write the agent may call and acts only on one with a form; any other pick goes to the loop as before. Conformance case forms/routing-leaves-other-writes-to-the-loop.
  • Site rebuilt the acahti.dev way: Markdown in docs/product/ (English and Chinese with the same headings), built by site/build.mjs into static pages with an architecture figure drawn at build time, markdown twins, llms.txt and llms-full.txt, and checked links; the Worker keeps the dock, ⌘K, /mcp and the Playground. Pages moved from /docs/<group>/<page>/ to /<page>/; the old addresses redirect.

0.3.0 (2026-11)

Host forms become an operation's one input path, and the React dock sits beside the page.

Breaking

  • Interrupt aidy:form for an operation's host form (x-aidy.form). metadata.aidy is {op, arguments, form, issues?} and the resume payload is {arguments: {...}}, the operation's complete arguments; responseSchema is {arguments: <input schema>}. Host forms used to arrive as aidy:input and resume with {answers}.
  • aidy:input is only the model's request_input (which thing or which action), resumed with {answers}.
  • @aidy-dev/client: answerForm is gone. answerInput(interrupt, answers) answers aidy:input; submitForm(interrupt, args) and submitFormAnswers(interrupt, answers) submit aidy:form. OpenInterrupt gains FormInterrupt (kind: 'form', meta).
  • @aidy-dev/react: AidyDock wraps the page, <AidyDock>{page}</AidyDock>. The open panel takes its room from the page instead of covering it; without children it is fixed at the window's right edge and the document gives up its width. --aidy-dock-width no longer sets the panel's width; the user drags it.

Runtime (@aidy-dev/core, @aidy-dev/spec)

  • Host forms: arguments the model got wrong are left out and the form opens with the rest, so the model never gets invalid_arguments for an operation with a form. A submission that fails the input schema opens the form again, starting from it, with issues by argument path; nothing runs. One that fits goes on to resolve, lookup and approval.
  • Routing: when the catalog has operations with a host form, every run that appends a user message first makes one quiet model call that sees only those operations and continue. A message that asks to create or change something one of them does is recorded as the assistant's call to it, and its form opens; the model loop does not run. Anything else (text included) goes on to the loop and leaves no events. Measured on TurboMesh: the form opened in 11 of 21 create requests before and in 21 of 21 after, while 9 of 9 questions were still answered in the conversation.
  • System prompt holds the input rule (call an operation with only what the user said; never collect its inputs in text or with request_input) and the knowledge rule (answer product questions from tool results and search hits only, and cite them). request_input's description says the same.
  • Grounding: with knowledge sources, each run that appends a user message starts with a search for the message's text (200 characters, limit 5) before the first model step, recorded as an ordinary search call so its hits can be cited.
  • Validation issues name a missing property at its own path (zone_id, required).
  • @aidy-dev/spec/protocol exports FormInterruptMeta, FormSubmission, FormIssue, submissionResponseSchema and answersToArguments; JSON schemas form-interrupt and form-submission.

Client and React (@aidy-dev/client, @aidy-dev/react)

  • forms on AidyProvider: the product's own form components by operation name (ComponentType<HostFormProps>, with {op, arguments, issues, submit, cancel}), rendered prefilled in the conversation. Operations without one get AidyForm with the generic form, which takes values, issues and onCancel.
  • suggestions on AidyProvider: () => string[] preset questions on an empty conversation, under a new welcome.
  • Dock layout: resizable 360–640 px (drag, arrow keys, Home/End, double-click to reset; DOCK_WIDTH), width remembered; expand mode with the history beside the conversation; full screen at 640 px and below; onLayoutChange(layout) (DockLayout); launcher prop; CSS variable --aidy-dock-top for a fixed header. Header actions are icon buttons.
  • Conversation: streaming text revealed at a steady pace with a caret; stick to the bottom with a "Jump to the latest" button; "Thinking for Ns"; context usage as a ring with a tooltip (amber at 70%, red at 90%); the composer grows with its text and takes focus back after an answer.

Conformance

  • New cases forms/routing-opens-form, forms/invalid-arguments-open-form, forms/invalid-submission-reopens-form and search/knowledge-before-first-step; forms/host-form-before-approval uses aidy:form. A case's model turn may answer routing (routing: true); routing calls a case does not script are answered with continue.

Other

  • Argos suite (argos/, pack aidy): contract cases and agent metrics (task success, tool precision and recall, argument validity, safety, forms, citations, latency, tokens, cost) for any product that integrates aidy, with targets for the Playground, TurboMesh, 鲲之源, Pipetil and Acahti. Guide: Testing your integration; results: Agent metrics.
  • Homepage and docs moved to https://aidy.acahti.dev; the old workers.dev address redirects there (301, or 308 for writes). Package homepage fields point to the new address.

0.2.4 (2026-11)

  • Deleting a thread cancels its run in progress. An event that cannot be recorded (its thread was deleted) fails that run without resting the model endpoint; it used to rest the only endpoint, so every user got model_unavailable for five minutes. Found in TurboMesh's office regression.

0.2.3 (2026-11)

  • MCP search refuses unknown arguments (it silently ignored the removed types).
  • MCP initialize returns instructions: mcp.instructions (AIDY_MCP_INSTRUCTIONS), by default the skill guide.

0.2.2 (2026-11)

  • GET /aidy/v0/info needs no credential: UIs on cookie hosts fetch the assistant's name before sign-in.
  • @aidy-dev/react: the history list's delete button is always visible on touch screens (it appeared only on hover, so phones could not delete a thread).

0.2.1 (2026-11)

  • Operations with a host form are offered to the model without required fields and with a note that a form collects the rest, so models call them with only what the user said (they used to answer in prose instead, and the form never appeared).
  • Identity and catalog errors: any 4xx from the host's identity operation or OpenAPI document means the credential was refused (401); a 5xx or an invalid answer is 502 host_unavailable (was 500 internal).
  • product: { name, summary? } (AIDY_PRODUCT_NAME, AIDY_PRODUCT_SUMMARY) names the product in /skill.md and /llms.txt for signed-out callers when the OpenAPI needs a sign-in.

0.2.0 (2026-11)

Gaps found by four product migrations (Acahti, Pipetil, kunzhiyuan and the aidy site).

Breaking

  • aidy.citation is {messageId, citations: [{n, hit}]}: each cited hit under the number the answer wrote. It was {messageId, hits} packed in order, so [11] or [2][4] linked the wrong hit. ThreadState.citations holds Citation[] (@aidy-dev/client).
  • aidy.model.retry carries endpoint and fallback.
  • Model chain. Any failure not retried on the same endpoint (4xx such as 400/401/403/404, quota answers, 429, retries used up) rests the endpoint and falls through to the next. A resting endpoint is skipped, and model_unavailable comes only when none is left (a rate-limited endpoint is no longer retried when all rest).
  • SearchHit has content (model-only); FederatedHit and citation hits exclude it. fuse returns FusedHit (with content).
  • Search operations default to a 2 s timeout and accept x-aidy.timeoutSeconds ≤ 10; a larger value is a catalog error.
  • @aidy-dev/client: ClientOptions.baseUrl is where aidy is mounted and optional (default ''); RunRequest.message is string | ContentPart[]; UserItem.attachments is required; ModelEndpointUpdate.id is required.
  • @aidy-dev/react: locale is any string and the Locale type is gone (Strings and locales replace it); Markdown takes citations as Citation[].
  • @aidy-dev/cli: the built-in whoami is now status.
  • Search tool: the model's and MCP's search tool no longer takes types (models invented values and got no hits); GET /aidy/v0/search?types= keeps it.
  • MCP serverInfo.name is the product's name (the catalog's info.title), not aidy.
  • /skill.md: a hand-written guide's own frontmatter and leading # title are dropped.
  • @aidy-dev/documents: SkillOptions.cli and LlmsTxtOptions.cli are CliOptions ({command, package?, install?}); skillName is new.
  • Store: putFeedback, listFeedback and deleteSettings are new required methods; SQL migration 002_feedback.
  • Conformance runner: RuntimeEnv.model is RuntimeEnv.endpoints.

Runtime (@aidy-dev/core, @aidy-dev/spec)

  • Host jobs: POST /aidy/v0/generate, signed with an Aidy-Host-Assertion for op generate, takes {instructions?, input, schema?, maxOutputTokens?} and answers {text} or {object} (validated against schema, one repair attempt, else 422 invalid_output), over the same model chain, without tools or a thread.
  • Model chain: rest durations 6 h for quota-like answers (402, or a body matching quota/insufficient/exhausted/401008), 60 s for 429, 5 min otherwise, overridable per endpoint with cooldownSeconds: {quota, rateLimit, error}. Per-endpoint temperature and maxOutputTokens. One chain per instance, shared by runs and host jobs.
  • Images and attachments: user messages take AG-UI text, image and document parts (≤ 10 attachments). Images on the host are fetched with the user's credential and inlined (≤ 5 MB); other URLs pass through; images go to vision endpoints only, others get a note. Text-like documents are read as text. Every attachment is named for the model with its URL.
  • Page context: the run's AG-UI context is added to that run's system prompt (≤ 16 entries, 8000 characters).
  • Async instructions: instructions may be an async function of the identity.
  • Search: per-source timeouts (x-aidy.timeoutSeconds, SearchSource.timeoutMs); hit content reaches the model through the search tool and MCP, never /search or citations.
  • Tool errors: a failed host call gives the model the host's redacted error body as error.detail (≤ 4 KB).
  • Feedback: PUT /aidy/v0/threads/{id}/messages/{messageId}/feedback (up/down, comment) and GET /aidy/v0/feedback for admins.
  • Info: GET /aidy/v0/info answers the assistant's name.
  • Settings: DELETE /aidy/v0/settings restores the configured models; secret may be a list to rotate it (the first seals, all unseal, old settings are sealed again); unreadable settings answer 503 settings_unreadable.
  • Host assertions are bound to aidy's public origin plus the path, so tasks and host jobs work behind a proxy.
  • Requests without a body (DELETE, cancel) no longer need Content-Type; a body must be JSON.
  • Generated documents answer without a credential: from the host's anonymous OpenAPI, or, when it needs signing in, the guide and how to connect without the operations.
  • Generated documents: skill.name (a valid slug even for non-ASCII product names), and skill.cli: {command, package?, install?}, named in /skill.md and /llms.txt.
  • Keys: importSigningKey and portableJwk; importPublicKeys accepts Node-exported JWKs (alg), which workerd refused.

Knowledge (@aidy-dev/knowledge)

  • Explicit heading ids ## Title {#anchor} set the anchor and are stripped from the title.
  • Hits carry the chunk text as content.

Client and React (@aidy-dev/client, @aidy-dev/react)

  • Client: run(threadId, {message, context?, resume?}), attachmentPart, attachmentsOf, info, setFeedback, listFeedback, resetSettings, baseUrl.
  • AidyProvider: upload (attach button, drag and drop, paste; thumbnails in the thread), context, locale + strings (exported Strings and locales; unknown locales fall back to English), and the assistant name from GET /info.
  • AidyDock remembers open state and thread per client baseUrl, and takes controlled open/onOpenChange and threadId/onThreadChange.
  • SearchPalette: controlled open/onOpenChange, useSearchPalette(), onAsk, and type labels through strings (type.<type>).
  • Thumbs up/down with an optional comment on answers; "Reset to defaults" in ModelSettings, whose new rows now get ids.
  • Every component carries the .aidy-root theme when used outside the dock, and the styles no longer depend on browser defaults that CSS resets (Tailwind preflight) remove.

CLI and server (@aidy-dev/cli, @aidy-dev/server)

  • Credentials from the environment (AIDY_HOST/AIDY_TOKEN, or a brand's own names with aidy brand --env-host --env-token); flags win over env over the saved login, and an env token is never written to disk or printed.
  • aidy brand --host is optional.
  • Host commands win over built-ins, which stay reachable as aidy:<name>; whoami is status.
  • Every command takes --help.
  • aidy keys generate and aidy-server keys write portable JWKs.
  • Server env: AIDY_SKILL_NAME, AIDY_CLI_COMMAND, AIDY_CLI_PACKAGE, AIDY_CLI_INSTALL, AIDY_PREVIOUS_SECRET.

Python kit (aidy)

  • SearchHit.content.
  • Wire models show their real camelCase JSON Schema in FastAPI's OpenAPI, and still omit absent fields.

Conformance

  • Cases can script a model chain (endpoints, a turn's endpoint), check what the model sees (sees), send content parts and context, and script plain host requests, raw bodies and delays. New cases: model fall-through, quota rest, rate limit, every endpoint failing; host, external and no-vision images; page context; hit content; citation numbers; source timeout; host error bodies.

0.1.0 (2026-11)

The first release.

  • @aidy-dev/spec: the language-neutral contract: the x-aidy catalog reader, delegation assertions, search fusion, and the AG-UI profile schemas.
  • @aidy-dev/core: the runtime and its Web-standard fetch handler (createAidy): threads, runs, approvals, forms, resolve, chains, AG-UI events, MCP, federated search, settings and generated documents. MemoryStore and SqlStore.
  • @aidy-dev/sql: the SqlDriver contract, drivers for Postgres, SQLite and Cloudflare D1, and a migration runner.
  • @aidy-dev/documents: generators for skill.md, llms.txt, the operation reference and CLI command names.
  • @aidy-dev/knowledge: Markdown ingestion, heading-based chunking and BM25 search, with vectors when an embedder is given; a search source named knowledge.
  • @aidy-dev/client: a typed client of the HTTP API and a reducer from AG-UI events to thread state.
  • @aidy-dev/react: AidyDock, AidyThread, ApprovalCard, AidyForm, SearchPalette, HelpViewer and ModelSettings.
  • @aidy-dev/server: aidy-server (serve, keys), configured by environment variables; nodeHandler; the Docker image ghcr.io/aidy-dev/aidy-server.
  • @aidy-dev/cli: the aidy command, a generic MCP client of any aidy host, plus check, skill, llms, reference, docs, keys generate and brand.
  • aidy (PyPI): the Python host kit: op(), AidyHost and AidyCall for FastAPI, verify_assertion, check_call, and the Identity and search models.

供 Agent 读取: changelog.md编辑此页