[KirbyInGitHub]

Final Identity And Delivery Policy

Correct the obsolete lca-background-data direction from PR #8. The final command,
bin/package build identity, help/errors, HTTP/MCP client, OAuth identity, environment
prefix and login store are querying-lca-datasets / Querying LCA Datasets, version
0.5.1. No abbreviation, old executable alias, old variable fallback or credential
import is introduced. Existing service wire routes and source repository URL remain.

The active release workflow is CDN-only: manual dispatch from clean reviewed
main, contents: read, no product tag trigger, npm publication, GitHub Release,
private release handoff or Actions artifact storage. Build and publish occur in one
macOS job so no other distribution transport is a prerequisite. Only the CDN step
receives the existing controlled AWS inputs; missing permissions fail, without
credential borrowing or fallback. Historical handoff/publication utilities and their
mock regressions are not active distribution steps.

Native Supply

• Build five self-contained binaries with the exact new command, then emit five
  single-root Host-compatible .tar.gz archives. Windows uses win32-x64 and
  bin/querying-lca-datasets.exe; manifest executable stays extensionless for Host.
• Each archive contains name/version/platform/executable, binary SHA256 and CI
  source commit in manifest.json. Normalize owners/timestamps and gzip metadata.
• Validate exact archive/checksum sets, file types, manifest, all Mach-O/ELF/PE
  target headers and native-host version/help/missing-credential doctor before
  publication. No external runtime is required on consumer machines.
• Publish only /cli/querying-lca-datasets/releases/v0.5.1/... objects by
  conditional-create or exact-byte replay. Verify every object by CDN readback.
  Different bytes, denied access, invalid checksum or corrupt readback stop.
  No mutable latest/root-installer pointer is created or overwritten.
• Render version-pinned POSIX/PowerShell installers from templates; mandatory
  exact-filename checksum verification, native tar extraction, no automatic login
  or user PATH mutation. Archives already satisfy the Host supply contract, so no
  second wrapper is necessary.

Validation

• npm test: 13/13 local pass in isolated HOME/XDG config with synthetic identities.
  OAuth display/agent/client_skill, new package/bin-only metadata, API-key precedence
  and ignored former stores/variables are covered.
• Offline CDN tests pass create/replay, conflict, denied metadata, checksum and
  readback gates; they use synthetic transport bytes, not real AWS/GitHub writes.
• Historical handoff/publication/retention mocks and clean-main-only guard tests
  pass; the active workflow is asserted to have no tag/npm/GitHub-release steps.
• Five final-name Host archives compile locally and pass checksum/layout/manifest/
  target-header checks. Native darwin-arm64 version/help and missing-credential
  doctor exit 2 pass. Temporary installer test passes against local Host archives.
• Shell/YAML syntax passes; Windows CI parses the PowerShell template without
  executing it. No real user credential, authenticated business query, model edit,
  EPD review, notification or Desktop UI installation is involved.

Boundaries

Do not consume v0.5.0's obsolete-name release for plugin supply. Its public release,
tag and task-created CDN objects are separately inventoried for authorized cleanup
after the final-name release/plugin verification. Nothing here deletes v0.4.2, old
npm versions, unrelated CDN objects or historical transfer evidence. No force push,
retagging or direct main push.

The plugin follow-up uses querying-lca-datasets-expert and member
querying-lca-datasets-guide, avoiding both cross-type ID and member-skill collisions
while preserving the standalone Chat querying-lca-datasets entry byte-for-byte.

🤖 Generated with Claude Code