[Blind-Striker]

Description

Maintainers currently have to reconstruct the dependency, service-catalog, image-test and release workflow from Git history. Add a single maintenance playbook and short discovery links from AGENTS.md and the documentation ownership map.

The playbook records the maintainer's current dependency-selection and dogfooding preferences, links five representative commits, and distinguishes catalog mappings, client-construction checks and emulator-operation evidence. It preserves the AWS Core compatibility/popularity exception and treats authenticated CI, actual consumer dependency discovery and Native AOT/framework work as future decisions or work, not completed capabilities.

Type and target

• Documentation update for the supported v2.x / AWS SDK v4 line (master).
• Related context: localstack/localstack:latest will require auth token from March 23 — docs & prerequisites update needed #51 and draft Native AOT Support via Source Generator + UnsafeAccessor Architecture #49. This documentation change does not close either item.

Validation

• 60 relative Markdown links resolve across the three changed documents.
• Five full-SHA history references exist and are ancestors of the reviewed base.
• Whitespace and change-scope checks pass; all three package/consumer README copies are unchanged and byte-identical.
• Independent evidence reproduction, cross-family contract review, and final Standards/Spec review completed.
• Builds, unit/integration/functional tests and Docker were not run: the change is documentation-only and makes no runtime verification claim.

Reviewer focus

Check the preferred maintenance order and AWS Core selection guidance, the separation of historical examples from current policy, and the image-authentication/dogfooding decision boundaries. No package, production code, workflow or credential changes are included.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None