Repository navigation
Adopt shared completion for the Node specification publisher - #7
Merged
Merged
Conversation
…ervation Retain the existing verified tag publisher and no-Lapis-input graph while adding the pinned read-only completion caller. Keep an independent normal test for the no-update shape so a future Lapis dependency addition requires actual intake qualification. Focused callback tests, normal check/spec/runtime/architecture lanes, workspace and Node tests, build and publint pass. Record pre-existing development advisory findings without changing the lockfile or introducing an exception, release intent or synthetic dependency.
Closed
9 tasks done
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.
Wire the existing Node-only Check workflow into the pinned shared completion observer, preserving the verified tag/OIDC npm publisher and its existing publication notifier. Source permissions remain read-only; no candidate files, artifacts, caches or inherited secrets enter the privileged callback.
Spec Validator currently consumes no Lapis npm dependency. A normal functional test preserves that no-update shape and requires source-owned qualification before future Lapis input is admitted. No synthetic dependency, Changesets job, public version bump, dependency graph change or release is introduced.
Validation: both focused tests, normal check/spec/runtime/architecture lanes, complete Node/workspace tests, build/publint, doctor/QMD and actionlint pass. Source record:
spec/records/2026-11-17-shared-completion.md.Fresh full audit separately records13 pre-existing development-tool findings, with clean production audit. The existing required Check workflow has no audit lane; no gate or advisory policy is changed. Compatible-refresh experimentation was discarded and the original lockfile is preserved. Remediation remains tracked in the adoption issue rather than an inferred exception.
Completion source/policy registration: lapismd/dependency-automation#74. Tracks lapismd/dependency-automation#62 and the final merge/activation queue in #50. Existing-App probe, post-merge completion and honest no-update reconciliation remain pending. Standing activation approval applies after source acceptance; no global rollout is requested.