Extract current public CLI and own npm releases - #21
Merged
Merged
Conversation
daveosterjr
marked this pull request as ready for review
September 24, 2026 23:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make this repository the owner of the current public CLI Commands and keep Next consuming an exact built package. The candidate adds public prospects, tags, driving and webhook Commands while retaining the existing npm alias and agent-plugin assets. Internal-only extensions remain in Next's private CLI and are excluded from the public source and packed files.
Standalone development and release guides, clean JavaScript builds, public-artifact checks, installation checks for both package names, synchronized versioning and an explicit GitHub npm publishing workflow are included. The reviewed candidate is
0.4.0-rc.1. Published@dealmachine/clianddealmachineboth remain on0.3.0; this merge does not publish or move npm tags. Publishing is a separate manual action requiring configured trusted publishers.Compatibility review restored both autocomplete
--scopeentrypoints, legacy response rendering, enrichment property counts, stored-login credential selection and existing phone/list text output. New metadata remains available in raw JSON. Builds clean old output before packing, and guards reject internal-only files, source-map contents and commands even when local feature switches are set.Validation at
04c91083c3497435e495e29448bb084a982110b0: TypeScript, plugin validation and all 62 CLI tests passed. Both packages installed in a clean consumer with executable, import, Playbook and loopback HTTP checks. The package fixture uses isolated synthetic encrypted credentials without touching the operator's home or credential store. Compatibility and artifact regressions failed before correction and passed afterward. No live API request or npm publication was performed.The pre-existing plugin validator required an untracked, unadvertised demo video; it now checks that optional asset when README advertises it. Related consumers in Next PR #2241 and the private API install the corrected archive explicitly. Factory #9 is merged with working CLI setup; its registry will return to master after this source merge. Internal source and cross-repository validation details remain in the private Factory change record.