task-ledgerlisted

# Development task ledger (Feishu Base) ## Hard rules 1. Development tasks **must** target an **allowlisted** root for the active agent (see Path guard / `tasks-allowlist.json`). main → wezdeck|team-repo; pm → FE1 (ops). Do not hard-code another machine's `/home/...` in commits. 2. If the user asks for another repo: **do not** `open` a ledger row as accepted work; refuse and explain allowlist policy. 3. When accepted, **time loop must close**: - `open` → (user confirms plan/初评/开发方式) → **`confirm`** if `--confirm-required 1` → work → `close` - `close --status done` **fails** if still 需确认 and never `confirm`ed - `cancelled` / `blocked` / `failed` may close without confirm 4. Never write secrets into the ledger. 5. Final reply **must** include `task_id`. 6. If CLI fails, say so; do not invent `task_id`. 7. When the request has a clear **需求提出人** (product / user who asked): record them on open/update with `--requester-id <ou_…>` (preferred). Feishu person field name: **需求提出人**. Do not leave it blank when known. 8. **Order with worktree:** `open` first; after claw worktree exists, `update` cwd/分支; after user confirms 初评+开发方式, **`confirm`**; then implement. 9. Pure Q&A: do not open a row. As soon as the user accepts **implementation**, open before assess/create (same turn is OK if open is first). 10. **Test hygiene:** after every smoke / CLI self-test that `open`s a row, **`delete`** that row (and local index entry). Do **not** leave `smo