Skip to content

Catalog v0.7.1, quieter pages, and a Gitee mirror for zh browsers - #36

Merged
yujiezhang-ops merged 2 commits into
mainfrom
feat/catalog-v071-and-detail-diet
Aug 18, 2026
Merged

yujiezhang-ops merged 2 commits into
mainfrom
feat/catalog-v071-and-detail-diet

Conversation

@yujiezhang-ops

Copy link
Copy Markdown
Collaborator

Three directives in one branch, two commits.

1. Catalog sync to upstream v0.7.1 (0fa77a8)

  • CLI contract: 8 → 10 agents. dsh (DeepSeek Harness) enters at rank 1, pi at rank 10; dsh leaves planned-agents.json per that file's own rule. Provider catalog gains jiekou at order 1. v0.7.2 left both locks byte-identical — checked, not assumed.
  • Desktop registry: 2 → 6 apps. DSH Desktop (carrying upstream's Unofficial flag — built by anywhere-labs, not DeepSeek, and the catalog copy says so), Claude Desktop (manual install via official page), WorkBuddy International, ZCode.
  • Every new adapter's protocol read from upstream's writer implementation, not assumed: WriteDSH/WriteOpenClaw/WriteKimiCode/WritePI write openai-completions, WriteHermes an OpenAI base_url, the registry declares claude-desktop anthropic and pins zcode to openai.
  • Marks synced: kimi-code.svg and pi.svg from lobe-icons, digests matching upstream's asset-rights records; shared-render rule extends (Claude Desktop → Claude mark, DSH Desktop → DeepSeek mark, reasoning in NOTICE). The explorer now renders 16 agents.

2. Engineering-detail diet (73576d6)

Per the review direction: versions, commit hashes, protocol names and hex digests are not what a mature product site leads with.

  • Hero eyebrow line deleted (both locales); stagger rebalanced.
  • Demo caption no longer prints v0.5.0 · 0fbbe94 — the pin lives on in data-source-release where e2e reads it.
  • Home stops enumerating wire protocols; agent rows drop the protocol chip. The explorer keeps protocol as a filter axis — there it is the catalog's data; on the home page it was decoration.
  • Download card/panels lose the version row, the 64-hex digest and the shasum block; the page routes to the release's published SHA256SUMS instead. The security page's evidence list likewise points at the release page for version+digest, keeping the per-platform signing states and the spctl verification it exists to teach.
  • Quickstart, install help and llms.txt updated to name the manifest as the verification source.

3. Gitee mirror for Chinese-language browsers (73576d6)

  • Per-file, build-time verified: the build queries the Gitee API for the release tag and emits data-cn-href only for assets the mirror actually hosts (currently the two macOS DMGs and a Linux deb). Unmirrored targets keep GitHub for everyone; an unreachable Gitee degrades to GitHub links and the mirror e2e skips honestly.
  • Byte-identity verified before wiring: the mirrored darwin-arm64 DMG hashes to 325cbcf6…01ee, matching GitHub's published digest. The security page's same-package section now names the channels that actually exist (GitHub Releases + Gitee mirror), retiring the file-host/internal-drive list flagged in the earlier review.
  • Client-side swap on navigator.languages (browser language, not page language), with a visible note and a GitHub fallback link. Verified interactively: zh browser → macOS on Gitee with note; Windows target → GitHub, note hidden.

Test plan

  • vitest 104 passed (new mark digests + catalog coverage bind automatically)
  • build: astro check 0 errors, 57 pages validated (new agent/provider pages)
  • e2e with GITHUB_TOKEN: 216 passed (+3 new mirror tests across projects; press-feedback test now scrolls the longer demo roster; mirror tests select the platform explicitly because Playwright's Desktop Chrome carries a Windows UA)
  • Six visual baselines re-rendered at the new hero height; diffs inspected, content identical
  • Note: if Gitee's API is unreachable during a CI build, pages ship GitHub-only links and the three mirror tests skip with a stated reason — degradation, not failure

🤖 Generated with Claude Code

yujiezhang-ops and others added 2 commits August 18, 2026 17:21
The vendored locks move to tag v0.7.1 (commit 4fe376cb; v0.7.2 left both
files byte-identical, which was checked rather than assumed). The
command-line contract grows to ten agents: dsh (DeepSeek Harness) enters
at rank 1 and pi at rank 10, so dsh leaves planned-agents.json — its own
note says shipping upstream is exactly when an entry must move out, or
the site lists the agent twice. The provider catalog gains jiekou at
order 1.

desktop-agents.json is re-transcribed from the v0.7.1 registry, which
tripled: DSH Desktop (built by anywhere-labs, not DeepSeek — the
registry's Unofficial flag, carried here and stated in the catalog
copy), Claude Desktop (detect and configure; install goes through the
official download page), WorkBuddy International and ZCode join the two
existing entries, ranked in the registry's own declaration order.

Each new adapter's protocol is read from upstream's writer rather than
assumed: WriteDSH, WriteOpenClaw, WriteKimiCode and WritePI all write
openai-completions blocks, WriteHermes an OpenAI base_url, the registry
declares claude-desktop anthropic and pins zcode to openai.

Marks: kimi-code and pi arrive from lobe-icons with upstream's own
digests (verified against the fetched files), and the shared-render rule
extends — Claude Desktop renders the Claude mark, DSH Desktop the
DeepSeek mark, with NOTICE stating why a vendor's mark can identify a
third-party app for that vendor's models. Aider, both WorkBuddy editions
and ZCode stay letter glyphs: no auditable mark exists to bundle.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ds via Gitee

Two changes that share the download surface.

The diet: version numbers, commit hashes, protocol names and hex digests
came off the visitor-facing pages. The hero's eyebrow line went entirely
(the stagger rebalances to five parts); the demo caption no longer
prints the walkthrough's release and commit — that contract lives on in
data-source-release, where the e2e suite reads it; the home catalog
section stops enumerating wire protocols and its agent rows drop the
protocol chip (the explorer keeps protocol as a filter — there it is the
data, not decoration); the download card and panels lose the version row
and the printed SHA-256 with its shasum block, replaced by a route to
the release's published checksum manifest; the security page's evidence
list points at the release page for version and digests instead of
reprinting them, keeping the signing states and the spctl verification
it exists for. Quickstart, the install help and llms.txt now name the
manifest as the place to verify against.

The mirror: a Chinese-language browser gets its download from the Gitee
mirror (gitee.com/maimory/BootAgent) — per file, not per site. The build
asks the Gitee API which assets the mirror actually hosts for the
release tag and emits a data-cn-href only for those, so unmirrored
targets keep GitHub for everyone and an unreachable Gitee degrades to
GitHub links with the mirror tests skipping honestly. The swap happens
client-side on navigator.languages, with a visible note and a GitHub
fallback link. Before any of this was wired, the mirrored darwin-arm64
DMG was downloaded and hashed: SHA-256 325cbcf6…01ee, byte-identical to
the digest GitHub publishes — the same-package promise now names its
real channels on the security page, replacing the file-host-and-drive
list that never existed.

Press-feedback and mirror e2e account for the longer demo roster and the
test browsers' Windows user agent; the six visual baselines re-render at
the new hero height, content verified unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@yujiezhang-ops
yujiezhang-ops merged commit 9cb549f into main Aug 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant