Summary
Implement the developer onboarding improvements from the Developer Onboarding Spec, and align them with the Raycast extension release workflow.
Specs:
Updated Scope
Developer onboarding
- One-line remote installer via:
curl -fsSL https://raw.githubusercontent.com/ReScienceLab/Perch/main/install.sh | sh
- Download prebuilt
perch CLI from latest GitHub Release by default.
- Initialize
~/.config/perch/sessions.json and ~/.config/perch/config idempotently.
- Install
/perch commands/skills for detected agents.
- Add
perch doctor setup diagnostics.
- Publish prebuilt macOS CLI artifacts and checksums.
- Update README with a 60-second Quick Start.
Raycast release dependency
The Raycast extension should be publishable only after the CLI onboarding path is reliable, because Store users need a simple prerequisite path before using Search/Add Sessions.
Raycast-specific requirements:
- Extension README must state the prerequisite one-line Perch CLI install.
- Empty/error states must guide users to install Perch or run
perch doctor.
- Mutation actions should call the installed
perch binary rather than reimplementing store writes.
- Release checklist must include
npm run lint, npm run build, icon, screenshots, CHANGELOG, and npm run publish / npx ray publish PR flow to raycast/extensions.
Non-goals
- No Perch.app installation or release artifact required.
- No DMG packaging.
- No launch-at-login.
- No signing/notarization for this issue.
- Raycast extension should not become an installer; it depends on the CLI installer.
Acceptance Criteria
Installer / CLI
Raycast publishing readiness
Summary
Implement the developer onboarding improvements from the Developer Onboarding Spec, and align them with the Raycast extension release workflow.
Specs:
markshare/raycast-extension-spec.mdUpdated Scope
Developer onboarding
curl -fsSL https://raw.githubusercontent.com/ReScienceLab/Perch/main/install.sh | shperchCLI from latest GitHub Release by default.~/.config/perch/sessions.jsonand~/.config/perch/configidempotently./perchcommands/skills for detected agents.perch doctorsetup diagnostics.Raycast release dependency
The Raycast extension should be publishable only after the CLI onboarding path is reliable, because Store users need a simple prerequisite path before using Search/Add Sessions.
Raycast-specific requirements:
perch doctor.perchbinary rather than reimplementing store writes.npm run lint,npm run build, icon, screenshots, CHANGELOG, andnpm run publish/npx ray publishPR flow toraycast/extensions.Non-goals
Acceptance Criteria
Installer / CLI
curl | shmode./perchcommands for detected agents.perch doctorreports actionable diagnostics and appropriate exit codes.perch doctor --jsonis available for automation.Raycast publishing readiness
raycast-extension/README.mddocuments one-line CLI install, default sessions path, andperch doctortroubleshooting.perch doctorwhere relevant.perchCLI path.raycast-extensionpassesnpm run lintandnpm run build.npm run publish/npx ray publishcan create the Raycast Store PR after prerequisites are met.