The source registry for packages installed by Runneth.
This repository is migrating from the retired Use Case Library format to the
OS package format. The complete pre-migration library remains available on
archive/full-library
and at the immutable pre-cleanup-2026-07-21-with-aligned-onboarding tag.
package-index.json is the package-manager registry. Each indexed source path
must contain a package.json schema-v1 manifest.
The validator enforces:
- kebab-case package IDs and semantic versions;
- matching metadata and policies in the index and manifest;
- GitHub sources from
Motion-Creative/runneth-appsatmain; - existing, relative resource paths without symlinks; and
- supported targets under
agent_apps,agent_brain,agent_skills, oragent_tools.
Run the contract tests with:
node --test scripts/validate-runneth-package-index.mjsChanges to auto-updating packages require core engineering approval and the
runneth-fleet-change-approved pull-request label.
- Add the package payload and its
package.json. - Add one matching entry to
package-index.json. - Run the package contract tests.
- Open a focused pull request for that package.
Package pull requests should be merged one at a time because they share the central index.
Legacy Creative Strategy, Bootcamp, Permissions, and other use-case payloads
are available from the archive branch and snapshot tag. Reintroduce one to
main only after rebuilding it as a schema-v1 package; do not restore its
legacy directory directly.
meta-and-voc-onboarding/ is a real indexed package: it carries a schema-v1
package.json manifest and is registered in package-index.json with
installPolicy: manual - nothing installs it except one explicit
package install "github:Motion-Creative/runneth-apps/meta-and-voc-onboarding#main"
call. The completed install records selected intent (VM rebuilds reinstall it) and
updatePolicy: auto rolls out merged updates. The install message must also tell the agent to read
/agent/brain/meta-and-voc-onboarding/post-install.md and execute its install-time
sequence in the same conversation - that clause is what kicks off the VoC/Meta
setup; the exact copy-paste message lives in meta-and-voc-onboarding/README.md under
"How to install". A branch ref instead of #main exists only for
branch testing. If an install fails, report the exact error and stop - never
work around the package manager by hand-copying files or editing state under
/agent/.runneth/packages/. building-integrations/ remains on main as a compatibility
exception. The corpus-search/ tool has been removed: retrieval now runs on
Knoweth, with per-creative summaries held in Cacheth (staging). The removed
payload remains available from the archive branch and snapshot tag.
use-case-library-site/ remains deployed as a rebuilding page. Its archived
catalog mode reads the immutable pre-cleanup tag and is available only for
local recovery and migration work. See its
README for build and deployment commands.