feat(meta-and-voc-onboarding): Meta + VoC onboarding package - installable by name

MIGRATION.md

@@ -26,18 +26,21 @@ unchanged.
 
 - `package-index.json` and its schema-v1 validator;
 - canonical package payloads as they are merged;
-- `aligned-onboarding`, `corpus-search`, and `building-integrations` as a
-  temporary compatibility set;
+- `meta-and-voc-onboarding` and `building-integrations` as a temporary
+  compatibility set;
 - the Runneth Library rebuilding-page site;
 - scripts and GitHub workflows; and
 - repository documentation.
 
 Legacy use cases that have no active package migration are available only from
 the archive branch and snapshot tag.
 
-Aligned Onboarding is intentionally retained with both directories referenced
-by its instructions. Do not remove any member of that set until a replacement
-package carries the same behavior and dependencies.
+Meta and Voice of Customer Onboarding is intentionally retained with `building-integrations`,
+which its instructions reference. `corpus-search` was removed with the v2
+onboarding package: retrieval runs on Knoweth with summaries in Cacheth
+(staging), and no remaining instruction depends on it. Do not remove
+`building-integrations` until a replacement package carries the same behavior
+and dependencies.
 
 ## Archived migration candidates
 
@@ -51,13 +54,13 @@ snapshot tag. They must return to `main` only as schema-v1 packages:
 | Permissions | Complete the active rework and add a schema-v1 manifest |
 
 They are not package-manager installable until a canonical package payload,
-matching `runneth-package.json`, and `package-index.json` entry are merged.
+matching `package.json`, and `package-index.json` entry are merged.
 
 ## Package acceptance criteria
 
 Every package pull request must:
 
-1. add one package payload and schema-v1 `runneth-package.json`;
+1. add one package payload and schema-v1 `package.json`;
 2. add a matching `package-index.json` entry;
 3. reference only existing relative paths without symlinks;
 4. target a supported root (`agent_apps`, `agent_brain`, `agent_skills`, or

README.md

@@ -47,12 +47,24 @@ 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.
 
-## Aligned Onboarding compatibility
-
-`aligned-onboarding/` remains on `main` with `corpus-search/` and
-`building-integrations/`. These are a deliberate compatibility exception so
-the recently merged onboarding flow keeps its source and referenced
-dependencies while it is migrated to the package contract.
+## Meta and Voice of Customer Onboarding
+
+`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.
 
 ## Library website