Refactor withSpinner to accept a callback with spinner control and dynamic success/failure messages

[adelrodriguez]

Refactor withSpinner to support dynamic messages and mid-spin updates

The withSpinner API on Prompter has been redesigned to be more flexible and expressive:

• The run argument is now a callback that receives a spinner control object, allowing callers to update the spinner message mid-operation via spinner.message(...). This is used in addPackageCandidate to display a "Fetching and materializing" message after the resolution step completes.
• The success option now accepts either a static string or a function that receives the operation's return value, enabling result-aware completion messages (e.g. showing the resolved package identity, or distinguishing between "missing" and "malformed" tsconfig/AGENTS.md outcomes).
• The error option has been renamed to failure and made optional. When omitted, the spinner stops without a message on failure.
• The implementation now uses Effect.acquireUseRelease instead of Effect.onExit, ensuring the spinner is always stopped even on interruption.
• addPackageCandidateReference has been split into resolvePackageCandidateReference and materializePackageCandidateReference to allow the spinner message to be updated between the two phases.
• Tests have been added for withSpinner covering success, failure, interruption, and omitted failure message cases.

[adelrodriguez]

• Archive completed v1 plans and add multi-registry groundwork plans 10–13 #24
• Add docs, ADRs, domain glossary, architecture reference, and actionable error messages #23
• Add first-party Packref agent skill with workflow, command boundaries, and README documentation #22
• Implement install command with committed lockfile materialization and narrow gitignore migration #21
• Refactor withSpinner to accept a callback with spinner control and dynamic success/failure messages #20 👈 (View in Graphite)
• Add --global flag to clean command and implement local project reference cleanup #19
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[adelrodriguez]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: 26a946207e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".