Repository navigation
Integrate Raycast and repair CI for the current read-only CLI - #1
Conversation
|
Exact-head check exposed an inherited CI template failure: setup-node's npm cache fails because the root lock file is absent; the workflow also calls lint/test scripts that the current CLI package no longer declares. Repaired with a dependency-free root lock, the actual existing syntax-check script, six behavioral CLI→real Worker→isolated fake-R2 tests, and an explicit Node>=18 minimum matching global fetch. Matrix retains Ubuntu/macOS and Node18/20, adds22/24 in place of incompatible14/16. Existing coverage tracking and tag release job remain; real native coverage is collected on Ubuntu24. All six cloud integration tests and operational syntax checks pass without an install or real storage write. Raycast source is unchanged and its separate hosted macOS full build will rerun. No laptop/Mini work, uploads, publish or client messages. |
The committed Raycast extension is still absent from main, and the inherited root CI fails before checking it: npm cache expects a missing root lock, followed by scripts absent from the current CLI package. Integrate Upload File/Recent Uploads while preserving the read-only asset-discovery CLI, add a dependency-free root lock and six CLI→Worker→isolated fake-R2 behavior tests, and run actual declared syntax/tests on Ubuntu/macOS with Node18/20/22/24. AGENTS now distinguishes explicit user-selected public uploads from read-only discovery. Existing coverage and tag-release tracking remain; Raycast code is unchanged.
Cloud checks: six end-to-end fixture tests and all native JS/Bash syntax checks pass, with no dependency install or actual storage mutation. They verify health, scoped/limited file listing, image URL encoding, pre-network validation and upstream errors. Hosted exact-head CLI and separate macOS Raycast test/typecheck/lint/build acceptance are required before merge. Earlier original extension head 4937396 passed run 37168201151; it is not proof for a newer head.
Each user supplies bucket-scoped password preferences, HTTPS endpoint/public URL, unique object keys, safe execFile arguments and environment-only credentials. No shared account or shell-config fallback. No laptop/Mini work, real uploads, credentials, runtime installation, tags/NPM publish, Store submission or client messages.
Build/source integration remains separate from native command registration, configured bucket/public receipt and user acceptance. Historical native/real-R2 observations remain dated source evidence. Owner Jack: current native preference/file-picker/copy/history acceptance and genuinely authorized harmless configured-bucket readback on 15 October or next installation; those outcomes stay open.