Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Rewrite P1] Factory logistics: host split, worktree protocol, cost telemetry

未关闭
#871 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, rust, typescript

调研方向

Start with parent issue #860 and locate factory-spans.ts and the existing docs/rewrite/ runbook sections. Check how factory jobs, worktrees, and cost reporting currently operate before attempting the end-to-end proof. Done means both hosts have documented runbooks and a trivial job produces a Rust change built on tauceti, reviewed on chappie, with spans recorded and Actual Cost filled on the board.

由索引模型根据 Issue 内容生成。

描述

factory rewrite

Parent: #860
Milestone: Phase 1: Rust foundation
Host: both · Expected cost: $200

The host split and the working agreement the factory runs under.

  • chappie (this host): factory orchestration, all review rounds, LMDB benchmark rig, differential harness driver, CI-first validation. Constraint measured: docker access is OPA-authz-scoped (labelled containers allowed; builds via BuildKit driver; no --load) — Rust builds here run in BuildKit via the container driver or natively on the host toolchain path the factory agents use
  • tauceti (Ada's host): release-grade builds (cargo build --release target matrix), the 72h soak, the 24h fuzz run — long-running jobs that shouldn't hold chappie's capacity. Access path: ssh + the shared worktree per phase; Ada's consent + the exact runbook (what may run, resource caps, scratch dirs) recorded here before first use
  • Worktree protocol: each phase gets ~/nostream-worktrees/phase-N/ on both hosts; chappie's factory jobs branch from the phase worktree; tauceti pulls the same branch refs; artifacts (benchmarks, fuzz corpora, soak logs) flow back as committed files under docs/rewrite/ or as artifacts attached to the phase issue
  • Cost telemetry: factory spans script (factory-spans.ts) runs per job; the factory manager reads spans → Actual Cost USD per issue on the board; weekly variance roll-up as an issue comment on #860
  • Model budget: the rewrite runs on the fleet's litellm config (no new provider); heavy review rounds schedule outside Anthropic peak hours where possible (13:00–19:00 UTC Mon–Fri) per the model-schedule policy

Acceptance: both hosts have the runbook sections; one end-to-end proof — a trivial factory job (spec → build → review → approve) lands a Rust change built on tauceti, reviewed on chappie, with spans recorded and the board item's Actual Cost filled.

主要语言
TypeScript
星标
829
派生
234
平均合并
18 小时 43 分钟
30 天内合并 PR
67

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cameri/nostream 的其他 Issue

查看 cameri/nostream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。