Repository navigation
Releases
v0.3.3
Fixed
- The suite's "only the vendor's official hosts and only the proxy's binary are used" test asserted the checkout's
native/binpath for every platform, so a normal npm install — where the lookup correctly opens the platform package it landed — failed that one assertion on Windows (issue #8). It now checks the file name the lookup answers and still requires the exact checkout path when that is what the install resolves, so both documented layouts are covered. No runtime code changed.
v0.3.2
Changed
- The embedded fallback catalog had drifted from the vendor's list: it was missing
deepseek-v4.1-flash-economy,gemini-4-argon,gemini-4-argon-official,gpt-6.2-astraandgpt-6.2-sol, and carried older context windows, modalities and credit rates for twelve more (gpt-6.1-solhad 128000 context where the vendor states 1050000,gpt-5.6-solhad 128000 with no reply ceiling where the vendor states 1050000 and 128000). Regenerated fromGET /v1/codar/models(20 models) withnode scripts/catalog.mjs, whose records are the plugin's owncatalogOfrules. The file is only the fallback — a signed-in magpie refreshes the live list every start — but an offline start used to show five models the account has and understate the rest.
Fixed
- The Go proxy sent
Host: <vendor host>:443on every request to the vendor. Its target URL was built with the port spelled out, and net/http writes a Host header from the URL as it is. The desktop sidecar joins a path onto a barehttps://<host>base, so its Host carries the name alone, and no official request has:443there; the proxy now builds the same shape. Captured on both sides of the wire (the 0.3.17 sidecar and this proxy against the same server): everything else — the TLS ClientHello, HTTP version, User-Agent, Authorization and Content-Type — already matched. - A proxy build that existed but did not come up (a spawn the OS refused, an exit before the ready file, the five-second deadline, no private temp directory) was reported as
no platform package for this machine, and during the new retry pause as nothing at all: the sentence sent a person reinstalling a package they already had. A failed start now says which failure it was, while an absent build still says it is absent. - A refusal nested five
datawrappers deep was read as a claim: the check-in's deep walk stopped one node short of whereunwrappedreads, so{code:200, message:"签到成功", data:{data:{data:{data:{data:{code:500}}}}}}settled the day at 0 points, and a free-model answer with a refusal that deep was read asavailableand claimed. Both walks now go as deep as the other readers do (eight nodes), so a wrapped refusal is reported as one and no claim is written against it; the failed card line is the refusal's own words or签到失败, never the outer success wording it was wrapped in. - A
403 {"detail":{"code":"client_not_supported"}}— the vendor refusing a login credential that is meant for its own client — reached the usage card as登录已过期,请重新登录and would mark the account signed out, so magpie asked for a sign-in that cannot fix it. The card, the check-in line and both balance reads now name the refusal (client_not_supported) and say to use a vendor-supported API key or contact Codar support, without marking the account expired; the plugin does not impersonate the vendor's client. The refusal is read anywhere in the wrapper chain, not only on the envelope: a success word outside with the gate underdatasettled the day as a claim, and a numeric 403 beside the gate sentence was reported as an expiry — re-login cannot fix a client gate. A word code spelled in upper case (CLIENT_NOT_SUPPORTED) is the same word. - A vendor field of several megabytes stalled or crashed a hook: the key-shape scans (
echoesKey,credentialish, the split walk) ran global regexes over the whole string, and an 8 MB field threwRangeError: Maximum call stack size exceededout of the activities read, while a 4–8 MB field of newlines took two to four seconds in the host every plugin shares. They now read the prefix a card could show, as the cleaners already do; a contiguous copy is still cut from the whole string, and the split walk, which was capped already, no longer pays its regexes over bytes it never read. A string longer than that cap also stopped reading as credential-shaped:shapeOnlycompared a truncated scrub against the whole field, so any 8 KB+ name of plain letters looked like a secret. - The desktop transport's byte body was written from the caller's buffer a turn after the call: a caller that reused its
Uint8Arrayright after calling changed the bytes on the wire, where fetch snapshots a body at call time. The bytes are copied when the request is made — and, through the proxy entry points, before the firstawait, since starting the proxy could take seconds and the copy used to happen only after it came up. - The folded-key cut (
strippedHas) ran two global replacements over the whole vendor string before answering: with a JWT-shaped key and a body of letter/newline pairs, a 4 MB field took over a second inside a hook, like the other shape scans that were already capped. It now reads the same card-sized prefix with the folded-key margin, a hundred milliseconds instead of a second. - An answer that states both
account_restrictedand the client-gate sentence answeredclient_not_supportedon the check-in, while the balance reads answeredaccount_restricted: one hook's order, not two. The restriction's word now speaks first everywhere — its fix is the vendor's support.
v0.3.1
Fixed
- The provider's
baseURLended at the gateway, without/v1: an OpenAI-compatible client joins/chat/completionsonto the base and askedhttps://api.claw.speedai.com/chat/completions, which the gateway answers with a 405 page (issue #3). The loader now answers the base with/v1, as the vendor's own documents it, and the config hook passes a user's own base through unchanged. - The fallback transport followed a redirect to any host. When the Go proxy could not run, requests and chat went through
fetch, which follows aLocationand carriesAuthorizationto it; the proxy refuses a hop off the host and port it started on, and the fallback now applies the same rule (lib/guarded.mjs): at most five hops on the origin the request started on, a one-shot body stops at the redirect, and the redirect is returned as the answer. - A user's own
apiwritten without a path was used as written, so the clients askedhost/chat/completionsandhost/messageswith no/v1: /v1 was there only when the user happened to type it. A user's address now follows the vendor's rule — an address that already ends in/v1is left as it is, any other is given/v1, ashttps://api.claw.speedai.comalways was. - The fallback transport refused redirects when the host handed it a
URLor aRequestinstead of a string, and read an upper-caseHTTPS://address as not https, which sent it out with no rule at all; both are now parsed the way the URL parser reads them. ARequestis sent with its own method, headers and body (the URL alone was sent, as an unauthenticated GET), aDataViewbody no longer throws, and anArrayBufferorBufferbody is copied at the call. - The fallback transport now follows fetch's own redirect rules for the method: a 303 asks for a GET with no body unless the request was a GET or a HEAD, a 301 or 302 after a POST does the same, and every other method (a PUT, a HEAD) keeps its own; before, it re-sent the POST through a 303 and turned a PUT through a 301/302 into a GET. A hop to a GET drops the headers that described the body (
content-type,content-length, which the old code tried to strip from the wrong object and kept), 307 and 308 keep the method and the body, and the redirect's own body is cancelled instead of left holding its connection. - A
Requesthanded to the fallback transport with an init is now read as fetch reads one: the init's headers replace the Request's (a merge kept anAuthorizationthe caller meant to drop), itssignaloverrides the Request's, and its stream body is sent with theduplexa stream request needs. - A user's own
apicarrying a query or a fragment was used as written and then given/v1, but magpie and both clients join the endpoint by string concatenation, so/gateway?route=chatproduced/gateway?route=chat/v1/chat/completions— the endpoint inside the query. The base is now read by scheme, host and path, with/v1on the end. - The sign-in page's SMS resend cooldown was checked before an
awaitand recorded after it, so several/sendrequests at once all passed it: a script holding the page's solved captcha could send SMS as often as it liked within the cooldown. The cooldown is now taken before the vendor is asked and given back when the vendor refuses the send. - A redirect that turns a request into a GET now drops every header that described its body (
content-encoding,content-languageandcontent-locationas well as the length and the type), as fetch does. - A redirect whose
Locationnames a user in its authority (https://someone@api.claw.speedai.com/…) is no longer followed as a hop on the same origin. - The sign-in page took the account's QR code image from any URL the vendor's answer named. It is now only loaded from the vendor's own hosts over https.
- The proxy refuses a redirect that names a port, not only one that names another host:
https://api.claw.speedai.com:8443is another service on the vendor's name. - The install check in
scripts/tarball.mjspassed without running when the checkout had nonative/bin(a fresh clone, anpm pack --dry-run): it printed that the platform packages were "not installed" and exited 0. A tree without builds now says the check was skipped, and the release run (prepublishOnly) passes--require-builds, where it is exit 2 — a release cannot ship on a check that did not run. - A sign-in the vendor answered with a refusal wrapped inside a
200({"code":200,"data":{"code":201,"status":"ip_verify_required",…}}) was saved as a finished sign-in, and its temp token — good for/v1/user/verify_ipalone — failed every request afterwards. A wrapped refusal is now the refusal it is, in the sign-in, the renewal and the IP check alike. - A token the plugin returned to the host was checked only for being a nonempty string. A login, renewal or IP-check answer whose token carried a newline or invisible characters, or whose own
exphad already passed, was saved and then rejected on every request; such a token is now refused where it arrives, with a sentence that says so. - A vendor sentence that quoted a credential reached the sign-in page and the host's failure text: a QR status answer with
message: "… token=eyJ…"was shown as written. The shapes the card already cuts for its own messages now cut these sentences at the source. - A password sign-in whose IP-check handover arrived after a newer sign-in had already finished wrote the stale handover anyway, so the next OAuth page continued the older account's check. An attempt that a newer sign-in superseded leaves nothing behind.
- A sign-in cancelled before its page finished opening spent the IP-check handover: the page never reached the host and no code was asked for, but the temp token was gone. It is put back, as when the page fails to open at all — unless a newer sign-in finished while the page was coming up, in which case the older account's handover is not offered.
- Closing the sign-in page left its vendor calls running to their own timeouts (a QR poll holds 35 seconds): the listener went away, the requests did not. The page now cancels them with itself.
- The Go proxy answered a vendor that sent no response head within its two-minute bound as
200with an empty body: the watchdog cancelled the upstream request and the handler returned before writing a head, and Go's ownfinishRequestwrote the success. The silence is now a504naming it. - The Go proxy forwarded a request-side header that the incoming
Connectionheader named hop-by-hop (Connection: Authorizationplus anAuthorization) — an input only another local process with the proxy's token could make, but one that put a value the plugin meant for the proxy on the vendor's wire. Named fields are now dropped, as the response side already did. - A plugin process killed outright never ran the cleanup that removes the proxy's private temp directory, and the directory stayed in the temp root for as long as the machine ran — one per such death. The proxy now removes its own empty directory on the way out, while the plugin keeps removing whatever is left in it.
- The install check's probe found the platform package by splitting the resolved path on
/, so on Windows — where the same path is written with backslashes — it answerednullfor a build that did come from the platform package, and the check would have failed for a reason of its own. Both separators are read now, and the check saysexit 2when this machine has no build in the platform table rather than reporting a package it never looked for. - The test that runs the gate against a tree without builds gave each of its two runs a 110-second bound; alone that is about a minute, and a machine running other suites ran past it — the run was killed and its silence read as a wrong exit code. Each run has its own generous bound now and the failure names a killed run as killed.
- The release-package test's three registry reads (a taken version, an unpublished one, a package that does not exist) had no answer for a registry that could not be reached: a dropped TLS connection under load read as a wrong preflight. A network failure now skips those three reads with a note, while a wrong answer is still a failure.
- The 9 MiB streaming-cap test had Bun's default five-second bound around a transfer that takes about 3.5 s under Bun: under load it timed out and read as a transport bug. It now states its own bound.
- A cancelled IP-check page left its
/v1/user/verify_ipcall running to its own timeout: the page's signal was passed among the call's fields, where the function never reads it, so the person had walked away and the plugin still finished the check at the vendor. The call is now cancelled with the page, as the SMS sign-in and the QR poll already were. - The usage card could spell the account token across activities: each activity's model ids were checked on their own, so a vendor spreading the token over twenty activities, two or three characters each, put the whole credential on the card in activity order. The names that survive the per-activity read are now read once more as one list, and a hit turns every name into
…. - The sign-in page showed a vendor error sentence as it came: a non-2xx answer whose message quoted a token put the token in the page and its script, against the module's own "the token never reaches the page at all". Every route's failure sentence is now shape-scrubbed, as the status word's sentence already was.
- The catalog generator's fallback fetch followed a redirect off the vendor: with no proxy it used plain
fetch, so a redirect could build the committed catalog from an answer the vendor never gave. It now goes through the plugin's guarded fetch, which reads a redirect off the vendor's origin as the answer. - A QR sign-in whose status answer carried a token the plugin cannot keep (a newline or invisible characters, or one already expired) was saved as a finished sig...
v0.3.0
Changed
- A release now publishes six packages, platform ones first (0.3.0). The compiled Go proxy and its platform packages are built inputs, so this ships as a minor version rather than a patch. Nothing a magpie user configures changes, but the shape of a release does: the five platform packages must be published before the main package, or an install lands without its proxy (it then falls back to the ordinary fetch, the old fingerprint, without saying so). Publish them with
node scripts/native-packages.mjs --publish, then the main package. - Each platform's proxy build ships in its own npm package.
magpie-plugin-codar-<os>-<cpu>(darwin/linux arm64+x64, win32 x64) carries one ~6 MB build and declaresos/cpu, and the main package names all five inoptionalDependencies, so a package manager installs only the one that fits the machine. An install drops from 32.0 MB unpacked (13.3 MB of tarball) to 7–8 MB on disk (about 3 MB of tarball: a 0.33 MB main package and one 2.4–2.8 MB platform package), and magpie's bun and npm both pick the right package. Thecpufield is npm's spelling —x64, never Go'samd64, which npm refuses withEBADPLATFORM— and the plugin resolves the build through the installed package rather than computing a path fromprocess.arch, so an x64 runtime under Rosetta gets the x64 build. Release:node scripts/native-packages.mjs --publishpublishes the five packages before the main one, whichCONTRIBUTING.mddocuments. - The release gate now performs an install.
node scripts/tarball.mjsserved the packed main package from a local registry to a scratch project, and requires the install to land exactly this machine's platform package and the plugin to start it. It previously only unpacked the tarball, which is why five builds in one package shipped for two minor versions without anything checking the install path. - The main package no longer carries
native/bin;filesand the gate refuse it, because the builds are the platform packages' now.
Removed
requireNativeBinno longer checks five builds in the tarball; the main package must carry none of them.
v0.2.4
Fixed
- The shipped proxy binaries carried a VCS stamp that named the wrong commit:
go buildreads the checkout it runs in, andnative/binwas last built
before the 0.2.0 tree, so every binary saidvcs.revision=c90d4d9(v0.1.2)
withvcs.modified=true.scripts/build-native.mjsnow passes
-buildvcs=false;go version -mreports the module as(devel)and no
commit, which is what a review should read. All five builds are remade from
the current source. - A
GOEXPERIMENTset in the releaser's owngo envreached the pinned
toolchains:greenteagcmade Go 1.24.3 refuse to build at all, and any
value it accepted would have changed the binary behind the build's back. The
build pinsGOEXPERIMENT=none(CODAR_GOEXPERIMENTnames another
deliberately).
Verified: node --test 440/440; the packed tarball runs bun test at 435 pass / 5 skip / 0 fail; go vet ./... && go test ./... in native/; go version -m on each shipped binary reports (devel) and no vcs.* field.
v0.2.3
Changed
- The README now says where the two things a review of 0.2.x asks about live: how
the shipped proxy binaries are made (built locally bynpm run native:all, not in a
release workflow; not byte-reproducible from a tag, since Go embeds its build path and
the binaries are not committed — what a tag fixes is the source and the toolchain), what
CI and the publish gate do and do not check, and exactly where the account's name and
password go (the vendor's ownPOST /v1/login, once, never kept).
Verified: node --test 439/439; the packed tarball runs bun test at 434 pass / 5 skip / 0 fail.
v0.2.1
Fixed
- The suite tried to bind unix sockets on Windows: twenty-one of
test/native.test.mjs's tests speak the proxy's unix transport, which Windows
Node cannot listen on (EACCES), so they now skip there. The loopback TCP
transport the proxy uses on Windows keeps its own test, which runs on every
platform. - The
tarballCI job would not take the package it was given:
upload/download-artifact carries bytes, not modes, so the builds thenative
job uploaded came back read-only, and the gate rightly refuses a package
whose proxy cannot be run. The job restores the executable bit after
downloading, as a local build leaves it.
Verified: node --test 439/439; the packed tarball runs bun test at 434 pass / 5 skip / 0 fail; node scripts/build-native.mjs --check --strict passes.
v0.2.0
Superseded by v0.2.1: this tag's CI failed on Windows (unix sockets in tests) and in the tarball job (artifact download drops the executable bit). v0.2.1 fixes both.
Added
-
A WeChat QR sign-in: the vendor's own code flow
(POST /v1/wechat/login/qrcode→{scene, qr_url}, then
POST /v1/wechat/login/status {scene}every two seconds, as the web app
polls it). The plugin serves the page on127.0.0.1and makes both calls
itself, so the image the vendor drew is shown from the plugin and the token
in the status answer never reaches the page. Expiry (including the vendor's
business code 404) refreshes the code; a WeChat that is not bound to an
account, or a scan that lands on the vendor's IP check, ends with the sign-in
that can finish it rather than spinning. -
POST /v1/user/verify_ipis now reached the way the vendor's web app
reaches it. When a password sign-in answerscode 201/
ip_verify_required, the plugin keeps the temp token that refusal carried
and the SMS page finishes that check for it — code typeip_verifywith the
account's own name, then the three fields the endpoint takes with the temp
token as its bearer — so the person is not asked for the password again.
The temp token is held in the plugin's memory only: never saved, never shown. -
The free-model campaign is claimed, not just reported. Beside a check-in the
plugin callsGET /api/codar/activities/free-modeland, when the campaign
saysavailable, posts itsclaim(the vendor's own one-click benefit on
its activities page), then says so in the check-in line. Best-effort
throughout: a campaign already claimed, none open, or a refused call leaves
the check-in's own answer untouched, so the extra can never fail the
check-in. It rides on the check-in, so it happens only for an account whose
check-in is switched on. -
Chat now leaves through the same Go proxy as the card's requests, when the
proxy can carry it. The loader answers afetch— magpie runs
typeof o.fetch === "function" ? o.fetch : fetch— so a conversation to the
gateway carries the desktop's TLS and HTTP shape instead of Bun's, and the
answer is streamed back as it arrives.
Changed
-
The reader, the sign-in page, the native transport and the fallback catalog
live inlib/(lib/internal.mjs,lib/signinpage.mjs,lib/native.mjs,
lib/catalog.mjs), so the repository root holds only the entry module and
the project's files. Nothing the plugin does changes; the two never-published
compatibility namessmslogin.mjsandwechatlogin.mjsare gone. -
The page method is labelled “科搭OAuth登录” in magpie's method list, so the
three entries read as what they are: a token, the vendor's own OAuth
sign-in (QR or phone, in one page), and the account's name and password. -
One “科搭OAuth登录” entry in place of the separate SMS (“科搭手机号短信登录”) and
WeChat QR (“科搭微信扫码登录”) methods. It opens a single page on
127.0.0.1whose tabs are the two ways in the vendor's own login dialog
offers (扫码登录 / 手机号登录), so switching between them no longer means
backing out to magpie's method list. The page is redrawn to match the
vendor's client and site: indigo active tab, near-black primary button, the
QR dimmed with a sentence over it once it was scanned or is being replaced,
and one final screen for “登录成功” or a sign-in the vendor will not finish.
The SMS captcha is loaded only when its tab is first shown, and the QR code
starts drawing only when the page opens. The IP-check handover now opens this
page straight on the security check. -
The sign-in page's last screen shares the page's design language instead of
standing apart from it: the card's own brand mark box (34px, the same radius
and soft shadow) in green for “登录成功” or red for “无法完成登录”, the card's
20px/600 heading, the body's 14px ink for the first sentence and the hint's
13px muted for the closing one, left aligned like the form. The sign-in's own
heading and hint give way to the end screen's, and a vendor's reason and the
closing instruction are two lines rather than one merged paragraph. Two
deeper shades join the page's palette in:rootfor the mark's gradients. -
The sign-in options are four now, not five: “读取本机科搭令牌” (keyless) and
“科搭访问令牌” (paste) are one entry with an optional token field — leaving
it empty reads the desktop app's own login on this machine, filling it uses
the pasted token, and both are checked the same way (visible ASCII, an
account name, an unexpired exp) before anything is saved. The password
sign-in sits after the SMS page, because the vendor's IP check commonly
hands it on to that page. -
The proxy flushes each piece of a streamed answer as it is written and
bounds the wait for a response head instead of the total length, so a long
chat answer is no longer cut at a deadline meant for short catalog requests.
After the head, silence on the body is bounded by the plugin's own stream
bound, which reaches the proxy as a cancelled request, not by a second
timer that would have to guess the same number. -
The proxy forwards
X-Api-KeyandAnthropic-Versionin addition to
AuthorizationandContent-Type: the vendor's Anthropic models
authenticate with the first and state the second, and a chat request that
carried them lost its credential and its protocol on the way out. A card
request never has either, so nothing changes for it. -
Models carry the vendor's own credit multiple:
rate_badge("0.20x") is
read as magpie'srate(a positive number; "0.20x"/"0.2×" and a bare
number are the same rate), live and in the embedded catalog, so the badge
the vendor's client shows appears beside the model. The vendor's prices in
CNY are still not reported (see README), and a model the vendor does not
badge carries noratekey in the catalog file (0is "not listed", not a
rate, and--checktreats a later badge as a change to regenerate for). -
A base32 or percent-encoded copy of the token is cut like base64 and hex:
on the card, in the keyless shape pass, in model ids and names, and in the
generator's encoded gate and cross-string check. A token split into pieces
that only read as one after percent-decoding is no catalog. -
A split of an encoded token is no catalog, no card and no
--checkline
either: pieces of a base32 or%XXcopy, an id or name on each record, are
read together and decoded before anything is served, written or printed
(%XXtriples the line or field boundaries cut in half included), each
field's strings are read on their own as well as with the other field, and
the walk follows the token, its base32 copy or its%XXcopy piece by
piece, and a piece padded with prose inside its own field is read field by
field (the run that continues the spelling, in order) — with no opening a
list must carry, so a piece behind a label in its id ("model-000-ey") is
read too. A split that alternates between a record's id and its name is
read both ways (the vendor order, the file order).--checkalso reads the
file's values with no order at all: the pieces' own three-character runs,
collected across the values, must not cover the spelling. A piece the
window rules refuse on its own is cut as before, and the pieces left do not
spell the token again.
An activity whose model ids in order spell the token — encoded or not — is
not drawn at all, and--checkprints no diff line when the old file's own
values reassemble into the token. -
A model id that reads as a word (
sk-whisper-large-v3,sk-live-…with
segments under 12 characters) is no longer mistaken for ansk-credential
and dropped from the whole catalog; a credential-shapedsk-run still is. -
A catalog of long names serves within the models hook's budget: the token
checks read the first 512 characters of each id and name, the cross-record
split scan is capped at 16 KiB, each field is judged once however many
lists read it, and a decoded form is only walked when it holds one of the
key's own characters. 1000 records of ~6 KB names answer in ~3.4 s inside
the 20 s host budget (was ~33 s). -
The entry module no longer has a default export. magpie's host and
OpenCode 1.x take every function a module exports as a plugin, while
OpenCode 2.x reads a package's default as its setup object and has no
fallback for a 1.x plugin's named functions; a default pointing at the same
plugin function is at best a duplicate entry and cannot stand in for 2.x's
setup.index.mjsnow exportsCodarPluginby name only, and the suite
asserts that no default export comes back. -
The catalog generator's terminal messages are English, like the rest of the
project's prose; what each exit code means is unchanged. -
The fallback catalog is regenerated in place (
node scripts/catalog.mjs);
the counts in the README and comments were updated and no longer promise a
fixed number. -
The generator validates the token's account and expiry before fetching,
reads a BOM-tolerated config like the plugin does, times out instead of
hanging on a vendor that never answers, and says local paths through
shownPath(no account name in a log or an issue). A permission failure
now says to check permissions instead of "sign in once", its own output
path is shortened the same way, and its 15 s timeout is named as this
script's own budget (the plugin's hooks keep the 8 s magpie's deadlines
leave them). -
The packed suite gate tells a Bun that is not installed (a skip locally) from
one that ran and failed (a failure everywhere, with or without
--require-bun); CI now runs it on Windows too, and every job has a
15-minute timeout.nodeandbunrun without a shell (a missing Bun is
then an ENOENT, not a shell's 127 that looks like a failing program), the
npm/tararguments are quoted for cmd.exe (a Windows temp path can carry
a spa...
v0.1.2
Fixed
- The test suite now passes from the npm tarball. The style test pinned
CONTRIBUTING.md, which is not shipped with the package, sonode --test
inside a fresh tarball failed 1 of 188 tests. The required documentation
files are nowREADME.mdandCHANGELOG.md, both of which ship.
Verified by packing the release, unpacking it, and running the full suite
inside the tarball: 188/188.
v0.1.1
magpie-plugin-codar 0.1.1
Changed
- The test hooks moved out of the entry module:
index.mjsnow exports only
the plugin function, and every reader plus thetestablesobject lives in
internal.mjs. OpenCode 1.x takes every export ofmainfor a plugin and
refused the package overtestables. - The auth hook gained a
loader, as the provider contract expects for a
provider served through config: a request for the account carries the
stored key, and an account with no usable key answers{}.
Added
CHANGELOG.md, shipped with the package.
Removed
- The Chinese README. Project documentation — the README, CONTRIBUTING,
this changelog and the GitHub release notes — is English-only.