diff --git a/CHANGELOG.md b/CHANGELOG.md index c5f5a1fb4..52623c759 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,57 @@ New entries are written as one fragment file per change in [changelog.d/](change ## [Unreleased] +## [0.2.21] - 2026-11-03 + +### Added + +- A pull request that edits an acceptance gate (`policy/gates.json`) must carry `Policy-sign:` naming a comment by someone other than its author that also names the tip it signs, so a signature cannot be carried over to a later push, and `Test` fails the pull request otherwise — a pull request can no longer change what "pass" means on its own ([#2054](https://github.com/ThinkFlowLab/FlyBot/issues/2054)). +- A task card in the Done column now says when it finished — a relative time (`2 h`, `Sep 22`) beside the assignee, on a Bot's board and a group's alike ([#2066](https://github.com/ThinkFlowLab/FlyBot/issues/2066)). The moment is the first terminal entry in the card's history (`accepted`, `cancelled` or `failed`), so editing a finished task no longer moves the time; a card recorded before that history existed falls back to its last update, and one with no usable stamp shows no time at all. +- With `stateJournal` on, the diagnostics report now says whether the state journal is recording or why it stopped, and `journal.status()` answers the same question to a host ([#2134](https://github.com/ThinkFlowLab/FlyBot/issues/2134)). +- A wire on the Settings → Workflows flowchart now says which two cards it joins and can be pointed at: two wires that end at the same port used to be one stroke to the eye and the wire layer was invisible to a pointer and to a screen reader, so a narration that named a hand-off left no way to find that wire on the picture. Each route now carries a 10px transparent hit path of its own, names both ends (`Reviewer → Deployer` — a hover tooltip and an `aria-label` inside a named `Connections` group), and while the pointer is on it that wire is drawn in the accent colour with the others dimmed. Read-only, this only points at a wire; it commits nothing ([#2142](https://github.com/ThinkFlowLab/FlyBot/issues/2142)). +- A window that holds the Bot team read-only now says so in the Settings header, in the host's own sentence, above every page that still offers its write controls: General, Bots, Groups, Secrets, Connectors, Capabilities, Scheduled tasks and Projects. Pressing a control there is refused by the host, and until now nothing on the panel explained why nothing moved. The standing sentence sits above the line that reports one refused write, and a blank or missing sentence draws nothing ([#2199](https://github.com/ThinkFlowLab/FlyBot/issues/2199)). +- The messages a Bot's chat loads above the current part are now messages you can act on: the reaction and reply buttons on a bubble from an earlier part used to do nothing, because the bubble was drawn without the identity a reaction is stored under and without a session to quote into. A reaction picked on such a bubble now sticks to that message and stays there when another page is loaded above it, and **Reply** quotes the line into the open chat instead of into the part it was said in. ([#2136](https://github.com/ThinkFlowLab/FlyBot/issues/2136)). + +### Fixed + +- A room board opened from a Bot board now counts each active card once in its rail: the bot board's read stayed in the rail's own list after the switch, so a room that draws two cards read `1/3` instead of `1/2` ([#2069](https://github.com/ThinkFlowLab/FlyBot/issues/2069)). +- The state journal now asks what its folder and its file are when it writes, not only when the host starts: a `home/journal` folder swapped for a link is refused with one warning and recording stops, and a `state.jsonl` swapped for a link is never written through, instead of silently appending a snapshot into a folder or a file outside the home. The append path refuses the write; the prune path replaces the link with a fresh file in the verified folder, so nothing is written through it ([#2074](https://github.com/ThinkFlowLab/FlyBot/issues/2074)). +- `memory/journal.jsonl`, a workspace `workflows/.json` and `workflows/project.json` are asked as files before a write, the way their folders already were: a missing file is created, a plain file is written, and a link or a directory is not written through ([#2079](https://github.com/ThinkFlowLab/FlyBot/issues/2079)). A linked journal file drops that one record with a warning and the memory write still lands; a linked workflow file refuses the save with `workflow/not-a-file` and one warning. +- The decision log and the diagnostics log now ask what their file is before they write, the way the state journal does: a `decisions.jsonl` or `logs/diagnostics.jsonl` swapped for a link is refused instead of appending the line into whatever the link points at. A refused decision is dropped with one warning and the tool answers `Not recorded: the decision log is not a plain file.`; the diagnostics log drops the line with one line on stderr, keeps it readable in memory, and `clear` no longer truncates a file behind such a link. +- A memory write and a frozen prompt snapshot are no longer written through a link left at their temporary name: `MEMORY.md..tmp` and `.md.tmp` are asked as files before the write, so a link there refuses the save (one warning, the memory file keeps what it had) instead of landing the bytes outside the home and replacing the file with the link ([#2097](https://github.com/ThinkFlowLab/FlyBot/issues/2097)). A window between the check and the write remains, as with every `lstat`-then-write guard. +- The memory panel can now tell a folder it could not read from a Bot that has never saved anything: `memory-view` carries a `blocked` entry (scope and the folder that failed) for each memory scope the host refused, and the panel prints one line naming that folder above its empty title instead of telling the user to save something that cannot be written. A folder that is merely empty, or not created yet, still renders exactly the copy it rendered before. +- The decision log's housekeeping no longer writes through a link left at its temporary name: it lands through `/decisions.jsonl.tmp` and renames it over the log, and that name is now asked as a file before the write. A link there refuses the trim — one warning, the new entry is still appended and the retained log simply grows past its bound — instead of writing the whole retained log outside the home and replacing the log itself with the link; the tool then answers `Written: … — the log was not trimmed` rather than `Recorded:` ([#2103](https://github.com/ThinkFlowLab/FlyBot/issues/2103)). A window between the check and the write remains, as with every `lstat`-then-write guard. +- The memory panel now names a refused memory folder even when the other memory scope has entries: `entries` is own and team merged, so the line added for the empty state disappeared as soon as either scope held a single entry. A second pure helper answers the same sentence from the view's `blocked` scopes alone, and the panel draws it above the summary and above the entries list; the empty state keeps its own copy and a view with nothing refused renders exactly what it rendered before. +- A link left at the temporary name a write lands through no longer takes the write: the team state, the OCR cache, the Automation-tasks defaults, the Bot Social server choice and the workflow store ask `..tmp` as a file before writing, so a link (or a folder) there refuses the save, with the temp name in the message, instead of putting the bytes outside the folder and renaming the link into place. A window between the check and the write remains, as with every `lstat`-then-write guard. ([#2109](https://github.com/ThinkFlowLab/FlyBot/issues/2109)). +- The timeline trace now asks its temporary name before a segment write lands through it: a symbolic or hard link left at `trace-000001.json.tmp`, or a directory, refuses the write with one warning, so a preset name can no longer take the bytes outside the trace folder or put a link where the segment belongs. The segment is neither created nor replaced on a refusal; a missing temp name stays the writer's to create and the plain leftover of a crashed writer is still overwritten. +- The Bot Social credentials file, its per-server backup and the settings file are written only after the path is asked what it is: a symbolic or hard link left there was followed, so an onboarding token, the owner id and the display name could land in a file outside the Bot's home. The write now refuses before the first byte, the file behind a link keeps its bytes, and the start fails with one line naming the path rather than running on a link. +- The run flowchart in Settings → Workflows now routes every wire on its own lane: a fork and a join no longer collapse onto one stroke, a wire leaves the card at its real bottom edge and never cuts through the card below it, and a back edge loops outside the cards as a visible return path instead of a stub. The dashed parallel frame is drawn from the measured card boxes with an equal margin on all four sides (#2122). +- A message with no text painted a row of its own: a turn that ended in tool calls only left the Bot avatar and a bubble holding nothing under the trace row. An empty or whitespace-only text is now no row at all, in a Bot's own chat, a group chat, a friend's line and the exchange sheet; a line that carries files keeps them and loses only the empty bubble. +- The state journal now refuses a `journal/state.jsonl` that is a hard link: its bytes are also a name outside this home, so the start-up read and the append both require the file to carry only this one name (`nlink === 1`). A shared inode is refused exactly like a symbolic link — one warning, nothing read, chmod-ed or appended — while a journal with one name records as before. +- A loop wire in the workflow flowchart turns in the gap above or below its row, so it no longer runs behind the card beside it ([#2138](https://github.com/ThinkFlowLab/FlyBot/issues/2138)). +- A start that moves to another server now asks the backup name before it asks the server for a home: the `.bak` copy (`flybot-social.json.`) is named from the credentials file already on disk, so a link left at that name refuses the start instead of spending a home on the server first and refusing afterwards. A free name still keeps the old server's credentials there, and a refused `.bak` leaves the credentials in use byte for byte ([#2140](https://github.com/ThinkFlowLab/FlyBot/issues/2140)). +- The Scheduled tasks page and a Bot's scheduled-tasks line no longer answer "No scheduled tasks yet." when the list is only narrow: once a member is signed in, each member sees their own tasks, so a list that dropped another member's rows now says "No scheduled tasks you can see." and adds either that another member's tasks stay hidden (the page) or that you can add one (the line). A list where nothing was hidden, and a host that narrows nothing, keep the plain empty state. ([#2145](https://github.com/ThinkFlowLab/FlyBot/issues/2145)) +- A state journal rotation now refuses a file whose name stands for a symbolic or a hard link ([#2146](https://github.com/ThinkFlowLab/FlyBot/issues/2146)): until now the rotation read the other file's lines as the team's history and its `rename` dropped the second name, while recording went on without a warning. The rotation asks the same question the append already asks; a journal with only its own name rotates as before. +- A wire between two cards on one row of a workflow flowchart — a loop across a parallel layer, or a skip across a row — now runs outside that row instead of through the card between them: the run fell back onto the row's own column and the card, drawn on top, covered it, so the stroke looked like a link to the neighbour. The two horizontal runs now sit in the space beyond the row's own cards, and the vertical run between them keeps clear of every card it passes, the two ends included ([#2151](https://github.com/ThinkFlowLab/FlyBot/issues/2151)). +- A diagnostics report from a window that another dsh keeps read-only no longer says `state journal: recording`: that window never reaches the journal write, so the line now says `state journal: paused (this window is read-only)` instead, while a journal that really stopped keeps its own reason ([#2153](https://github.com/ThinkFlowLab/FlyBot/issues/2153)). +- The state journal no longer stays stopped for the rest of the run after one failed open or write. The next save asks once more whether it can record again: a folder or file repaired meanwhile resumes recording, appending the change that save carried, while a journal that still refuses stays stopped and that save still lands. The asking is silent, so a refusal is warned once rather than once per save ([#2154](https://github.com/ThinkFlowLab/FlyBot/issues/2154)). +- A Condition link that cannot be honoured is now refused instead of saved as a plain Link: a blank output name, or one the graph will not accept (`result_ok`, `ready.now`, `with space`), names the reason in the Settings alert and writes nothing, where it used to land as an unconditional edge that fired whether or not the condition held. Settings keeps **Add link** disabled for a Condition until an output name is typed, and a loop's `until` follows the same rule — absent still means no early stop, a partially filled one is refused ([#2155](https://github.com/ThinkFlowLab/FlyBot/issues/2155)). +- A file that another name also holds is no longer written through at its leaf: the decision log, the diagnostics log, the memory journal, and a workflow definition or project file that is hard-linked to a name outside the home are refused exactly like a symbolic link there — one warning, the other name keeps its bytes, the record is dropped or the save is refused — instead of the append or the truncate landing in the shared inode ([#2079](https://github.com/ThinkFlowLab/FlyBot/issues/2079), [#2114](https://github.com/ThinkFlowLab/FlyBot/issues/2114)). The leaf now asks the same `nlink === 1` rule the temporary name already used, so the two answers for one file cannot disagree; a file carrying one name is written as before, and a missing file is still created ([#2159](https://github.com/ThinkFlowLab/FlyBot/issues/2159)). +- A wire that leaves a row for one below now clears the tallest card in that row instead of running through a shorter neighbour: the corridor is measured from the row's lowest measured bottom, so a 96px card beside a 48px source no longer hides the horizontal run behind its own body ([#2160](https://github.com/ThinkFlowLab/FlyBot/issues/2160)). +- A wire or a reconnect in the workflow drawer that would repeat a pair the graph already lists now adds nothing, instead of committing the duplicate that the host refuses: before, that save failed with `Link A → B is listed twice` and the plane shows only `workflow.edges`, so the drag left no edge, no change and one red line nobody asked for. Reconnecting an edge onto a target its source already reaches now keeps exactly one edge and drops the one that was dragged, and a wire to a Bot that was not connected yet still adds its edge as before ([#2163](https://github.com/ThinkFlowLab/FlyBot/issues/2163)). +- A wire that leaves a row for one below turns in the corridor under that row and never below the next row's top: at the factory 108px row pitch a card beside a 48px source can reach past that top, and the turn is then clamped a pixel above it instead of landing inside the cards below ([#2164](https://github.com/ThinkFlowLab/FlyBot/issues/2164)). +- The state journal recovers a last line a crash left half written instead of refusing the file on every start and every save: when the complete prefix before it replays, the journal is replaced with that prefix, the dropped line is warned once, and recording continues from it, so a person no longer has to delete `journal/state.jsonl` ([#2166](https://github.com/ThinkFlowLab/FlyBot/issues/2166)). A broken line above the last one, a `seq` gap, a `prev` mismatch or an unknown op still refuses the whole journal and leaves it as it is. +- The `Read-only` row of a host diagnostics report no longer says another dsh holds the team when it does not: a team file saved by a newer FlyBot reads `update FlyBot` and an unreadable one reads `could not be read` with its cause, exactly the sentence the sidebar shows, while a window that really lost the team to a live `state.lock` keeps the other-dsh wording ([#2167](https://github.com/ThinkFlowLab/FlyBot/issues/2167)). +- **Add link** in Settings → Workflow graphs now reads the graph before it submits: a pair the graph already links is a no-op instead of a save the host refuses and discards whole, a pair given a different kind says which link is already there instead of the host's `listed twice`, and the **To** list marks the targets the chosen node already reaches ([#2173](https://github.com/ThinkFlowLab/FlyBot/issues/2173)). +- A window that holds the team read-only no longer offers **Edit** on Settings → Workflows: the page draws the host's own read-only sentence in its place, drops rename and delete, and never asks the host to save a graph, so a layout is not built only for the save to be refused ([#2176](https://github.com/ThinkFlowLab/FlyBot/issues/2176)). +- A Condition (`when`) or Loop (`until`) link in Settings → Workflow graphs now offers the output names the **From** node declares instead of asking for one to be typed, so a name the host would refuse is never submitted; **Add link** waits for a declared name, and a node that declares no outputs keeps the text box ([#2178](https://github.com/ThinkFlowLab/FlyBot/issues/2178)). +- While another dsh holds the Bot team, a window can only show it: Settings → Workflow graphs now says so in the host's own words and offers no **Edit**, **Add link** or wire port, instead of taking a change core refuses with `bot/read-only` and then drops ([#2187](https://github.com/ThinkFlowLab/FlyBot/issues/2187)). +- The host's read-only sentence now stays visible when the sidebar is collapsed to the rail, clipped to one line with the full sentence on hover and in its accessible name, instead of disappearing until the window is wide again; a host that sent an empty or whitespace-only sentence draws no hint in either shape ([#2188](https://github.com/ThinkFlowLab/FlyBot/issues/2188)). +- A write the host refuses in Settings now shows its sentence under the dialog heading instead of at the top of the scrolling page: after scrolling down to the switch that was pressed, the refusal used to land above the viewport, so the window looked as if the click had done nothing. The line sits outside `.bt-settings-scroll`, in view wherever the page is scrolled ([#2194](https://github.com/ThinkFlowLab/FlyBot/issues/2194)). +- While another dsh holds the Bot team, the Workflow list in the sidebar no longer offers **New**, **Rename**, **Delete** or **Hand a task to a Workflow**: a read-only window shows the list only, instead of taking a change that core refuses with `bot/read-only` ([#2200](https://github.com/ThinkFlowLab/FlyBot/issues/2200)). +- A write that lands through a temporary name now refuses a hard link left there as well as a symbolic one: `lstat` reports a hard link as a plain file, so the team state, the OCR cache, the Automation-tasks defaults, the memory files and snapshot, the decision log's trim and the Bot Social server choice could still be written into an inode another name held outside the Bot's home. The guard asks for a file with only its own name (`nlink === 1`), while the plain leftover a crashed host leaves behind stays replaceable. +- The Scheduled tasks page lists tasks on a host where a member is signed in — the list no longer needs a Session in its request — and each signed-in member is shown only their own tasks. + ## [0.2.20] - 2026-11-02 ### Added diff --git a/changelog.d/2054-gate-signature.added.md b/changelog.d/2054-gate-signature.added.md deleted file mode 100644 index 4d726aadb..000000000 --- a/changelog.d/2054-gate-signature.added.md +++ /dev/null @@ -1 +0,0 @@ -A pull request that edits an acceptance gate (`policy/gates.json`) must carry `Policy-sign:` naming a comment by someone other than its author that also names the tip it signs, so a signature cannot be carried over to a later push, and `Test` fails the pull request otherwise — a pull request can no longer change what "pass" means on its own ([#2054](https://github.com/ThinkFlowLab/FlyBot/issues/2054)). diff --git a/changelog.d/2066-board-done-time.added.md b/changelog.d/2066-board-done-time.added.md deleted file mode 100644 index 0c2be90dd..000000000 --- a/changelog.d/2066-board-done-time.added.md +++ /dev/null @@ -1 +0,0 @@ -A task card in the Done column now says when it finished — a relative time (`2 h`, `Sep 22`) beside the assignee, on a Bot's board and a group's alike ([#2066](https://github.com/ThinkFlowLab/FlyBot/issues/2066)). The moment is the first terminal entry in the card's history (`accepted`, `cancelled` or `failed`), so editing a finished task no longer moves the time; a card recorded before that history existed falls back to its last update, and one with no usable stamp shows no time at all. diff --git a/changelog.d/2069-room-rail-double-count.fixed.md b/changelog.d/2069-room-rail-double-count.fixed.md deleted file mode 100644 index 1eb7e1a72..000000000 --- a/changelog.d/2069-room-rail-double-count.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A room board opened from a Bot board now counts each active card once in its rail: the bot board's read stayed in the rail's own list after the switch, so a room that draws two cards read `1/3` instead of `1/2` ([#2069](https://github.com/ThinkFlowLab/FlyBot/issues/2069)). diff --git a/changelog.d/2074-journal-link-swap.fixed.md b/changelog.d/2074-journal-link-swap.fixed.md deleted file mode 100644 index 4527c2044..000000000 --- a/changelog.d/2074-journal-link-swap.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The state journal now asks what its folder and its file are when it writes, not only when the host starts: a `home/journal` folder swapped for a link is refused with one warning and recording stops, and a `state.jsonl` swapped for a link is never written through, instead of silently appending a snapshot into a folder or a file outside the home. The append path refuses the write; the prune path replaces the link with a fresh file in the verified folder, so nothing is written through it ([#2074](https://github.com/ThinkFlowLab/FlyBot/issues/2074)). diff --git a/changelog.d/2079-leaf-file-link.fixed.md b/changelog.d/2079-leaf-file-link.fixed.md deleted file mode 100644 index 09fc8bdde..000000000 --- a/changelog.d/2079-leaf-file-link.fixed.md +++ /dev/null @@ -1 +0,0 @@ -`memory/journal.jsonl`, a workspace `workflows/.json` and `workflows/project.json` are asked as files before a write, the way their folders already were: a missing file is created, a plain file is written, and a link or a directory is not written through ([#2079](https://github.com/ThinkFlowLab/FlyBot/issues/2079)). A linked journal file drops that one record with a warning and the memory write still lands; a linked workflow file refuses the save with `workflow/not-a-file` and one warning. diff --git a/changelog.d/2089-decisions-diagnostics-leaf.fixed.md b/changelog.d/2089-decisions-diagnostics-leaf.fixed.md deleted file mode 100644 index ca3e02a46..000000000 --- a/changelog.d/2089-decisions-diagnostics-leaf.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The decision log and the diagnostics log now ask what their file is before they write, the way the state journal does: a `decisions.jsonl` or `logs/diagnostics.jsonl` swapped for a link is refused instead of appending the line into whatever the link points at. A refused decision is dropped with one warning and the tool answers `Not recorded: the decision log is not a plain file.`; the diagnostics log drops the line with one line on stderr, keeps it readable in memory, and `clear` no longer truncates a file behind such a link. diff --git a/changelog.d/2097-temp-leaf-guard.fixed.md b/changelog.d/2097-temp-leaf-guard.fixed.md deleted file mode 100644 index d51d9c4ca..000000000 --- a/changelog.d/2097-temp-leaf-guard.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A memory write and a frozen prompt snapshot are no longer written through a link left at their temporary name: `MEMORY.md..tmp` and `.md.tmp` are asked as files before the write, so a link there refuses the save (one warning, the memory file keeps what it had) instead of landing the bytes outside the home and replacing the file with the link ([#2097](https://github.com/ThinkFlowLab/FlyBot/issues/2097)). A window between the check and the write remains, as with every `lstat`-then-write guard. diff --git a/changelog.d/2101-memory-blocked-empty.fixed.md b/changelog.d/2101-memory-blocked-empty.fixed.md deleted file mode 100644 index 30158760b..000000000 --- a/changelog.d/2101-memory-blocked-empty.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The memory panel can now tell a folder it could not read from a Bot that has never saved anything: `memory-view` carries a `blocked` entry (scope and the folder that failed) for each memory scope the host refused, and the panel prints one line naming that folder above its empty title instead of telling the user to save something that cannot be written. A folder that is merely empty, or not created yet, still renders exactly the copy it rendered before. diff --git a/changelog.d/2103-decisions-trim-temp.fixed.md b/changelog.d/2103-decisions-trim-temp.fixed.md deleted file mode 100644 index 27d985df0..000000000 --- a/changelog.d/2103-decisions-trim-temp.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The decision log's housekeeping no longer writes through a link left at its temporary name: it lands through `/decisions.jsonl.tmp` and renames it over the log, and that name is now asked as a file before the write. A link there refuses the trim — one warning, the new entry is still appended and the retained log simply grows past its bound — instead of writing the whole retained log outside the home and replacing the log itself with the link; the tool then answers `Written: … — the log was not trimmed` rather than `Recorded:` ([#2103](https://github.com/ThinkFlowLab/FlyBot/issues/2103)). A window between the check and the write remains, as with every `lstat`-then-write guard. diff --git a/changelog.d/2106-memory-blocked-partial.fixed.md b/changelog.d/2106-memory-blocked-partial.fixed.md deleted file mode 100644 index c2b6fb5a6..000000000 --- a/changelog.d/2106-memory-blocked-partial.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The memory panel now names a refused memory folder even when the other memory scope has entries: `entries` is own and team merged, so the line added for the empty state disappeared as soon as either scope held a single entry. A second pure helper answers the same sentence from the view's `blocked` scopes alone, and the panel draws it above the summary and above the entries list; the empty state keeps its own copy and a view with nothing refused renders exactly what it rendered before. diff --git a/changelog.d/2109-temp-name-sweep.fixed.md b/changelog.d/2109-temp-name-sweep.fixed.md deleted file mode 100644 index 41f569370..000000000 --- a/changelog.d/2109-temp-name-sweep.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A link left at the temporary name a write lands through no longer takes the write: the team state, the OCR cache, the Automation-tasks defaults, the Bot Social server choice and the workflow store ask `..tmp` as a file before writing, so a link (or a folder) there refuses the save, with the temp name in the message, instead of putting the bytes outside the folder and renaming the link into place. A window between the check and the write remains, as with every `lstat`-then-write guard. ([#2109](https://github.com/ThinkFlowLab/FlyBot/issues/2109)). diff --git a/changelog.d/2115-timeline-temp-name.fixed.md b/changelog.d/2115-timeline-temp-name.fixed.md deleted file mode 100644 index 710ee6acc..000000000 --- a/changelog.d/2115-timeline-temp-name.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The timeline trace now asks its temporary name before a segment write lands through it: a symbolic or hard link left at `trace-000001.json.tmp`, or a directory, refuses the write with one warning, so a preset name can no longer take the bytes outside the trace folder or put a link where the segment belongs. The segment is neither created nor replaced on a refusal; a missing temp name stays the writer's to create and the plain leftover of a crashed writer is still overwritten. diff --git a/changelog.d/2116-social-credentials-leaf.fixed.md b/changelog.d/2116-social-credentials-leaf.fixed.md deleted file mode 100644 index d69e223c7..000000000 --- a/changelog.d/2116-social-credentials-leaf.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The Bot Social credentials file, its per-server backup and the settings file are written only after the path is asked what it is: a symbolic or hard link left there was followed, so an onboarding token, the owner id and the display name could land in a file outside the Bot's home. The write now refuses before the first byte, the file behind a link keeps its bytes, and the start fails with one line naming the path rather than running on a link. diff --git a/changelog.d/2122-flow-wire-routing.fixed.md b/changelog.d/2122-flow-wire-routing.fixed.md deleted file mode 100644 index d701e9d22..000000000 --- a/changelog.d/2122-flow-wire-routing.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The run flowchart in Settings → Workflows now routes every wire on its own lane: a fork and a join no longer collapse onto one stroke, a wire leaves the card at its real bottom edge and never cuts through the card below it, and a back edge loops outside the cards as a visible return path instead of a stub. The dashed parallel frame is drawn from the measured card boxes with an equal margin on all four sides (#2122). diff --git a/changelog.d/2123-empty-message-cell.fixed.md b/changelog.d/2123-empty-message-cell.fixed.md deleted file mode 100644 index 51cf5c7c8..000000000 --- a/changelog.d/2123-empty-message-cell.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A message with no text painted a row of its own: a turn that ended in tool calls only left the Bot avatar and a bubble holding nothing under the trace row. An empty or whitespace-only text is now no row at all, in a Bot's own chat, a group chat, a friend's line and the exchange sheet; a line that carries files keeps them and loses only the empty bubble. diff --git a/changelog.d/2131-journal-hardlink.fixed.md b/changelog.d/2131-journal-hardlink.fixed.md deleted file mode 100644 index ed83c8068..000000000 --- a/changelog.d/2131-journal-hardlink.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The state journal now refuses a `journal/state.jsonl` that is a hard link: its bytes are also a name outside this home, so the start-up read and the append both require the file to carry only this one name (`nlink === 1`). A shared inode is refused exactly like a symbolic link — one warning, nothing read, chmod-ed or appended — while a journal with one name records as before. diff --git a/changelog.d/2134-journal-status.added.md b/changelog.d/2134-journal-status.added.md deleted file mode 100644 index cbaffe5f0..000000000 --- a/changelog.d/2134-journal-status.added.md +++ /dev/null @@ -1 +0,0 @@ -With `stateJournal` on, the diagnostics report now says whether the state journal is recording or why it stopped, and `journal.status()` answers the same question to a host ([#2134](https://github.com/ThinkFlowLab/FlyBot/issues/2134)). diff --git a/changelog.d/2138-back-edge-row.fixed.md b/changelog.d/2138-back-edge-row.fixed.md deleted file mode 100644 index 7746e2927..000000000 --- a/changelog.d/2138-back-edge-row.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A loop wire in the workflow flowchart turns in the gap above or below its row, so it no longer runs behind the card beside it ([#2138](https://github.com/ThinkFlowLab/FlyBot/issues/2138)). diff --git a/changelog.d/2140-social-bak-precheck.fixed.md b/changelog.d/2140-social-bak-precheck.fixed.md deleted file mode 100644 index ae0bba274..000000000 --- a/changelog.d/2140-social-bak-precheck.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A start that moves to another server now asks the backup name before it asks the server for a home: the `.bak` copy (`flybot-social.json.`) is named from the credentials file already on disk, so a link left at that name refuses the start instead of spending a home on the server first and refusing afterwards. A free name still keeps the old server's credentials there, and a refused `.bak` leaves the credentials in use byte for byte ([#2140](https://github.com/ThinkFlowLab/FlyBot/issues/2140)). diff --git a/changelog.d/2142-wire-hit-targets.added.md b/changelog.d/2142-wire-hit-targets.added.md deleted file mode 100644 index 4d6d082b2..000000000 --- a/changelog.d/2142-wire-hit-targets.added.md +++ /dev/null @@ -1 +0,0 @@ -A wire on the Settings → Workflows flowchart now says which two cards it joins and can be pointed at: two wires that end at the same port used to be one stroke to the eye and the wire layer was invisible to a pointer and to a screen reader, so a narration that named a hand-off left no way to find that wire on the picture. Each route now carries a 10px transparent hit path of its own, names both ends (`Reviewer → Deployer` — a hover tooltip and an `aria-label` inside a named `Connections` group), and while the pointer is on it that wire is drawn in the accent colour with the others dimmed. Read-only, this only points at a wire; it commits nothing ([#2142](https://github.com/ThinkFlowLab/FlyBot/issues/2142)). diff --git a/changelog.d/2145-schedules-hidden.fixed.md b/changelog.d/2145-schedules-hidden.fixed.md deleted file mode 100644 index 124111285..000000000 --- a/changelog.d/2145-schedules-hidden.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The Scheduled tasks page and a Bot's scheduled-tasks line no longer answer "No scheduled tasks yet." when the list is only narrow: once a member is signed in, each member sees their own tasks, so a list that dropped another member's rows now says "No scheduled tasks you can see." and adds either that another member's tasks stay hidden (the page) or that you can add one (the line). A list where nothing was hidden, and a host that narrows nothing, keep the plain empty state. ([#2145](https://github.com/ThinkFlowLab/FlyBot/issues/2145)) diff --git a/changelog.d/2146-journal-rotation-leaf.fixed.md b/changelog.d/2146-journal-rotation-leaf.fixed.md deleted file mode 100644 index e564bad64..000000000 --- a/changelog.d/2146-journal-rotation-leaf.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A state journal rotation now refuses a file whose name stands for a symbolic or a hard link ([#2146](https://github.com/ThinkFlowLab/FlyBot/issues/2146)): until now the rotation read the other file's lines as the team's history and its `rename` dropped the second name, while recording went on without a warning. The rotation asks the same question the append already asks; a journal with only its own name rotates as before. diff --git a/changelog.d/2151-same-row-wire.fixed.md b/changelog.d/2151-same-row-wire.fixed.md deleted file mode 100644 index 32b3033ac..000000000 --- a/changelog.d/2151-same-row-wire.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A wire between two cards on one row of a workflow flowchart — a loop across a parallel layer, or a skip across a row — now runs outside that row instead of through the card between them: the run fell back onto the row's own column and the card, drawn on top, covered it, so the stroke looked like a link to the neighbour. The two horizontal runs now sit in the space beyond the row's own cards, and the vertical run between them keeps clear of every card it passes, the two ends included ([#2151](https://github.com/ThinkFlowLab/FlyBot/issues/2151)). diff --git a/changelog.d/2153-journal-readonly-paused.fixed.md b/changelog.d/2153-journal-readonly-paused.fixed.md deleted file mode 100644 index fca840188..000000000 --- a/changelog.d/2153-journal-readonly-paused.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A diagnostics report from a window that another dsh keeps read-only no longer says `state journal: recording`: that window never reaches the journal write, so the line now says `state journal: paused (this window is read-only)` instead, while a journal that really stopped keeps its own reason ([#2153](https://github.com/ThinkFlowLab/FlyBot/issues/2153)). diff --git a/changelog.d/2154-journal-reopen.fixed.md b/changelog.d/2154-journal-reopen.fixed.md deleted file mode 100644 index f0eed72f6..000000000 --- a/changelog.d/2154-journal-reopen.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The state journal no longer stays stopped for the rest of the run after one failed open or write. The next save asks once more whether it can record again: a folder or file repaired meanwhile resumes recording, appending the change that save carried, while a journal that still refuses stays stopped and that save still lands. The asking is silent, so a refusal is warned once rather than once per save ([#2154](https://github.com/ThinkFlowLab/FlyBot/issues/2154)). diff --git a/changelog.d/2155-condition-when-refused.fixed.md b/changelog.d/2155-condition-when-refused.fixed.md deleted file mode 100644 index 44f995c12..000000000 --- a/changelog.d/2155-condition-when-refused.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A Condition link that cannot be honoured is now refused instead of saved as a plain Link: a blank output name, or one the graph will not accept (`result_ok`, `ready.now`, `with space`), names the reason in the Settings alert and writes nothing, where it used to land as an unconditional edge that fired whether or not the condition held. Settings keeps **Add link** disabled for a Condition until an output name is typed, and a loop's `until` follows the same rule — absent still means no early stop, a partially filled one is refused ([#2155](https://github.com/ThinkFlowLab/FlyBot/issues/2155)). diff --git a/changelog.d/2159-hardlink-leaf.fixed.md b/changelog.d/2159-hardlink-leaf.fixed.md deleted file mode 100644 index 5cebb2186..000000000 --- a/changelog.d/2159-hardlink-leaf.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A file that another name also holds is no longer written through at its leaf: the decision log, the diagnostics log, the memory journal, and a workflow definition or project file that is hard-linked to a name outside the home are refused exactly like a symbolic link there — one warning, the other name keeps its bytes, the record is dropped or the save is refused — instead of the append or the truncate landing in the shared inode ([#2079](https://github.com/ThinkFlowLab/FlyBot/issues/2079), [#2114](https://github.com/ThinkFlowLab/FlyBot/issues/2114)). The leaf now asks the same `nlink === 1` rule the temporary name already used, so the two answers for one file cannot disagree; a file carrying one name is written as before, and a missing file is still created ([#2159](https://github.com/ThinkFlowLab/FlyBot/issues/2159)). diff --git a/changelog.d/2160-forward-wire-row-clearance.fixed.md b/changelog.d/2160-forward-wire-row-clearance.fixed.md deleted file mode 100644 index 4ca409acb..000000000 --- a/changelog.d/2160-forward-wire-row-clearance.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A wire that leaves a row for one below now clears the tallest card in that row instead of running through a shorter neighbour: the corridor is measured from the row's lowest measured bottom, so a 96px card beside a 48px source no longer hides the horizontal run behind its own body ([#2160](https://github.com/ThinkFlowLab/FlyBot/issues/2160)). diff --git a/changelog.d/2163-workflow-drawer-duplicate-edge.fixed.md b/changelog.d/2163-workflow-drawer-duplicate-edge.fixed.md deleted file mode 100644 index 7097e64a2..000000000 --- a/changelog.d/2163-workflow-drawer-duplicate-edge.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A wire or a reconnect in the workflow drawer that would repeat a pair the graph already lists now adds nothing, instead of committing the duplicate that the host refuses: before, that save failed with `Link A → B is listed twice` and the plane shows only `workflow.edges`, so the drag left no edge, no change and one red line nobody asked for. Reconnecting an edge onto a target its source already reaches now keeps exactly one edge and drops the one that was dragged, and a wire to a Bot that was not connected yet still adds its edge as before ([#2163](https://github.com/ThinkFlowLab/FlyBot/issues/2163)). diff --git a/changelog.d/2164-forward-wire-factory-pitch.fixed.md b/changelog.d/2164-forward-wire-factory-pitch.fixed.md deleted file mode 100644 index b9378daf6..000000000 --- a/changelog.d/2164-forward-wire-factory-pitch.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A wire that leaves a row for one below turns in the corridor under that row and never below the next row's top: at the factory 108px row pitch a card beside a 48px source can reach past that top, and the turn is then clamped a pixel above it instead of landing inside the cards below ([#2164](https://github.com/ThinkFlowLab/FlyBot/issues/2164)). diff --git a/changelog.d/2166-journal-incomplete-last-line.fixed.md b/changelog.d/2166-journal-incomplete-last-line.fixed.md deleted file mode 100644 index bd3afa786..000000000 --- a/changelog.d/2166-journal-incomplete-last-line.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The state journal recovers a last line a crash left half written instead of refusing the file on every start and every save: when the complete prefix before it replays, the journal is replaced with that prefix, the dropped line is warned once, and recording continues from it, so a person no longer has to delete `journal/state.jsonl` ([#2166](https://github.com/ThinkFlowLab/FlyBot/issues/2166)). A broken line above the last one, a `seq` gap, a `prev` mismatch or an unknown op still refuses the whole journal and leaves it as it is. diff --git a/changelog.d/2167-diagnostics-readonly-reason.fixed.md b/changelog.d/2167-diagnostics-readonly-reason.fixed.md deleted file mode 100644 index f202f453d..000000000 --- a/changelog.d/2167-diagnostics-readonly-reason.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The `Read-only` row of a host diagnostics report no longer says another dsh holds the team when it does not: a team file saved by a newer FlyBot reads `update FlyBot` and an unreadable one reads `could not be read` with its cause, exactly the sentence the sidebar shows, while a window that really lost the team to a live `state.lock` keeps the other-dsh wording ([#2167](https://github.com/ThinkFlowLab/FlyBot/issues/2167)). diff --git a/changelog.d/2173-settings-link-duplicate.fixed.md b/changelog.d/2173-settings-link-duplicate.fixed.md deleted file mode 100644 index 8f868c226..000000000 --- a/changelog.d/2173-settings-link-duplicate.fixed.md +++ /dev/null @@ -1 +0,0 @@ -**Add link** in Settings → Workflow graphs now reads the graph before it submits: a pair the graph already links is a no-op instead of a save the host refuses and discards whole, a pair given a different kind says which link is already there instead of the host's `listed twice`, and the **To** list marks the targets the chosen node already reaches ([#2173](https://github.com/ThinkFlowLab/FlyBot/issues/2173)). diff --git a/changelog.d/2176-workflows-readonly-hides-edit.fixed.md b/changelog.d/2176-workflows-readonly-hides-edit.fixed.md deleted file mode 100644 index 064490a56..000000000 --- a/changelog.d/2176-workflows-readonly-hides-edit.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A window that holds the team read-only no longer offers **Edit** on Settings → Workflows: the page draws the host's own read-only sentence in its place, drops rename and delete, and never asks the host to save a graph, so a layout is not built only for the save to be refused ([#2176](https://github.com/ThinkFlowLab/FlyBot/issues/2176)). diff --git a/changelog.d/2178-condition-output-picker.fixed.md b/changelog.d/2178-condition-output-picker.fixed.md deleted file mode 100644 index 34049f357..000000000 --- a/changelog.d/2178-condition-output-picker.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A Condition (`when`) or Loop (`until`) link in Settings → Workflow graphs now offers the output names the **From** node declares instead of asking for one to be typed, so a name the host would refuse is never submitted; **Add link** waits for a declared name, and a node that declares no outputs keeps the text box ([#2178](https://github.com/ThinkFlowLab/FlyBot/issues/2178)). diff --git a/changelog.d/2187-plugin-workflow-settings-readonly.fixed.md b/changelog.d/2187-plugin-workflow-settings-readonly.fixed.md deleted file mode 100644 index 62d093abe..000000000 --- a/changelog.d/2187-plugin-workflow-settings-readonly.fixed.md +++ /dev/null @@ -1 +0,0 @@ -While another dsh holds the Bot team, a window can only show it: Settings → Workflow graphs now says so in the host's own words and offers no **Edit**, **Add link** or wire port, instead of taking a change core refuses with `bot/read-only` and then drops ([#2187](https://github.com/ThinkFlowLab/FlyBot/issues/2187)). diff --git a/changelog.d/2188-sidebar-rail-readonly.fixed.md b/changelog.d/2188-sidebar-rail-readonly.fixed.md deleted file mode 100644 index f8f0de74b..000000000 --- a/changelog.d/2188-sidebar-rail-readonly.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The host's read-only sentence now stays visible when the sidebar is collapsed to the rail, clipped to one line with the full sentence on hover and in its accessible name, instead of disappearing until the window is wide again; a host that sent an empty or whitespace-only sentence draws no hint in either shape ([#2188](https://github.com/ThinkFlowLab/FlyBot/issues/2188)). diff --git a/changelog.d/2194-settings-refusal-line.fixed.md b/changelog.d/2194-settings-refusal-line.fixed.md deleted file mode 100644 index 9fbd38549..000000000 --- a/changelog.d/2194-settings-refusal-line.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A write the host refuses in Settings now shows its sentence under the dialog heading instead of at the top of the scrolling page: after scrolling down to the switch that was pressed, the refusal used to land above the viewport, so the window looked as if the click had done nothing. The line sits outside `.bt-settings-scroll`, in view wherever the page is scrolled ([#2194](https://github.com/ThinkFlowLab/FlyBot/issues/2194)). diff --git a/changelog.d/2199-settings-readonly-head.added.md b/changelog.d/2199-settings-readonly-head.added.md deleted file mode 100644 index ba777ba03..000000000 --- a/changelog.d/2199-settings-readonly-head.added.md +++ /dev/null @@ -1 +0,0 @@ -A window that holds the Bot team read-only now says so in the Settings header, in the host's own sentence, above every page that still offers its write controls: General, Bots, Groups, Secrets, Connectors, Capabilities, Scheduled tasks and Projects. Pressing a control there is refused by the host, and until now nothing on the panel explained why nothing moved. The standing sentence sits above the line that reports one refused write, and a blank or missing sentence draws nothing ([#2199](https://github.com/ThinkFlowLab/FlyBot/issues/2199)). diff --git a/changelog.d/2200-workflow-list-readonly.fixed.md b/changelog.d/2200-workflow-list-readonly.fixed.md deleted file mode 100644 index 6e460b327..000000000 --- a/changelog.d/2200-workflow-list-readonly.fixed.md +++ /dev/null @@ -1 +0,0 @@ -While another dsh holds the Bot team, the Workflow list in the sidebar no longer offers **New**, **Rename**, **Delete** or **Hand a task to a Workflow**: a read-only window shows the list only, instead of taking a change that core refuses with `bot/read-only` ([#2200](https://github.com/ThinkFlowLab/FlyBot/issues/2200)). diff --git a/changelog.d/earlier-part-actions.added.md b/changelog.d/earlier-part-actions.added.md deleted file mode 100644 index 28d2de449..000000000 --- a/changelog.d/earlier-part-actions.added.md +++ /dev/null @@ -1 +0,0 @@ -The messages a Bot's chat loads above the current part are now messages you can act on: the reaction and reply buttons on a bubble from an earlier part used to do nothing, because the bubble was drawn without the identity a reaction is stored under and without a session to quote into. A reaction picked on such a bubble now sticks to that message and stays there when another page is loaded above it, and **Reply** quotes the line into the open chat instead of into the part it was said in. ([#2136](https://github.com/ThinkFlowLab/FlyBot/issues/2136)). diff --git a/changelog.d/hardlink-temp-name.fixed.md b/changelog.d/hardlink-temp-name.fixed.md deleted file mode 100644 index 8b819ea4e..000000000 --- a/changelog.d/hardlink-temp-name.fixed.md +++ /dev/null @@ -1 +0,0 @@ -A write that lands through a temporary name now refuses a hard link left there as well as a symbolic one: `lstat` reports a hard link as a plain file, so the team state, the OCR cache, the Automation-tasks defaults, the memory files and snapshot, the decision log's trim and the Bot Social server choice could still be written into an inode another name held outside the Bot's home. The guard asks for a file with only its own name (`nlink === 1`), while the plain leftover a crashed host leaves behind stays replaceable. diff --git a/changelog.d/schedules-list-scope.fixed.md b/changelog.d/schedules-list-scope.fixed.md deleted file mode 100644 index 8d8a95acd..000000000 --- a/changelog.d/schedules-list-scope.fixed.md +++ /dev/null @@ -1 +0,0 @@ -The Scheduled tasks page lists tasks on a host where a member is signed in — the list no longer needs a Session in its request — and each signed-in member is shown only their own tasks. diff --git a/core/package-lock.json b/core/package-lock.json index cdd29bec6..fdf086e64 100644 --- a/core/package-lock.json +++ b/core/package-lock.json @@ -1,12 +1,12 @@ { "name": "ds-bot", - "version": "0.2.20", + "version": "0.2.21", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "ds-bot", - "version": "0.2.20", + "version": "0.2.21", "license": "Apache-2.0", "dependencies": { "@larksuiteoapi/node-sdk": "1.76.0" diff --git a/core/package.json b/core/package.json index a225b31cf..b605cca7b 100644 --- a/core/package.json +++ b/core/package.json @@ -1,6 +1,6 @@ { "name": "ds-bot", - "version": "0.2.20", + "version": "0.2.21", "description": "DS Bot: a team of long-lived Bots for DeepSeek Harness, with Main Bots, Bot-to-Bot messages and group chats", "keywords": [ "dsh-plugin", diff --git a/patches/ds-bot/0007-version-and-tooling.patch b/patches/ds-bot/0007-version-and-tooling.patch index ccf18aebb..151592ed5 100644 --- a/patches/ds-bot/0007-version-and-tooling.patch +++ b/patches/ds-bot/0007-version-and-tooling.patch @@ -68,14 +68,14 @@ diff --git a/package-lock.json b/package-lock.json { "name": "ds-bot", - "version": "0.1.5", -+ "version": "0.2.20", ++ "version": "0.2.21", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "ds-bot", - "version": "0.1.5", -+ "version": "0.2.20", ++ "version": "0.2.21", "license": "Apache-2.0", + "dependencies": { + "@larksuiteoapi/node-sdk": "1.76.0" @@ -706,7 +706,7 @@ diff --git a/package.json b/package.json { "name": "ds-bot", - "version": "0.1.5", -+ "version": "0.2.20", ++ "version": "0.2.21", "description": "DS Bot: a team of long-lived Bots for DeepSeek Harness, with Main Bots, Bot-to-Bot messages and group chats", "keywords": [ "dsh-plugin",