v0.8.6 — 完善定期会话关于复用会话的逻辑

v0.8.6

中文

• 完善定期会话关于复用会话的逻辑：cron 定期任务现在可明确选择“每次新建会话”或“首次新建会话，后续复用”，也仍可指定当前项目中的既有会话。
• 复用策略不再受“完成后移回待办”或“完成后新建下一轮待办卡”影响；选择“首次新建、后续复用”时，首轮会话会安全传递到下一周期卡。
• 一次性定时任务维持原有的单次执行语义；已有定期任务保持此前的自动续用行为，升级不会静默改变配置。

English

• Improved periodic session reuse logic: cron tasks can explicitly choose “new session every time” or “create first, then reuse,” while still allowing selection of an existing session from the current project.
• The reuse policy no longer depends on whether periodic completion rearms the current card or creates a successor; create-then-reuse safely carries its first session into the next period card.
• One-shot tasks retain their original single-run semantics, and existing periodic tasks retain their prior automatic-reuse behavior without silent configuration changes.

Verification

• npm run typecheck
• npm test — 371 tests passed
• npm run build
• node tests/smoke-host.mjs — SMOKE OK
• npm pack --dry-run --json — dsh-taskboard@0.8.6

v0.8.5 — 修复默认执行权限样式

v0.8.5

• 修复设置页“默认执行权限”的显示问题：三个选项恢复正常排列，选中状态也能清楚显示。

English

• Fixed the default execution permission choices in Settings: the three options are laid out correctly again, with a clear selected state.

v0.8.4 — 会话复用与看板体验改进

中文

• 定时任务可延续已有对话：创建或编辑任务时，可选择当前项目中的会话；默认仍为新建会话。见 #41。
• 看板读取更稳妥：部分内容读取失败时，已显示的任务和项目会保留，并给出更清楚的提示。见 #42。
• 表单更顺手：新建与编辑窗口更宽，执行权限和紧急度并排显示为下拉框。点击窗口外不会关闭表单；Esc、关闭和取消仍可退出。

感谢 @Arnozzc87 对 #42 的报告与复核。#42 所述偶发响应中断的根因尚未确定；本版修复了已确认的看板处理和错误提示问题。如果新版本再次出现中断，请附上失败请求记录和相关日志。

English

• Continue an existing conversation for scheduled tasks: choose a session from the selected project, or keep the default new session. See #41.
• More reliable board loading: a partial read failure keeps tasks and projects already on screen and shows a clearer message. See #42.
• A simpler task form: a wider create/edit dialog with permission and urgency dropdowns side by side. Clicking outside does not close it; Esc, Close, and Cancel still do.

Thanks to @Arnozzc87 for reporting and checking #42. The cause of the intermittent response interruption remains unconfirmed. This release fixes the confirmed board behavior and error reporting; if the interruption recurs, please share the failed request and relevant logs.

v0.8.3

这次更新

• 看板刷新或更新时，正在进行的任务不会再被提前写成失败，会继续等到它真正结束。#39
• “认领超时”提示更准确：只有仍在进行、并且很久没有新进展的任务才会显示；已经结束的任务不会再被误标。#40
• 点击正在进行的任务后，会直接打开对应的工作位置。PR #37
• 多个更新同时发生时，任务内容会更稳妥地按顺序保存，减少内容被互相覆盖的风险。PR #38

感谢 @Fishsb 贡献 PR #37 和 PR #38。

验证

已完成完整检查，相关使用场景均已确认正常。

---

What changed

• Work that is still in progress is no longer marked as failed just because the board was refreshed or updated. #39
• The claim-stale hint is now more accurate: it appears only for work that is still running and has had no progress for a long time. #40
• Selecting work that is in progress now takes you straight to its working place. PR #37
• When several updates happen together, task information is saved in a safer order to reduce the chance of one update overwriting another. PR #38

Thanks to @Fishsb for contributing PR #37 and PR #38.

Checked

The complete checks passed and the affected use cases were confirmed to work as expected.

v0.8.2 — 周期任务完成策略与 DSH V4 兼容

0.8.2

修复与改进

• DSH 0.1.7-rc.2 / V4 会话格式兼容：执行开场消息改用看板自身的 producer-owned dsh-taskboard 来源，修复手动和定时任务在首轮因 format v4 message requires a producer-owned source kind 而失败的问题（#34、#36；PR #33）。感谢 @weibaohui 提交并合入此修复。
• 周期任务完成策略（#35）：新增「完成后新建待办」（默认）与「完成后移回待办」选项。由宿主在结算时落实策略，不再依赖 agent 是否自行变更状态。
• 默认策略会将本轮卡片保留在待验收，并新建带 cron 的下一轮待办卡；选择「完成后移回待办」时复用原卡。模板、复制和后继卡会保留该策略；既有未设置策略的 cron 任务也采用默认的新建待办行为。
• 开发依赖统一升级到 DSH 0.1.7-rc.2。

验证

npm run typecheck、构建、host smoke test、npm test（351/351）和 git diff --check 均已通过。

---

Fixes and improvements

• DSH 0.1.7-rc.2 / V4 session-format compatibility: execution framing now uses the board's producer-owned dsh-taskboard source, fixing opening-turn failures with format v4 message requires a producer-owned source kind for both manual and scheduled work (#34, #36; PR #33). Thanks to @weibaohui for contributing and merging this fix.
• Periodic completion policies (#35): adds Create a new todo after completion (the default) and Return to todo after completion. The host enforces the policy during settlement instead of relying on an agent's status transition.
• By default, the completed round remains in review and a fresh cron-bearing todo successor is created. Choosing return-to-todo reuses the original card. Templates, copies, and successors retain the choice; existing cron tasks with no explicit policy use the new default as well.
• Development dependencies are aligned to DSH 0.1.7-rc.2.

Verification

npm run typecheck, build, host smoke test, npm test (351/351), and git diff --check all passed.

v0.8.1 — 定时队列止损与可观测性

0.8.1

修复 / 调度：

• #32 同点批量定时任务：持久 FIFO 队列现提供排队深度、最久等待时间和最大并发数；进行中卡片显示排队数，可打开队列查看正在等待派发的任务，并可二次确认清空任务队列。清空只移除尚未派发的队列项，已运行会话不受影响。
• 新增可选的队列保质期（queueMaxAgeMinutes，默认 0，继续保留跨重启补跑）与定时会话启动间隔（dispatchIntervalMs，默认 1000 ms；可显式设为 0 关闭节流）。
• 调度器以单飞 tick 和全局派发闸门避免 interval/catchup 重叠时并行放行队列。
• 移除 DSH STORE 的客户端产物大小预算与专用测试；仍保留客户端压缩作为常规构建优化，而非发布门槛。

English:

Fixes / Scheduling:

• #32 concurrent scheduled tasks: the durable FIFO queue now exposes its depth, oldest wait, and concurrency cap; the in-progress card shows the queued count, and users can open the queue to inspect waiting tasks or double-confirm clearing it. Clearing only removes entries that have not been dispatched; running sessions are unaffected.
• Adds optional queue shelf life (queueMaxAgeMinutes, default 0, retaining restart replay) and scheduled-session start spacing (dispatchIntervalMs, default 1000 ms; set it explicitly to 0 to disable throttling).
• The scheduler uses a single-flight tick and global dispatch gate to prevent interval/catchup overlap from releasing queued work in parallel.
• Removes the DSH STORE client-artifact size budget and its dedicated test. Client minification remains a normal build optimization, not a release gate.

v0.8.0 — 官方 Slot API 挂载（双轨兼容）

0.8.0

1. 新版本增强兼容性（#31）：侧边栏的注入在 dsh ≥ v0.1.7 使用官方 API（sidebar.panellist + main 注册一等侧边栏面板），同时兼容 dsh < v0.1.7 版本使用 DOM 注入。

   Enhanced compatibility on newer versions: the sidebar entry uses the official API on dsh ≥ v0.1.7 (registered as a first-class sidebar panel via sidebar.panellist + main), while staying compatible with dsh < v0.1.7 through DOM injection.

   安装 / Install

   dsh plugin --profile web add dsh-taskboard

   Full Changelog: v0.7.6...v0.8.0

v0.7.6

修复

• 修复 #30：定时任务在并发满载时会将到期窗口持久化进入 FIFO 队列；槽位释放后继续执行，不再因等待超过旧 5 分钟阈值而静默跳过。
• 真正离线错过的周期任务会留下系统评论，便于追溯。
• 在「🛠 设置」中新增最大并发执行数（1–100）和「离线错过超时后不补任务」（1–1440 分钟）；保存后立即作用于后续调度与执行门禁，已排队任务不受超时影响。

验证

• npm test：339 项测试通过
• npm run typecheck：通过
• npm run build：通过

English

Fixes

• Fix #30: due scheduled tasks persist in a FIFO queue while concurrency is saturated and continue after a slot frees, instead of being silently skipped after the former five-minute threshold.
• Truly offline-missed periodic windows now leave a system comment for traceability.
• 🛠 Settings now provides maximum concurrent executions (1–100) and an offline missed-window timeout (1–1440 minutes). Changes apply immediately to subsequent scheduler and execution gates; queued work is never expired by this timeout.

Verification

• npm test: 339 tests passed
• npm run typecheck: passed
• npm run build: passed

v0.7.5

新特性

• 增加已归档和已删除卡片的批量删除或清理功能（#29）。

New features

• Add batch delete / purge for archived and deleted cards (#29).

v0.7.4

新特性 / New features

中文

• 执行方式三档：认领制、定时执行（新增，指定 runAt 时间点只执行一次，触发即消费；错过超过 5 分钟窗口不补跑，留系统评论提示）、定期执行（原 cron 定时执行）。
• 定期任务接棒机制：每轮执行成功后，原卡正常进入「待验收」并摘除 cron，同时系统自动新建一张全新 todo 接棒卡承接 cron 继续周期（nextRunAt 从结算时刻重算，不补偿连跑），新卡 spawnedFrom 指回原卡并以系统评论互相链接；验收走原卡，周期不断。
• 调度器与执行原子门禁一律只认 todo：in_review 卡片不再被定时触发（原「循环任务在 in_review 继续运行」语义由接棒卡取代）；存量停在 in_review 的 cron 卡需手动移回待办。失败结算仍回 todo 且周期由接棒卡承接，不受影响。
• 任务表单执行方式三选项排成一行；npm 包版本常量与 package.json 同步至 0.7.4。

English

• Three execution modes: claim, one-shot scheduled (new — a runAt instant that fires exactly once and is consumed; windows missed by more than 5 minutes are skipped with a system comment) and periodic scheduled (the former cron mode).
• Periodic hand-off: after each successful round the finished card settles in review with its cron stripped, while a fresh todo successor card carries the cron onward (nextRunAt recomputed from settlement — no catch-up burst). The successor links back via spawnedFrom and system comments on both cards.
• The scheduler and the atomic execution gate only fire todo cards: in_review cards are never triggered again. Legacy periodic cards parked in in_review must be moved back to todo manually. Failure settlement still returns to todo and the cycle continues on the successor.

Full changelog: v0.7.3...v0.7.4