docs(ios-runner): RUNNER_PROTOCOL.md points at the wrong file and omits recovery and busy codes
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
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:
commandIdandstatusrecovery (the command journal)runnerFatalandrunnerMainThreadBusy- the error codes
RUNNER_BUSY,RUNNER_WEDGEDandMAIN_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-guidanceis 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstack/agent-device
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
callstack/agent-device#2842 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/agent-device#1869 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
callstack/agent-device#2856 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
callstack/agent-device#2853 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
callstack/agent-device#2833 ·
All issues in callstack/agent-device
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·