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

docs(ios-runner): RUNNER_PROTOCOL.md points at the wrong file and omits recovery and busy codes

Open Beginner friendly
#2,797 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
swift, typescript
Domain
documentation

Research direction

The file to update is apple/runner/RUNNER_PROTOCOL.md. First, verify the current command names location in packages/platform-apple/src/runner/runner-contract.ts:53-94. Then, examine the linked files for recovery and error codes: runner/runner-command-recovery.ts, AgentDeviceRunnerUITests/RunnerTests+Transport.swift, and RunnerTests+CommandJournal.swift. Update the document with correct references and brief explanations, ensuring all symbols exist via git grep. Finally, run pnpm check:agent-guidance to confirm the changes pass.

Written by the indexing model from the issue text.

Description

documentation good first issue ready-for-agent

Purpose

apple/runner/RUNNER_PROTOCOL.md:67 says the command names live in runner-client.ts. They are in packages/platform-apple/src/runner/runner-contract.ts:53-94. The doc also doesn't mention:

  • commandId and status recovery (the command journal)
  • runnerFatal and runnerMainThreadBusy
  • the error codes RUNNER_BUSY, RUNNER_WEDGED and MAIN_THREAD_TIMEOUT

Line references are at 01328de411.

Required behavior

  • Fix the pointer.
  • Add a short section for each missing concept: when it is produced, what it means, and what the daemon does with it. Link to the declaration sites (runner-contract.ts, runner/runner-command-recovery.ts, apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Transport.swift, RunnerTests+CommandJournal.swift) and don't copy tables.

Completion conditions

  • Every symbol the doc names exists: check with git grep.
  • pnpm check:agent-guidance is green, if the doc is part of that check.
Dominant language
TypeScript
Stars
4.7k
Forks
304
Avg merge
11h 29m
Merged PRs (30d)
514

Contributor guide

Open the contributing guide

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.