Repository navigation
feat(cli): read organization Wiki and prepare v0.5.0 - #3
Merged
Merged
Conversation
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.
Changes
Adds read-only organization Wiki commands to the existing
hiq-cortexclient:knowledge search/read/links/sources --org <organization-id>, with published revision binding, pagination, source quotations and credential-free download URLs.doctor --orgreports the actual current user and organization. Every knowledge request uses the selected organization and current user SSO; API keys cannot establish organization membership or silently select another stored account.cortex_dataconsent for LCA data and organization knowledge. The returned credential is the user’s full SSO login, as disclosed by the consent page; current access is checked server-side. An explicit absoluteXDG_CONFIG_HOMEselects the native store without falling back to a legacy identity.Prepares version 0.5.0 in package.json, lockfile and generated source, and updates package metadata/README. Existing REST, JSON output and exit-code conventions remain in use. No new SDK, credential service or generic proxy is introduced.
Validation
npm test, 18 passed, including actual CLI processes, loopback HTTP, fake OAuth and a clean npm package install.knowledge.jsis included, no credentials or env files; all four commands anddoctor --orgexercised from the clean installation. Nine help/version invocations passed.actionlint1.7.7 passes both workflows. CI’srunner.tempreference is on the test step, where that expression context is supported. Build/mirror shell syntax, POSIX installer syntax andgit diff --checkpass.d501d781880c78936f5207659977226ed3ed0b09: Ubuntu 24.04.5 and Windows Server 2025 (10.0.26100), both Node 22.23.2 / npm 10.9.8, 18/18 tests on each. These are npm/HTTP/package checks, not native binary or installer execution.Consumers and release conditions
Uses the existing base and exact public routes
/api/cortex/organizationand/api/cortex/wiki/organization/*. The gateway routes, organization resolver andcortex_dataconsent must be deployed and verified with an authorized current user before release.Keep this PR unmerged until the coordinating Cortex session finishes production query acceptance and reviews this exact head. Do not tag or publish npm/GitHub/CDN from this PR merely because CI passes. The existing v-tag workflow owns the five native artifacts, npm Trusted Publishing, GitHub Release, CDN mirror and installation checks. This change neither installs over a user’s existing CLI nor modifies any real credential.