repl: add .clearhistory command

[bitpshr]

This pull request adds a .clearhistory REPL command that clears the current session history, both in memory and in the persistent history file when one is configured.

It clears the in-memory history array, resets the navigation index, and truncates the backing file through the open handle. Any pending debounced flush is cancelled first so it cannot rewrite the file after it has been cleared.

Fixes: #63905

[bnb]

This feels a bit off to me. The functionality makes sense, I could see wanting this. But I'm not sure if it's clear when I'd want this vs .clear and the naming is too similar. Is there a more concise name, potentially?

[bitpshr]

@bnb good call. A few options:

• .history clear: reads like history -c in a shell, keeps .clear unambiguous, and leaves room for .history to do more later (listing the entries, for instance). Bare .history would just print a short usage line for now.
• .forget: short and distinct, though on its own it's a little vague about what's being forgotten.
• .resetHistory (or .wipeHistory): still a single command, just renamed off the clear prefix so it stops shadowing .clear, but not really any more concise.

I lean toward .history clear. It's the most concise as a base command and it sidesteps the overlap with .clear entirely.

[SudhansuBandha]

@bnb This functionality will help users to remove commands/contents from previous sessions if they are trying to use same variables or functions with different purpose in subsequent new sessions. Without this functionality user will have to delete/clear contents of the history file to achieve the same.

I would also agree that the name can be changed since it is quite similar to that of clear command.

[bitpshr]

Went with .history clear (renamed from .clearhistory). It reads like history -c in a shell, keeps .clear unambiguous, and leaves .history open to grow later, like listing. Bare .history prints a short usage line for now. Updated the command, docs, and test.

[codecov]

Codecov Report

❌ Patch coverage is 86.66667% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.12%. Comparing base (e2cb91d) to head (69c9188).
⚠️ Report is 28 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/internal/repl/history.js	88.88%	3 Missing ⚠️
lib/repl.js	83.33%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #64450      +/-   ##
==========================================
+ Coverage   90.09%   90.12%   +0.02%     
==========================================
  Files         752      752              
  Lines      252335   252358      +23     
  Branches    47461    47448      -13     
==========================================
+ Hits       227353   227443      +90     
+ Misses      16266    16213      -53     
+ Partials     8716     8702      -14     

Files with missing lines	Coverage Δ
lib/internal/repl/history.js	93.34% <88.88%> (-0.28%)	⬇️
lib/repl.js	92.80% <83.33%> (-0.14%)	⬇️

... and 54 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bitpshr]

Hey @bnb, circling back on this. I reworked it to .history clear per your suggestion. It reads like history -c in a shell, keeps .clear unambiguous, and leaves room for .history to grow later (listing, for instance), with bare .history printing a short usage line. Does that direction look good to you? Happy to adjust if you had something else in mind.