docs: fix every documented make target that does not exist
The tmi repo swept this class in 2efc4c7c but stopped at its own boundary, so
the wiki kept 18 targets that no longer resolve. Same method: diff every
`make <target>` referenced in *.md against the real list from `make -qp`,
filtering prose hits ("make certain choices", "make threat identification
easier", "the make target").
Renames, all verified against the Makefile rather than guessed:
build-container-db -> build-db
build-container-redis -> build-redis-container
build-container-tmi -> build-server-container
build-containers-all -> build-all
containers-security-scan -> scan-containers
oauth-stub-stop -> stop-oauth-stub
start-postgres -> start-database
db-ping -> check-database
db-reset -> reset-database
restart -> dev-restart
Four needed more than a rename, because the target they named never had a
one-to-one replacement:
- `build-container-oracle` was described as "the dedicated Oracle container
target". There isn't one. Oracle support comes from the OCI build, which
uses Oracle Linux 9 with Instant Client -- build-app-oci.
- `build-containers-multiarch{,-local}` don't exist either; multi-arch is the
build script's `--arch` flag. Pointed at build-app-aws (the target that page
is actually deploying to) and build-app for the local case.
- `check-grype` implied a preflight target. Grype is invoked by `--scan`
inside the build scripts, so the line now says scan-containers needs Grype
and Syft installed instead of pretending a check target exists.
- `build-wstest` claimed a separate build step. scripts/run-wstest.py runs
`go build -o wstest` on every invocation, so `make wstest` already builds;
the standalone step was never real. `clean-wstest` -> clean-process, which
is what actually stops the harness ("Stop OAuth stub and wstest processes").
Two blocks ended up invoking scan-containers twice, since the old scan and
report targets both map to it; collapsed with a note that it writes to
security-reports/ itself.
`make start-server` in Local-Development-Cluster.md is deliberately left: that
page documents the target as retired, so the reference is correct prose.
Every `make <target>` reference in the wiki now resolves.
docs: rename deprecated dev make targets to dev-* (start-dev->dev-up, restart-dev->dev-restart, stop-dev->dev-down)
Follow-up to the dev-environment rationalization (tmi #478). The wiki dev-onramp
and operations pages still referenced the deprecated start-dev/restart-dev/stop-dev
target names (kept as aliases for one release). Update them to the canonical
dev-up/dev-restart/dev-down names across 8 pages.
docs(dev): cluster-based start-dev contributor onramp (#447)
Add a dedicated "Local Development Cluster" wiki page documenting the new
cluster-based dev workflow delivered by #442, and update the stale
host-process descriptions across the contributor onramp pages.
New page covers: prereqs (kubectl/docker + kind or k3s, optional tilt);
kind vs k3s cluster setup incl. the k3s registries.yaml mirror snippet and
the prod-context guard; database config as the developer's responsibility
(localhost -> host.docker.internal/node-IP gotcha, cloud Postgres, and
OCI ADB via DB=oracle + TMI_ORACLE_WALLET_ZIP); the command reference
(dev-cluster-up/down, start-dev [DB=oracle], restart-dev, stop-dev,
tilt-up/down); the optional Postgres-only Tilt fast loop; and a breaking-
change callout that the host-process dev path is retired.
Updated Getting-Started-with-Development, Configuring-Local-Development,
and Contributing to replace the old "start-dev brings up containers +
host server" descriptions with the cluster model and cross-links; added
the new page to the sidebar.
Closes #447
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
docs(config): revamp configuration documentation for the two-category model
Rewrites the configuration docs around the post-#415 model (Bootstrap vs
Operational categories, plus the still-live env > file > db precedence):
- Configuration-Model (new): the concept hub — the two categories, how values
are resolved (categories decide WHERE a value may live; precedence decides
WHICH wins), vault://env://file:// secret references, the secret-vs-bootstrap
orthogonality with Timmy as the worked example, hot vs static, visibility,
the three bootstrap-only config files, required settings.
- Configuring-Local-Development (new): dev setup, config-example -> -development,
TMI_* overrides, the OAuth stub + login_hint, operational settings in dev.
- Bootstrapping-Production (new): the bootstrap-only skeleton, secret wiring +
three-phase resolution, first-run DB seeding, --import-legacy migration,
platform notes (OCI/ADB, Heroku, Kubernetes), worker bootstrap, a checklist.
- Managing-Operational-Settings (new, replaces Configuration-Management):
/admin/settings CRUD + reencrypt, the source field + 409-on-config-controlled,
runtime reconfiguration of Timmy/content sources, dbtool import flags.
- Configuration-Reference (rewritten): generated from the classification
registry via 'make generate-config-docs' — drift-guarded, never hand-edited.
- Configuration-Management and Config-Migration-Guide retired to redirect stubs.
- Sidebar updated; Content-Extractors page cross-linked.
Pairs with the dev/1.4.0 generator (EnvVar field + cmd/genconfigdocs).