docs(wiki): document choosing on the fleet, and fix the ORM members

The catalog page still listed the ORM group as `sequelize`, `prisma`. The bare
`prisma` addon is gone as of 5.0.0 and the members are `pg-prisma`,
`sequelize` — so the one table a reader consults before passing --packages
named an id that now errors, and omitted the one it should reach for.

Neither page mentioned that the four one-of-many choices now follow the fleet,
which is the whole point of the release: an unexplained (recommended) marker
that moves between runs reads as a bug. The VCS/CI table's bold value needed
saying differently too — it is the fallback when there is no fleet to learn
from, not a fixed default, and it is overridden non-interactively as well.

The prompt transcript is copied from an actual run against a two-service
Sequelize fleet, choice order included.

Author: Mikhus

wiki/Creating-Services.md

@@ -15,15 +15,28 @@ If omitted, `name` defaults to the current directory's name and `path` to `.`
 
 Service creation is organized around four independent, pluggable axes, so you
 can mix the tools you actually use. Each resolves via the standard precedence
-(flag → `.imqrc.json` → global config → prompt → default).
+(flag → `.imqrc.json` → global config → fleet → prompt → default).
 
-| Axis | Flag | Choices (default **bold**) |
+| Axis | Flag | Choices (fallback **bold**) |
 |---|---|---|
 | VCS host | `--vcs` | **github**, gitlab, bitbucket |
 | CI provider | `--ci` | **github-actions**, circleci, travis |
 | Container registry | `--registry` | **dockerhub**, google, aws-ecr, azure-acr |
 | Addon packages | `--packages` | (none) — see [Package Catalog](Package-Catalog) |
 
+The bold value is the fallback, not a fixed default. With nothing configured,
+`imq service create` reads the git remotes and CI config of the services that
+already sit alongside the new one and proposes what they use — a service
+joining services hosted on GitLab is going on GitLab. The bold value applies
+when there is no fleet to learn from, or when the fleet does not agree with
+itself. [Package Catalog](Package-Catalog#following-the-fleet) describes the
+analysis and its cache.
+
+A VCS host and a CI provider get picked either way — unlike an addon, choosing
+none is not an option — so this applies to non-interactive runs too. If you
+script `imq service create` inside a fleet and want a specific host or
+provider regardless of its neighbours, pass `--vcs` / `--ci` explicitly.
+
 CI choices are filtered to those compatible with the selected VCS host. See
 [Providers](Providers) for the details and tokens each one needs.
 

wiki/Package-Catalog.md

@@ -27,11 +27,13 @@ imq service packages --json   # machine-readable
 
 Packages belong to groups. **Exclusive** groups accept at most one member;
 selecting two members of the same exclusive group is rejected with an error.
+At most one, not exactly one — selecting none is a normal answer, and for a
+service that talks to no database it is the right one.
 
 | Group | Exclusive? | Members |
 |---|---|---|
 | **Tracing / APM** | yes | `opentelemetry`, `dd-trace` |
-| **ORM / database** | yes | `sequelize`, `prisma` |
+| **ORM / database** | yes | `pg-prisma`, `sequelize` |
 | **Service features** | no | `pg-cache`, `pg-pubsub`, `tag-cache`, `job`, `net`, `http-protect`, `graphql-dependency`, `type-graphql-dependency` |
 
 ## What each addon does when selected
@@ -55,6 +57,43 @@ and you will get a multi-select for the feature group and single-selects for
 the exclusive groups. Non-interactive runs use your config/flags and never
 prompt.
 
+Each exclusive list marks one member **(recommended)**, and `(none)` is always
+the first choice. The recommendation is `pg-prisma` for the ORM and
+`opentelemetry` for tracing — unless the fleet says otherwise.
+
+### Following the fleet
+
+`imq service create` looks at the directory the new service is being created
+into, and treats every sibling directory whose `package.json` depends on
+`@imqueue/rpc` as part of your fleet. If those services already agree on an
+ORM or a tracing backend, that member becomes both the preselected and the
+recommended one, with a line above the list saying why:
+
+```
+? Select ORM / database:
+  Only if the service uses a database — none is normal.
+  Preselected sequelize to match 2 services in this fleet. Moving the fleet to
+  pg-prisma is worth considering — as its own piece of work, not as part of this.
+  (none)
+  Prisma ORM + @imqueue/pg-prisma toolkit
+❯ Sequelize ORM + @imqueue/sequelize toolkit (recommended)
+```
+
+A new service in an established fleet belongs on the fleet's stack: matching
+what is already there beats taking the default.
+
+A fleet that disagrees with itself gets no proposal: with a strict majority the
+majority wins, and on a tie nothing is preselected and only the fallback is
+marked. The same analysis drives the VCS host and CI provider prompts — see
+[Creating Services](Creating-Services).
+
+Scanning is cheap but not free, so the result is cached in
+`~/.imq/var/fleet.json`, keyed by directory (`IMQ_CLI_HOME` relocates it with
+the rest of the CLI's files). The cache is invalidated when the set of sibling
+directories changes. Choosing against the analysis is taken as intent: your
+choice is recorded as an override for that directory and proposed next time,
+until a later scan agrees with it on its own.
+
 ## Extending the catalog
 
 Because the catalog is data, you can publish new addons by editing