[LeeroyHannigan]

What changed

This branch fixes the four documentation problems #663 lists. The quick start
problem also appears in pages that #523 removes; those pages are left to that
PR and named under the quick start item.

README quick start

The quick start ran aws dynamodb list-tables right after serve. Requests
must be signed with an access key this server issued, and nothing in the quick
start created one, so the AWS CLI stopped with Unable to locate credentials
(exit 255). A reader who already has AWS credentials configured gets
UnrecognizedClientException instead, because the server does not know those
keys.

The quick start now reads the default account's ID with
extenddb manage list-accounts, because init prints the admin password but
not the account ID. It then creates an IAM user, attaches a policy that allows
dynamodb:*, creates an access key for the user with extenddb manage, and
sets AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to the access_key_id
and secret_access_key that create-access-key prints. These are the admin
commands docs/local-dev-docker-compose.md already uses.

The Linux and macOS install manuals and the MongoDB setup page also run
list-tables with no key. #523 removes those pages, and its
docs/install-from-source.md creates the key before the first request.

Monitoring commands

/metrics requires an admin user's name and password as HTTP Basic auth and
answers 401 Missing Authorization header without them. The curl commands
in the README, the admin guide and the event ticketing demo sent none. They now
pass -u admin:<password> (the demo reads the EXTENDDB_ADMIN_PASSWORD it
exports in step 3), and the deployment guide's monitoring checklist says the
poller needs the admin credentials. Step 13 of the demo also wrote the port as
**18443** inside a code block. curl refuses that URL (exit 3), so the
asterisks are removed from both URLs in that step.

/health, extenddb status and extenddb healthcheck work as written and are
unchanged.

Backend count

The storage design's status line ("PostgreSQL is the only supported backend")
named PostgreSQL as the only backend. It now names the four backends in
crates/: PostgreSQL, SQLite, MongoDB and Cassandra. No support tiers are
added; #662 covers those.

This branch first made the same correction to the README crate list and the
architecture guide overview ("currently PostgreSQL"). #412 corrected both on
main before this branch was rebased, so the rebased commit keeps main's
text there and no longer changes docs/manuals/01-architecture-guide.md.

Design index

docs/design/README.md linked version 2.0 of the auth design
(05-component-auth.md). Version 3 (05-component-auth-v3.md) states that it
supersedes version 2.0. The index row now links version 3 and links version 2.0
as superseded.

How it was measured

The measurements ran on a release build of main at 817b240 (cargo build --release -p extenddb, the PostgreSQL backend) against PostgreSQL 16 in a
container, in a clean HOME and an environment with no AWS settings. init
was given the container's host and port, and the server listened on port 15740
in place of 18443; the other commands ran as the docs write them.

Command	Before	After
quick start aws dynamodb list-tables	Unable to locate credentials, exit 255	{"TableNames": []}, exit 0
curl ... /metrics (README, admin guide)	401 Missing Authorization header	200 with the JSON metrics
demo step 13, curl ... | python3 -m json.tool	curl exit 3	exit 0
demo step 23, curl ... | python3 -c ...	401, then JSONDecodeError	exit 0, summary printed
curl ... /health	200	unchanged

The corrected quick start then ran end to end in a fresh HOME against a fresh
database, and list-tables returned an empty table list. The AWS CLI on the
build host is 1.18.147; the docs name version 2, which was not run.

After the rebase onto f49c5f823, the quick start ran again on 2026-10-31,
from init to list-tables, with a SQLite build of 1c0523c9
(init --backend sqlite). That commit
has the same init and extenddb manage code as f49c5f823. init printed
the admin password and no account ID, list-accounts printed the default
account, and create-user, put-user-policy and create-access-key exited 0.
The quick start's last command,
aws dynamodb list-tables --endpoint-url https://127.0.0.1:18443 --region us-east-1,
returned {"TableNames": []} with exit 0.

Testing

• No conflict markers in the tree.
• The 48 relative links in the six changed files resolve.
• tests/cli/test-doc-consistency.sh reports the same 110 failures on main
  (f49c5f823) and on this branch.
• Before the rebase, cargo test --release -p extenddb-storage-postgres --test doc_version_literals passed (3 tests). The workspace tests in CI run it on
  this branch.

The change is documentation only. No Rust, workflow or test file changes.

Overlap with the open docs PRs

After the rebase this branch no longer changes the architecture guide. Its
commit applies without conflicts on top of the current heads of #491, #523,
#530 and #666.

Refs #663