[fas89]

Summary

Docs for forge-cli #735. Merge it after that PR.

• fluid bundle --env --format tgz records a retargeted overlay patch (overlay_patch_retargeted) in the bundle's manifest as source.overlayWarnings.
• fluid validate <bundle>.tgz reports it as an OVERLAY-WARNING finding, so --strict fails on it. Pipeline stage 2 runs exactly that command.
• This replaces the "a bundle does not carry it" bullet that docs: trigger.type continuous, and --strict on a retargeted overlay patch (forge-cli #734) #157 added.

Every new statement is marked (unreleased, forge-cli #735).

Page	Change
docs/cli/validate.md	The bundle bullet under "--env and environment overlays" now says a bundle carries the warning, and that contract-validation and test do not read the record. "Validating a bundle" has these additions: an "overlay warnings" item under "What it checks"; a --strict output example; the new pass and --quiet output; and OVERLAY-WARNING in the codes table.
docs/cli/bundle.md	A source.overlayWarnings row in the MANIFEST table, and one sentence noting that fluid validate reports the record, escaped.
docs/concepts/environments-and-overlays.md	The overlay_patch_retargeted bullet says a bundle carries it too.

The output block is copied from the CLI on the #735 branch.

Checks (local)

• scripts/check_cli_docs.py was run against the local forge-cli (#735 branch). All 1,333 documented fluid invocations match, and the subcommand, quickstart, contract-pin and version-sweep checks are OK. The pin check fails only because that CLI is a dev build, not 0.18.1.
• scripts/check_providers.py: OK.
• npm run docs:build, then node scripts/check-dist-links.mjs: clean (137,867 references, 242 pages).