This repository was archived by the owner on Nov 11, 2026. It is now read-only.
Repository navigation
feat: rename native CLI to lca-background-data - #8
Merged
Merged
Conversation
Use the new command, configuration and login identity without old-name fallbacks. Release self-contained binaries without an npm publication prerequisite, preserving verified handoff, immutable artifact gates and old releases. Co-Authored-By: Claude Code <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Source-Level CLI Rename
Rename the command to
lca-background-datafor LCA background-database search and process-dataset matching, version0.5.0. The name covers individual inventory items and supported query batches, not just BOMs. The plugin revision is a separate PR after the real native release is available.LCA_BACKGROUND_DATA_API_KEYwins over only this CLI's native store; login uses$XDG_CONFIG_HOME/lca-background-data/credentials.json(absolute XDG home), otherwise~/.config/lca-background-data/credentials.json. Existing credential files are untouched; users sign in again.cortex_dataconsent scope and source-repository URLs. The credential remains full SSO state, not a technically restricted read-only token. New OAuth identity/consent presentation is not live-verified.Why Binaries-Only
Consumers receive five self-contained binaries, with no Node/Python runtime prerequisite. The renamed npm identity has no established bootstrap/Trusted Publisher evidence; do not add npm permissions or secrets to force it through. Make package metadata private and remove active npm packing/publication and npm OIDC from the new release workflow.
npm ci/build/test and local package integrity tests remain developer tooling, not npm distribution.The existing verified private draft handoff and exact file/platform/digest contracts remain. GitHub publication receives only five archives plus checksums and keeps its byte-identical rerun gate. Historical npm publisher/generic handoff helpers remain unused by this release workflow; old npm versions, GitHub releases and CDN objects are not changed or deleted. Historical old-tag workflows are not retagged or modified.
Removing npm must not remove the old tag/version gate: add exact stable version-tag plus main-ancestry checks before build/publication. Add five-archive checksum/member/Mach-O/ELF/PE checks and isolated native-host version/help/missing-credential doctor before the private handoff. This is not native execution on all five targets.
The CDN mirror verifies checksums and uses conditional-create/identical-replay gates for the new namespace, including stable installer/latest keys. Different existing bytes or denied metadata access fail closed; no clobber or credential fallback. Later channel-pointer updates require separate review. Installer checksum verification is mandatory and tied to exactly one filename. Post-publication installer checks pin and compare the exact version, rather than trusting a moving latest version.
Verification
npm testwith fresh HOME/XDG config and no real credential environment: 13/13 pass. Covers new help/version, ignored old environment/store fixtures, new API-key precedence, OAuth client identity and selected storage, and a clean local package with only the new bin key.version=0.5.0, help and empty-store doctor exit 2 pass.git diff --checkpass. No live authenticated business query, EPD review, model calculation or notification performed. Other target binaries have not been executed locally.Merge only after CI is green and no review thread remains unresolved. Release only from the reviewed merged commit; no direct main push, forced tag or permission bypass.
🤖 Generated with Claude Code