docs: the contributor guide asked for SQLite headers and a server you don't need

[skyoo2003]

Summary

Four statements in the docs contradicted the source files they describe — a prerequisite that stopped being true at v1.0.0, two claims about how the tests run, and a frontend that lives in another repository. All four are corrected against the source, plus three gaps filled from the same files.

Related Issue

Refs #128

Changes

Corrections — each verified against the file it describes:

• contributing.md: SQLite3 development libraries listed as a prerequisite. Stale since v1.0.0, which made the driver pure Go precisely so that no build needs a C toolchain or SQLite headers (fix: released binaries could not start — swap SQLite driver to pure Go #128). docker/Dockerfile:7 says as much in a comment. Removed, and replaced with a note on why nothing needs one.
• contributing.md: "make test runs all Go tests with CGO enabled (required for SQLite)". Makefile:8 is CGO_ENABLED=0, as are ci.yml, compat.yml, release.yml, smithy-sync.yml and every Go pre-commit hook. Corrected, with the reason it is 0 (it is the mode .goreleaser.yaml publishes in).
• contributing.md: compatibility tests "require a running DevCloud instance". They do not — the devcloud_server session fixture (tests/compatibility/conftest.py:104) starts one via go run on a free port, against a temp data dir it removes afterwards. Corrected, and the three env vars that override that behaviour (DEVCLOUD_EXTERNAL, DEVCLOUD_BIN, DEVCLOUD_PORT) are now documented — DEVCLOUD_BIN in particular is a large speedup and was discoverable only by reading the fixture.
• getting-started.md: Docker Compose "starts a Next.js dev server on port 3000 with hot-reload". docker/docker-compose.yml declares one service. The dashboard UI moved to a separate repository — getting-started.md already said so 50 lines further down. Rewritten to describe what the file actually starts, including that it runs a six-service subset via DEVCLOUD_SERVICES.

Gaps filled from the same sources:

• A Make target table generated from the Makefile, marked <!-- AUTO-GENERATED -->. clean, changelog and stats appeared in no document.
• A pre-commit and linting section. .pre-commit-config.yaml was undocumented, and golangci-lint was named in the root CONTRIBUTING.md and the PR checklist but never in the contributor guide — including the fact that pre-commit does not run it, so CI is the first place it fires.
• GET /devcloud/api/fidelity and GET /devcloud/api/unrouted in the admin API list. Both are registered in internal/admin/api.go:42-43; getting-started.md listed only the other three.

Files Changed

File	Type	Change
docs/contributing.md	Modified	3 corrections, Make target table, pre-commit/lint section
docs/getting-started.md	Modified	Compose section rewritten, 2 admin routes added

No source, test, or config files are touched.

Test Plan

Documentation only — nothing to execute. Each claim was checked against its source rather than reasoned about:

• Env vars: grep -rn 'os.Getenv' internal/ cmd/ returns exactly the three documented in configuration.md — that table was already correct and is unchanged.
• Make targets: comm of every target in the Makefile against every make <target> in contributing.md — no target is now undocumented.
• Residual claims: a repo-wide grep for CGO.{0,12}enabl, brew install sqlite, Next.js, port 3000 returns nothing stale. The remaining hits are in changes/v0.1.0.md and changes/v1.0.0.md, which are historical release notes and correct as history.
• Every relative link and heading anchor added here resolves.
• Pre-commit passed on the commit.

docs/configuration.md was reviewed against internal/config/config.go and needed no change.

Checklist

• Self-reviewed the code
• Added/updated tests — N/A, documentation only
• Lint/format passes (golangci-lint run) — no Go files changed; pre-commit passed
• Updated documentation (if applicable) — this PR is the documentation update
• Added a Changie changelog fragment for user-facing changes — N/A per the template, docs only