docs(release): clarify maintenance runbooks

- Remove duplicated metadata update guidance from the README
- Clarify when to run metadata freshness checks manually
- Replace ambiguous validation wording with wrapper script commands

Author: iziz

README.md

@@ -407,34 +407,18 @@ swift scripts/updateMetadata.swift <libphonenumber-version>
 
 Use `--only main,geocoding` or `--skip carrier,timezones` when the release intentionally covers only specific metadata families. See the [release runbook](docs/RELEASE_RUNBOOK.md) for the full release flow.
 
-### Main And Short-Number Metadata
+### Direct Metadata Scripts
 
-Run the metadata generator from the `scripts` directory:
-
-```bash
-cd scripts
-./metadataGenerator.swift <libphonenumber-version> --pretty
-```
-
-This downloads metadata from Google's libphonenumber repository, updates the generated Objective-C metadata files from compact JSON, and writes pretty-printed `generatedJSON` files for review.
-
-### Geocoding Metadata
-
-Generate SQLite geocoding databases with the command-line updater:
+Use the individual generators only when debugging or intentionally updating one metadata family outside the normal release flow:
 
 ```bash
+swift scripts/metadataGenerator.swift <libphonenumber-version> --pretty
 swift scripts/updateGeocodingMetadata.swift <libphonenumber-version> --replace-bundle
+swift scripts/updateCarrierMetadata.swift <libphonenumber-version> --replace-bundle
+swift scripts/updateTimeZonesMetadata.swift <libphonenumber-version> --replace-bundle
 ```
 
-Examples:
-
-```bash
-swift scripts/updateGeocodingMetadata.swift 9.0.29 --replace-bundle
-swift scripts/updateGeocodingMetadata.swift master --output /tmp/geocoding
-swift scripts/updateGeocodingMetadata.swift --source /tmp/libphonenumber --output /tmp/geocoding
-```
-
-Use `--output` to inspect generated databases before replacing the checked-in bundle. Use `--source` when you already have a local Google libphonenumber checkout or an extracted `resources/geocoding` directory.
+Use `--output` to inspect generated review artifacts before replacing checked-in bundles. Use `--source` with the individual scripts when you already have a local Google libphonenumber checkout or extracted resource directory.
 
 ## Validation
 

docs/RELEASE_RUNBOOK.md

@@ -115,7 +115,7 @@ Run CocoaPods lint for every shipped podspec when packaging, dependency, or rele
 swift scripts/publishPodspecs.swift --lint
 ```
 
-Re-run freshness after the metadata update to confirm the checked-in metadata matches the selected upstream ref:
+The all-in-one updater runs the freshness check after checked-in updates. Run it manually only if you used `--skip-freshness-check` or individual generator scripts:
 
 ```bash
 swift scripts/checkMetadataFreshness.swift --current-ref <metadata-ref> --output .build/metadata-freshness

docs/TESTING.md

@@ -94,16 +94,16 @@ For a small implementation or test-only change:
 For metadata updates:
 
 - Use a patch version for metadata-only releases. Use a minor version only when the change also adds public API, new modules, or additive behavior beyond metadata freshness.
-- `swift scripts/checkMetadataFreshness.swift --current-ref <metadata-ref> --output .build/metadata-freshness`
+- `swift scripts/checkMetadataFreshness.swift --output .build/metadata-freshness`
+- `swift scripts/updateMetadata.swift <metadata-ref> --dry-run`
 - `swift scripts/checkUpstreamTestParity.swift --upstream-ref <metadata-ref>`
 - `swift scripts/checkUpstreamAPIParity.swift --upstream-ref <metadata-ref>`
-- `swift scripts/updateMetadata.swift <metadata-ref> --dry-run`
 - `scripts/testGeocodingMetadataUpdater.sh` if the geocoding updater changed.
 - Update `docs/METADATA_UPDATE_LOG.md` with the upstream comparison and validation results.
 - `swift test`
 - `LC_ALL=ko_KR.UTF-8 LANG=ko_KR.UTF-8 swift test`
 - `swift build -c release`
-- all three Xcode schemes
+- `swift scripts/testXcodeSchemes.swift`
 - `git diff --check`
 
 For public API or parser/formatter behavior changes: