align M2 trust and lockfile guidance

Author: LadyBluenotes

docs/cli/intent-skills.md

@@ -6,29 +6,29 @@ id: intent-skills
 `intent skills` manages `intent.lock`, the committed record of which skill-bearing sources you've approved and what their content looked like when you approved it. Four subcommands: `scan`, `diff` (read-only), `approve`, and `update` (mutating).
 
 ```bash
-npx @tanstack/intent@latest skills <scan|diff|approve|update> [source] [--json] [--all] [--yes] [--frozen] [--no-frozen]
+npx intent skills <scan|diff|approve|update> [source] [--json] [--all] [--yes] [--frozen] [--no-frozen]
 ```
 
 See [Lockfile and frozen mode](../security/lockfile) for what `intent.lock` is and what frozen mode guarantees.
 
 ## `intent skills scan`
 
 ```bash
-npx @tanstack/intent@latest skills scan [--json] [--frozen] [--no-frozen]
+npx intent skills scan [--json] [--frozen] [--no-frozen]
 ```
 
 Read-only. Discovers current skill-bearing sources, computes each source's `contentHash`, and reports drift against `intent.lock`.
 
 - No lock found: prints `No intent.lock found. Run \`intent skills approve --all\` to create one.`
 - Lock is clean: prints `intent.lock is up to date.`
 - Lock is stale: prints `intent.lock is out of date: N added, N removed, N changed.`
-- Discovered sources not in `intent.skills`: prints a count and points at `intent.skills`/`intent.exclude`
+- Discovered sources not in `intent.skills`: names each source with bounded dependency provenance when available, falls back to `provenance unknown`, and points at `intent.skills`/`intent.exclude`. Agent-mode output remains count-only.
 - `--json` prints `{ frozen, hiddenSourceCount, hasLockfile, added, removed, changed, isClean }`
 
 ## `intent skills diff`
 
 ```bash
-npx @tanstack/intent@latest skills diff [--json] [--frozen] [--no-frozen]
+npx intent skills diff [--json] [--frozen] [--no-frozen]
 ```
 
 Read-only. Same underlying computation as `scan`, but change-focused: prints only `Added:`/`Removed:`/`Changed:` sections with per-field diffs (`version`, `resolution`, `skills`, `contentHash`, `manifestHash`, `capabilities`). Unchanged sources are omitted.
@@ -44,7 +44,7 @@ Changed:
 ## `intent skills approve [source]`
 
 ```bash
-npx @tanstack/intent@latest skills approve [source] [--all] [--yes]
+npx intent skills approve [source] [--all] [--yes]
 ```
 
 Writes `intent.lock`. This is the trust decision — approving means a human reviewed this exact change.
@@ -59,7 +59,7 @@ Writes `intent.lock`. This is the trust decision — approving means a human rev
 ## `intent skills update [source]`
 
 ```bash
-npx @tanstack/intent@latest skills update [source] [--all] [--yes]
+npx intent skills update [source] [--all] [--yes]
 ```
 
 Writes `intent.lock`. It mechanically re-syncs version and resolution for matching **already-locked** entries. Changes to skills, content hashes, manifests, capabilities, declared secrets, or MCP metadata require `--yes` after reviewing `intent skills diff`.

docs/concepts/trust-model.md

@@ -21,8 +21,8 @@ Intent reads package data as files. It never imports, requires, or executes the
 
 One exception is sanctioned: in Yarn Plug'n'Play projects, Intent loads Yarn's PnP runtime (`.pnp.cjs`) to map package identities to readable locations. It loads no package entry points, bins, lifecycle scripts, or other package-provided JavaScript. An ESLint rule enforces this invariant in the discovery code.
 
-## What the allowlist does not cover yet
+## Source identity and remaining limits
 
-Matching is currently by package name. A `workspace:foo` entry and a bare `foo` entry both authorize a discovered package named `foo`, because the scanner does not yet distinguish a workspace member from a published package of the same name. This errs toward permitting a same-named package, never toward denying one you listed. A future version tightens matching once the scanner carries that signal.
+Intent matches allowlist entries by `(kind, id)`. `workspace:foo` authorizes only the workspace member named `foo`; it does not authorize an installed `npm:foo`. A bare `foo` entry is normalized to the npm source kind. Same-named workspace and npm packages remain distinct sources throughout discovery, locking, and approval.
 
 The `git:` source kind is reserved. Intent parses and validates the shape, then rejects it until a future version can pin the resolved ref and content hash. A git entry never loads silently.

docs/security/lockfile.md

@@ -73,7 +73,7 @@ Run the frozen scan in the consumer repository after dependencies and `intent.lo
 
 ```yaml
 - name: Verify approved skill sources
-  run: npx @tanstack/intent@latest skills scan --frozen
+  run: npx intent skills scan --frozen
 ```
 
 The generated `Check Skills` workflow is for library-maintainer validation and review; it does not add this consumer lockfile gate automatically.

packages/intent/README.md

@@ -121,23 +121,21 @@ The real risk with any derived artifact is staleness. `npx @tanstack/intent@late
 
 ## CLI Commands
 
-| Command                                                | Description                                         |
-| ------------------------------------------------------ | --------------------------------------------------- |
-| `npx @tanstack/intent@latest install`                  | Set up skill loading guidance in agent config files |
-| `npx @tanstack/intent@latest hooks install`            | Install hook enforcement for supported agents       |
-| `npx @tanstack/intent@latest list [--json]`            | Discover local intent-enabled packages              |
-| `npx @tanstack/intent@latest load <use>`               | Load `<package>#<skill>` SKILL.md content           |
-| `npx @tanstack/intent@latest meta`                     | List meta-skills for library maintainers            |
-| `npx @tanstack/intent@latest scaffold`                 | Print the guided skill generation prompt            |
-| `npx @tanstack/intent@latest validate [dir]`           | Validate SKILL.md files                             |
-| `npx @tanstack/intent@latest setup`                    | Copy CI templates into your repo                    |
-| `npx @tanstack/intent@latest stale [dir] [--json]`     | Check skills for version drift                      |
-| `npx @tanstack/intent@latest skills scan`              | Discover sources and diff against `intent.lock`     |
-| `npx @tanstack/intent@latest skills diff`              | Show pending `intent.lock` changes                  |
-| `npx @tanstack/intent@latest skills approve`           | Approve pending changes into `intent.lock`          |
-| `npx @tanstack/intent@latest skills update`            | Re-sync already-locked sources to installed state   |
-| `npx @tanstack/intent@latest skills stale`             | Check locked sources for content/version drift      |
-| `npx @tanstack/intent@latest skills generate-manifest` | Write a package's `skills/intent.manifest.json`     |
+| Command                                            | Description                                         |
+| -------------------------------------------------- | --------------------------------------------------- |
+| `npx @tanstack/intent@latest install`              | Set up skill loading guidance in agent config files |
+| `npx @tanstack/intent@latest hooks install`        | Install hook enforcement for supported agents       |
+| `npx @tanstack/intent@latest list [--json]`        | Discover local intent-enabled packages              |
+| `npx @tanstack/intent@latest load <use>`           | Load `<package>#<skill>` SKILL.md content           |
+| `npx @tanstack/intent@latest meta`                 | List meta-skills for library maintainers            |
+| `npx @tanstack/intent@latest scaffold`             | Print the guided skill generation prompt            |
+| `npx @tanstack/intent@latest validate [dir]`       | Validate SKILL.md files                             |
+| `npx @tanstack/intent@latest setup`                | Copy CI templates into your repo                    |
+| `npx @tanstack/intent@latest stale [dir] [--json]` | Check skills for version drift                      |
+| `npx @tanstack/intent@latest skills scan`          | Discover sources and diff against `intent.lock`     |
+| `npx @tanstack/intent@latest skills diff`          | Show pending `intent.lock` changes                  |
+| `npx @tanstack/intent@latest skills approve`       | Approve pending changes into `intent.lock`          |
+| `npx @tanstack/intent@latest skills update`        | Re-sync already-locked sources to installed state   |
 
 See [Lockfile and frozen mode](https://tanstack.com/intent/latest/docs/security/lockfile) and [`intent skills`](https://tanstack.com/intent/latest/docs/cli/intent-skills) for what `intent.lock` is and full command details.