Repository navigation
Synchronize cli master into staging - #34
Merged
Merged
Conversation
Track staging work in Factory with durable Linear links
Add active-phone filtering to public export Commands
* Automate production CLI npm releases from master * Report production builds and release outcomes to Factory * Bind manual deployments to the reviewed source commit * Keep automatic npm publication disabled until commissioning
Add CLI live smoke and package regression coverage
…repeat Add bulk prospect lifecycle commands
Adopt E2E-first testing policy and prune redundant checks
…c-20261010-master # Conflicts: # docs/development.md
…master Promote staging CLI smoke tooling to master
Sync feature-2 and master into cli master
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.
User-authorized coordinated integration. Bring master into staging, preserving both branch histories. The candidate tree equals the previously validated source; the owning PR gates run again. Next remains staging-only. See changes/feature2-sync-20261013.json in Factory for exact source/artifact evidence and validation limits. No manual production activation, migration, registry publication or native release.