Repository navigation
Add a per-Bot task board updated from conversation - #1071
Conversation
7b44650 to
def67c7
Compare
Rebased onto 2e54119. core/client.js was rebuilt with core/scripts/build-client.mjs and the 0002 (src/host/constants.js, src/host/tools.js) and 0008 (client.js) sections were regenerated from ds-bot/ (no git here, so `generate` cannot run; `node scripts/ds-bot-patches.mjs check` applies the series strictly and is ok).
bb4c797 to
059ea25
Compare
Keep the #1058 task board and take main's Settings friends and sharing page (#1074 / #1091). The generated client-bundle hunk header was the conflict; the bundle was rebuilt from the merged client sources and the patch regenerated so it applies. Fixes #1058 Co-authored-by: Danyang Chen <birfychen@gmail.com>
…anban Co-authored-by: Danyang Chen <birfychen@gmail.com>
|
Verdict: PASS at b1a4f7b Ran:
Not run:
Findings: Security fence / display names: no new untrusted-message or untrusted-file path. The T3 hit on This comment is not merge authority. It does not enqueue. |
|
Verdict: PASS at b1a4f7b Ran:
Not run:
Findings: Security fence / display names: no new untrusted-message or untrusted-file path. The T3 hit on Correction from Reviewer: the earlier cursor[bot] comment at this tip is not a conclusion (bot accounts never are). This Birfy-posted report is the Verifier conclusion for the tip. This comment is not merge authority. It does not enqueue. |
Written-by: Dev
Fixes #1058
Owner: Dev
Reviewer: Reviewer
What changed
Each Bot keeps a task list on the existing
state.tasksrecords and updates it from the conversation withtrack_tasks. A Tasks board under Inbox shows Not started, In progress and Done for that Bot, with id, priority, status and progress on each card. Drag or Start / Complete walks the existing states forward. A tree parent can read a descendant's tasks. A group admin can read the tasks member Bots are tracking in that group; another member cannot.Deferred
No turn-end model summarizer: the conversation path is the tool plus a prompt line. The Agent inbox stays a list (#471 is not this board). Cards do not move backward, and a blocked task stays put until its wait clears. A group admin and a parent who does not own the Bot can read, not update. The rail lists Bots the viewer owns; a cross-owner child is readable by
botIdand is not added to the roster.Brought up to date with main
Tip SHA: b1a4f7b
Base: 3f7e951
The branch contains current
main. The conflict while merging the Settings friends page (#1074 / #1091) was onlypatches/ds-bot/0008-client-bundle.patch, a generated hunk header.core/client.jswas rebuilt from the merged client sources and that patch was regenerated so the series applies. Overlapping sources (core/src/client/i18n.js,docs/subsystems/core-client.md,patches/ds-bot/0001-core-fixes.patch) kept the task-board strings and main's copy. The following main commit (#1080) merged with no conflicts.Verification
At
c5f375ff(task board plus main through #1091):TZ=UTC npm run verify→ exit 0 (core 1425/1425, social 465/465, tree 125/125, timeline 125/125,.github/scripts417/417, interop 37/37, live-e2e 16/16;arch-docs: OK (33 changed file(s)); patch check ok)npx --yes -p typescript@5.9.3 tsc --noEmit --strict --skipLibCheck types/*.d.tsincore/→ exit 0node .github/scripts/changelog.mjs check→ 15 fragmentsAt this tip
b1a4f7b7(clean merge of #1080; social files matchmain; core sources unchanged):TZ=UTC npm --prefix plugins/social test→ 467/467node scripts/ds-bot-patches.mjs check→ oknode .github/scripts/changelog.mjs check→ 16 fragmentsNot run: smoke bench (no DeepSeek Harness checkout at
../deepseek-harness); a running Desktop window.Raw output at this tip (b1a4f7b)
Re-run after the merge of main into this branch (the tree, not the merge commit, is what these check):