feat: add one-command local quickstart - #1059
Merged
Merged
Conversation
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.
Outcome
Adds
openadapt quickstart, a single command that runs the complete local first-value loop: bundled synthetic recording, compilation, explicit demo certification, deterministic replay, and a retained run report. It never overwrites an existing output directory, enables no model or Cloud call, and ends at the existing secure local-to-Cloud connection plus workflow-qualification paths.The flagship README now uses this path instead of asking a first-time user to orchestrate four separate commands.
Evidence
uv run --extra dev pytest -q tests/test_cli_smoke.py(29 passed, 5 skipped)uv run --extra dev ruff check openadapt testsgit diff --checkopenadapt-flow==1.20.1) end-to-end run completed and wroterun/REPORT.mdProduct signal
The bounded 30-day privacy-safe product signal has 3 signup milestones but only 1 first-success milestone. This change targets that activation gap without adding telemetry to the local runtime or weakening qualification gates.