v0.3.0

Breaking change: your search files move to my-search/

Your ICP, search config and scoring profile now live in a my-search/ folder that Git ignores, instead of tracked paths. They are no longer published with the code, and upgrading no longer conflicts with them.

If you set Scout up on v0.2.0, move your files before running anything:

mkdir -p my-search
mv docs/job-search-icp.md profiles/job-search.json my-search/
cp profiles/jobs.json my-search/jobs.json
npm run jobs:config:check

If .env sets SCOUT_PROFILE_PATH or SCOUT_JOB_SEARCH_PATH, point them at the new locations or remove them. New setups start from the example instead: cp -R examples/john-doe my-search.

Cloud routines need your files in a private repository of their own; see "Keep your search in a private repository" in the README.

New

• Private search repository. my-search/ can be its own private GitHub repository. npm run jobs:search:sync commits and pushes it, and npm run jobs:update warns when local edits have not been pushed.
• Cloud routines clone the code and your private search repository side by side.
• Releases and upgrading are documented, including how to upgrade a fork.

Documentation

• Quick-start prompt now creates the private search repository for you.
• Visual guide to the Google Cloud setup, with direct console links and a troubleshooting table.
• "Set up Claude Code" section covering the cloud environment dialog.
• Architecture diagram and example images of the sheet.

What's Changed

• feat!: keep each person's search in a Git-ignored my-search folder by @Hritvik-Mohan in #8
• docs: document releases, upgrading a fork, and publishing a release by @Hritvik-Mohan in #7
• docs: keep each user's search in their own private repository by @Hritvik-Mohan in #9
• docs: add a visual guide to the Google Cloud setup by @Hritvik-Mohan in #11
• feat: add search sync command and README visuals by @Hritvik-Mohan in #10

Full Changelog: v0.2.0...v0.3.0