chore: stop tracking the public site, now its own repository - #14
Merged
Conversation
…g seam The index is rebuilt for this branch's layout -- Go at the repository root, no Python -- and .gitignore now covers it, since whether to build one is each developer's call and `codegraph index .` takes half a second. Two things worth writing down came out of using it here. internal/binding was missing from the directory list even though it is the only seam between React and Go. Exploring AgentService returns three files that have to move together: the Go service, the generated frontend/bindings, and the hand-written frontend/src/backend/wails.ts. The types in frontend/src/types/api.ts are hand-written rather than imported from the bindings, so a backend DTO and that file are two sources of truth for the same shape -- the index is the fastest way to find the half that was not updated. The blast radius warning "no covering tests found" only follows direct callers, so an implementation invoked inside a higher-level function reads as untested when it is not. Noted so nobody adds a test that already exists. go vet and go test ./... are clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The site moved to MaimoryLab/OneAgent-site, carrying its 13 commits via git subtree so its history survives the move. It had exactly one build-time dependency on this repository -- catalog.ts imported agents.lock.json and providers.lock.json from the root -- and those are now vendored there, refreshed from a release tag rather than following this repository's main. That is deliberate: the site describes what a published release supports, so tracking main would advertise agents that are merged but unshipped. Documentation is corrected rather than merely repointed. public-site-operations.md was describing two workflows that no longer exist here (technical-preview.yml, site.yml -- only build-artifacts.yml remains), so its release sequence was already unusable as a guide; it is now trimmed to the obligations this repository still carries. ADR-006 keeps its text and is marked Partially Superseded, since only its "same repository" clause was overturned. The migration plan's directory listing is annotated instead of edited, being a completed acceptance record. .gitignore now ignores site/ rather than its build subdirectories: on machines cloned before this commit the directory stays in the working tree, and without the entry git status reports an entire Astro project as untracked. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
yujiezhang-ops
force-pushed
the
chore/extract-public-site
branch
from
August 4, 2026 08:12
543a392 to
03a47d7
Compare
Collaborator
Author
|
补一处遗漏（已 amend 并 force-push）： 站点的启动配置现在在站点仓库自己的 |
This was referenced Aug 4, 2026
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
1 participant
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.
公开站已迁出到 MaimoryLab/OneAgent-site（private，14 个提交：
git subtree split保留的 13 个原有历史 + 1 个改造提交）。本 PR 从这个仓库移除site/。唯一的耦合点
site/src/lib/catalog.ts从仓库根 importagents.lock.json和providers.lock.json。这两个文件现在 vendor 在站点仓库的data/下，从发行 tag 刷新，而不是跟随本仓库main。这是刻意的：站描述的是已发布版本支持什么。跟着
main会把已合并但未发布的 Agent 宣传成可用，也等于把改一行文案重新绑回桌面端的发布节奏——正是拆分要消除的耦合。副作用是新增 Agent 或改披露字段后，需要到站点仓库刷新一次，这一点写进了docs/public-site-operations.md。下载链接、体积、校验和不在 vendor 范围，仍由站点在构建时从 GitHub Releases API 读取。下载页上一个过期的校验和比没有校验和更糟。
文档是修正，不只是改指向
docs/public-site-operations.md通篇按technical-preview.yml和site.yml两个工作流写，而这两个文件在本仓库已经不存在（只剩build-artifacts.yml）——它的发布顺序早就不能照着执行了。这次删掉失效步骤，只留本仓库仍然承担的义务：Release 是公开事实源、providers.lock.json的商业字段边界、Stable 门禁。ADR-006 保留原文，标记为 Partially Superseded——被推翻的只有「在同一仓库维护」这一条，「不把营销路由加入 Launcher」以及决策 2–5 仍然有效。
wails-v3-migration-plan.md是已完成的验收记录，目录清单加注而不改写。.gitignore
改成忽略
site/整个目录，而不是它的构建子目录。迁出前克隆过的机器上site/仍躺在工作区里，不忽略的话git status会把一整个 Astro 项目报成未跟踪文件。验证
站点仓库（拆分后）：单测 40/40、
pnpm run build32 页、e2e 133 passed / 23 skipped（桌面/平板/手机三视口，含 axe 无障碍检查），与拆分前一致。本仓库（移除后）：
go vet ./...无输出、go test ./...13 个包全 ok、前端 139/139 通过。没有任何 Go 或 TS 代码引用过site/，go:embed也没有。顺带发现的既有问题（未在本 PR 处理）
.gitignore的注释说!frontend/dist/.keep是为了让manifest_embed.go的go:embed all:frontend/dist能在全新克隆上工作，但那个.keep实际并未被跟踪。新 worktree 里go vet直接失败于pattern all:frontend/dist: no matching files found，要先跑一次前端构建才能编译 Go。这跟本 PR 无关，所以没混进来。🤖 Generated with Claude Code