Problem
The repo root contains 10 markdown files totaling ~3,200 lines. Most are process artifacts (release guides, migration post-mortems, AI-development rules) that bloat the repo without informing contributors.
The README documents a workflow that drops short-lived AWS STS credentials in the repo root as credentials.json. The file is .gitignored (correctly), but the pattern depends on a single line of defense across an evolving file and instructs forks to repeat the pattern.
Acceptance criteria
Notes
Independent of the API refactor.
Problem
The repo root contains 10 markdown files totaling ~3,200 lines. Most are process artifacts (release guides, migration post-mortems, AI-development rules) that bloat the repo without informing contributors.
The README documents a workflow that drops short-lived AWS STS credentials in the repo root as
credentials.json. The file is.gitignored (correctly), but the pattern depends on a single line of defense across an evolving file and instructs forks to repeat the pattern.Acceptance criteria
MIGRATION_SUMMARY.md,RELEASE.md,RELEASE_INSTRUCTIONS.md,RELEASE_QUICK_REFERENCE.md,TODO.md,AI_ASSISTED_DEVELOPMENT_RULES.md,S3PROXY_DOCKER_ADAPTATION_GUIDE.md,load-test-results-*.json.MAINTENANCE.mdandPERFORMANCE.mdcontent into README sections ordocs/(decide based on length).~/.s3proxy/credentials.json, bind-mount from there." Keep the file.gitignored.credentials.jsonitself — it's intentional dev tooling for short-lived Docker testing. Leave it alone.Notes
Independent of the API refactor.