Repository navigation
feat: a started board task gets its own conversation, bound to the engine's link - #189
Open
polymaniadeveloper-hub wants to merge 13 commits into
Open
polymaniadeveloper-hub wants to merge 13 commits into
polymaniadeveloper-hub wants to merge 13 commits into
Conversation
…ts task Board and task ids are percent-encoded in the marker, so board a:b with task c and board a with task b:c no longer share a marker, a create command and a thread. Plain ids keep the spelling #186 wrote. boardTaskOfMarker resolves a thread's marker to its task, one way only; boardTaskThreadId names the one thread a task is created as. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ne's link The server reads the engine's lanes on a beat. A task the engine shows in work with no boardThread gets one thread, created under the task's own command id and thread id with the marker stamped at creation, led by the seat the engine's team configuration names as its lead. The link is registered by the PUT route with setBy the environment and expect null; a conflict leaves the other writer's link standing and archives the thread made here. The task is claimed with the thread's origin and each pass is the heartbeat. No client starts any of this, and act refuses the link and claim routes. Tested against a scratch engine that models the frozen 6a contract. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
lib/taskConversation reads boardThread, on the task and on its card, and stays the only reader of it. The task.source stand-in is gone with no second source: a task with no link is a draft, queued or unlinked, and the thread a task was filed from is never shown as its conversation. A link wins wherever the task stands, so a task sent back to the queue keeps what was said. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A task that ended leaves its thread archived, and no thread list shows a board task's thread. The board toolbar now opens a list of them, each to open, restore or delete. The server finds them by their marker and names the board and task of each; the client never reads a marker. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… it owes The card carries the engine's message count, how many are new and the last line. The Waiting on you lane adds up its open questions and sign-offs in its header. A board task's conversation raises nothing in the sidebar or as a notification, so the card and this lane are where a person sees they are asked. Every number is a field the engine already sends on the card. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…e and read back The marker no longer escapes its ids. A task id is what the engine's routes take ([\w-]+) and a board id carries no colon, whitespace or control character; an id outside that is refused at write (boardTaskOf), so the task gets no thread and no link, and board-task:a:b reads one way. The pin covers only the two ids T3 writes into the marker: a thread id the engine supplies in boardThread is taken as it is. Every boardThread write waits in one server-side queue. On a 409 conflict the current link is read from the engine and stands; the thread made here is archived. moved and not-found are final: the thread is archived and an archived thread is never linked, on a later pass or after a restart, until a person restores it. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…task A board task's conversation is in no thread list, so the linked threads of a pull request or an issue left it out. It now returns as "Board task: <title>" and opens the task view, conversation and engine facts together, never the raw thread: the row carries no thread id. The rows are selected on the board-task: marker prefix, apart from the ordinary list, whose exclusion of server-owned threads is untouched. The title is the engine's when it lists the task. A task it does not list (deleted, moved, or the engine away) keeps the title its thread was made with, and one whose conversation is archived is told as ended and opens the board, where the archive is. Mobile has no board: its issue screen shows the row and says where to open it. The three new strings are in every web and mobile catalog, machine-translated. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Brings in the merged hardening round (#187). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ository BoardTaskThreads.engine.test.ts was named by two comments and lived only in a scratch folder. It is now a test that skips unless T3_BOARD_THREAD_ENGINE_ROOT names an engine checkout, and scripts/board-thread-engine.ts is the engine it starts: the real engine on a temp home, one bound repository and one board, stopped when the test ends. The lead's model is read from the engine's own team file, not written into the test. Also, after the merge of master: the archived-send test made its markers from an unbranded task, which this branch's marker no longer takes. It uses boardTaskOf. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The shell counts only a project's active board conversations, so a project whose board conversations were all archived got no line about them and was told only that any archived threads are deleted. Those are kept. The confirmation now asks each environment for its archived board conversations (the read the board's archive list uses, once, with a two second deadline) and says how many are kept when none is active. With an active one the existing line already says so. An environment that does not answer, or has no such read, counts as none and the confirmation is what it was. The new string is in every web and mobile catalog, machine-translated. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…gain A board task's thread restored from the board's archive stayed open for good when its task was deleted or held by another conversation: the archive command id was the same on every attempt, so the first archive's receipt answered the retry and nothing happened. The thread was then in no list and not in the archive. The archive command id now ends with the thread's revision (the version of its event stream), which every event raises. A pass repeated over the same state is still answered by the first archive; a thread restored since is archived anew. A restored thread whose task moved to another machine is archived again too. Tests: the deleted task's thread restored, the displaced thread restored, the moved task's thread restored, and a task back in work with its link free, whose restored thread the next pass links. The real-engine test covers the same and the hold without the approval key. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…take the thread The archive offered Restore for every thread, including one whose task was deleted, where a restore leaves it holding nothing. The archived board threads read now says how each thread's task stands in the engine: open (its link is free or names this thread), held (another conversation holds it, or it moved), deleted (not in the lanes and the engine answers 404 for it), or unknown (the engine did not answer in time). Only an open task's row offers Restore; the others offer Open and Delete and say why. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…val read's deadline Removing a project reads the archived board threads with a two second deadline. The engine check now has a single 1.5 second wait for the lanes and every task read together: past it each task is unknown and the rows are still answered, so a slow engine never costs the removal confirmation its count. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Board revamp slice 2, T3 half: a board task that the engine shows in work gets one conversation of its own, made by the server and bound to the engine's
boardThreadlink. Built on the hardening round (#187), which is merged into this branch.Spec:
docs/context/delivery-system/BOARD-REVAMP-UI-SPEC.md(Operation-PaperClip, branchdocs/board-revamp-ui-spec), sections 4, 5, 6, 6a, 7, 9, 10.How a thread is created, and why it only reads engine facts
apps/server/src/delivery/BoardTaskThreads.tsreads the engine's lanes (/api/lanes?view=development&set=all) every 30 seconds. A task counts as started when its lane is not one ofdraft,chat,queue,intake,ready, not finished (completed,closed-not-done) and notmoved/moving. A started task with noboardThreadgets one thread, then the link is written back, then the task is claimed with the thread as origin. Each later pass is the claim's heartbeat.The engine is the only source: its lanes say what started and which thread a task holds, its team configuration says who leads. T3 never starts a task, no client asks for a thread, and
delivery.actrefuses the link and claim routes. That keeps one writer per fact, so a board open in two clients or a restarted server cannot disagree with the engine about which thread is a task's.Idempotence across double starts and restarts
board-task:<board>:<task>and<marker>:thread). A second pass, a second server and a restart between the create and the link all dispatch the same command and get the one thread (command receipts).reconcileruns under a one-permit lock, and is safe to run twice at once.Write-back semantics
PUT /api/tasks/<id>/board-threadwithsetBythe environment andexpect: null: the write only lands if no link was set.movedandnot-foundare terminal: the thread is archived, and an archived thread is never linked, on a later pass or after a restart.codedecides, never its message text.Marker grammar and its exact scope
board-task:<board>:<task>, with task id[\w-]{1,256}(what the engine's routes take) and a board id of 1 to 256 characters with no colon, whitespace or control character. Ids outside that are refused at write byboardTaskOf(holdunmarkable-id): no escaping, no thread, no link. The pin covers only the two ids T3 writes into a marker. A thread id the engine supplies inboardThreadis taken as it is and never re-validated.Lead selection and the holds
The lead is the seat with role
team-lead, else the seat namedlead, of the task's team in the engine's team configuration. Its harness picks the provider instance: the driver's default instance, or the sole enabled instance of that harness. Two instances of one harness are two accounts and the engine names a harness, not an account, so that case is held, not guessed.A started task with no conversation is held for a logged reason:
no-board,unmarkable-id,no-project,no-lead,no-lead-model,no-provider,ambiguous-provider,foreign-thread,archived-thread,no-key,refused,moved.The archive door
A task's thread is in no thread list, and one whose task ended is archived, never deleted. The board toolbar opens "Archived task conversations" (
delivery.archivedBoardThreads): each can be opened, restored or deleted. The server finds them by marker and names the board and task; the client never reads a marker.Card and lane surfacing
A card carries the engine's message count, how many are new and the last line. The "Waiting on you" lane adds up its open questions and sign-offs in its header. A board task's conversation raises nothing in the sidebar or as a notification, so the card and this lane are where a person sees they are asked. Every number is a field the engine already sends.
Linked rows
A pull request's or issue's linked threads now include board tasks as "Board task: <title>". The rows are selected on the
board-task:prefix, carry no thread id and open the task view (conversation and engine facts together). The ordinary list's exclusion of server-owned threads is untouched. An archived one reads as ended and opens the board. Mobile has no board: its issue screen shows the row and says where to open it.Merge of master (#187) and what was checked
origin/master(360306b) was merged in, no rebase and no force push. Git merged every file without a textual conflict. One semantic seam: #187's archived-send test built markers from an unbranded{board, id}, which this branch's marker no longer takes; it now usesboardTaskOf(2902be8).Present after the merge, with their test files passing:
OrchestratorThreadArchivedErrorwithrefuseArchivedThreadMessageand the archived-send test:ThreadLaunchService.test.ts78 passed.ThreadRouteViewserverOwnedtag exemption and the hidden-tag matrix cases:ThreadRouteView.browser.test.tsx9 passed.ThreadManagementServiceincludeSubagentsfamily rule:ThreadManagementService.test.ts36 passed.ComposerArchivedThreadwith the ChatView banner:ChatView.archivedSend.browser.test.tsx2 passed.fea770db813e04c2): in all 10 web catalogs, and the sentence in all 10 mobile catalogs.node scripts/i18n-check.tspasses.Also run, one file at a time:
BoardTaskThreads.test.ts13,boardThreadMarker.test.ts4, client-runtimedelivery.test.ts4,deliveryModelBinding.test.ts1,projects.test.ts2,ProjectSettingsPanel.logic.test.ts10,ProjectSettingsPanel.browser.test.tsx26,ArchivedBoardThreads.logic.test.ts1. Typecheck is clean inpackages/client-runtime,apps/server,apps/web,apps/mobile. The full suite was not run.Real-engine validation, reproducible (review ask-back)
The repo already gates environment-dependent tests with
skipIfand keeps host-side verifiers inapps/server/scripts, so the runner is committed under that convention:apps/server/src/delivery/BoardTaskThreads.engine.test.ts: skipped unlessT3_BOARD_THREAD_ENGINE_ROOTis set.apps/server/scripts/board-thread-engine.ts: the engine process the test starts and stops.Replay, against engine commit a658892b:
I ran exactly this on a fresh archive of a658892b: 1 passed. Without the variable: 1 skipped.
Seed data (all under a temp folder, removed at the end): an engine home with one repository
appbound to a new git repository with one empty commit, one boardwork, the engine's ownteamsfolder, and an approval passphrase generated per run. Tasks are added through a control port on the script, because the engine's API offers no way to add a task in a chosen lane, move one or delete one.Asserted, against the real engine's store and HTTP API:
team.json.{environmentId, threadId, setBy}of this environment; the lease origin isthread:<environment>/<thread>; a second pass renews the same claim; exactly onetask.board-thread-setevent.:,/and%; the engine's link stands, ours is archived, no lease is held.moved, thread archived, never retried (archived-thread) even after the task returns.refused, nothing written or archived; the right key then links.Real: the engine, its store, its HTTP API, the delivery service's request path,
BoardTaskThreads. Stubbed: T3's thread store (commands kept in memory with command receipts), the project lookup, the provider registry (codex and claudeAgent enabled), the board thread rows read. No provider or worker runs.What ran only against the scratch engine (
boardThreadEngine.testkit.ts, a model of the frozen 6a contract): the 13 cases ofBoardTaskThreads.test.ts, including the restart between the create and the link write, the one-at-a-time write queue, the holds for lead and provider selection, an engine without the link, and a client'sactbeing refused. Restore re-enabling linking follows from the archived-thread rule (a restored thread is no longer archived) and has no dedicated test case.Removal dialog (QA round 3, finding 1)
The shell's
serverOwnedThreadscount covers only active board threads, so a project whose board threads were all archived was told only "Any archived threads are deleted from T3 Code", which is false for them. The confirmation now readsdelivery.archivedBoardThreadsonce per environment (2 second deadline), counts the rows of the project's members, and when none is active adds "N archived conversation(s) started by a board are kept, not deleted." With an active one the existing line already says so, so there is one line, not two. An environment that does not answer or lacks the read counts as none.Tests in
ProjectSettingsPanel.logic.test.ts: the all-archived case, the count per member and environment, failed, absent and never-answering reads, and no doubled line. The new string (a65acdb87eac322b) is in every web and mobile catalog, machine-translated.Not verified by hand in a running app: the dialog was exercised through the logic test and the existing browser test, not clicked through on web or mobile.
Capability gaps
T3_DELIVERY_BOARD_THREAD_KEYmust be set on the server host. Without it links are held asno-key.T3 pieces reused
ui/popover,ui/button,ui/toast,RelativeTime, anduseThreadActionsfor restore and delete.PullRequestThreadLinksandIssueThreadLinksrows and the command palette's open action.planProjectRemovalconfirmation on both surfaces (api.dialogs.confirmon web,Dialog.confirmon mobile), the existingdelivery.archivedBoardThreadsread throughcreateEnvironmentRpcCommandanduseAtomCommand. No new UI element.gt generateandscripts/i18n-check.ts.Deferred
🤖 Generated with Claude Code
Independent QA, 2026-11-22 (head 8664955)
QA ran on a separate model from the builder, in its own detached worktree at the head. No product code was changed and nothing was pushed or merged. The engine repository was only read (
git archive).Verdict: pass with findings. 1 blocking finding.
Findings, ranked
1. Blocking: restoring the archived conversation of a deleted task makes it unreachable.
The archive door offers Restore on every row, including conversations whose task no longer exists. Restore clears
archivedAt. The thread is then in no thread list (by design), it leaves the archive door (which lists only archived threads), and the reconciler never re-archives it: more than two passes later it was still unarchived. Its project's removal dialog still counts it ("1 conversation started by a board or the engine is archived, not deleted"), but no surface opens it. The only way back is its raw URL.Reproduction, live (real engine at a658892b plus a T3 dev server at this head):
/add, statetriage,submittedset) and let a pass link it./deletethe task. Within one pass the thread is archived and listed under "Archived task conversations".archived_atis now empty.The PR body says restore is what re-enables linking, which fits a task that still exists (conflict or moved). For a task that is gone, restore turns a recoverable conversation into an orphan. Suggested fixes: offer Restore only when the engine still lists the task, or have the reconciler re-archive an unarchived marker thread whose task the engine positively reports as not found (never when the engine is away).
2. Not a defect in this PR:
UsageService.test.tsfails on this Mac."returns other providers' usage while Muse home discovery is still pending" expects
/var/folders/...and receives/private/var/folders/...(macOS tmp symlink). It fails alone too. The PR touches no usage file; it ran only because import tracing pulled it in. Not re-run on master.Observation (not counted): the task centre's composer reads "No team" for a board thread. That may be intended, since the lead's model is already set. Noted for the owner.
1. Real-engine test (
BoardTaskThreads.engine.test.ts)T3_BOARD_THREAD_ENGINE_ROOT: 1 skipped, clean.git archive a658892b delivery teams): 1 passed.: / %, moved, not-found, a wrong key, and archive on delete. The missing-key (no-key) hold is covered only by the scratch test (BoardTaskThreads.test.ts:465), not against the real engine.2. Full loop in a real web client: pass, apart from finding 1
Setup:
node apps/server/scripts/board-thread-engine.ts <a658892b archive>withT3_BOARD_THREAD_ENGINE_PHRASE, andpnpm dev --home-dir <scratch>withT3_DELIVERY_BOARD_THREAD_KEYset to the same phrase anddelivery.engineUrlpointed at the helper. Setup note: the host'sT3_WORKSPACE_*variables must be unset for a scratch dev server. Otherwise delivery refuses with "settings do not match its bound engine endpoint" and the home gets stamped to the host profile. This was a QA environment issue, not a product bug.no-project(logged). After the folder was added through Add project > Local folder, the next pass linked it:boardThread.threadId = board-task:work:task-30a52d2a86,setBy= this environment.teams/development(codex,gpt-6-astra). Its title is the task title./Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mwrxuny0-46dc9c26.pngtask_messages), the card showed "2 messages, 1 new, lead: QA: which base should this go on?".needs-decision, the "Waiting on you" lane header showed "1 question". Screenshot:/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mwrxxmhx-83632551.pngreadyand then back totriageover two passes. Still one thread, one link, and exactly onetask.board-thread-setevent./delete, the thread was archived within one pass and listed in the board's archive door. Screenshot:/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mwry1w5a-d5c13a7b.pngdeleted_atwas set, and the row left the door.3. Linked rows: pass (pull request), not run (issue)
The second board thread was linked to this PR through the palette's "Link pull request to thread" (a T3-side link; GitHub was only read). The PR detail showed "Linked from 1 thread". Its row read "Board task: QA linked rows task" / "Opens the task on the board" and opened
/board?...&task=task-22d2d8462c(the task view), never the raw thread. Screenshot:/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mwrya10s-98d6d9f8.pngAfter the task was deleted, the row read "Task ended. Its conversation is in the board's archive" and opened the board. After the thread was deleted, the link control was gone.
Issue rows were not exercised live: there was no issue tracker bound to a scratch repository. They share
linkedBoardTaskswith the pull request path.4. #187 regression: partial
Tests run (serialized, after the client pass)
Every test file importing a module this PR changes (import-traced, 94 files) plus the PR's own tests:
Not verified
Fix round, 2026-11-22 (head 0468243)
For QA finding 1: restoring the conversation of a deleted task orphaned it. Three commits on top of 8664955, no force push.
Cause.
settleEndeddid try to archive the restored thread again, but the archive command id was the same on every attempt (<marker>:archive:<reason>), so the first archive's receipt answered the retry and nothing happened. The same receipt swallowed the second archive of a displaced thread. The door offered Restore on every row.Part B, the server (0b69b15). The archive command id now ends with the thread's revision: the version of its event stream (
MAX(stream_version)of the thread, one indexed lookup in the rows read). Every event raises it and it never repeats, so a pass repeated over the same state is still answered by the first archive, and a thread restored since is archived anew. I chose it over a restore counter because it needs no new field on the thread and no new event.settleEndedand the door now share one rule,boardThreadStanding(linked,free,displaced,moved), and a restored thread whose task is on another machine is archived again too: before, it would also have sat open in no list.Part A, the door (59da50e, 0468243).
delivery.archivedBoardThreadsnow says how each thread's task stands, in a new fieldtask:open: the engine lists the task and its link is free or names this thread. The row offers Open, Restore and Delete.held: another conversation holds the task, or it moved. Open and Delete, with "The task is held elsewhere."deleted: the task is not in the lanes and the engine answers 404 for it. Open and Delete, with "The task was deleted."unknown: the engine did not answer. Open and Delete, with "The task could not be checked." Never called deleted.This is one step past the brief ("only for a thread whose task the engine still lists"): a displaced or moved thread is listed, but its restore would be undone by the next pass, so it is not offered either. The read lives in
apps/server/src/delivery/archivedBoardThreads.ts; the handler only maps the error. The whole engine check has one 1.5 second wait, because the project removal dialog reads the same list with a 2 second deadline: past the wait every task isunknownand the rows are still answered.Tests.
BoardTaskThreads.test.ts(13 passed): a deleted task's thread restored twice is archived again each time, on this server and on a new one; a displaced thread restored twice is archived again; a moved task's thread restored is archived again; a task back in work with its link free, whose restored thread the next pass links and claims. The earlier expectation ("it is not archived a second time") is replaced. With the old command id, the three changed cases fail.BoardTaskThreads.engine.test.tsagainst the real engine at a658892b (1 passed): the deleted and displaced restores, the restore that links, and the missing-key hold (no-key), which only the scratch engine covered before.ThreadLaunchService.test.ts(78 passed), on the real store: the read'sopen,held,deletedandunknownanswers, and the revision rising across archive and restore.ArchivedBoardThreads.logic.test.ts(2 passed): which rows offer Restore and what the others say.boardThreadMarker.test.ts4,ws.test.ts34,ProjectSettingsPanel.logic.test.tsand webstate/delivery.test.ts(53 with the door's test), client-runtimedelivery.test.ts4. Typecheck is clean inpackages/contracts,apps/server,packages/client-runtime,apps/web,apps/mobile.QA finding 2,
UsageService.test.ts. Run once on master (360306b) and once on this head: the same single case fails on both ("returns other providers' usage while Muse home discovery is still pending",/private/var/...received where/var/...is expected), 69 others pass. It pre-exists and is not fixed here.Not verified.
T3 pieces reused. The door keeps its
ui/popover,ui/buttonanduseThreadActions. The read followslinkedBoardTasks(the same lanes read through the delivery service, an engine that does not answer is never an error).Independent QA of the fix round, 2026-11-22 (head 0468243)
QA ran on a different model from the builder, in its own detached worktree at the head. No product code was changed and nothing was pushed or merged. The engine repository was only read (
git archive a658892b delivery teams). Setup was the same as the first round:board-thread-engine.tswithT3_BOARD_THREAD_ENGINE_PHRASE, and onepnpm dev --home-dir <scratch>withT3_DELIVERY_BOARD_THREAD_KEYset to the same phrase and the host'sT3_WORKSPACE_*variables unset. The project was added through Add project > Local folder. One server and one engine ran at a time, and both were stopped cleanly.Verdict: pass with findings. 0 blocking findings. The first round's blocking orphan is fixed.
Findings, ranked
1. Should fix, not blocking: against the real engine, a moved task is never
held, and a forced restore of its thread is not undone.At a658892b,
laneOfreturns null formoved(delivery/lib/views.mjs:274), so a moved task is in no lane of/api/lanes?view=development&set=all. Both new checks read those lanes, so themovedstanding never applies with a real engine:/api/tasks/<id>, gets 200, and labels the row "The task could not be checked." while the engine is up and answering. The design says "The task is held elsewhere." Restore is still withheld, so this part is only a wrong label.settleEndedsees no card, gets 200 from/api/tasks/<id>, and moves on. A restored thread whose task is still moved stays open. The fix note's claim ("a restored thread whose task is on another machine is archived again too") holds only for the scratch engine inBoardTaskThreads.test.ts:375-380, which lists moved cards. The real-engine test restores the moved thread only after the task is back in triage (BoardTaskThreads.engine.test.ts:402).Reproduction, live: add a started task (QA2) and let a pass link it. Clear its link with the key (
DELETE /api/tasks/<id>/board-thread) and control/moveit tomoved. Archive its thread with a directthread.archivecommand. The door row says "The task could not be checked.". Dispatchthread.unarchive, then wait more than two passes: the thread stays open (archived_atempty, no new archive event). It is in no thread list and not in the door, and the task centre for QA2 says "No conversation is linked to this task yet." No UI path offers that restore, which is why this is not blocking. The same open, unlisted state was reached without any restore: clearing the link of a moved task leaves its thread open forever (QA2 before the forced archive).Related, and fine: a moved task that keeps its link (QA4, which is what the engine's own move-away in
bundle.mjsdoes) keeps an open thread, and the task centre opens it from the sidebar's "With the team" list. So it is reachable.Suggested fix: when a row's task is missing from the lanes, read its
statefrom the/api/tasks/<id>answer that is already fetched. Treatmoved/movingasheldin the door, and asmovedinsettleEnded.2. Not a defect of this PR:
UsageService.test.tson macOS. The builder's master check matches the first round's finding 2. Not re-run.Observation: with the engine frozen (SIGSTOP), the board itself showed "Some requests are slow: 2 requests waiting longer than 15s" (the lanes reads). The door was not affected (below).
1. The orphan, as first reproduced: pass
/delete: archived within one pass and listed in the door as "QA1 deleted task · Archived 1m ago · The task was deleted.", with Open and Delete only (no Restore). Screenshot:/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mws000q3-1fa489b8.pngthread.unarchivecommand over the client's socket.board-task:work:task-a15dcf3ffd:archive:deleted:3. Forced restore 2: re-archived with...:archive:deleted:6. After that, more than two idle passes wrote no further archive event (idempotent). The row was back in the door each time. Delete still showed in every row. Delete was exercised in round 1 and not clicked again here.2. The meaningful restore: pass
A free link was reached by displacement, not by "moved" (see finding 1 for why "moved" cannot produce it on this engine). QA3 was linked, then a rival link was PUT with the key: archived as displaced. Then the rival link was cleared.
/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mws0b27n-5108ea3f.pngboard-task:work:task-1944b6d78a, this environment). The engine's events show exactly onetask.board-thread-setafter the restore (the full history is: set (ours), set (rival), cleared, set (ours)). The thread stayed open over a further pass, and T3 has one thread for the task./board?...&task=task-1944b6d78a) opens the conversation, with no archived notice. Screenshot:/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mws0cv1g-e0d9afb4.png3. Displaced: pass
QA5 and QA3, after a rival link PUT with the key, were archived within one pass. Both read "The task is held elsewhere." with no Restore. Screenshot:
/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mws09ax8-51c3a7e5.png. A forced restore of QA5 was re-archived on the next pass (...:archive:displaced:2), and the rival link was untouched.4. Unknown: pass
delivery.archivedBoardThreadscall answered in 1519 ms, every rowunknown. Screenshot:/Users/tevinmuparadzi/.polymania/t3-pm/userdata/browser-artifacts/browser-screenshot-localhost-mws0khqg-33c85d03.pngunknown.5. Regression: pass
6. Real-engine test: pass
T3_BOARD_THREAD_ENGINE_ROOT: 1 skipped, clean.:394,:402), and theno-keyhold (:363).Tests run (serialized, after the client pass)
BoardTaskThreads.test.ts,ThreadLaunchService.test.ts,boardThreadMarker.test.ts,ws.test.ts: 4 files, 129 passed.ArchivedBoardThreads.logic.test.ts,state/delivery.test.ts: 2 files, 43 passed.Not verified
movedby the pass itself (the link write racing a move) was not produced live. Its door label and forced restore were inferred from the code path and from the hand-archived QA2 thread.