docs(router): reframe as a structured task resolver (proposal-only)

WP-5 of the ECC execution plan.

docs/SKILL-ROUTER.md: retitled "Structured task resolver (proposal-only)".
The opening now states plainly that the hook suggests <=3 skills per prompt
and does not select, activate, switch profiles, or implement affaan-m#3037's
`routed` disposition. Added a "Relationship to context profiles" section
quoting affaan-m#3037's own contract verbatim (scripts/lib/context-profiles.js:
"Selection modes are recorded intent; task routing and automatic switching
are not implemented.") and its design doc's lane-table entry for this PR
("Future structured task resolver; selectionMode: 'auto' alone implements
none of this"), then states input (the carrier's catalog, which after the
carrier binds to the compiler is the compiler's routedIds) and output
(suggestions only, no disposition changed).

docs/PLUGIN-PROFILES.md: added a short cross-reference to the router under
"The ecc-catalog Skill and On-Demand Content" -- it did not mention the
router/resolver at all before this change (verified by grep; a discrepancy
from the plan's assumption that it already did, recorded here since the
correct fix is the same either way: add the reference).

The header-comment reframing for scripts/hooks/skill-router.js and
scripts/lib/skill-router.js landed in the previous commit (touches the
same regions as that commit's JSDoc additions).

tests/hooks/skill-router.test.js already carries the required "suggestion
resolver output is suggestion-only" test (previous commit); it passed
immediately (GREEN on first run), meaning it is a pin, not a fix -- the
router never emitted selection/activation language and was already <=4
lines. See evidence/WP-5-pr-bodies.md and
evidence/WP-5-rename-inventory.md for the drafted-but-unposted PR bodies
and the task-resolver rename inventory (not applied; gated on a user
decision per the plan).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MLu1Dhxs54ndeS3CTvSHSC

Author: montjeffrey

docs/PLUGIN-PROFILES.md

@@ -368,6 +368,12 @@ needs a skill outside the profile, the agent reads it from inside the plugin.
 Because on-demand content is copied at generation time, a carrier reflects the
 catalog as it was when generated. Regenerate after updating ECC.
 
+An optional, opt-in **task resolver (suggestion hook)** can shorten the
+distance between a prompt and an on-demand entry: it scores the prompt
+against the carrier's catalog and suggests up to three matching skills by
+path. It never installs, activates, or switches anything — see
+[docs/SKILL-ROUTER.md](SKILL-ROUTER.md).
+
 ## Custom Selections
 
 `plan` and `generate` accept the same selection vocabulary as the installer:

docs/SKILL-ROUTER.md

@@ -1,13 +1,21 @@
-# Skill Router (opt-in)
+# Structured task resolver (proposal-only)
 
-A discovery affordance inside an already-selected carrier. It does not decide
-what a session can do; the carrier already did that.
+A `UserPromptSubmit` hook that **suggests** up to three skills per prompt into
+context. It does not select, activate, or switch profiles, and it does not
+implement the `routed` disposition #3037's context-profile compiler assigns
+to `routedIds` — that contract stays exactly what it says: "recorded intent;
+task routing and automatic switching are not implemented." This hook proposes
+candidates for a human or the model to act on; it commits to nothing on its
+own.
 
-A `UserPromptSubmit` hook scores each prompt against the catalog the carrier
-already holds and names up to three skills that look relevant. It **suggests;
-it never loads**. The model reads a skill because it decided to, from a path
-inside the plugin — the router only shortens the distance between "I need
-something" and "it is at `on-demand/<skill>/SKILL.md`".
+It is a discovery affordance inside an already-selected carrier. It does not
+decide what a session can do; the carrier already did that.
+
+The hook scores each prompt against the catalog the carrier already holds and
+names up to three skills that look relevant. It **suggests; it never loads**.
+The model reads a skill because it decided to, from a path inside the plugin
+— the resolver only shortens the distance between "I need something" and "it
+is at `on-demand/<skill>/SKILL.md`".
 
 That boundary is what makes the feature small enough to be worth having:
 
@@ -25,6 +33,36 @@ That boundary is what makes the feature small enough to be worth having:
 The router changes what the model sees on every matching prompt, so it is a
 separate behavioral feature from profile carriers and is **off by default**.
 
+## Relationship to context profiles
+
+#3037's context-profile compiler (`scripts/lib/context-profiles.js`) assigns
+every catalog skill a disposition: `selected` (eager), `routed` (recorded as
+a candidate but not shipped), or `excluded`. Its own source is explicit about
+what that disposition does and does not mean:
+
+> Selection modes are recorded intent; task routing and automatic switching
+> are not implemented.
+
+and the design doc's own lane table names this hook directly:
+
+> [#2945] Task routing and automatic-selection proposals — Future structured
+> task resolver; `selectionMode: "auto"` alone implements none of this
+
+This hook is that "future structured task resolver," landing as a proposal
+step, not the routing #3037 explicitly does not implement:
+
+- **Input**: the carrier's catalog — after the carrier binds to the compiler
+  (WP-3), that catalog *is* the compiler's `routedIds` (plus the eagerly
+  selected skills), copied into `on-demand/` and listed in the receipt.
+- **Output**: suggestions only, printed to stdout for the model to read. No
+  disposition is changed, no profile is switched, no skill is activated —
+  the compiler's `selected`/`routed`/`excluded` labels for a session are
+  exactly what they were before this hook ran.
+
+Closing the gap between "recorded intent" and actual task routing — a
+disposition that changes based on what this hook suggests — is future work,
+not something landed here.
+
 ## Enabling
 
 ```bash