Repository navigation
Support ZCode 3.17.2 - #95
Merged
Merged
Conversation
Upstream tagged v3.17.1 and v3.17.2 again, so the baseline is the tag v3.17.2 (a9fe401). 3.16.3 has no public source and is reviewed from its changelog only. The vendored contracts are resynchronized (126 files); the sync script now deletes vendored files the new baseline no longer needs instead of failing. The ADR 19 patch applies unchanged; only its target commit changed.
- Give the Server the runtime's ZCode version in ZCODE_APP_VERSION, as Desktop and 3.17.2's remote Core do. Without it the Agent reported the CLI version (0.17.1) in model request headers. - Classify replies that the provider's content filter blocked, which ZCode 3.17.1+ fails at once with reason content_filter, as MODEL_CONTENT_FILTERED (ADR 23). - Mark the MCP servers Paseo passes as user servers on 3.17.1+, so the new project MCP trust review does not block them when the project declares the same name, and warn when a session that uses the project's MCP configuration has servers awaiting trust. Closes #70 Closes #84
zcode-runtime-v3.17.2-paseo.1 was built, verified on all five managed platforms, attested and published from f0dd526 by run 42576870272. Existing users need to reinstall the runtime from the Runtime tab.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #70
Closes #84
Problem
package.jsonis 3.16.3. Upstream then taggedv3.17.1(a60ba6a) andv3.17.2(a9fe401) again, with GitHub Releases. The changelog lists only 3.16.3 and 3.17.2 after 3.16.2, so this PR moves straight to 3.17.2 and reviews 3.16.3 from its notes.Source and build
v3.17.2(a9fe401eede6e6e5e01be9048679c206fe6f02d9). A tag satisfies ADR 15 directly. ADR 20 gets a dated note: prefer a matching tag, and keep the untagged-commit rule for releases like 3.16.1/3.16.2.EventErrorRPC frame.sync-zcode-source.mjs --writefailed on a vendored file the new baseline no longer needs. It now deletes such files; verification still rejects unexpected files.0a9b571) and applies unchanged. Only its header's target commit changed; the SHA-256 is now6f670f8….build-zcode.mjs,builtin-provider-config.mjs, the archive layout, Node 24.14.0+ and pnpm 10.33.2 are unchanged. The result is Server 3.17.2 / Agent 0.17.1.Provider changes
ZCODE_APP_VERSIONinUser-Agent/X-ZCode-App-Version, or its CLI version without it.ZCode/0.17.1.content-filter/content_filter/GLM'ssensitive) fails at once withreason: "content_filter"instead of being retried. That reason is outsideModelFailureReason, so it fell toMODEL_REQUEST_FAILEDand was dropped from the diagnostic. It is nowMODEL_CONTENT_FILTERED.workspaceMcpAdmission.source. ZCode treats them as project declarations when the project declares the same name or its config is unreadable, and blocks them. The provider now sends the new protocolscope: "user"(as Desktop does for user servers), only to 3.17.1+ Servers, because older strict schemas reject it.Reviewed, no code change
defaultEnabled): its CLI runs from Bash and authenticates through the Server's official endpoint, which the stdio Server builds too. Only its panel is Desktop-only, and that panel's tools are hidden from the model. It is not suppressed; deployment itself is untested.!blocks become ordinary Bash calls.stopped(provider). ZCode itself lets the session be reclaimed and resumes them on the next open, so the ADR 25 veto is unchanged.resultPendingis still never cleared.userInputrow, so ADR 22 holds.oauth,setting(CAS),provider-settingsandusage-statsare unchanged where the provider uses them. Provider templates grew (Kimi, MiniMax M3.1 Flash, …).ZCODE_CUA_PRODUCT_HELPERandmcp__node_repl__jsare unchanged.Verification (macOS arm64)
typecheck,npm test(24 files, 238 tests),build,format:check,check:zcode-source(126 files) andcheck:zcode-patches(cleanv3.17.2checkout) pass.test:upstreamagainst Paseo v0.15.3 (d91ae138). All checks pass.v3.17.2with Node 24.21.0, pnpm 10.33.2 andZCODE_ENV=production, then packaged as3.17.2-paseo.0. It is not published.test:stdio-runtime. All checks pass, including three new ones:'0.17.1' !== '3.17.2').sensitivereply arrives asMODEL_CONTENT_FILTEREDwith exactly one model request.scope, this fails on 3.17.2 (the tool is missing).test:e2e. Real model, isolated data: all passed.test:native-restore. Still fails as recorded (expectededit+ Plan ON, gotyolo+ Plan OFF).test:stdio-runtimepasses; the 3.17-only checks are gated.Managed runtime 3.17.2-paseo.1
After the first CI run passed,
zcode-runtime-v3.17.2-paseo.1was pushed onf0dd526.zcode-runtime-3.17.2-paseo.1.tar.gz, 83,086,942 bytes, SHA-25624e3a9b03260d7b800958ccba4cfdc8233eee67936170636da79d440245bd15d.gh attestation verifyconfirms the release workflow at that tag, with sourcef0dd526.BUILD-INFO.jsonrecordsa9fe401(3.17.2) and patch6f670f8…; the bundled patch is byte-identical to the repository's.f2da56e.XDG_DATA_HOME, andtest:stdio-runtimepassed on it withsource: managed(Server 3.17.2, Agent 0.17.1).pnpm installwithERR_PNPM_ENOENT(renaming intonode_modules/tsup/node_modules/esbuild), then passed on the third attempt.node-linker=hoisted. It is recorded but not worked around.Not verified