Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Remove interaction readiness result forwarding left after the readiness-wait removal

Open
#3,607 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
40/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start from packages/daemon/src/execution/interaction/internal/interaction-touch-response.ts and packages/replay-port/src/daemon-port/session-replay-runtime-failure-response.ts, removing the 'readiness' in result copy and the 'readiness' entry in SAFE_CAUSE_DETAIL_KEYS. Then update interaction-touch-response.test.ts and session-replay-runtime-failure-response.test.ts as the issue lists. Do not start until #3599 is merged, since these sites only become unreachable after it lands. Done when the git grep -n -w readiness check on the two directories returns no hits and pnpm check:affected --base origin/main --run passes.

Written by the indexing model from the issue text.

Description

on-hold refactor

Purpose

#3599 removes the replay target-readiness wait, which was the only producer of an interaction readiness result ({ polls, waitedMs, end }). Two consumers still forward that field, and their tests still build the old shape. Delete them so no code describes a field that can no longer exist.

Blocked by: #3599 (merge first; these sites are unreachable only after it lands).

Required change

  • packages/daemon/src/execution/interaction/internal/interaction-touch-response.ts: drop the 'readiness' in result copy into responseData.
  • packages/replay-port/src/daemon-port/session-replay-runtime-failure-response.ts: drop 'readiness' from SAFE_CAUSE_DETAIL_KEYS.
  • Tests: in interaction-touch-response.test.ts, remove the readiness-shaped selectorResult fixture and the two readiness assertions, keeping the prior-warning assertion. In session-replay-runtime-failure-response.test.ts, remove "a replay divergence carries the readiness evidence of an exhausted target wait".

Done when

  • git grep -n -w readiness -- packages/daemon/src/execution/interaction packages/replay-port/src/daemon-port returns no interaction-result or replay-cause hits.
  • pnpm check:affected --base origin/main --run passes.
  • No behavior change: nothing produces the field after #3599.
Dominant language
TypeScript
Stars
5k
Forks
334
Avg merge
13h 19m
Merged PRs (30d)
630

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstack/agent-device

All issues in callstack/agent-device

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.