docs(plans): refocus priority list on install friction and add bundled-plugin policy

docs/plans/2026-07-19-next-steps-code.md

@@ -118,11 +118,21 @@
 
 ## Workstream C — Catalog depth Batch 1 (Bet 1)
 
-### Task C1: Re-verify Batch 1 Nu pins in upstream Cargo.toml
+### Task C1: Re-verify priority plugin Nu pins in upstream Cargo.toml
 
 **Repo:** numan-plugins (read + notes)
 
-- [ ] For candidates `idanarye/nu_plugin_skim`, `FMotalleb/nu_plugin_clipboard`, `FMotalleb/nu_plugin_desktop_notifications`, `FMotalleb/nu_plugin_image`: record actual `nu-plugin` / `nu-protocol` versions from upstream tag.
+- [ ] For the priority candidates from the six-month strategy audit
+  (`yybit/nu_plugin_compress`, `Neuron-Mr-White/nu_plugin_terminal_qr` /
+  `FMotalleb/nu_plugin_qr_maker`, `kaathewisegit/nugins` (`nu_plugin_endecode`),
+  `JosephTLyons/nu_plugin_units`, `ArmoredPony/nu_plugin_hashes`,
+  `amtoine/nu_plugin_kdl`, `cptpiepmatz/nu-jupyter-kernel`
+  (`crates/nu_plugin_plotters`; registry id is `nu_plugin_plotters`, not the
+  jupyter kernel),
+  `devyn/nu_plugin_dbus`): record actual `nu-plugin` / `nu-protocol` versions,
+  tag status, and archive shape from each upstream tag or commit.
+- [ ] Do not include core / bundled Nu plugins or the `clip` / `clipboard`
+  native command in this catalog work; those ship with Nu (see Task D1).
 - [ ] Drop any that fail gates (pre-0.112, NO_RELEASE, broken Windows, etc.) into deferred notes in `docs/backlog.json` or intake-state.
 - [ ] Commit notes only if backlog metadata changes.
 
@@ -164,8 +174,8 @@
 
 **Repo:** numan
 
-- [ ] Define static table of core plugin ids/names (polars, formats, gstat, query, inc) in a small module (e.g. `src/core/core_plugins.rs`) or const in `search.rs`.
-- [ ] Failing test: `search polars` returns a row labeled `core (ships with Nu)` and does not offer install as a registry package.
+- [ ] Define static table of core plugin ids/names (`polars`, `formats`, `gstat`, `query`, `inc`) and the `clip` / `clipboard` native command in a small module (e.g. `src/core/core_plugins.rs`) or const in `search.rs`.
+- [ ] Failing test: `search polars` returns a row labeled `core (ships with Nu)` and does not offer install as a registry package; `search clip` is labeled `native command (ships with Nu)`.
 - [ ] `activate` path: if binary present beside Nu / on `NU_PLUGIN_DIRS`, allow register via existing activate machinery; otherwise doctor/info points to Nu channel.
 - [ ] Commit: `Detect core Nu plugins in search without owning install`
 

docs/plans/2026-07-19-six-month-strategy-audit.md

@@ -234,35 +234,67 @@ critical path until intake Stages 1–2 are boring.
 
 ---
 
-## 7. numan-plugins backlog rubric (summary)
+## 7. Priority list: third-party plugins with real install friction
+
+Keep the catalog focus on what people actually have trouble installing. Do not
+compete with plugins or commands that already ship with Nu (see §8).
+
+Priority candidates (re-verify each upstream `Cargo.toml` Nu pin and archive
+shape before promotion):
+
+- `yybit/nu_plugin_compress`: archive compression (zstd/gzip/bzip2/xz)
+- `Neuron-Mr-White/nu_plugin_terminal_qr` (or `FMotalleb/nu_plugin_qr_maker`)
+  : terminal QR codes
+- `kaathewisegit/nugins` (`nu_plugin_endecode`): extra `encode`/`decode`
+  schemes (nugins monorepo, crate at `endecode/`)
+- `JosephTLyons/nu_plugin_units`: common unit conversions
+- `ArmoredPony/nu_plugin_hashes`: extended hash functions
+- `amtoine/nu_plugin_kdl`: KDL format support
+- `cptpiepmatz/nu-jupyter-kernel` (`crates/nu_plugin_plotters`): chart
+  plotting; or `Euphrasiologist/nu_plugin_plot` if it remains the better 
+  maintained plotting option
+
+  **Note:** the registry id will be `nu_plugin_plotters` (the plotters crate 
+  from the monorepo's `crates/` directory), not `nu-jupyter-kernel`. The 
+  jupyter kernel repository is the build source, but the package being 
+  promoted is the plotters crate.
+- `devyn/nu_plugin_dbus`: Linux D-Bus interface
+
+These are not all 0.114-ready; the goal is to remove install friction through
+upstream outreach, commit-snapshot intake where there is no tag, or a
+`numan-maintained` fork under ADR 0001 when the maintainer has moved on.
+
+Gated / defer: `audio_hook` (stale Nu tag); `from_beancount`, `nuts`, `vec`
+and other pre-0.112 plugins unless a Nu-bumped tag or approved fork appears.
 
-Gates before scoring:
-
-1. `NO_RELEASE` → ask upstream for a tag (Lane 1), do not build from floating tip
-2. Tags targeting pre-0.112 Nu → defer (forces bad pins for new users)
-
-Scoring (max 14): Demand 0–4, Build cost 0–3, Nu currency 0–3, Platform 0–2,
-Maintenance 0–2.
+Source of truth for backlog data: `numan-plugins/docs/backlog.json`.
 
-**Batch 1 candidates (from strategy pass; re-verify each `Cargo.toml` Nu pin
-before promotion):** skim, clipboard, desktop_notifications, image.
+---
 
-**Gated / defer:** plot and compress (NO_RELEASE → upstream tag requests);
-dbus (Linux-only + libdbus); audio_hook (stale Nu tag).
+## 8. Official / bundled plugins and native commands (not via numan)
 
-Source of truth for backlog data: `numan-plugins/docs/backlog.json`.
+Numan does not install, distribute, or compete with the plugins and commands
+that ship with Nu or that have become experimental native commands. Those come
+from the user's Nu channel, package manager, or `cargo install nushell`, not
+from the Numan registry.
 
----
+Core / bundled plugins that ship with Nu releases:
+`nu_plugin_polars`, `nu_plugin_query`, `nu_plugin_formats`,
+`nu_plugin_gstat`, `nu_plugin_inc`.
 
-## 8. Relationship to core plugins
+Experimental native commands that replace earlier plugins:
+`clip` / `clipboard` (Nushell 0.111+; supersedes `FMotalleb/nu_plugin_clipboard`).
 
-**Detect and offer activate-only.** Do not compete on install. Do not ignore.
+**Policy for `search`, `info`, `install`:**
 
-`search polars` → row labeled `core (ships with Nu)`, install disabled,
-activation offered via same plugin-registry path. `doctor` reports
-present-and-registered / present-unregistered / absent, and for absent points
-at the user's Nu channel (or `cargo install nu_plugin_polars`) without owning
-install. Revisit install only if a major Nu channel ships without core plugins.
+- Label these as `core (ships with Nu)` for bundled plugins or `native command (ships with Nu)` for native commands.
+- `numan install` does not offer them.
+- `numan activate` may register a binary already present beside `nu` or on
+  `NU_PLUGIN_DIRS`, but it does not download or own the install.
+- `numan doctor` may report present/registered/unregistered; for absent core
+  plugins it points the user to their Nu channel (or `cargo install
+  nu_plugin_polars`, etc.) without owning the install.
+- Revisit only if a major Nu channel ships without core plugins.
 
 ---
 

docs/plans/handoff-promote-0114-plugins.md

@@ -52,7 +52,7 @@ Research → Promote to manifest → Build dispatch → Spec download → Regist
 - No existing `numan-plugins` release tag for that version (immutability)
 
 **Already researched and blocked (skip these):**
-- `PRE_0_112`: clipboard (0.110), dbus (0.101), audio_hook (0.110), vec (0.105), from_beancount (0.76), nuts (0.110)
+- `PRE_0_112`: clipboard (superseded by `clip` native command; not a numan candidate), dbus (0.101), audio_hook (0.110), vec (0.105), from_beancount (0.76), nuts (0.110)
 - `PROMOTED` (skip; already shipped): skim, highlight, desktop_notifications, image, port_extension, prometheus; Wave 1 Nu 0.114 (`highlight`, `port_extension`, `regex`, `file`, `hcl`); Wave 2 Nu 0.114 (`ulid`, `jwalk`, `strutils`, `query_git`, `nutext`). Use this fixed name list for this revision (do not re-derive Wave membership by intersecting or unioning `backlog.json` with `manifest.json` `active[]`).
 - `nu_plugin_bigquery`: nu-plugin 0.112.2 (eligible minor) but needs Google creds for lifecycle proof — skip unless you can prove without credentials