when choudoufu #894 ships: drop the two acceptance gates, the ops-page caveat, and move the version floor

[lex00]

INTENTIUS/choudoufu#894 (live-plan -json unreachable on a configuration that names its own estate, and progress mixed into stdout ahead of the document) is being fixed upstream in choudoufu PR #915. When that merges and a release carries it, five things in this repository come back.

The upstream fix confirms both halves as filed: the document becomes reachable on a live block and on an estate.chdf.hcl sidecar, and stdout is kept to the document (the progress was the plan graph's own views.UiHook writing through streams.Stdout, not the discovery heartbeat, which was already a no-op).

What to do when a choudoufu release contains PR #915:

1. lexicons/terraform/src/composites/terraform-adopt-op.acceptance.test.ts: flip CHOUDOUFU_894_OPEN to false and let the adoption round trip run against the emulator for real.
2. lexicons/terraform/src/op/activities/choudoufu.acceptance.test.ts: drop the same gate, added by ops(temporal): TMP012/TMP013 validate steps against a static activity registry that cannot see another lexicon's activities #2101 because the suite fails today when a binary and the emulator are both present.
3. lexicons/terraform/src/op/activities/terraform.ts: decide what happens to liveDocumentFrom, which slices the document from the first bare { line. It is harmless once stdout is clean, since it returns its input unchanged when no such line exists, so keeping it as defensive code is defensible. Either way its comment should stop describing a live defect, and choudoufu.test.ts's liveDocumentFrom (choudoufu #894) block should say the same.
4. lexicons/terraform/docs/pages/ops.mdx: remove the "Known upstream gap, for the two Ops that read the document" paragraph and regenerate the site.
5. MIN_CHOUDOUFU_VERSION in terraform.ts moves to the release that carries the fix, since describeResources() and both document-reading Ops depend on it.

Epic #2102 closed with two Definition-of-done lines resting on this: chant lifecycle diff <env> --live reporting real owned verdicts on a live root, and the watch Op's emulator run. Both are held by fixtures and unit tests today and become end-to-end evidence once this lands, so this issue is where that evidence gets recorded.