nodus-consumerlisted

# Nodus Consumer Help the user consume agent packages with Nodus in a predictable way. Treat `nodus.toml`, `nodus.lock`, and the managed runtime roots as the source of truth. Assume some users may have little or no coding background. In those cases, optimize for plain language, safe defaults, and doing the work for them. ## Workflow 1. Identify the repo role. - If the repo is consuming packages, work from the root `nodus.toml`. - If the user points at a package repo directly, use `nodus info` first before changing anything. 2. Switch into plain-language mode when needed. - Explain Nodus as: "a tool that installs and keeps AI helper packages in sync for this repo." - Explain an adapter as: "which AI app should receive the package, such as Codex or Claude." - Avoid unexplained terms like discovery roots, managed outputs, or manifest invariants unless they are necessary to solve the task. 3. Pick the dependency source and ref. - Prefer a Git tag for released packages. - Use `branch` only when the package intentionally tracks a moving head. - Use `revision` for exact reproducibility. - Use `path` for local development checkouts. 4. Choose the simplest useful install. - Default to the full package unless the user clearly needs only `skills`, `agents`, `rules`, or `commands`. - If the user does not know which components they need, omit `components`. - If the user is a beginner who just wants a one-stop setup and does not name anothe