Clean, focused change. The getThreadContext integration follows the same pattern used in app-mention.ts and direct-message.ts. isInThread logic, the Promise.all parallelization, and the threadContext || undefined coercion to avoid rendering empty <slack_thread_context> blocks are all correct. The DM path also gets a nice perf improvement by parallelizing the getSlackUserInfo call.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

PR Review Summary

(0) Total Issues | Risk: Low

This PR adds thread context support to the resumeMention and resumeDirectMessage functions in the Slack work app. The changes are minimal, well-structured, and follow existing codebase patterns.

What Changed

1. resumeMention (lines 159-179): Added thread context retrieval using the same isInThread pattern used elsewhere in the codebase (app-mention.ts, direct-message.ts, block-actions.ts). The getThreadContext call is correctly parallelized with existing async operations via Promise.all.

2. resumeDirectMessage (lines 238-255): Same pattern applied consistently. Previously a single await for getSlackUserInfo, now correctly parallelized with getThreadContext.

3. Changeset: Appropriate patch bump for @inkeep/agents-work-apps.

Review Notes

✅ Correctness: The isInThread check (Boolean(intent.threadTs && intent.threadTs !== intent.messageTs)) correctly matches the established pattern in peer files.

✅ Performance: Thread context is fetched in parallel with other async operations, maintaining the existing performance characteristics.

✅ Consistency: The threadContext || undefined conversion properly handles the empty-string-to-undefined transform for the optional threadContext field in FormatSlackQueryOptions.

✅ Edge cases: When not in a thread, Promise.resolve('') is returned, avoiding unnecessary API calls.

Summary: Clean, well-structured bugfix that adds thread context to resume link messages in Slack. The implementation follows established patterns perfectly and parallelizes async operations appropriately. Ship it! 🚢

PR Review Summary

(0) Total Issues | Risk: Low

This is a re-review scoped to the delta since the last automated review (commit b3d673358).

Delta Review

1 commit (fix test) — 1 file (resume-intent.test.ts, +11/-2)

The delta adds proper test coverage for the thread context functionality that was already approved in the previous review:

1. Mock addition (line 57): Added getThreadContext mock returning sample thread messages
2. Verification (lines 149-153): Test now verifies getThreadContext is called with correct channel and thread timestamp
3. Output assertion (lines 142, 157): Test validates the formatted question includes thread context prefix and that formatSlackQuery receives the threadContext parameter

✅ Correctness: Test assertions correctly verify the thread context integration added in resume-intent.ts

✅ Test pattern: Uses existing mock patterns (vi.fn().mockResolvedValue) consistent with the rest of the test file

✅ Coverage: The test now properly verifies the full thread context flow for the mention entry point

Summary: Clean test fix that completes the thread context feature. The delta correctly adds test coverage for the getThreadContext call and validates the formatted output includes thread messages. Ready to ship! 🚀

PR Review Summary

(0) Total Issues | Risk: Low

This is a re-review scoped to the delta since the last automated review (commit 4b9987c98).

Delta Review

1 commit (fix raw query build error) — 1 file (agents-api/tsdown.config.ts, +9/-0)

The delta adds a resolveId hook to the rawQueryPlugin in the tsdown build configuration:

resolveId(source, importer) {
  if (!source.endsWith(rawQuery)) return;
  const basePath = source.slice(0, -rawQuery.length);
  const resolved = importer
    ? path.resolve(path.dirname(importer), basePath)
    : path.resolve(basePath);
  return resolved + rawQuery;
}

✅ Correctness: The implementation follows standard Rollup/tsdown plugin conventions. It properly:

1. Strips the ?raw suffix to get the base path
2. Resolves relative paths using path.dirname(importer) when an importer exists
3. Falls back to path.resolve(basePath) for entry points without importers
4. Re-appends the ?raw marker for the load hook to process

✅ Root cause fix: The prior load hook was receiving unresolved relative paths (e.g., ../../../../../../templates/v1/prompt/system-prompt.xml?raw) which fs.readFile cannot resolve. The new resolveId hook ensures absolute paths are passed to load.

✅ Consistency: Aligns with the existing load hook's path handling logic.

Summary: Clean build tooling fix that resolves the ?raw import path resolution issue. The resolveId implementation is correct and follows standard plugin patterns. Combined with the previously-approved thread context feature, this PR is ready to ship! 🚀

PR Review Summary

(0) Total Issues | Risk: Low

This is a re-review scoped to the delta since the last automated review (commit 114222355).

Delta Review

1 commit (revert tsdown changes) — 1 file (agents-api/tsdown.config.ts, -9 lines)

The delta reverts the resolveId hook that was added in the previous commit (fix raw query build error). This brings tsdown.config.ts back to its state on main, removing an unrelated build tooling change from the PR scope.

✅ Correctness: The revert is clean and complete — the file now matches main. The rawQueryPlugin remains functional with just the load hook, as it was before this PR.

✅ PR scope: The final PR diff now only contains the intended thread context feature:

• resume-intent.ts — thread context retrieval for mention and DM resume flows
• resume-intent.test.ts — test coverage for the new functionality
• Changeset for @inkeep/agents-work-apps

✅ No regression: The build fix was unrelated to the thread context feature and its removal doesn't affect the core functionality being shipped.

Summary: Clean housekeeping commit that removes an unrelated build tooling experiment from the PR. The thread context feature (previously approved) remains intact. Ready to ship! 🚀

PR Review Summary

(0) Total Issues | Risk: Low

This is a re-review scoped to the delta since the last automated review (commit c2aa4a9ecf83).

Delta Review

1 commit (Merge branch 'main' into fix/resume-link-in-thread) — brings in unrelated changes from main (Microsoft SSO feature #3134 + version packages #3131).

The PR's feature files (resume-intent.ts, resume-intent.test.ts, changeset) are unchanged since the prior review. No new code to evaluate.

Prior Review Summary

The core feature was thoroughly reviewed in 4 prior automated reviews, all with 0 findings:

✅ Pattern consistency: The isInThread check (Boolean(intent.threadTs && intent.threadTs !== intent.messageTs)) matches established patterns in app-mention.ts, direct-message.ts, block-actions.ts, and modal-submission.ts.

✅ Performance: getThreadContext is parallelized via Promise.all with existing async operations — no sequential overhead added.

✅ Correctness: The threadContext || undefined coercion properly handles empty-string-to-undefined conversion for the optional threadContext field.

✅ Test coverage: The test correctly verifies getThreadContext is called with the right arguments and that the formatted question includes thread context.

✅ Changeset: Appropriate patch bump for @inkeep/agents-work-apps.

Summary: The delta is a clean merge from main with no changes to the PR's feature code. The thread context implementation (previously approved) follows established Slack event handler patterns perfectly. Ship it! 🚀