[fas89]

Summary

Docs for forge-cli #737; merge after it. Builds on #157 (merged).

• A continuous trigger on a build forge-cli runs as a batch run is a fluid validate warning, so --strict fails: dbt, dbt-<adapter>, python or no engine (the runner refuses the trigger by name), and inline SQL on local DuckDB or Snowflake or a duckdb / airbyte / meltano / dlt acquisition (runs only when fluid apply runs builds).
• The python runner takes every build no other runner does (no engine, a local spark / glue / custom script, an ingestion engine without pattern: acquisition), so those are warned too. A continuous spark / glue / custom build that names a runtime.platform other than local, or inline SQL on a platform with no embedded-SQL executor, gets no warning, and fluid apply --mode amend-and-build leaves it to that platform, as it does a Flink job.
• fluid scaffold-composer writes no DAG for a contract whose every build is continuous or runs outside forge-cli, unless it declares orchestration.tasks, and names a DAG it wrote before. Its cron is the first one of a build a scheduler starts.

Every new statement is marked (unreleased, forge-cli #737). The sentence #157 added about the gaps ("The dbt and python runners refuse it (Unknown trigger type: continuous) ... still writes its nightly DAG") is replaced.

Page	Change
docs/cli/validate.md	New section A continuous trigger on a batch build: the warning as printed, exit codes, a table of what forge-cli does with each kind of continuous build, the fluid apply line for one it leaves to its platform.
docs/concepts/builds-exposes-bindings.md	The Where it belongs bullet of Continuous builds states the new behaviour and links the section above.
docs/cli/scaffold-composer.md	The cron comes from a build a scheduler starts; no DAG for an all-unscheduled contract (with the orchestration.tasks exception), and the old-DAG message.

npm run docs:build passed locally on these pages (no broken internal links).