Register Item 42 lever 2 as an open question for the maintainer

[mixmansoundude]

Summary

Pure documentation housekeeping, no functional or test change.

CLAUDE.md Active Backlog Item 42's lever 1 (console-output tiering) shipped and merged in PR #466. Lever 2 (the two elective Y/N prompts a fresh interactive build shows -- :run_postexec_checkpoint's "Run again via the interpreter now?" and :offer_optimized_build's "Want to build an optimized version too?") is the remaining piece.

Re-reading both prompts' current wording directly against run_setup.bat before filing this: both already carry a plain-language rationale line before the Y/N prompt itself, and the jargon term the original audit called out ("Visual Studio Build Tools") only appears in a [WARN]-tier post-failure hint, not in either prompt. So the remaining question is genuinely open-ended:

• Is there still a real gap here, or has this already been substantially addressed by wording that evolved separately from the item's own filing?
• If something is still worth doing, should it stay a small, additive reword (e.g. an explicit "(optional)" cue) on the two existing, separately-tested prompts, or should the two prompts be combined into one ask (a materially bigger restructuring touching prompt count, existing test coverage, and how declining is expressed)?

Unlike lever 1 (a single, objectively-correct technical mechanism), this is user-facing copy and interaction flow -- the kind of call where a wrong unilateral guess costs the maintainer real rework rather than being one valid implementation among several. Registered as a new numbered question in docs/open-questions.md, matching this repo's own "a blocked item needs a registered, traceable question" house rule (see the other 4 entries already there for Items 35/38/46).

Verification

tools/run_sanity_sweep.sh -- all checks pass (compileall, pyflakes, delimiter check, CRLF check, markdownlint, yamllint, actionlint, ASCII sweep, PowerShell AST parse sweep, full pytest: 563 passed / 3 skipped). Diff touches only docs/open-questions.md.

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[mixmansoundude]

@coderabbitai review

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2cef0120-8ad2-49aa-8f33-a11d6778434d

📥 Commits

Reviewing files that changed from the base of the PR and between f7d5dfc and b555740.

📒 Files selected for processing (1)

• docs/open-questions.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (1)

• GitHub Check: auto_merge

🧰 Additional context used

📓 Path-based instructions (2)

**/*.{md,bat,cmd,ps1,py,sh,yml,yaml,json}

📄 CodeRabbit inference engine (AGENTS.md)

Keep text ASCII-only and do not manually change line endings; follow .gitattributes.

Files:

• docs/open-questions.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Cite run_setup.bat locations by stable label or subroutine name rather than exact line number in documentation.

Files:

• docs/open-questions.md

🪛 LanguageTool

docs/open-questions.md

[grammar] ~106-~106: Ensure spelling is correct
Context: ...## 5. CLAUDE.md Active Backlog Item 42, lever 2: is the two-prompt fresh-build flow s...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (1)

docs/open-questions.md (1)

106-144: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Added an open maintainer question about whether to reword or combine elective prompts in the fresh-build flow.
  • Documented current wording, test and consent behavior, proposed options, and potential impact.

Walkthrough

The change adds a fifth open maintainer question about rewording or combining two elective prompts in the fresh-build flow. It records current behavior, possible wording changes, interaction choices, test implications, and the need for maintainer approval.

Changes

Fresh-build Prompt Wording

Layer / File(s)	Summary
Document maintainer decision docs/open-questions.md	Adds the open question for CLAUDE.md Item 42, lever 2. It documents both prompts, their rationale, wording options, separate-versus-combined interaction choices, and related test implications.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to b5557

This change only records an open documentation question and does not alter product behavior, runtime configuration, or tests; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the documentation change: registering Item 42 lever 2 as an open maintainer question.
Description check	✅ Passed	The description accurately explains the documentation-only change and its purpose in tracking Item 42 lever 2.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/batch-crlf-strategy-pdi9h5

---

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.}

[coderabbitai]

@mixmansoundude I will review pull request #467.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.