Split iter-51 into three focused iterations

[ractive]

Summary

Splits the original 11-task-group iter-51 (from dogfooding session 40) into three sequential iterations sized for realistic PR review cycles.

• iter-51 (Connection diagnostics & onboarding) — port-collision detection, ff-rdp doctor, meta.connection envelope metadata, branched "no tabs" error, and explicit doctor-promotion tasks (contextual hints, --help troubleshooting, README first-contact for AI agents).
• iter-52 (Input & eval ergonomics) — React-aware type, --selector/--text synonyms, IIFE-wrapped eval with --no-isolate opt-out.
• iter-53 (Stability fixes) — navigate --wait-text console-actor re-resolution, benign daemon "registry not found" warning suppression, screenshot actor-load fallback / version error.

iter-53 depends on iter-51's meta.connection.firefox_version for its version-mismatch error message; otherwise the three are independent.

Why split

Each iteration runs through CI + Copilot + CodeRabbit — the per-PR overhead is real. Three is the right number: smaller chunks would amortize less of that overhead, larger chunks would overload review attention.

Doctor promotion is a deliverable

Session 40 made it clear: a doctor command is useless if no one knows to run it. iter-51 now has a dedicated promotion task hitting five surfaces — first contextual hint after launch, every connection-error hint, --help troubleshooting block, README first-contact section, and an audit pass over all error messages.

Test plan

• Each iteration plan is internally consistent (tasks → acceptance criteria)
• Wikilinks resolve (hyalo links fix --dry-run)
• No code changes; ralph-loop will pick these up sequentially as iter-51 → 52 → 53

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Updated roadmap for upcoming iterations covering: connection diagnostics with port collision detection, enhanced error handling and troubleshooting guidance, type system improvements for React/Vue/Svelte, input and eval command ergonomics refinements, and stability enhancements for reliability and robustness.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6f2b9a2a-0b66-4811-80d9-33e5d43aed75

📥 Commits

Reviewing files that changed from the base of the PR and between 72ac2f7 and ff1644d.

📒 Files selected for processing (3)

• kb/iterations/iteration-51-onboarding-fixes.md
• kb/iterations/iteration-52-input-eval-ergonomics.md
• kb/iterations/iteration-53-stability-fixes.md

---

📝 Walkthrough

Walkthrough

This PR restructures three iteration planning documents: revising Iteration 51 to focus on connection diagnostics and onboarding, and creating two new focused iterations (52 for input/eval ergonomics and 53 for stability fixes) to split out previously bundled work.

Changes

Iteration Planning Reorganization

Layer / File(s)	Summary
Iteration Scope Revision kb/iterations/iteration-51-onboarding-fixes.md	Title and branch renamed to "Connection Diagnostics & Onboarding" (iter-51/connection-diagnostics); motivation expanded around port collision detection and diagnostic improvements; scope narrowed as ergonomic and stability tasks are moved to separate iterations.
Core Iteration Plans & Tasks kb/iterations/iteration-51-onboarding-fixes.md, kb/iterations/iteration-52-input-eval-ergonomics.md, kb/iterations/iteration-53-stability-fixes.md	Iteration 51 tasks restructured to emphasize doctor subcommand, port collision detection, connected-target metadata, and no-tabs error handling. Iteration 52 introduces three tasks: type command React/Vue/Svelte support, improved type ergonomics with flag handling, and eval IIFE wrapping. Iteration 53 introduces three tasks: console actor re-resolution, benign daemon warning suppression, and graceful screenshot fallback.
Acceptance Criteria kb/iterations/iteration-51-onboarding-fixes.md, kb/iterations/iteration-52-input-eval-ergonomics.md, kb/iterations/iteration-53-stability-fixes.md	Each iteration defines success conditions: Iteration 51 covers doctor integration and metadata propagation; Iteration 52 covers input ergonomics and eval scoping semantics; Iteration 53 covers reliability improvements and quality gates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• ractive/ff-rdp#50: Planned eval IIFE wrapping and type/dom/styles ergonomics improvements in Iteration 52 directly correspond to concrete changes in this PR.
• ractive/ff-rdp#49: Launch/port-collision handling and doctor subcommand planned in Iteration 51 align with onboarding and diagnostic changes in this PR.
• ractive/ff-rdp#38: Console actor re-resolution and daemon event handling improvements planned in Iteration 53 directly match the evaluate_js_async and network/daemon event draining fixes in this PR.

Poem

🐰 Three rabbits sorted into tidy rows,
Where chaos once dwelled, now order flows,
Diagnostics hop, ergonomics dance, stability stands tall,
The warren's refactored—we've got plans for it all! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Split iter-51 into three focused iterations' directly and accurately describes the main change: reorganizing a large iteration plan into three smaller, sequential iterations for better PR review cycles.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kb/split-iter-51-onboarding

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}