refactor(meta-and-voc-onboarding): self-describing names for the staged rule files

[Eric Smith (motionBuilderEric)]

What

Renames the staged guard folder and files so anyone browsing a VM understands them without opening one:

Before	After
guards/	meta-onboarding-rules/
account-context-guard.md	meta-analysis-account-context.md
meta-validation-gate.md	meta-analysis-validation.md
knoweth-organize.md	brain-organization.md
knoweth-brain.md	brain-file-conventions.md

Pure renames (100% similarity, content unchanged) plus the reference updates that follow: the manifest resource map (id, sourcePath, VM target path), post-install step 3's staged folder and filenames, four README mentions, and the three docs that cite staged rule paths.

What deliberately does not change

Sentinel names inside the blocks (runneth:account-context-guard, runneth:meta-validation-gate, runneth:knoweth-organize, runneth:knoweth-brain) stay as they are, so blocks already merged into /agent/user.md on live VMs keep matching and re-merge in place on future installs. Prose that refers to "guard blocks" as a concept also stays.

Validation

Scoped review passed on all counts: every rename verified byte-identical by git blob hash (sentinels included), a repo-wide grep finds zero surviving references to the old folder or filenames, the new paths are consistent across all six edited files, and the manifest changes are exactly the one resource entry plus the version bump to "2" (matched in package-index.json, since v1 is the released baseline).

Update-path note

On already-installed VMs, the auto-updater should stage meta-onboarding-rules/ and remove the no-longer-owned guards/ folder - this is the first resource rename through that path, so worth watching on the dedicated staging VM before promoting to main.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

_{Reviews (3): Last reviewed commit: "feat(meta-and-voc-onboarding): version 2" | Re-trigger Greptile}