Fix the uninstall path, and stop the landing page sending users to a source build

A second cold read-the-site-and-install run found three things.

The documented uninstall left a running, network-exposed database behind.
Verified on a clean container: after `apt remove --autoremove documentdb
documentdb-18`, apt reports `Package 'documentdb' is not installed` (the meta
is never pulled by installing `documentdb-18`), `postgresql-18-documentdb`
is still `ii` installed with its .so and .control files on disk, the other
four packages are left in `rc` state with their config, and -- because
package removal does not stop a service -- the gateway is still listening on
0.0.0.0:10260 and still answering queries. `apt purge --autoremove
documentdb-18 postgresql-18-documentdb` leaves nothing behind, so document
that, and tell people to stop the stack first.

The landing page told full-stack users to build the gateway from source: ""Linux
packages install the PostgreSQL extension; the Linux package guide adds the
extra source-gateway steps needed when you want a host install that still
exposes a MongoDB-compatible endpoint."" On Ubuntu 24.04 and RHEL 9 the gateway
is packaged and `documentdb-setup` starts it, so that sends people off to
build a Rust project they do not need.

The connection URI had no note about percent-encoding, so a password containing
`@` silently misparses. Add the note and the flag-based form that avoids the
problem entirely.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 8df9084a-ccaf-432c-b015-2ccd8893a9d8

Author: GuanzhouSong

PACKAGE-INSTALL.md

@@ -102,6 +102,14 @@ mongosh 'mongodb://admin:<password>@127.0.0.1:10260/mydb?tls=true&tlsAllowInvali
         --eval 'db.runCommand({ping: 1})'
 ```
 
+If the password contains `@`, `:`, `/` or other reserved characters it must be percent-encoded
+in the URI (`@` becomes `%40`). To avoid encoding entirely, pass the credentials as flags:
+
+```bash
+mongosh localhost:10260 -u admin -p --authenticationMechanism SCRAM-SHA-256 \
+        --tls --tlsAllowInvalidCertificates --eval 'db.runCommand({ping: 1})'
+```
+
 A first database and collection are created on first write:
 
 ```javascript
@@ -163,16 +171,22 @@ instead; re-run `documentdb-setup` to restart it.
 **Remove or reset:**
 
 ```bash
+# Stop the stack first — package removal deletes files but does not stop a
+# running gateway. On systemd hosts:
+sudo systemctl stop documentdb-local@18.target
+# Without systemd the wizard started the gateway directly; kill that process.
+
 sudo documentdb-setup --restore                              # detach the managed integration
 sudo documentdb-local-reset --pg-version 18 --confirm-destroy # DESTROYS the data directory
 
-# Removing the meta package alone leaves the stack installed — it only owns the
-# dependency on the per-major package. Remove that too, and let autoremove reap
-# documentdb-common, documentdb-gateway and documentdb-postgresql-tools.
-sudo apt remove --autoremove documentdb documentdb-18
-sudo dnf remove documentdb documentdb-18 && sudo dnf autoremove
+# Name the package you installed AND the extension: autoremove does not reap
+# postgresql-18-documentdb, and `remove` would leave its config behind.
+sudo apt purge --autoremove documentdb-18 postgresql-18-documentdb
+sudo dnf remove documentdb-18 postgresql18-documentdb && sudo dnf autoremove
 ```
 
+If you installed the `documentdb` meta package rather than `documentdb-18`, name that instead.
+
 ### What the packages are
 
 | Package | Role |

app/packages/page.tsx

@@ -498,7 +498,10 @@ export default function PackagesPage() {
             </summary>
             <div className="mt-4 space-y-4">
               <p className="text-sm text-gray-400">
-                Use the commands below to discover available versions before pinning. Replace{" "}
+                Use the commands below to discover available versions before pinning. The
+                examples name the extension package; substitute{" "}
+                <code className="text-gray-300">{selectedPackageNames}</code> to pin the package
+                your selected target actually installs. Replace{" "}
                 <code className="text-gray-300">&lt;VERSION&gt;</code> with the version string
                 shown by the list command (e.g.{" "}
                 <code className="text-gray-300">{repoAptVersionExample}</code> for APT,{" "}
@@ -604,10 +607,12 @@ export default function PackagesPage() {
               3. Connect and try it
             </h2>
             <p className="text-sm leading-6 text-gray-400">
-              Docker starts a gateway-backed local endpoint on port 10260. Linux packages install
-              the PostgreSQL extension; the Linux package guide adds the extra source-gateway
-              steps needed when you want a host install that still exposes a MongoDB-compatible
-              endpoint.
+              Docker starts a gateway-backed local endpoint on port 10260. On Ubuntu 24.04 and
+              RHEL-compatible 9 the packages give you the same thing: install, then run{" "}
+              <code className="text-gray-300">sudo documentdb-setup --admin-user admin</code>,
+              which creates the database and starts the gateway. On the extension-only
+              distributions the Linux package guide covers the additional source-gateway steps
+              needed to expose a MongoDB-compatible endpoint.
             </p>
           </div>
 

app/services/articleService.ts

@@ -163,6 +163,13 @@ mongosh 'mongodb://admin:<PASSWORD>@127.0.0.1:10260/mydb?tls=true&tlsAllowInvali
         --eval 'db.runCommand({ping: 1})'
 \`\`\`
 
+If the password contains \`@\`, \`:\`, \`/\` or other reserved characters it must be percent-encoded in the URI (\`@\` becomes \`%40\`), otherwise the URI misparses. To avoid encoding entirely, pass the credentials as flags instead:
+
+\`\`\`bash
+mongosh localhost:10260 -u admin -p --authenticationMechanism SCRAM-SHA-256 \\
+        --tls --tlsAllowInvalidCertificates --eval 'db.runCommand({ping: 1})'
+\`\`\`
+
 A database and collection are created on first write:
 
 \`\`\`javascript
@@ -211,16 +218,22 @@ On hosts without systemd the wizard starts the gateway directly; re-run \`docume
 Remove or reset:
 
 \`\`\`bash
+# Stop the stack first — package removal deletes files but does not stop a
+# running gateway. On systemd hosts:
+sudo systemctl stop documentdb-local@18.target
+# Without systemd the wizard started the gateway directly; kill that process.
+
 sudo documentdb-setup --restore                               # detach the managed integration
 sudo documentdb-local-reset --pg-version 18 --confirm-destroy  # DESTROYS the data directory
 
-# Removing the meta package alone leaves the stack installed - it only owns the
-# dependency on the per-major package. Remove that too and let autoremove reap
-# the shared payload.
-sudo apt remove --autoremove documentdb documentdb-18
-sudo dnf remove documentdb documentdb-18 && sudo dnf autoremove
+# Name the package you installed AND the extension: autoremove does not reap
+# postgresql-18-documentdb, and \`remove\` would leave config behind.
+sudo apt purge --autoremove documentdb-18 postgresql-18-documentdb
+sudo dnf remove documentdb-18 postgresql18-documentdb && sudo dnf autoremove
 \`\`\`
 
+(If you installed the \`documentdb\` meta package rather than \`documentdb-18\`, name that instead.)
+
 ## Upgrading
 
 A package upgrade only replaces files. Afterwards, update the extensions in every database that has DocumentDB installed: