Ship one organization knowledge skill for native agent hosts

[KirbyInGitHub]

Organization Wiki commands were available in the CLI, but agent hosts had no shared retrieval skill. Ship one organization-knowledge/SKILL.md with the npm package and an importable ZIP from the existing binary-release job. The existing checksums, GitHub assets, and CDN hiq-cortex-* mirror include that ZIP.

The skill uses native terminal calls to verify the current account/organization, search published pages, bind reads/links/sources to the returned revision, and cite original material references. It does not carry knowledge, credentials, publication permissions, or another API/MCP implementation. README documents Cowork Skills Center import, Codex project .agents/skills, and Claude Code project .claude/skills from the same archive. Version remains 0.5.0 because that release has not been published.

Validation:

• macOS arm64, Node 24.19.0: npm test 18/18, including actual CLI processes, HTTP fixture, clean npm installation, and installed skill bytes equal to source. First clean-install attempt timed out; after confirming isolated registry reachability, both subsequent complete runs passed (15s and 13s).
• Negative proof: remove skills from package files; real npm tarball assertion fails. Restore and rerun: 18/18.
• Existing ZIP command executed locally; archive contains only organization-knowledge/SKILL.md, byte-identical to source. Current Cortex extractSkillArchive, validateSkillMd, and parseSkillFrontmatter source functions accept this archive.
• Codex CLI 0.154.0 native skills/list discovers the extracted skill with scope=repo, enabled=true, without a model call.
• Shell syntax, git diff --check, actionlint 1.7.7 for CI/release, and local knowledge --help pass.

Release/acceptance boundary: actual Cowork UI import/plugin mount, Claude native loading, and all three hosts querying a real published page remain pending. No model calls, account changes, npm/GitHub/CDN release, or production writes were performed. No full cross-platform binary rebuild was needed for the unchanged compilation step; release-platform checks still apply. Root Cortex session independently reviews this shared consumer contract and coordinates the real acceptance and release.