Report compile and publication progress - #21
Merged
Conversation
Expose the retained lifecycle without leaking private projection data, and keep stdout stable for repository URL consumers. Coordinate the strict progress response with API contract 0.2.0.
Publication failure can mirror an unsuccessful Compilation before any GitHub work. Select terminal progress from the validated Compilation state so the CLI never attributes that outcome to GitHub.
Preserve the closed safe-output boundary while accepting legacy preflight evidence and stage-specific fallback classifications from the coordinated API 0.2 contract.
Separate compatibility-line semantics from the approval-gated npm channel. Release the coordinated API 0.2 candidate as ordinary 0.1.0 while keeping next as the initial distribution path and latest promotion separate.
raghubetina
marked this pull request as ready for review
August 7, 2026 19:33
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.
Summary
First Draft:progress on stderr for analysis, Compilation, and GitHub Publication@firstdraft.com/cli@0.1.0for service API contract 0.2nextas the approval-gated initial channel independently of version syntax, without movinglatestVerification
npm ci --ignore-scriptsnpm audit(0 vulnerabilities)npm run check(typecheck, lint, format, 150 tests, pack check, packed executable smoke)Coordination boundary
This is an unreleased ordinary
0.1.0candidate requiring the First Draft API 0.2 service contract and the coordinated plugin0.1.0candidate. Exact candidate identities must pass the cross-repository compatibility gate before release. Merge, npm publication undernext, any laterlatestpromotion, plugin promotion, and service deployment remain separately serialized operations; this pull request performs none of them.