Bohan Jiang 129efb7688 feat(runtime): allow qoder as a custom runtime profile base (#4883) (#4912) ...

Qoder CN (`qoderclicn`) users could only reach a working custom runtime by
misrouting through the Kiro backend, which launches `<cmd> acp
--trust-all-tools`. That is incompatible with Qoder's global `--acp` / `--yolo`
argv, so the task failed immediately with `kiro initialize failed` and no run
messages.

Expose `qoder` in the custom-profile protocol_family whitelist across every
lockstep layer:
- server/pkg/agent SupportedTypes (+ whitelist pin test)
- migration 134 runtime_profile protocol_family CHECK (NOT VALID, mirroring 126)
- packages/core RUNTIME_PROFILE_PROTOCOL_FAMILIES

The existing qoderBackend already honors an ExecutablePath override and launches
`<cmd> --yolo --acp`, so a profile with protocol_family=qoder and
command_name=qoderclicn now launches with the correct argv instead of the Kiro
shape. Provider branding/logo for qoder already exists.

MUL-4018

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

2026-07-04 23:16:01 +08:00

..

core

feat(runtime): allow qoder as a custom runtime profile base (#4883) (#4912)

2026-07-04 23:16:01 +08:00

eslint-config

fix(deps): add eslint phantom dep detection + fix existing violations (MUL-2654) (#3249)

2026-05-26 09:42:29 +08:00

tsconfig

…

ui

fix(markdown): render inline data-URI images (MUL-3961) (#4832)

2026-07-02 14:02:05 +08:00

views

fix(agents): defend AccessPicker against undefined invocation_targets (GH #4915) (#4924)

2026-07-04 18:07:03 +08:00