docs(contributor): refresh task board around current bottlenecks - #3099
Conversation
Rewrite CONTRIBUTOR_TASKS.md around the live constraints: merge-queue gating, Turn fencing convergence onto the typed Effect Program settlement algebra (#3074), caller-approved validation for self-reported completion (#3082), CLI output budgets/ergonomics (#2881), dashboard cost projection (#3085), fresh-project onboarding (#3092), release docs timeline, and hot-module maintainability debt. Retire stale rows, add M7.1 parity fixtures and a read-only replay lens tasks, and keep all docs-governance and benchmark-workflow smoke invariants intact.
Premerge validation summaryChanged surface: CONTRIBUTOR_TASKS.md only (docs / contributor metadata). Checks run:
Failures/skips: none. Manual holds: none. Coverage rationale: the two docs smokes encode the repository's hard invariants for this board (required current-state strings, stale-row exclusions, benchmark seam phrasing, public-safety snippets); canary docs/public-boundary checks confirm the diff is safe and single-purpose. |
Replace the operational bottleneck framing with six project development directions (management surface, Effect Program runtime maturity, verified state transitions, operator observability, contributor/operator experience, maintainability) and drop the merge-queue row from maintainer-owned work.
huangruiteng
left a comment
There was a problem hiding this comment.
PR #3099 exact-head 评审(head ab401d30e468cf8cd73ef179d6e66649d777a67b)
详细中文评审
动机
CONTRIBUTOR_TASKS.md 此前以“Current Bottlenecks”(当前瓶颈清单)组织,内容贴近维护者近期调度(合并队列、#3074、#3082、#3085、#3092、release 文档时间线等),对贡献者来说更像一份过期的运维待办,而不是可据此选活的方向性指引。本 PR 把它重写为围绕产品发展方向的贡献者任务板:六个方向、新增 7 个 contributor slice、退役过期行。
改动思路
- 用
Project Development Direction(六方向:管理面、Effect Program runtime 成熟度、verified state transitions、operator observability、contributor/operator experience、maintainability)替换旧的瓶颈列表;每个方向都指向现有协议/问题号(#3082/#3074/#3085/#3092/#2881),并要求“不做第二套 ledger/抽象”。 - 新增 GH-C83(M7.1 parity fixtures)、GH-C84(read-only
interpret_turn_journalreplay lens)、GH-C85(validation_command caller)、GH-C86(dashboard cost projection)、GH-C87(onboarding regression fixture)、GH-C88(budget-aware CLI ergonomics)、GH-C89(AGE-style attractor design),并给每个任务写了 scope 边界与验证命令。 - 退役过期行:移除 GH-C91(批量合并队列——属于 maintainer/自动化职责,不该是 contributor 任务);把 global risks 改为“next command”,observable handle slice 标注等 #3080 合并后启用,task leases 与 Turn fencing 对齐现状。
具体改动
CONTRIBUTOR_TASKS.md(+74/-28):方向段重写 + Priority Queue 行增删;Starter/Focused 表新增条目均带明确 in/out-of-scope 与验证命令;保留 docs-governance 与 benchmark-workflow smoke 所需的结构不变量。
对主干的风险
docs-only、单文件、无代码/CI/首屏变化。内容与当前产品方向一致(Effect Program、typed settlement、verified completion 都是活跃控制面路线),新任务都有真实后续(#3074/#3082 等)而非空想脚手架。公开/私有边界扫描 clean,无内部路径或凭据。风险低。
我的整体评价
这是一次高质量的贡献者入口重构:把“维护者近期待办”换成“产品方向 + 可认领切片”,每个新 GH-C 都有明确 scope、验证与归属,过期任务也干净退役。与仓库 scope-fit 与 right-sized 原则一致。无阻塞项,结论 APPROVE(作者即 owner,GitHub 禁止形式化 self-approve,按仓库约定以 COMMENTED 记录同一结论)。
验证
- exact head
ab401d30e468cf8cd73ef179d6e66649d777a67b(评审时 head 未变):python3 examples/docs-governance-smoke.py:通过python3 examples/benchmark-developer-workflow-doc-smoke.py:通过loopx check --scan-path CONTRIBUTOR_TASKS.md:public boundary clean- CI:dependency-review SUCCESS
Approval conclusion (author-owned PR; GitHub blocks formal self-approval)
Head: ab401d30e468cf8cd73ef179d6e66649d777a67b
Verdict: APPROVE — docs-only rewrite of CONTRIBUTOR_TASKS.md from a bottleneck backlog to a development-direction task board: six directions, seven new scoped contributor slices (GH-C83..GH-C89), and clean retirement of stale rows including GH-C91. No code, CI, or first-screen changes; governance and benchmark-workflow smokes plus the public-boundary scan pass at the exact head.
Key finding: No blockers. The board stays aligned with active control-plane routes (Effect Program, typed settlement, verified completion) and each new slice names its scope, validation, and ownership.
Validation: docs-governance smoke, benchmark-developer-workflow-doc-smoke, and loopx check --scan-path CONTRIBUTOR_TASKS.md all pass; dependency-review green.
What
Rewrite CONTRIBUTOR_TASKS.md around the project's development direction instead of an operational backlog:
Project Development Directionsection with six directions: management surface, Effect Program runtime maturity, verified state transitions, operator observability, contributor/operator experience, and maintainability.interpret_turn_journalreplay lens), GH-C85 (validation_command caller), GH-C86 (dashboard cost projection), GH-C87 (onboarding regression fixture), GH-C88 (budget-aware CLI ergonomics), GH-C89 (AGE-style attractor design).Validation
python3 examples/docs-governance-smoke.py: passedpython3 examples/benchmark-developer-workflow-doc-smoke.py: passedloopx check --scan-path CONTRIBUTOR_TASKS.md: public boundary cleangit diff --check: cleanloopx canary premerge --from-git-diff --goal-id loopx-meta: all selected checks passed, 0 run/direct failures (receipt recorded after PR creation)