chenchenandClaude Opus 4.7
d8f61957f0
Bundled release bumping Manager to 1.4.2 with four product-doc gap
closures lined up in a single deploy.
VERSION:
- 1.2.0 → 1.4.2 (catches up after Sprints 1-5 shipped under 1.2.0)
H2 — sk- hash phase A (server-side, zero client impact):
- tokens table: new key_hash varchar(64) index column
- Token.Insert() dual-writes Key + KeyHash on every new token
- BackfillTokenKeyHash() runs at startup, batches 500 rows at a
time, idempotent. Fills legacy rows that pre-date the column
without blocking app boot
- 5 unit tests pin: sha256 correctness, dual-write on Insert,
empty Key → empty hash, backfill behaviour, idempotency
- Phase B (switch lookup index off plaintext + drop Key column)
can ship later once telemetry shows key_hash IS NULL count is 0
M9 — task detail drawer with audit timeline:
- Deployments page click → Sheet drawer with RunDetailPanel +
new RunAuditTimeline component
- Timeline pulls from existing /api/agnet/deployments/:id/events
which Sprint 1 already wired to the persistent
agnet_audit_events table — no new backend
- Vertical timeline w/ coloured dots (primary / amber / rose by
classifyEventLevel), occurred_at + correlation_id per row,
max-height + overflow for long traces
- 15s polling; empty/loading/error states all rendered
M3 — project_doc as a first-class binding step:
- Resource binding wizard split "SK or project docs" into two
distinct steps: "Connect project docs" + "Connect SK skill packs"
- Each step's Connect button pre-selects the matching type in
the advanced sheet so users don't accidentally tag a doc repo
as Git or SK
- Summary dialog still receives the combined skOrDocSources view
to keep the recommendation-card contract unchanged
M7 — secret vault status (admin panel):
- controller/secret_store.go: new GetSecretStoreStatus handler
+ fetchHealth() method. Hits OpenBao /sys/health (token-less
upstream endpoint), maps to a sanitized response — NEVER
returns secret names or values per product docs §13.9
- Graceful degradation: env vars unset → "not configured" pill;
network error → "unreachable"; sealed → amber warning; healthy
→ green
- Mounted at GET /api/secret-store/status behind middleware.AdminAuth
- New SecretStoreSection in system-settings/maintenance,
registered before Performance. Read-only card with refresh
button, 7 status fields, message line, "how to enable" hint
Verification:
- go vet ./... clean
- go test ./controller/... ./middleware/... ./model/... all green
- tsc --noEmit clean
- Backend M7 endpoint deliberately tolerant — production may not
have OPENBAO_ADDR set yet, UI shows "not configured" instead of
500ing
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Heicode
Heicode 面向多人协作、可追溯交付的软件团队：把需求对齐、实现、验证、发布和持续运营连成一条少断层的链路，并用可编排的智能体角色承接其中可标准化的环节——强调「能复盘、能审计、能按团队规模裁剪」，而不是罗列某一家的工具栈。
下面的目录表仅供工程查阅；**不代表对外产品承诺、路线图或你必须采用的集成方式。 **
这个仓库里有什么（工程布局）
| 目录 | 大致含义 |
|---|---|
cc-haha/ |
Heicode（终端与桌面客户端及本地服务；此为源码目录名）。 |
heicode/ |
Heicode Manager（网关与管理控制台服务端；此为源码目录名）。 |
website/ |
产品介绍站点（Next.js；可 pnpm dev 或 Docker 预览）。 |
docs/ |
愿景与范式；docs/milestones/ 交付里程碑；docs/integration/ Agnet 等平台接口设计。 |
产品在解决什么问题
- 协作范式：把瀑布 / 敏捷下的角色分工落到可复述的闸门与智能体承接边界（方向与原则见
docs/vision-heicode-full-stack-agentic-dev.md；编队明细在文档附录）。 - 交付可追溯：文档、沟通与变更尽量与版本、发布对齐，便于复盘与合规。
- 工程上：同一仓库便于客户端与服务端同步发版、统一回归，减少「谁和谁版本对不上」的摩擦。
详细愿景与范式
docs/vision-heicode-full-stack-agentic-dev.md
快速启动（开发联调）
# 根依赖（Bun monorepo 根目录）
bun install
# Heicode 客户端本地服务（目录 cc-haha）
cd cc-haha
bun run src/server/index.ts
# 另开终端：桌面端
cd cc-haha/desktop
bun run tauri dev
联调网关时示例：
HEICODE_TAIJIAICLOUD_BASE_URL=http://localhost:3000 bun run src/server/index.ts
Heicode Manager（heicode/）中与 Heicode 登录相关的路由（最小集，以实际代码为准）：
GET /heicode/oauth/authorizeGET /heicode/oauth/session
平台侧能力还包括模型发现（如 GET /v1/models）与 Anthropic Messages 兼容入口等，详见 Heicode Manager（heicode/）与 Heicode 客户端（cc-haha/）各自 README。
官网（Next.js）
cd website && pnpm install && pnpm dev
若根目录提供 docker compose，可按 compose 说明构建预览镜像（以仓库内 docker-compose.yml 为准）。
发版与回归建议
- 同一版本标签发布客户端与网关镜像。
- 每次发版至少回归：登录、模型拉取、对话请求。
- 先在本地 Docker / 本地联调通过，再做外网域名与证书。
相关外部参考（概念）
- oh-my-claudecode — Claude Code 类工具的高效实践参考。
- Agnet 平台以实际部署环境与文档为准。
许可证
各子项目许可证见各子目录内 LICENSE（例如 Heicode Manager / heicode/ 侧常见为 AGPLv3）。