feat(authoring): stage and verify private npm entrypoint pair - #170
Draft
777genius wants to merge 7 commits into
Draft
feat(authoring): stage and verify private npm entrypoint pair#170777genius wants to merge 7 commits into
777genius wants to merge 7 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 6, 2026
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
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.
Change
Create two independent private npm archives from the verified, frozen Linux amd64 candidate. Each installed wrapper selects its fixed product, forwards the CLI contract, and uses the shared acquisition verifier. Exercise both packaged products through generation and the existing installer planner's injected dry-run boundary.
This is a private preparation checkpoint. Public publication, platform acceptance and attestation remain disabled. Useful plugin.yaml implementation, dependencies, tests and design documents are preserved.
Dependencies and scope
Depends on #167 (shared npm verifier) and #169 (release CLI composition), and their existing upstream release gates. The integrated dependency base is 08716f8. The temporary base branch feat/authoring-private-npm-base combines those reviewed dependencies. This draft must be retargeted onto the accepted upstream stack after #167 and #169 land; do not merge into the temporary base as a release delivery.
At 070663e, the diff from that combined base is 2,053 changed lines across 15 files. It slightly exceeds the approximate 2,000-line review target because the packaged generation path and its planner handoff form one coherent verification boundary. The two-file discovery correction is included.
Evidence at dcfa206
These results belong to dcfa206 only. A later test commit must retain this identity explicitly and add its own appropriate verification; historical output must not be relabelled as a new-head run.
Remaining gates
Final exact-head CI and release acceptance remain pending. Node 18 execution, other native platforms, public registry/provenance and release activation remain unproved. Upstream Windows concurrency and macOS policy gates remain open. This PR does not narrow or bypass them.
Final integrated local proof at 070663e
Frozen candidate build, verification, bare native journey, actual npm staging and packaged native E2E all passed. Packaged native: 741 invocations, 2 tests, zero failures/skips. The same-commit packed-to-planner test passed all 10 project subtests and 30 plans. These are Linux amd64 private, injected-planner proofs; all release/platform/attestation claims remain false.
GitHub native CI remains red: the ordinary matrix discovers the separate opt-in packed test without its evidence, Windows also discovers its Linux-only source harness, and Windows amd64 repeats the existing concurrent-init failure. CI integration is being designed without relaxing skip gates; no retry-to-green was requested.