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 摘要。