docs: setup files and the client, shared and CI docs describe what is (#6277)

.dockerignore, .gitignore, deploy/initdb, ci-requirements.md,
client/README.md, shared/README.md and two web/scripts test names: dates,
issue/rule/spike ids and the stories behind each exclusion removed.

Corrected:
- client/README.md: the dev lane bundles its own APK; :main no longer
  exists; main bundles the recorded sidecar instead of re-deriving the
  version name. Its smoke-test step wrote a bare "v0.2.0", which the
  server rejects as a sidecar that is not JSON; it now writes the JSON
  shape, which the README documents.
- ci-requirements.md: one workflow, not four; the android lane builds no
  debug APK; main reads the recorded sidecar.
- .gitignore: CI fills client/ on every image build, not tag releases only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

shared/README.md

@@ -3,12 +3,8 @@
 `fabledsword.tokens.json` is the canonical statement of the FabledSword
 palette — the dark, light and flat cohorts in one machine-readable place.
 
-It lived under `flutter_client/shared/` until that client was deleted
-(2026-08-16). It was never Flutter-specific: the Android theme
-(`FabledSwordTokens.kt`) names it as its source of truth, and the web
-client's CSS custom properties carry the same values. It moved here rather
-than going with the client, because losing the one place all three cohorts
-are written down together would have been collateral damage.
+The Android theme (`FabledSwordTokens.kt`) names it as its source of
+truth, and the web client's CSS custom properties carry the same values.
 
 Nothing generates from it today — both clients hold their own transcription,
 so this is the reference they must agree with, not a build input. If the