inspect: store profiles in project/local settings, user picks where

main

Commit

dipree2mo ago

Profiles were written to clone-local preferences (.git/entire/preferences.json) — hidden and unshareable. Persist them to .entire/settings.json (shared, committed) or .entire/settings.local.json (per-developer) instead, and let the user choose:

  • guided setup / --configure / --edit prompt for the destination,
  • scripted --configure honors a new --local flag (default: project),
  • non-interactive first run writes the project file.

saveReviewProfile / saveReviewProfileConfig now do a raw read-modify-write on the chosen file (preserving unrelated keys and other profiles) and ensure .entire/ exists.

settings.Load now merges review_profiles per profile name across project → clone-prefs → local, so a team can share profiles in the project file while individuals add or override profiles locally without hiding the shared set (previously a later layer replaced the whole map).

Improves the output-destination picker wording and adds tests for the project-vs-local save (no leakage of local-only profiles into the shared file).

Entire-Checkpoint: a84cf443023b

Checkpoints

Checkout the hand off doc that I just added.

PiOpus 4.8
View session
Checkpoint 1