chore(z-ai): retire harness — no active subscription #2
Reference in New Issue
Block a user
Delete Branch "retire-z-ai"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Retires the
z-aiprovider harness from the framework. Companion to the agent-runtimes PR. Same rationale: no active subscription, never cut over to ESO.What's removed
harnesses/contexts/z-ai/v1/{harness.yaml, init.sh}gitea-admin/v1/init.shandgitea-https/v1/init.shcomments (the staging pattern they describe applies to all wrapper-script providers; the comment listed z-ai as an example)CLAUDE.md"no secrets in this repo" section (and updated to acknowledge ESO has now replaced the SOPS file model)No composites layer z-ai. Verified via grep.
Test plan
grep -rn 'z-ai' agent-runtime-framework/returns no live config refsRemoves harnesses/contexts/z-ai/v1/. Mirrors the agent-runtimes companion PR — the z-ai harness was never cut over to ESO and there's no active subscription. Revival path documented in agent-runtimes planning/future/providers F49. Removed: - harnesses/contexts/z-ai/v1/{harness.yaml, init.sh} Updated: - CLAUDE.md — drops z-ai from the 'no secrets in this repo' context list. Retirement note added. - gitea-admin/v1/init.sh — comment ref to z-ai removed. - gitea-https/v1/init.sh — comment ref to z-ai removed. No composites layer z-ai (verified via grep across composites/); no model registry entries reference it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>