next recommends reindex on an empty workspace, and points at advisors instead of resolving verbs

[jasonssdev]

Priority: P3. Two defects in the same priority ladder.

a) The bootstrap state is not a rung

Freshly created workspace, 0 sources, 0 concepts:

$ openkos next
Run: openkos reindex
Dense retrieval and candidate edges are unavailable -- the vector index is missing or empty.

Reindexing an empty bundle is meaningless — there is nothing to embed. The
correct advice is to ingest the first source.

_tier_missing_vector_index is declared "Rank 1: ranked first because it
BLOCKS...". That holds for a bundle with content; in an empty one the missing
index is not a problem to solve, it is the expected consequence of having
nothing.

status has the same defect from the same root: it reports "Needs attention:
Dense retrieval and candidate edges unavailable" in a brand-new workspace.

This is the mirror image of the earlier bug (#186): it used to say "nothing
needs attention" while things were pending; now it claims something is pending
when nothing is. The verb designed to guide new users fails precisely for new
users.

b) It points at advisors, not at the resolving action

With a duplicate group pending:

$ openkos next
Run: openkos duplicates

duplicates is read-only: it merely displays the group again. The resolving
action is merge (or curate). next also never mentions curate, which
leaves the consolidated loop as undiscoverable as the individual advisors.