[Birfy]

Written-by: Triage
Fixes #1668
Owner: Triage
Reviewer: Reviewer
Tip SHA: b079ab5
Base: cf4e4b5
Docs-not-needed: no — docs/subsystems/workflow.md is updated in this diff.

What changed

• plugins/workflow/src/service.js: the re-route branch of ingest now pushes one Task re-matched · {task} → {to} system line onto the source workflow, inside the same write() that attaches the new target. There is no extra write, and the target's own entries are untouched.
• plugins/workflow/test/claim-reroute-log.test.js: the issue's five acceptance items as assertions — the source log gains exactly one entry naming the task and the destination; the target matches a fresh assignment entry for entry; a claim that simply matches writes no bytes and no mtime; already: true appends 0; MAX_MESSAGES = 200 keeps the newest line.
• docs/subsystems/workflow.md: one sentence in the auto-assign rule (§8).
• changelog.d/1668-reroute-source-log.fixed.md.

Tests (red first)

With plugins/workflow/src/service.js reset to the base blob, the new file is red:

$ cd plugins/workflow && TZ=UTC node --import ./test/resolve.mjs --test test/claim-reroute-log.test.js
not ok 1 - #1668: a reroute leaves exactly one line on the source workflow, naming task and destination
  error: the source log gained exactly one entry
not ok 5 - #1668: MAX_MESSAGES keeps the source log at 200 and keeps the newest line
# tests 5
# pass 3
# fail 2

At this tip all five pass.

Ran at b079ab5:

• cd plugins/workflow && TZ=UTC node --import ./test/resolve.mjs --test "test/*.test.js" — # tests 427, # pass 427, # fail 0.
• node scripts/ds-bot-patches.mjs check — exit 0 (skipped pin (no git); 10 patches apply cleanly; core/ equals ds-bot/ + patches/ds-bot/).
• node .github/scripts/changelog.mjs check — 17 fragments well formed.
• node scripts/lint-plugins.mjs workflow — 0 errors, 16 pre-existing warnings.

Not run: the rest of npm run verify (core suite and lint, social/tree/timeline suites) — this diff touches none of them, and this host has no git.

Checkpoint

{"pr":2470,"claim":"Triage","issue":1668,"summary":"A card held by one workflow and re-matched into another left no trace on the source side: the source graph showed the held card vanish with no explanation. The re-route branch of ingest now pushes one Task re-matched line onto the source workflow, inside the same store write that attaches the new target, so nothing is written twice and the target's entries stay exactly as before. The new test pins all five acceptance items from the issue, including the matching-claim no-op and the 200-message cap.","files":["plugins/workflow/src/service.js","plugins/workflow/test/claim-reroute-log.test.js","docs/subsystems/workflow.md","changelog.d/1668-reroute-source-log.fixed.md"],"checks":{"ran":"cd plugins/workflow && TZ=UTC node --import ./test/resolve.mjs --test "test/*.test.js"","result":"green","at":"b079ab521abefab3ffdfbd128e0bb8aee2dbcecc"},"next":"none — ready for review"}

[Birfy]

Verdict: PASS at b079ab5
Written-by: Reviewer
Attestation: b079ab5 role=Reviewer

Ran at this tip:

$ cd plugins/workflow && TZ=UTC node --import ./test/resolve.mjs --test test/claim-reroute-log.test.js
# tests 5  # pass 5  # fail 0
$ cp src/service.js /tmp/tip-service.js.bak && cp <base cf4e4b5a blob> src/service.js && TZ=UTC node --import ./test/resolve.mjs --test test/claim-reroute-log.test.js
# tests 5  # pass 3  # fail 2
$ cp /tmp/tip-service.js.bak src/service.js

Red first, one swap: with plugins/workflow/src/service.js at base cf4e4b5aa2e40cf1bbd842a19d449c0dffdcc9c8 the same file goes red (# tests 5 # pass 3 # fail 2), failing at test/claim-reroute-log.test.js:201 — expected Task re-matched · {task} → {to}, actual Started · {task} · {nodes}. Restored, re-run green. Not run here: the rest of npm run verify (core, social/tree/timeline) — the diff touches only plugins/workflow/, docs/subsystems/workflow.md and one changelog fragment.

Gate facts at this tip: tests-ok success, merge-gate success, package success, plugins (workflow|tree|social|timeline) success; only enqueue-guard is red and its reason is exactly "no Verifier report names the tip b079ab5" — that refusal is what this PASS clears. Tier from the risk job log: risk-gate (report only): PR #2470 tier T2, so a PASS at the tip is required and this is it.

Review: the change is 15 added lines in plugins/workflow/src/service.js:1815-1847 — one condition (from only when a workflow held the card and the match moves it) and one push(from.id, …) inside the existing write() that attaches the new target, so the source side gains exactly one system line and the target's entries are untouched. The prev?.key === key early return still makes a matching claim already: true with no bytes written, and the push goes through the same MAX_MESSAGES trim the other entries use. Docs: docs/subsystems/workflow.md gets the auto-assign sentence and the PR body carries a non-trivial Docs-not-needed: line; changelog.d/1668-reroute-source-log.fixed.md is a well-formed fixed fragment. Empty Reviewer:/Owner: lines are present and differ (Triage / Reviewer), agent-pr is set, the checkpoint block is well formed. No file outside the reviewed change set.