Repository navigation
Point new users at one recommendation before a full report - #3023
Conversation
The end of `hyp setup` and the README both sent people straight to `hyp report generate`. A full report is the long way to a first fix. Both now lead with the one-recommendation ask from docs/workflows/get-one-recommendation.md. Setup: the closing pointer prints the `hyp ask` command for one recommendation instead of naming `hyp report generate`. Its gate follows the command: a client this run left recorded, its CLI on PATH, and the hypaware-query skill on disk. The report skill and the analyst worker no longer decide it, so `recordedReportClientLaunchable` becomes `recordedAskClientLaunchable`. README: the Reports section becomes "Recommendations and reports", with the one-recommendation ask first and the report as the step for reviewing a whole period. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Final review (HypForge steward), head b86f308Clean. Rating LOW. What I checked
Lines
For Brendan to know
|
|
Landing note (HypForge orchestrator): enqueuing at b86f308. The author handed this PR over with
One point left as it is unless the author says otherwise: the pointer prints even when nothing has been recorded yet, as the old report pointer did. A merge is not a release. The new setup line reaches users with the next published version. The companion site PR (hyparam/hypaware.ai#143) is held for a separate reason, stated on that PR. |
|
Merged (HypForge orchestrator) as 1720cb1 at 00:03:56Z on 2026-11-18, on the first pass through the merge queue. The merge-group CI was green. The push CI on this commit was cancelled when the next merge (#3025) arrived a few minutes later, as the queue does; CI on that newer commit is running.
|
New users were pushed toward a full report too early. The end of
hyp setupand the README both namedhyp report generateas the next thing to do. Both now lead with the one-recommendation ask from get one recommendation and fix it, and the report stays as the step for reviewing a whole period.End of
hyp setupBefore:
After:
The wording is the workflow page's "let it find the biggest one" prompt without "in this repo", because setup is not run from a project.
The gate follows the command it names. It still needs a client this run left recorded with its CLI on
PATH, and now checks for thehypaware-queryskill on disk. Thehypaware-reportskill and thehypaware-analystworker no longer decide it.recordedReportClientLaunchableis renamedrecordedAskClientLaunchable, and the test-only optionreportGenerateAvailablebecomesrecommendAskAvailable. Placement is unchanged: ahead of the privacy close and the closing offers.This reverses what #2704 (issue #418) added: setup no longer names
hyp report generateat all.README
"Reports" becomes "Recommendations and reports": the one-recommendation
hyp askcommand and a link to the workflow page come first, then the existing report command and publishing text.Companion: hyparam/hypaware.ai#143 makes the same change to step 5 of the site quickstart.
Not in this PR
a Claude install whose analyst copy failed is not ready).hyp report generateitself still checks for the report skill throughreportSkillLaunchers, which is untouched.hyp askany time: HypAware suggests a skill", so setup now names twohyp askforms. Left as is.Checks.
npm testpasses (9737 pass, 0 fail, 9 skipped) andnpm run typecheckis clean. I did not run the wizard smokes or a realhyp setup.CPU and memory. No concern. The gate runs once at the end of setup and does one
fs.accessper launchable recorded client, which is less work than the stat-per-client plus skill lookup it replaces.🤖 Generated with Claude Code