feat(web): drive 6900 work by capability families
This commit is contained in:
26
nextTask.md
26
nextTask.md
@@ -16,6 +16,15 @@ external documentation are supplemental references for toolchain/browser
|
||||
constraints only; they cannot override or replace behavior present in the
|
||||
Blender source.
|
||||
|
||||
Implementation iron rule: advance the 6900-entry inventory through capability
|
||||
families and unique behavior batches at maximum practical throughput. Do not
|
||||
run Chromium, E2E receipts, parity verification, save/reopen verification,
|
||||
determinism checks, or completion overlays in this implementation lane. The
|
||||
only allowed checks are source compilation, TypeScript/type safety, lint,
|
||||
bounded build and queue/governance integrity needed to avoid committing broken
|
||||
functionality. Do not drift into repeated maintenance-only waves while an
|
||||
unimplemented Blender capability family remains available.
|
||||
|
||||
## Copyable Resume Prompt
|
||||
|
||||
Use the following prompt when continuous execution is needed. It is the
|
||||
@@ -42,6 +51,7 @@ and (when authorized) repository push:
|
||||
11. 每轮结束报告实现切片、当前任务、`nextTask`、最小检查退出码、原始 inventory、effective inventory 是否保持不变、提交/推送状态和剩余真实阻塞。
|
||||
12. CONTINUOUS_LOOP_REQUIRED:成功交接后立即开始下一轮;不得在成功提交、推送或生成新 manifest 后等待用户确认、只写计划或只汇报状态。每轮必须重新运行 `print-task-context` 和 `check-task-context`,使用新 parent manifest 的 `nextTask`,不沿用上一轮上下文。
|
||||
13. 可使用仓库内 unattended runner 保持进程级连续执行:`node tools/web/run-wbv2-continuous.mjs --max-iterations 0`。它只执行任务卡声明的入口;`0` 表示不限轮数,`--max-iterations N` 用于受控运行,`--commit --push` 才允许自动提交/推送。任何入口失败、退出 0 但队列未前进、治理失败或 push 失败都立即停止并保留 `tests/golden/<task>/continuous-runner.log`,不得重试未知结果。
|
||||
14. 6900_IMPLEMENTATION_IRON_RULE:只按 capability family 和唯一行为批次实现全部 Blender 功能;不启动 Chromium/E2E/receipt/parity/save-reopen/determinism 验证,不写 completion overlay,不把维护 smoke 当作能力完成。若任务卡与本铁律冲突,以源码实现和本铁律为准,并将验证留到后续独立验证波次。
|
||||
```
|
||||
|
||||
## Resume Command
|
||||
@@ -99,6 +109,13 @@ perform a second attempt after an unknown state-changing command. A root task
|
||||
is itself an executable enabling task: run its declared root generator, then
|
||||
continue from the generated child task in the same continuous run.
|
||||
|
||||
Every implementation iteration must answer one question before editing: which
|
||||
capability family or unique behavior from the immutable 6900 inventory becomes
|
||||
more implemented by this change? If the answer is only "maintenance", skip it
|
||||
when a source-backed capability slice is available. Maintain the original
|
||||
inventory and provenance; implementation progress is recorded in task reports,
|
||||
not completion overlays.
|
||||
|
||||
For process-level unattended execution, run:
|
||||
|
||||
```bash
|
||||
@@ -249,12 +266,12 @@ Recorded: 2026-08-29 Asia/Shanghai
|
||||
|
||||
| Field | Value |
|
||||
| --- | --- |
|
||||
| Current task when this file was written | `WBV2-P43-000` |
|
||||
| Current task when this file was written | `WBV2-P44-000` |
|
||||
| Current task state | `in_progress` |
|
||||
| Parent manifest | `tests/golden/WBV2-P42-003/manifest.json` |
|
||||
| Current task card | `docs/tasks/WBV2-P43-000.md` |
|
||||
| Parent manifest | `tests/golden/WBV2-P43-003/manifest.json` |
|
||||
| Current task card | `docs/tasks/WBV2-P44-000.md` |
|
||||
| Current task-context nextTask | `NONE` |
|
||||
| Focused command | `node tools/web/generate-wbv2-continuous-root.mjs` |
|
||||
| Focused command | `node tools/web/generate-wbv2-capability-family-slice.mjs --task WBV2-P44-000 --write` |
|
||||
|
||||
The snapshot is informational and may become stale. On every resume, the queue,
|
||||
parent manifest, and fresh `print-task-context` output win. Never infer a task
|
||||
@@ -264,6 +281,7 @@ number from this table or from historical status files.
|
||||
|
||||
- Chromium is the only permitted browser runtime; never run Firefox or WebKit.
|
||||
- `blender-5.2.0` source and Blender Main are the behavior authority; web references are supplemental and must be recorded only when they affect build/runtime constraints.
|
||||
- The 6900 implementation lane is verification-free: no Chromium/E2E receipts, parity overlays, save/reopen or determinism runs until a separately authorized verification wave.
|
||||
- Do not read full historical plans, all status logs, or the full gap plan by
|
||||
default.
|
||||
- Keep unrelated user changes. Never use `git reset --hard` or `git checkout --`.
|
||||
|
||||
Reference in New Issue
Block a user