[bassilkhilo-ag2]

Summary

• Companion test PR for fix(task-bridge): archive context-drop results when voice client is offline #1189 — these tests will fail on main until fix(task-bridge): archive context-drop results when voice client is offline #1189 is merged; they are designed to be merged immediately after it
• 13 tests across 3 suites covering both files changed by fix(task-bridge): archive context-drop results when voice client is offline #1189
• Source-inspection approach avoids the node:sqlite availability constraint that affects task-bridge-format.test.ts

What is tested

main.swift writeTask() (2 tests):

• Emits source: context-drop header so the TS bridge can identify the task origin
• source: context-drop appears before task: — any field after task: is invisible to consumers that enforce the stop-at-delimiter rule (fix(agent-api): close task-file field injection via /task body #982)

task-bridge.ts result watcher (6 tests):

• Has the /^source:\s*context-drop/m detection regex
• Context-drop check is inside the !clientConnected block (not outside, which would archive results even when voice is live)
• Branch calls _sendTaskStatus, _deliveredResults.add, _pendingTasks.delete
• ≥2 archiveFile() calls — both the result file and the task file are archived

Pure regex contract (5 tests):

• Matches well-formed context-drop task body
• Matches with extra whitespace after colon
• Does NOT match voice / discord tasks
• Does NOT match source: context-drop appearing mid-line in task body prose (line-start anchor with /m)

Test plan

• Merge fix(task-bridge): archive context-drop results when voice client is offline #1189 first, then merge this PR
• npx tsx --test tests/task-bridge-context-drop.test.ts — all 13 pass after fix(task-bridge): archive context-drop results when voice client is offline #1189 lands
• Regex contract suite (5 tests) passes independently on any branch

🤖 Generated with Claude Code

[VasiliyRad]

The context-drop test file (tests/task-bridge-context-drop.test.ts) is solid — source-inspection approach is correct given the inline implementation, the 13 tests cover the right properties (regex, placement in !clientConnected block, archiveFile × 2, _sendTaskStatus, _deliveredResults.add, _pendingTasks.delete), and the pure regex contract suite is a good addition.

Two bundled unrelated changes need to come out before merge:

1. src/health-check.py + tests/health-check-bridge-multi-pid.test.py — these belong to the multi-pid path-display fix (Pass 207), not the context-drop archive fix. They should go in their own PR so the test/fix pair stays together and reviewable independently.

2. build_log.md — this is a workspace runtime file, not repo source. It should not be committed to the repo at all (it lives under SUTANDO_WORKSPACE, not SUTANDO_REPO_DIR). Please drop it from this branch and add build_log.md to .gitignore if it isn't there already.

Once those two are removed, this PR is ready to approve.

[bassilkhilo-ag2]

Rebased to single commit d95b60d — just the context-drop test file, no unrelated commits. PR diff: tests/task-bridge-context-drop.test.ts (183 lines, 13 tests). Tests gate on #1189 code: will pass 13/13 after #1189 merges, expected to show 3 failures on current main (source: context-drop field not yet present in main.swift).

[VasiliyRad]

Companion test for PR #1189 (which I approved earlier this pass cycle). Source-inspection over both halves — Swift writeTask() emits source: context-drop, TS task-bridge.ts detects + archives. The structural-test choice (vs spinning up the bridge) is the right level here because the new logic is inline rather than exported. 1 file, no bundling.

LGTM 👍