Commit Graph
95 Commits
Author SHA1 Message Date
huanghuoguoguo d967601129 fix(box): preserve control responsiveness during large file transfers 2026-11-16 10:33:38 +08:00
69b7b45682 fix(agent): bound token counting and continue text turns on failure (#2969)
* fix(provider): decouple token counting from reasoning validation

Co-authored-by: multica-agent <github@multica.ai>

* fix(plugins): 修复 EssentialCommands !func 兼容性并清理 HelloPlugin 调试输出 (LANG-391) (#2967)

Co-authored-by: multica-agent <github@multica.ai>

* fix(plugin): wait for runtime recovery before workspace dispatch (#2968)

Co-authored-by: multica-agent <github@multica.ai>

* fix(runner): wait for installed plugins to initialize (LANG-393) (#2971)

Co-authored-by: multica-agent <github@multica.ai>

* fix(persistence): release SQLite writer during image refresh (#2973)

Co-authored-by: multica-agent <github@multica.ai>

* fix(telemetry): report cancellations as cancelled, keep route failure detail, tolerate already-terminal runs (#2974)

- Cancelled ingress / handed-off lanes / event deliveries close as `cancelled`
  instead of `failed` (CancelledError and GeneratorExit).
- Every `runner_failed` event-route record carries the exception type and
  message in `error`, including invalid Agent configuration.
- Closing the stream of a run another writer already finalized no longer
  raises "Cannot transition terminal run"; the ledger status is kept and
  reported, and the Runner's own error propagates.
- Platform API calls that return None without raising are `success`, not
  `unknown`.
- Command lanes name their adapter and no longer claim the Pipeline's
  configured Runner; only a Runner that actually ran is attributed.

LANG-395

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

* fix(agent): bound token counting and preserve text turns on failure

Co-authored-by: multica-agent <github@multica.ai>

---------

Co-authored-by: multica-agent <github@multica.ai>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-11 12:31:59 +08:00
RockChinQandmultica-agent 927a719454 fix(persistence): accept SQLAlchemy 2.1 tenant upserts (#2975)
Co-authored-by: multica-agent <github@multica.ai>
2026-11-11 12:31:23 +08:00
RockChinQandmultica-agent 718991c484 fix(persistence): release SQLite writer during image refresh (#2973)
Co-authored-by: multica-agent <github@multica.ai>
2026-11-11 09:20:34 +08:00
RockChinQandmultica-agent a0c096d560 fix(runner): wait for installed plugins to initialize (LANG-393) (#2971)
Co-authored-by: multica-agent <github@multica.ai>
2026-11-11 09:20:30 +08:00
RockChinQandmultica-agent 9a65a9c5b4 fix(plugin): wait for runtime recovery before workspace dispatch (#2968)
Co-authored-by: multica-agent <github@multica.ai>
2026-11-11 03:32:47 +08:00
0b7c137f33 fix(plugin): stop member-driven install paths from stalling on permission confirmation (#2961)
* fix(plugin): stop member-driven install paths from stalling on permission confirmation

- Runner/event-processor installs from the Agent and Pipeline forms and
  knowledge-engine installs from the knowledge base form now auto-confirm
  declared permissions, so their registration polling no longer times out.
- RAG migration confirms the plugins it installs on behalf of the member
  running it and reports plugin_permission_confirmation_required otherwise.
- Upgrading a confirmed compatibility-mode installation to another
  compatibility-mode package keeps it enabled with the full legacy grant set.
- The WebUI install task reads pending_permission_confirmation, the key the
  backend actually writes; the marketplace task clears it after auto-confirm.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

* test(web): expect auto-confirm on inline marketplace installs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-09 22:08:41 +08:00
bdc0dc11e1 refactor(runtime): use stdio for Core-launched Plugin/Box runtimes on Windows (#2952)
Plugin and Box now share one transport rule via
ManagedRuntimeConnector.select_runtime_transport(): an explicit endpoint,
Docker or --standalone-* means WebSocket to an external runtime; every
other case (Windows, Linux, macOS) launches the runtime as a child
process and talks over its stdio pipes.

The Windows-only "subprocess + WebSocket" branch is removed from both
connectors together with its helpers (control-token generation, port
probing, readiness polling, subprocess disposal). Since langbot-plugin
0.6.0 the runtime side reads/writes stdio from blocking threads on
Windows, so the WinError 6 that motivated the branch no longer applies.

Docs (zh/en/ja compatibility + deep-dive, ARCHITECTURE.md, dev-docs
reviews) now describe the actual transports, including the Windows
runtime-to-worker WebSocket on the plugin debug port.

Refs #2545

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-09 20:01:35 +08:00
ece1f3fdf9 fix(plugin): resolve the WebSocket debug proxy bot from the runtime, not the bots table (#2953)
The pipeline debug chat runs on a per-Workspace in-memory RuntimeBot with the
reserved uuid websocket-proxy-bot. It never has a bots row, yet three plugin
guards looked data["bot_uuid"] up in that table, so SEND_MESSAGE (and
call_platform_api send_message), GET_BOT_INFO and authorize_action all
rejected it with "Bot ... not found" / "Bot is not available in this
Workspace". GET_BOT_INFO additionally called bot_service.get_runtime_bot_info,
which queries the table again.

- utils/constants: WEBSOCKET_PROXY_BOT_UUID; replace the 9 hardcoded literals.
- PlatformManager.has_websocket_proxy_bot(workspace_uuid): presence check
  that never creates a proxy.
- authorize_action and the handler's new _bot_available() accept the proxy
  uuid only while this Workspace has a live proxy; persisted bots still go
  through the bots table, and capability checks are unchanged.
- GET_BOT_INFO builds the proxy's info from the live runtime (no adapter
  config, no webhook). bot_service / the bot.runtime.get operation are
  untouched, so HTTP/MCP/Workspace API behavior does not change.

Closes #2935

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-09 18:19:42 +08:00
cc96ab5b85 fix(plugin): retry the whole Marketplace sweep when startup is saturated (LANG-323) (#2918)
On cloud.langbot.app the final run failed before touching any Workspace:
fetching Marketplace versions hit BlockingWorkCapacityError while about
1400 bots reconnected, and the once-per-process sweep gave up. Retry the
idempotent run after 60, 120, 300 and 600 seconds.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-06 18:05:31 +08:00
cb98131afd fix(plugin): retry the Marketplace sweep and confirm every pending install (LANG-323) (#2909)
The first fleet-wide Cloud run hit DNS errors and blocking-executor
saturation while 1400 bots reconnected, and an upgrade whose confirmation
failed was left disabled and was not confirmed by a later run. Retry
upgrade and confirmation, and confirm every listed installation that is
pending confirmation. Tenant-disabled installations keep their confirmed
snapshot and stay off. Document that env overrides persist in
data/config.yaml.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-06 15:42:14 +08:00
664f0f9e27 feat(plugin): operator sweep to upgrade Marketplace plugins in every Workspace (LANG-323) (#2902)
Cloud tenants can only upgrade plugins one Workspace at a time in the
WebUI. plugin.marketplace_upgrade.plugins lets an operator upgrade listed
Marketplace plugins across all active Workspaces from inside Core, through
the same tenant fence and upgrade_plugin path as the WebUI. Installations
that were enabled have their declared permissions confirmed as an owner
operator, so plugins without a permission declaration are not left
disabled. Tenant-disabled installations stay disabled. An optional
Workspace allowlist supports a canary run.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-06 14:00:16 +08:00
ff7482fc7d feat(monitoring): show messages handled by plugins in monitoring (#2897)
* feat(monitoring): show messages handled by plugins in monitoring

A plugin can take a message over with prevent_default() and answer through
ctx.reply / send_message / invoke_llm. Monitoring then showed the user
message as handled by the pipeline Runner, with no reply, no LLM call and
no delivery errors (LANG-320).

- monitoring_messages.handled_by (0045): runner:<id> | plugin:<author>/<name>;
  plugin-handled messages no longer claim the Runner.
- Attribute prevent_default to the plugin reported by the Runtime, falling
  back to a single emitted plugin for older Runtimes.
- Record ctx.reply and plugin send_message as assistant messages, with
  PluginReplyError / PluginSendError on failure; delivery behaviour is
  unchanged and monitoring failures are swallowed.
- Link plugin-level LLM calls and sends to the triggering message through
  origin_query_uuid. The Host opts in per event (origin_attribution), so
  plugins never send the new field to Hosts with strict schemas. Used for
  attribution only, never for authorization.
- WebUI: "Handled by plugin" badge in the execution list and detail.
- Docs (zh/en/ja) and dev-docs contract note.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

* test(migrations): account for the 0045 handled_by index on downgrade

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

* test(postgres): register the capacity requester instead of patching _build_provider

#2896 builds providers on a staged ModelManager during load_models_from_db,
so the per-instance _build_provider patch no longer applied and the populated
Cloud startup test loaded zero providers on master. Register a network-free
requester that the staged manager inherits instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-06 02:04:33 +08:00
huanghuoguoguoandClaude Opus 5.5 97ef5b457d feat(api): provide Workspace and execution API foundations (#2648)
Unified Workspace and execution APIs for LangBot (#2639).

- Versioned Application API shared by HTTP, MCP, the Workspace assistant
  and plugins, with one authorization and error contract.
- Execution API facade for every plugin and Runner action.
- Plugin installation permissions: manifest declarations, member
  confirmation, capability ceilings, compatibility mode, revocation and
  audit. Typed Workspace API in the plugin SDK.
- Processor tool configuration: workspace operations, event and bot tools,
  default tool sets for new Agents and Pipelines, and sensitive-tool
  warnings.
- Plugin permission picker in the WebUI; LocalAgent declares every
  plugin-callable permission.
- Documentation for plugin permissions and the Workspace API in English,
  Chinese and Japanese.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 16:36:22 +08:00
RockChinQandmultica-agent 33e482a357 feat(telemetry): report execution model and feature usage (#2876)
Co-authored-by: multica-agent <github@multica.ai>
2026-11-04 23:48:48 +08:00
532b8ce204 feat(agent): add cross-platform interactive cards for QQ, WeCom, Feishu and DingTalk (#2787)
* feat(agent): add cross-platform interactive card tool

* fix(agent): create pipelines with selected runner defaults

* fix(agent): enable reliable cross-platform card interactions

* feat(dingtalk): deliver A2UI cards and restore agent replies

* Fix DingTalk A2UI form submissions and agent replies

* Restore LangBot branding on DingTalk A2UI cards

* Use compatible Markdown link in DingTalk A2UI branding

* Place LangBot branding above DingTalk card content

* Stream DingTalk replies without a source message

* Move DingTalk branding into compact card footer

* fix(wecombot): handle native select card callbacks

* fix(wecombot): stream replies after HITL cards

* fix(dingtalk): show submitted HITL choices in cards

* fix(lark): stream replies after HITL submissions

* fix(plugins): refresh LocalAgent source hashes

* fix(dify): merge HITL resume streaming into in-tree plugin

* feat(interactions): resume runner in place after card submission

* fix(interactions): respect live adapter APIs and preserve deadlines

* fix(ci): lock blocking interaction SDK for dependent checks

* test(runner): keep legacy SDK probe importable

* fix(interactions): align adapter manifests and close timed-out streams

* fix(agent): avoid duplicate replies and enable LocalAgent cards

* chore(plugins): sync LocalAgent catalog version

* refactor(agent): unify blocking interaction callbacks and adapters

* chore(deps): pin blocking interaction SDK revision

* test(agent): remove obsolete async fixture mark

* test(interaction): update legacy admission assertions

* fix(qqofficial): keep card callbacks responsive

* fix(runner): keep blocking card interactions alive

* ci(plugins): expect SDK 0.7.20 in Runner workflows

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

* ci(plugins): test coding Runners against SDK 0.7.20

Claude Code and Codex now call ctx.request_interaction, first released in 0.7.20.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

* fix(discord): deliver guild interaction cards to the originating channel

Pipeline group conversations are keyed by guild id, so send_interaction
targeted the guild and Discord returned Unknown Channel. Resolve the channel
from the message being answered, edit cards in that channel, and report the
card's conversation on callbacks so the Host scope check matches.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>

---------

Co-authored-by: RockChinQ <rockchinq@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
2026-11-03 21:45:49 +08:00
huanghuoguoguo 1a344aeb9f fix(agent): prepare plugin execution identity at context creation (#2842)
* fix(tools): propagate current execution identity to plugin calls

* fix(agent): construct complete execution identity before tool dispatch
2026-11-02 19:44:35 +08:00
Li-john1021andLi-john1021 bd4e408d7e fix(plugin): honor display_plugin_debug_url port for managed Runtime (#2782)
Stdio and Windows launches always bound the SDK default debug port 5401,
so changing plugin.display_plugin_debug_url only updated the console URL
and a second Core instance hit Address already in use. Pass the configured
debug (and Windows control) ports into the Runtime CLI, and document the
behavior.

Fixes #2713

Co-authored-by: Li-john1021 <li-john1021@users.noreply.github.com>
2026-10-27 20:56:26 +08:00
huanghuoguoguo 7865ad51f7 perf(plugin): negotiate ordered batch event dispatch (#2778) 2026-10-27 11:36:47 +08:00
RockChinQandmultica-agent da508f9603 fix(plugin): reject archive entry names the SDK would refuse to extract (#2757)
The host inspects a package to read manifest.yaml and requirements.txt before the
SDK extracts it. Inspection normalized entry names with only
replace('\\','/').strip('/'), so it accepted names its own extractor rejects
(absolute paths, '..' components, drive letters) and it silently kept the first
member when two normalized to the same path.

There was no traversal write, because the SDK's _extract_verified_zip validates
every member before writing and the host only reads members by ZipInfo. The bug
is the divergence: a package could pass inspection and then fail to install, and
the two rule sets could drift further as either side changes.

Inspection now applies the same rule set as the SDK, via
_normalize_archive_entry_name: reject empty/NUL names, absolute paths, any '..'
component and drive letters; reject a duplicate after normalization. '.' and
empty segments are still collapsed, so './manifest.yaml' and 'components//x.py'
keep working.

Tests: 13 cases covering each rejection, the duplicate, traversal taking
precedence over the duplicate check, and two positive cases (nested/unicode
layout, cosmetic separators).

Co-authored-by: multica-agent <github@multica.ai>
2026-10-22 22:04:36 +08:00
huanghuoguoguo cc19395f5c perf(core): reduce execution projection and dispatch overhead (#2746)
* perf(core): join execution projection and reuse authorized tool schemas

* perf(pipeline): avoid duplicate checks before stage output validation

* perf(plugin): reuse reconciled settings within event dispatch

* fix(workspace): keep execution projection reads free of unrelated flushes
2026-10-22 20:00:42 +08:00
RockChinQandmultica-agent d9e4e7d9df fix(pipeline): decouple Runner from extension permissions (LANG-54) (#2723)
* fix(pipeline): decouple runner from extension allowlist

Co-authored-by: multica-agent <github@multica.ai>

* fix(pipeline): complete runner diagnostics and real runtime coverage

Co-authored-by: multica-agent <github@multica.ai>

---------

Co-authored-by: multica-agent <github@multica.ai>
2026-10-19 23:07:11 +08:00
huanghuoguoguo ec57b6a51d Merge pull request #2684 from langbot-app/test/quality-agent-plugin-oracles-20261017
test: verify persisted Agent and Plugin behavior boundaries
2026-10-17 20:11:24 +08:00
huanghuoguoguo ecea4c3d41 Merge pull request #2675 from langbot-app/test/quality-self-duplicates-20261017
test: remove redundant backend checks and migration aliases
2026-10-17 20:10:30 +08:00
huanghuoguoguo e0c738557a test(agent): verify persistence and denied action side effects 2026-10-17 15:35:33 +08:00
RockChinQ c05aac538f fix(discord): complete streaming media and event delivery 2026-10-17 15:11:29 +08:00
huanghuoguoguo 4afd86c1f6 test: consolidate duplicate backend contracts and strengthen stage checks 2026-10-17 15:03:50 +08:00
huanghuoguoguo bbf517edbc test(auth): exercise knowledge and event action boundaries (#2667) 2026-10-17 12:46:41 +08:00
huanghuoguoguo d54e533985 fix(skill): pin revisions per run and preserve shared Box state 2026-10-17 09:32:41 +08:00
RockChinQandHyu 616981b0cf perf(llm): harden request policy and optimize connections, reasoning and prompt caching (#2661)
* fix(llm): centralize request policy and preserve stream diagnostics

* test(llm): dispose SQLite engine after migration regression

* perf(llm): reuse connections and unify reasoning and prompt cache policy

* fix(llm): preserve explicit native prompt cache options

* perf(llm): fix measured TLS setup and streaming reuse overhead

* fix(llm): resolve plugin request-chain regressions found by E2E

---------

Co-authored-by: Hyu <chenhyu@proton.me>
2026-10-15 19:48:35 +08:00
RockChinQ b5fad9f04a feat(cloud): configure dedicated and shared worker quotas independently 2026-10-13 03:19:36 +00:00
Hyu 34b5fe0202 fix(plugin): share the runtime file-transfer root and 404 uninstalled icon requests
The SDK binds one transfer root inode (mode 0700) and picks it per profile: a shared worker uses /tmp/lbp-rpc while a host without the profile env fell back to data/temp/lbp, so plugin icons and assets died with 'Invalid file transfer capability'. The host now pins the shared root, and a plugin absent from the resolved Workspace answers 404 instead of 500.
2026-10-02 01:34:47 +08:00
Hyu 38d5750785 fix(plugin): report when an installation failure happened, not when it was sampled
The connector stored only uuid/code/message, so the ops reporter stamped every entry with its own sampling time and a stale failure looked freshly broken on each report. Failures now carry failed_at and the payload publishes it.
2026-10-02 01:34:46 +08:00
Hyu 4c71de5eca feat(plugin): push plugin runtime ops samples to the Space control plane
The shared Cloud deployment runs one Plugin Runtime for every Workspace, but
nothing reported its health: the instance only exposed two aggregate numbers on
its own health probe, and the per-installation failure registry, the desired
state registry and the reconcile outcome lived in memory with no reader.

Add RuntimeOpsReporter, which every 30 seconds reads the Runtime ``/healthz``
probe over HTTP (derived from ``plugin.runtime_ws_url``), merges it with the
connector's desired-state, failure and reconcile summaries, and posts one
sample to the Space control plane on the existing authenticated direction.
Delivery is best-effort and bounded: a single in-flight request, a ten second
timeout, dropped samples counted in ``runtime_ops`` on the instance health
probe, and a failed probe recorded as a drop so the dashboard shows staleness
instead of grading a stale sample as healthy.

Cloud-only: a non-cloud deployment never enables the reporter, and the channel
is independent of product telemetry so ``space.disable_telemetry`` cannot blind
the ops dashboard.
2026-10-01 19:01:16 +08:00
RockChinQ 1fde3b4283 fix(certification): align certified sharing and unsigned dedicated admission (#2610)
Integrate certification policy, SDK/Core semantics, and documentation on canonical branch. Resolve duplicated documentation and keep invalid Cloud signatures rejected.
2026-09-29 00:56:18 +08:00
RockChinQ ce118b4f41 fix(plugin): allow unsigned Cloud plugins on dedicated workers 2026-09-28 14:26:10 +00:00
RockChinQ c384e4715a test(plugin): include stateless certificate model in shared fixtures 2026-09-28 09:14:54 +00:00
RockChinQ b51a448b1e feat: stateless certified shared worker
Implements stateless singleton component model for certified shared Workers, integrating with SDK 0.7.0.
2026-09-28 13:25:40 +08:00
huanghuoguoguo 3987051da3 test(skill): align native exec assertion with mount API 2026-09-28 11:10:37 +08:00
RockChinQ f488087cc4 Merge remote-tracking branch 'origin/master' into feat/certified-cross-tenant-worker-pool 2026-09-25 13:33:22 +00:00
RockChinQ 300f5825bb fix(plugin): fail closed on incomplete certification records 2026-09-25 13:13:35 +00:00
RockChinQ 9f296bd57e feat(plugin): route certified installs to shared workers 2026-09-25 12:48:55 +00:00
TyperBody afe700f1d8 fix(plugin): keep certified marketplace packages installable on OSS
The certified-archive admission gate treated any declared certificate it could
not resolve as an untrusted archive and rejected the install with
CERTIFIED_PLUGIN_OSS_FORCE_REQUIRED. OSS ships an empty
plugin.certification.trusted_public_keys ring and the marketplace signs every
package with its own issuer key, so all certified marketplace packages (for
example langbot-team/RunnerDemo and langbot-team/LocalAgent) failed at the
'validating plugin package' step before artifact storage.

Admission now distinguishes an unresolvable declaration from a configured trust
decision that fails:

- record certificate_id only when the key_id is actually present in the
  configured ring, so an empty ring yields an unresolvable declaration;
- OSS degrades an unresolvable declaration to the existing oss_dev dedicated
  profile with CERTIFIED_PLUGIN_OSS_UNTRUSTED_DEDICATED instead of blocking;
- a resolvable declaration that still fails keeps requiring the explicit
  administrator force (CERTIFIED_PLUGIN_OSS_FORCE_REQUIRED);
- Cloud stays fail-closed and rejects before storage.

No shared-runtime privilege is granted when the issuer is not trusted, so this
withholds isolation rather than escalating it.
2026-09-25 19:32:54 +08:00
RockChinQ 5d9684731e merge(4.11): integrate master marketplace updates preserving Runner lifecycle 2026-09-21 16:58:35 +00:00
RockChinQ 27871e4363 merge: integrate master certification and document identity fixes into 4.11 2026-09-21 10:55:40 +00:00
RockChinQ 52f5699533 fix(plugin): honor requested marketplace version (#2555) 2026-09-20 23:59:50 +08:00
RockChinQ 20a04a77bf feat(plugin): enforce certified archive admission (#2553)
* feat(plugin): add certified admission policy

* feat(plugin): enforce certified archive admission

* chore(plugin): pin certified SDK beta

* fix(plugin): consume SDK beta 5

* style(plugin): format certification admission
2026-09-20 18:54:45 +08:00
RockChinQ 79cac0c6a3 fix(reasoning): apply explicit per-call levels without runner config caching 2026-09-19 00:05:49 +08:00
RockChinQ 60606e1997 fix(migration): improve runner migration and plugin installation feedback 2026-09-18 13:10:32 +08:00
RockChinQ b264d46d77 feat: delegate sandbox policy to runners and simplify pipeline migration 2026-09-17 23:05:27 +08:00